From Fedora Project Wiki
m (added informational links)
m (minor grammatical/stylistic revisions)
Line 1: Line 1:
Over the next few months, I will be taking part in the Fedora Summer Coding project (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 proposal is the creation of 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 the optimization of a Fedora Linux system for audio creation.  The focus will be on robust solutions, warning of the possible pitfalls and dangers associated with a system optimized for audio creation.
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.


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 procedures and instructions have the intended results; the second ensures that prospective users will understand what they are doing, why they are doing it, and how it applies to real-world usage.
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 out.  In fact, you don't even need to be a Linux user to help out!  There will be tasks for anybody who believes that this guide should be written, and who wishes to help out.
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:
The following software will be discussed:
* [http://en.wikipedia.org/wiki/Audacity Audacity] -- simple recording software
* [http://en.wikipedia.org/wiki/Audacity Audacity] -- simple recording software
* [http://en.wikipedia.org/wiki/Ardour_%28software%29 Ardour] -- advanced multi-track recording software
* [http://en.wikipedia.org/wiki/Ardour_%28software%29 Ardour] -- advanced multi-track recording software (like ProTools)
* [http://en.wikipedia.org/wiki/Super_Collider SuperCollider] -- text-based audio synthesis
* [http://en.wikipedia.org/wiki/Super_Collider SuperCollider] -- text-based audio synthesis
* [http://en.wikipedia.org/wiki/FluidSynth FluidSynth] (with [http://qsynth.sourceforge.net/qsynth-index.html Qsynth]) -- MIDI-based audio synthesis
* [http://en.wikipedia.org/wiki/FluidSynth FluidSynth] (with [http://qsynth.sourceforge.net/qsynth-index.html Qsynth]) -- MIDI-based audio synthesis engine
* [http://en.wikipedia.org/wiki/Qtractor Qtractor] -- audio and MIDI sequencing program
* [http://en.wikipedia.org/wiki/Qtractor Qtractor] -- audio and MIDI sequencing program
* [http://en.wikipedia.org/wiki/Rosegarden Rosegarden] -- audio and MIDI sequencing program
* [http://en.wikipedia.org/wiki/Rosegarden Rosegarden] -- audio and MIDI sequencing program
Line 17: Line 17:


In addition, the following topics will be discussed:
In addition, the following topics will be discussed:
* Adding the Planet CCRMA at Home repositories (for software such as SuperCollider) (Fedora-specific)
* Adding the ''Planet CCRMA at Home'' repositories (for software such as SuperCollider) (Fedora-specific)
* Understanding sound cards
* Understanding sound cards
* Using ALSA, PulseAudio, JACK (with Qjackctl), and Phonon)
* Using ALSA, PulseAudio, JACK (with Qjackctl), and Phonon)
* Using a Planet CCRMA's realtime kernel (Fedora-specific)
* Using Planet CCRMA's real-time kernel (Fedora-specific)
* Compiling your own realtime kernel (schedule permitting) (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.
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 made available at a later time, and you will get your choice of which tasks to test.  It will be your choice to volunteer for as much or as little as you like.
More information will be posted here, as I determine what tasks will be required.
 
and you will get your choice of which tasks to test.  It will be your choice to volunteer for as much or as little 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.
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.

Revision as of 05:07, 5 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.

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:

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.

and you will get your choice of which tasks to test.  It will be your choice to volunteer for as much or as little 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.