m (more minor revisions) |
m (added last sentence to the first paragraph) |
||
| Line 1: | Line 1: | ||
Over the next few months, I will be taking part in the Fedora Summer Coding effort (like the [http://en.wikipedia.org/wiki/Google_Summer_of_Code Google Summer of Code], but run by the [[Overview#What_is_the_Fedora_Project|Fedora Project]]). My particular project will create a user guide for some of the music and audio software available in [[Overview#What_is_the_Fedora_Distribution|Fedora Linux]]. Not only will the use of these programs be addressed, but also how to know which program to use, and how to optimize the Fedora Linux system for audio creation. The focus here will be on robust solutions, warning of the possible dangers associated with such a computer system. | Over the next few months, I will be taking part in the Fedora Summer Coding effort (like the [http://en.wikipedia.org/wiki/Google_Summer_of_Code Google Summer of Code], but run by the [[Overview#What_is_the_Fedora_Project|Fedora Project]]). My particular project will create a user guide for some of the music and audio software available in [[Overview#What_is_the_Fedora_Distribution|Fedora Linux]]. Not only will the use of these programs be addressed, but also how to know which program to use, and how to optimize the Fedora Linux system for audio creation. The focus here will be on robust solutions, warning of the possible dangers associated with such a computer system. Other foci will be knowing which tool to use for which task, and applicability to real-world creative tasks. | ||
An important part of the document-creation process is testing, and for this I will need help from volunteers. There are two aspects that must be tested: the first ensures that the instructions have the intended results; the second ensures that users will understand what they are doing, why they are doing it, and how it applies to the real world. | An important part of the document-creation process is testing, and for this I will need help from volunteers. There are two aspects that must be tested: the first ensures that the instructions have the intended results; the second ensures that users will understand what they are doing, why they are doing it, and how it applies to the real world. | ||
Revision as of 04:00, 7 June 2010
Over the next few months, I will be taking part in the Fedora Summer Coding effort (like the Google Summer of Code, but run by the Fedora Project). My particular project will create a user guide for some of the music and audio software available in Fedora Linux. Not only will the use of these programs be addressed, but also how to know which program to use, and how to optimize the Fedora Linux system for audio creation. The focus here will be on robust solutions, warning of the possible dangers associated with such a computer system. Other foci will be knowing which tool to use for which task, and applicability to real-world creative tasks.
An important part of the document-creation process is testing, and for this I will need help from volunteers. There are two aspects that must be tested: the first ensures that the instructions have the intended results; the second ensures that users will understand what they are doing, why they are doing it, and how it applies to the real world.
You don't need to be a Fedora user to help. In fact, you don't need to be a Linux user, or even know what Linux is! There will be tasks for anybody who believes in the ideas behind this guide, with a desire to help out.
The following software will be discussed:
- Audacity -- simple recording software
- Ardour -- advanced multi-track recording software (like ProTools)
- SuperCollider -- text-based audio synthesis
- FluidSynth (with Qsynth) -- MIDI-based audio synthesis engine
- Qtractor -- audio and MIDI sequencing program
- Rosegarden -- audio and MIDI sequencing program
- LilyPond (with Frescobaldi) -- notation/engraving software
- GNU Solfege -- ear-training software
- Icecast and Darkice or Darksnow (schedule permitting) -- webcast creation
In addition, the following topics will be discussed:
- Adding the Planet CCRMA at Home repositories (for software such as SuperCollider) (Fedora-specific)
- Understanding sound cards
- Using ALSA, PulseAudio, JACK (with Qjackctl), and Phonon)
- Using Planet CCRMA's real-time kernel (Fedora-specific)
- Compiling your own real-time kernel (schedule permitting) (Fedora-specific)
Please note that only a small portion of the final document will be exclusive to Fedora Linux. These include the portions marked "Fedora-specific" in the preceding list, and those sections covering software installation. What this means is that users of any distribution can help with testing (especially target-audience testing)! In particular, Ubuntu's standard repositories have all the software except SuperCollider, which is available from a PPA.
More information will be posted here, as I determine what tasks will be required. It will be your choice to volunteer for as few or as many tasks as you like.
If you would like to volunteer, or if you have suggestions or comments, please contact me by leaving a note on this page's Talk: page, or by sending an email to GMail (my username is crantila). Any assistance is greatly appreciated.