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.
Currently number 5 out of 11 for torrent downloads! Not bad for the new kid.
Its very quiet on this list at the moment, so tell us what you've been
doing with music! Fedora / Linux / recording etc etc
Me, I've been trying to organize my many samples into sfz format for
use. Also found new interest in guitar (my new schecter rocks!)
I'm no drummer, but have been studying drumming a lot lately to fill out
some triggered recordings. Would love to hear other peoples experience
in this area.
kick out the jams
I have my other laptop (HP Pavilion dv4 - the one with decent audio)
running Fedora 20 Jam nightly from 2013-09-14! Installation was
flawless and KDE came up fine. I haven't had a chance to do any audio
testing yet other than browsing to player.allclassical.org, but all
the computational journalism / R stuff is working fine.
The GNOME 3 desktop works and there haven't been any instabilities or
crashes or even glitches. I'll probably take it out into the wild
tomorrow to make sure the Broadcom WiFi is working - that needs a
proprietary firmware chunk so I have to load the machine via a wired
network. In any event, Heisenbug is in *much* better shape than
Spherical Cow was at this stage in the life cycle.
Next step will be to install PureData and ChucK - I'm learning both in
parallel because I want to start doing some live performance stuff and
algorithmic composition. They're in Planet CCRMA but I think I'm going
to build them from upstream source instead.
Twitter: http://twitter.com/znmeb; Computational Journalism on a Stick
Pondering the pandemonium of pontificating pantheism to ponderous
pandas since 1994
Hello Docs and Audio Creation SIGs:
Now that I have a little more time in my life, I'd like to properly
update the Musicians' Guide for Fedora 20. Since there are so many
possible tasks, and I'm not really the best person to judge what changes
would be most useful, I want to include others in the revision-planning
These broad goals can help focus our efforts:
(1) Incorporate changes to software since Fedora 16.
(2) Eliminate content present in upstream documentation. This would
preserve Fedora-specific information, the sample creative projects, and
(3) Do copyediting to ensure high-quality, low-ambiguity, easily
translated text. If we do this, it should be a concerted effort in one
place, to minimize the amount of text that requires re-translation.
Possible specific tasks:
- see what can be removed from Qtractor, referring to upstream docs
- include Ardour 3, if it'll be ready during Fedora 20 cycle
- use the SuperCollider GUI rather than the GEdit plugin
- rationalize the SuperCollider chapter, which is half the guide
In addition, I'd like to finish my long-standing goals of changing the
specific piece used for the LilyPond piano tutorial, and of using a
freely-available recording as the basis for the Qtractor activity.
I appreciate any feedback or new tasks, and especially offers to help.
In the coming days, I'll start filing these issues on Bugzilla so we can
track their progress.