Audio creation spin development
- Create a Fedora spin configured with software and optimizations designed for audio creation work.
- 2010-07-22: Creation of the Spin Development page.
- 2010-07-18: There has been renewed interest on the music list in developing a Fedora Music Creation spin.
- 2012-02-19: Another head for the chopping block. Renewed interest here
The aim is to release with the next mainstream Fedora release, Fedora 18
If any of these areas interest you, please put your name next to an item, and indicate when you think you might be able to complete the task, etc.
- Develop the list of primary audio packages. (collab)
- Develop the list of other audio packages. (collab)
- Develop a list of system tweaks to improve the user experience.
- Build initial kickstart file based on primary audio packages. done. [[see Spin Page.
- Publish the first cut via torrent/site for SIG feedback. (crantila: this should be done via fedorahosted?) (dtimms: not sure, but time is of essence - so I have tried publishing both the torrent and ks so that people can further test the spin).
- Make a cool name for the spin.
- Prioritize tasks; assign them to people.
- Team up with Artwork for themes and CDs/DVDs.
- Document "primary" software (Christopher).
- Get space at fedorahosted to store development materials.
- Write information on this page.
- Get a beat written for the Release Notes (Christopher).
- Contact the Spins SIG to notify them of our project, and ask for help done, review of late spin submission requested. The Spins Meeting voted on a nogo for F14. Unfortunately a request for someone representing the music spin to be present at the meeting wasn't forwarded, so we had no voice there, although it sounds like it would have been welcomed.
- Convert this page to the format suggested by the Spins SIG. done, see standard spin page. standard Spin Page
The spin developers consider this group of packages to cover key audio creation areas.
Written Music / Sheet Music
- crantila: Do we need these at all? We're looking to create a spin targeted for audio creation. People using LilyPond might be better off doing it in the standard distribution, unless they want other audio creation programs. The point is that we don't need to include it as essential software, so let's cut it out and reduce the size of the installation media.
- dtimms: This highlights a few things: who is our target audience ? I'm thinking someone who can't afford a hardware IO box, and just wants to mess around with an instrument / computer to get started. You need to get them hooked on digaudio: cool fx, easy recording, faultless playback, reading of guitar tabs, playback of published music as backing...
- crantila: We should sort out the target audience first, to make it easier to agree on later decisions.
- LilyPond-mode for Emacs
- LilyPondTools for jEdit
Recording and DAWs
- Audacity [1.3.12-beta]
- FluidSynth & Qsynth
- Specimen Sampler
- (LinuxSampler and Qsampler were on this list but do not meet licensing restrictions)
- SuperCollider 3.4
- CSound 5
Sound Server and Configuration
- jack or jack2 (crantila: jack2 should be a top priority)
Kernel and Drivers
- Real-time kernel
- FFADO: FireWire audio capture/output
crantila: aren't USB & MIDI already included by default? sunset: since I don't have either, I don't know if there are boxes that need firmware packages or specific drivers, if not, then great.
Tertl3: I have heard that the spin must use a normal Fedora kernel or it will have to be classified as a remix as opposed to a spin. It is not a big deal, but I just thought it was worth noting. I, personally, would really like the spin to have a real-time kernel.
Default Desktop Environment(s)
- crantila: If we end up with a DVD, it may be possible to include GNOME and KDE, and maybe even others. Probably only one would fit on a CD. They all have their advantages, so I suggest voting by FAS username. That way, we can pick what would please the greatest number of existing audio creation users.
- dtimms: I would suggest including a single desktop e. that most existing documentation refers to. I would think we want as much as possible for it to be light weight, since we most likely won't have a specialised kernel. We could write some tools to 1. disable all the stuff that can mess up your real-time-d-ness (updatedb), with an option to say - do your maintenance now. A web browser and internet connection stuff should be included.
- crantila: We also want people to use it. I don't know about you, but I don't want to be switching between two installations of the same OS just so that I can do audio creation work in one of them. Of course, including a light-weight installation by default doesn't mean that users won't later be able to install something else.
These packages would be nice to have, but shouldn't be necessary for release.
these packages are not in the repos, but can be downloaded from the linux rtwiki and linux audio creation sites.
rtirq- this script, (if I understand it correctly), determines which IRQ numbers are used for soundcards and sets them for realtime audio priority.
realtimeconfigquickscan-this script performs a number of checks and with every check also provides the method of fixing the corresponding settings.
rtirq actually changes setting whereas the realtimeconfigquickscan merely checks for real time optimization and offers suggestions.
I would like to write a tutorial for these in the fedora musicians guide. Let me know if you think this is a good/bad idea.(William Backburn)
Spin Issues and Bugs for F13 alpha CD Lite Spin
- please add yours here:
- Spins Sig Guideslines / meeting comments:
- can't disable standard services: but then you can on some spins ;-)
- shouldn't delete wireless networking drivers: these can fit after removing locale stuff
- the spin should be installable to disk: not tested
- attempt at setting the default group for all users is not recognised: you still have to mess with users and groups to add the user to jackuser. this is probably one of the key things that is needed for the spin to be instantly usable by beginners.
- existing package bugs:
We want to keep track of new and existing bugs. Maybe some cached BugZilla queries?