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.
On 25 December 2012 21:19:50 M. Edward Borasky wrote:
> Is there a master list of documentation?
I sort of missed the deadline for anything official, so for Fedora 18 we're
going to have to go with the usual "Fedora Audio"-style menagerie.
Over the next week, I hope to start collecting all of our discussions through
the spin development process, so that we'll be able to write:
1.) A chronicle of the efforts it tooks us to actually make a spin.
2.) Official documentation to add to the Musicians' Guide, about the software in
the spin, the differences between it and a default Live Fedora installation,
and maybe a brief history.
3.) Unofficial documentation for the wiki, about additional things you can do,
that we can't write in the official docs... like "here's how to install the
realtime kernel" and "here's how to install MP3 support for Audacity" and
I expect that much of this already exists, and I'll just have to start
> I'm itching to go into full-on blogging / tweeting mode on this.
Why not start right away, with a blog post that describes your involvement in
the spin's development? In fact, if several of us did this, we'd have a really
interesting "chronicle of the efforts it took us to actually make a spin."
I would like to thank everyone for their participation this year on
making the Fedora Music Spin a reality. It was by all means a group
effort so we can all give ourselves a pat on the back and say "job well
done" (Do it now! Don't think you don't deserve it).
Now that we have our own ISO built every night and we can official call
ourselves *Fedora* Jam, we have completed the first step. Now we have to
work together to make this the best audio- and music-creation/ Linux
distro out there. This will need a lot of community work and spreading
the word as much as possible. We also need to make sure the software is
up to scratch, so bug reporting and testing will be very important. So
keep up the good work, and have a nice relaxing Christmas holiday. I
hope we can keep up the momentum after the Holidays and I'm looking
forward to continue contributing in the coming year.
Merry Christmas and have a Happy New Year
(If this is considered off topic, please accept my sincere apologies)
I've committed a change that should fix the problem of the install
option still showing up on the installed system that Edward Borasky
A new compose is at
also includes the changes Jørn made in response to Christoph Wickert's
suggestions. We no longer have our own theme set automatically :(
still, there are rules, we have to play by them.
Will see if I can add anything to the Jack/Pulse stuff on the wiki
this weekend, was holding off while I tried to figure out if anything
would be likely to be different to previously, but it seems not.
The new look calf plugins 0.19.0 has been released. This comes at
somewhat of a cost as LADSPA and DSSI support has been deprecated.
KxStudio have since forked the project incorporating the new look GUI
whilst retaining LADSPA / DSSI and external LV2 UI support.
Not sure what I'm going to do about this state of affairs (if anyone was
wondering why we haven't updated calf yet)
I probably will just submit the fork for review under a new name.