Ubuntu Studio S Audio

Registered by Kaj Ailomaa on 2013-04-18

The audio workflow, and meta

Blueprint information

Status:
Complete
Approver:
Ubuntu Studio Core
Priority:
Undefined
Drafter:
Ubuntu Studio Core
Direction:
Needs approval
Assignee:
None
Definition:
Superseded
Series goal:
Proposed for saucy
Implementation:
Unknown
Milestone target:
None
Completed by
Kaj Ailomaa on 2013-09-23

Related branches

Sprints

Whiteboard

(?)

Work Items

Work items:
[ubuntustudio-dev] Do research on all avilable audio workflow applications, and see if 1. we should include more 2. if the apps include all wanted features (might need to be rebuilt): TODO
[ubuntustudio-dev] Check jackd1/jackd2 dependency issues (installing jackd1 removes many applications), there may be a Debian bug - this should also be fixed in Debian: TODO
[len-ovenwerks] Add jack-keyboard: DONE
[ubuntustudio-dev] Add Ardour 3: TODO
[len-ovenwerks] Add IDJC: DONE
[len-ovenwerks] Add all avilable midi utilities, gmidimonitor, qmidiarp, qmidinet - and any other similar tools: DONE
[len-ovenwerks] Add qasmixer and ALSA utilities: DONE
[ubuntustudio-dev] default jack settings - set reasonable, yet sane, default jack settings (some changes could be made upstream, like sample rate): TODO
[ubuntustudio-dev] audio plugins - we ship a large amount, can this be cleaned up (or can we add a ubuntustudio categorization, to help find recommended plugins?): TODO
[ubuntustudio-dev] audio-plugins - see about adding nice presets for the most popular ones: TODO
[ubuntustudio-dev] investigate a good set of defaults for supercollider: TODO
[ubuntustudio-dev] Define applications and settings to be installed for audio coding (subgroup of audio workflow): TODO
[ubuntustudio-dev] Look at changing how jackd2 is packaged, make changes in Debian repo - recommendation is to not have jackd2 and jackdbus installed in paralell http://trac.jackaudio.org/wiki/SuggestedPackagingApproach: TODO
[ubuntustudio-dev] Make jack applications report an error, if they need jack to be running when launched (some apps don't do this) - choices are 1. add code, and send upstream 2. make feature request upstream 3. add a wrapper script for those applications in packaging: TODO

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.