From Fedora Project Wiki

Revision as of 14:59, 21 July 2010 by Dtimms (talk | contribs) (add spin dev page, first cut at ideas, need to review the mailing list for further info.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Audio Creation | Spin Development


A pre-configured Fedora spin, with the most outstanding audio software ready for novice audio creators to put to work. The aim is to release at the next Fedora release (14), due to go live around 2010-10-01. A serious amount of testing needs to be performed, with the expectation that any elements that seem to make use of the spin unreliable should be culled from the spin before release. At the time of Fedora release, the collaborators shall meet to determine whether to push the spin as a fully marketed cd/dvd, or whether to leave it in the wild for continued appraisal until the next Fedora cycle.



Creation of the Spin Development page. Remember that this is a wiki, and hence your valued contribution is welcomed, in the form of edits / spelling fixes.


There has been renewed interest on the music list in developing a Fedora Music Creation spin.


David Timms


  • develop list of primary audio packages
  • develop list of other audio packages
  • develop list of config / system tweaks to improve the use experience for each package.

Primary Audio Packages

The spin developers consider this group of packages to cover key audio creation areas, such as:

written music

sheet music editor

tablature editor

mic and instrument recording / editor

audacity [1.3.12-beta]

drum machine

keyboard synth


digital effects


audio system configuration


audio system

jack or jack2


  • usb audio capture/output
  • firewire audio capture/output
  • midi receive and transmit

Other Audio Packages

These packages would be nice to have but might not be ready in time, too large, not packaged for fedora. Other's might provide an alternative should some of the primary goal items not be achievable.

  • jack2
  • real time kernel


We want to keep track of both existing bugs, and new bugs we find during the development. Maybe some cached bz queries ?

Further links

  • audio software packaging
  • packages requiring testing (koji and bodhi)
   We should require all audio packages to be listed, and require minimum 2 users of each build to confirm normal, crash free operation.
  • ... some more ...