I've been spending a lot of time on the #opensourcemusicians channel
talking to Ubuntu Studio users about their kernel and latency times they're
getting. Seems like most of them are using g a stock kernel with the
preemptive option enabled and they are getting great latency results
(2ms)while utilizing the @audio group on their user. I ended up compiling
my own low latency kernel and I haven't had any issues with it yet. If this
is what we are missing for the spin I'd be happy to maintain packaging for
the kernel. I know ccrma has been behind a few kernel releases.
I saw the instructions for adding the real time patch for a tick less
kernel and from what I can tell it wouldn't be hard to get that rolling as
I'm not entirely sure what ccrma does differently with their kernels
compared to other Linux users, and I'm still a bit of a noob so I could be
off base with this, but I would reason that we should be able to just
utilize the same settings to archive similar performance enhancements.
I thought I read that ccrma uses a unique scheduler, but if we could get a
2ms latency time without it, the point may be moot.
Hi, is there any interest in the Audio SIG for taking this package on? Thanks,
---------- Forwarded message ----------
From: Jason L Tibbitts III <tibbs(a)math.uh.edu>
Date: 30 March 2012 00:25
Subject: Re: plug software for fender mustang
To: Development discussions related to Fedora <devel(a)lists.fedoraproject.org>
>>>>> "IM" == Ian Malone <ibmalone(a)gmail.com> writes:
IM> So, what's the next step? If necessary I can volunteer to maintain
IM> it myself (and would have to volunteer as a maintainer), but would
IM> be more than happy for someone else to take it.
Well, assuming that nobody else takes it, and also assuming that you're
not already a packager, you can head to
for the huge, massive list of steps involved.
IM> Minor issue that still needs sorted out with .spec file: the source
IM> is hosted at bitbucket, which means that the source package gets
IM> downloaded through a redirection URL by commit id and also contains
IM> an extra subdirectory level, I haven't found a REST request yet that
IM> can get round that.
you what to do.
devel mailing list
-----BEGIN PGP SIGNED MESSAGE-----
Congratulations to Jorn Lomax, who was accepted to Google Summer of
Code 2012 for the Fedora Audio Spin!
This is good news for all of us here in the Audio SIG, and I hope we
can all find the time to lend a hand where possible.
A list of accepted proposals can be found here:
Fedora has 10, and they all look interesting and useful.
Thank you to all the students who applied. I hope everybody finds a
way to contribute in the future.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----
there's been talk of a road map for the Audio spin and I'd just like to
jot down some suggestions for what we might like to achieve.
- installation media requirements. I'm proposing a smaller Live CD
(lite) and a full blown DVD installer.
- default Desktop for both installations. I would like something with
a really small size/footprint for the Live CD. Perhaps we can try LXDE
for the smaller and KDE for the DVD?
- default set of packages for both
- revisit multimedia-menus package and determine which packages need
additional Categories in the desktop file
- how best to package the Musicians guide
- how to achieve optimal RT performance from the stock kernel (adding
threadirqs to the kernel command, assigning jackuser/pulse-rt group
- default pulse/jack setup with pulse->jack bridging 'out-of-the-box'
- determine what packages from CCRMA and RPMFusion are must haves in
the Fedora repos and can be rebuilt to comply with Fedora licensing.
- desktop style and icons on install- darker themes are an obvious
choice for audio (often poor lighting etc) but can be a pain for normal
use. There are ways around this (Arch linux has some good tips for
achieving this - perhaps we just need to document it somewhere)
- and of course updating the Wikis
Most of this stuff is pretty trivial (but possibly time consuming).
Achieving the perfect setup out of the box w.r.t. RT performance, jack
and pulseaudio is going to require a lot more thought and possible
*real* development. As I've said before KXStudio has tried to solve this
problem with its cadence app (still pre-alpha). It makes a few
assumptions about applications (presence of ladish for example) which
may not necessarily apply here, but we can certainly learn a lot from
I'm thinking that some of this could be assigned to the successful GSoC
As I said I'm really just listing these as suggestions - and to try and
promote some more discussion (please!). I'd like to document this
somewhere on the wiki as well. Please let me know if I've missed
anything or if you have strong objections to what I've suggested.
I'd also like to round up all interested parties for an IRC meeting for
a round table of sorts (and to determine who is actually committed to
making this work).
I've recently noticed that the multimedia menus package doesn't
translate to Gnome3. Not sure if there's a way around this but I thought
I'd make a note of it here.
As the idea of submenus doesn't seem to exist in the Applications
screen, I wonder if there is another way or if it is even required under
I've had conversations with others about packaging content material for the
Audio spin and it doesn't seem like that currently possible with how things
are packed in Fedora.
I know we don't quite have our package list together at this point, but I
think there's a need for decent content for some of the plugins like
samplers, reverbs, drumloops and the like. I think the more stuff like this
we have available immediately for the audio spin, the more end users we're
going to attract. Even presets for things like graphic EQs and the like.
Anything to make less hassle for users...
Anyone else feel this way, or am I alone in my line of thought? I may be
easily persuaded after seeing it from another's point of view and I wonder
how important it is in the large scheme of things.
On a side note, I have sourceforge project that we could host content at if
needed. (hurray for unlimited bandwith and drive space for large files) I
know we're a ways off in implementing something like this, but it's not too
soon to start gathering resources for it.
After going through the music digest volumes I believe that some of
the packages might not make it to the official repository due to
Fedora Packaging Guidelines and some of them might be really good.
I do not know if there is a provision for providing additional details
in Fedora Musicians guide for those packages that does not make it to
the official repository.
If there is a possibility, then for those packages we can make entries
to the musicians guide which will provide additional resources and
methodologies to build and run those packages on their system which
will inturn reduce there hassles.
Again, we can provide details about the script(or its DE frontend) and
its consequences in the musicians guide if it allows.
I'm Feroze and I'm doing my undergrad in Engineering. I love recording and
"mixing" my own music and have helped with my school skits and theatre.
Most of my audio production work was done on Windows.
I have a lot of experience with Linux development and would like to create
Fedora Audio Spin. I am attracted to Fedora for its values regarding free
software. I have been wanting an audio production environment with truly
free and un-patented software. I want to make the Audio Spin very simple
and intuitive for users with no prior Linux experience.
My project proposal -
I'd like the Live CD to focus on production and editing. I've gone through
I would love to hear your feedback as we need to shortlist the packages to