Tobias Brodel | 17 Nov 02:32 2014

Fedora 21/arm7


I'm doing an internship in the Audiokinetic Research lab at my university next semester and plan to
do some work with embedded ARM boards. Fedora 21 will be the first release to support many
armv7 boards as an official target architecture so I'd like to offer my help in packaging
Planet CCRMA for F21 and hopefully make a successful port of as many of the applications as
possible to ARM.

Is anyone currently working on Planet CCRMA for F21? If so, what's the best way for me to contribute?

PlanetCCRMA mailing list
PlanetCCRMA <at>
Tony White | 15 Oct 12:53 2014

kernel-rt-3.14.17-200.rt9 compiled against Fedora 19

I compiled the Fedora 20 kernel-rt X86_64 rpm - kernel-rt-3.14.17-200.rt9 for Fedora 19 yesterday and it works great here.
Anyone still running Fedora 19 (or mashing planet CCRMA's Fedora 19 repo into CentOS 7) who is interested can download the rpms from my gdrive :
All I did was compile the kernel-rt-3.14.17-200.rt9 source rpm from the planet CCRMA Fedora 20 repo on Fedora 19.
The current kernel-rt in the official Planet CCRMA Fedora 19 repo is 3.10.25-200.rt23.1 and It is missing some stuff which prevented bluetooth working properly for me, so I thought it was worth a shot to see if it solved my issue and it seems to have paid off.
I have stable temps, no xruns from jack and importantly KDE bluetooth integration now works! :)
should you want to do a recompile yourself. It was a case of installing the rpm dev tools, gcc, etc and doing :
rpm -ivh kernel-3.14.17-200.rt9.1.fc20.ccrma.src.rpm
rpmbuild -bb --target=`uname -m` ~/rpmbuild/SPECS/kernel.spec
then installing the rpms
from the build using yum.
Have a great day!
Kind Regards,
Tony White
twhite <at>
-- -- - Same, same, but different...
PlanetCCRMA mailing list
PlanetCCRMA <at>
Oded Ben-Tal | 4 Oct 16:29 2014

help with compiling

I am trying to compile SCMIR (Music Information Retrieval library for Supercollider) and running into problems. Unfortunately Nick Collins (the author of said library) isn't a linux user.
When I try to make I get an error message
make[2]: *** No rule to make target `/usr/lib64/libgsl.a', needed by `gmm'.

There is a there. I never used cmake (and the last time I used makefiles was ~15 years ago). Does anyone know if I can just try to find where this is specified and change it to .so (how do I find that?) or would it be simpler to try and install the .a version?
PlanetCCRMA mailing list
PlanetCCRMA <at>
Oded Ben-Tal | 23 Sep 18:23 2014

supercollider quarks?

I'm trying to figure out how I get SC to use quarks installed from planet
rpms. These are installed on my machine (use/share/) and I have 
.local/share/supercollider/quarks direcotry. But when I try to look up
something in scide (for example I was trying to see if I can use MarkovSet) it
can't find it. Or at least it can't find the help files that explain it. What
am I missing? 

many thanks
Oleg Samarin | 21 Sep 16:42 2014

kernel panic while loading realtime kernel


When I try to load a realtime kernel, it often (~50% attepmts) does not
start and raises a kernel panic with the stack attached.

No I use kernel_rt 3.14.17-200.rt9.1 but the same issue was with the
elder versions.

How can I resolve this issue?

PlanetCCRMA mailing list
PlanetCCRMA <at>
Oleg Samarin | 5 Sep 21:35 2014

Performance degradation with kernel-rt-3.14.17-200.rt9.1.fc20.ccrma.x86_64


I use Fedora 20 with PlanetCCRMA realtime kernel.

After upgrading the kernel from kernel-rt-3.12.12-300.rt19.1.fc20.ccrma to 
the last one - kernel-rt-3.14.17-200.rt9.1.fc20.ccrma, the huge sound
distortion started occurring. When I boot my station with kernel-rt-3.12.12,
everything seems all right.

The most probably reason is a bug in intel_pstate driver, that prevents CPU
 speeding up:,  There is a
patch that should solve this problem. 

Could you include this patch in the next build of kernel-rt?
Robert Vogel | 29 Aug 04:22 2014

[PlanetCCRMANews] GMorgan0.70 tar file available from Sourceforge.

Download the Gmorgan 0.70 tar file from Don't use svn, 
it is not updated.

Gmorgan is a midi processor. It can be voiced using Linux synths, midi 
connected equipment, or using one or more of the many soundcards 
available. I like to use a velocity sensing keyboard so that voices can 
be mixed or layered. It recognizes chords being played on the keyboard, 
and on the background terminal prints the input notes in both numeric 
and alpha form. Other features include a rhythm arranger, a style based 
sequencer, midi recorder. See the Youtube video links from the 
sourceforge home page.

GMorgan .70, the latest version for GNU/Linux, incorporates a new drum 
pattern panel based on the FLTK spreadsheet example, and
includes some miscellaneous cleanup.

Runs well on Ubuntu 12.4 with proprietary NVidia drivers.

If you have tried it before, be sure to go to Settings->global, renew 
the file paths to the current .70 gmorgan directory, and save them. The 
sound file has been renamed sounds.gmox and slightly reformatted, so 
results could be unpredictable if you don't at least reset this file.

Mark Cochran | 26 Aug 22:08 2014

yum error updating planetccrma-core

I saw an update to planetccrma-core made available the other day, but get this dependency error from yum when I try to update it.

Error: Package: planetccrma-core-2014.08.24-1.fc20.ccrma.x86_64 (planetcore)
           Requires: kernel-x86_64 = 3.17.17-200.rt9.1.fc20.ccrma.rt

Should that dependency be on kernel 3.14.17 perhaps?

Mark Cochran
PlanetCCRMA mailing list
PlanetCCRMA <at>
Yoann LE BARS | 19 Aug 03:42 2014

[PlanetCCRMANews] What is to become concerning real time in Linux kernel

Hello everybody out there!

	As it is my first post to this mailing list, let me introduce myself

	I am a long time musician (I started in sometime like 1985), mostly
using acoustic instruments. I am also a Unix (including GNU/Linux) user
since quite a while (starting in 1997). Of course, when I need a
computer for music, I use Planet CCRMA.

	The reason I am posting today is I have some question about soft
real-time Linux kernel future.

	During Real Time Linux Workshop in November 2013, developers involved
in the real-time patch have indicated the project will be done in 2014,
“one way or another” (<>). In this
workshop, it has also been said that 95 % of the real-time work was
already upstream.

	The question was how will it be done? In considering that the 95 % is
good enough? In getting the rest of the code upstream – which imply an
important effort and several people involved in it? Something between
these two options?

	As SCHED_DEADLINE has been incorporated into Linux 3.14 kernel
(<>), it seems
to me that it has been decided to get some more code upstream. Still,
the question remains: what way will be the project done? Moreover, as I
am using Fedora 20, I can choose between real-time Linux kernel 3.12
from Planet CCRMA and Fedora’s mainstream 3.15 kernel. What about
real-time capabilities of the 3.15 kernel in contrast with the 3.12
real-time kernel?

	Does anyone have any more information about it? As for my part, I
cannot find anything more.


Don Estabrook | 19 Aug 06:32 2014

Fedora 20 3.12.12-300.rt19.1 with Focusrite Saffire Pro40

Hello -

Recently I've been trying to get a Focusrite Saffire Pro40 working on my HP EliteBook 8540w, currently running Fedora 20 with CCRMA RT kernel.

I eventually pieced together enough information from various web sources to get it working, but the issue I have now is that qjackctl reports xruns - sometimes one every couple seconds, sometimes several minutes apart - even with nothing connected through jack.  If I play something using sndfile-jackplay[*], I notice that, around the time of each xrun, there's a 1- to 2-second gap in sound output (on headphone out 1), during which time the player app also freezes.  I've tried setting large values for frames/period and periods/buffer -- up to 1024 and 64, giving a whopping 1.49 seconds of latency at 44.1 kHz.  While the xrun frequency tends to be higher with smaller latencies (< 10 ms say), the variation is pretty small compared to trial-to-trial variation, so I can't say for sure.  Also I've noticed that after the sound returns after a gap, there's some distortion. including something that sounds vaguely like a high-hat cymbal closing softly, about once a second or so.  It gradually fades away after a few seconds.  (Weird, eh?)

The Pro40 was purchased new from a large on-line retailer at the end of 2013.  It's still running the original firmware (nothing I've read so far said conclusively there was any benefit to upgrading), and it's been connected to Focusrite's MixControl (on a Mac) only once, and that was brief - just to see if MixControl recognized it.

Although it may not be a very useful comparison, I've also used an M-Audio Fasttrack Pro (USB) interface with this same lap-top on and off for months with only an occasional xrun - but that's been mostly on the stock kernel.  With the RT kernel I've yet to see an xrun, although the machine locked up once when I was playing from Ardour3 -- the sound kept playing, but since the UI was unresponsive and I couldn't log in over the network, I resorted to holding the power button down.

ffado-dbus-server throws quite a number of ominous-looking errors at various times, although they don't seem to correlate to the xruns in time.  I can provide output if it would be useful.

ffado-diag output starts with the following:
>  kernel version............ 3.12.12-300.rt19.1.fc20.ccrma.x86_64+rt
>    Preempt (low latency)... False
>    RT patched.............. True
>  old 1394 stack present.... False
>  old 1394 stack loaded..... False
>  old 1394 stack active..... False
>  new 1394 stack present.... True
>  new 1394 stack loaded..... True
>  new 1394 stack active..... True
> . . .
> Hardware...
>   Host controllers:
>46:06.0 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 06) (prog-if 10 [OHCI])
>        Subsystem: Hewlett-Packard Company Device [103c:1521]
>        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
>        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>        Latency: 64 (500ns min, 1000ns max), Cache Line Size: 64 bytes
>        Interrupt: pin A routed to IRQ 20
>        Region 0: Memory at d3101000 (32-bit, non-prefetchable) [size=2K]
>        Capabilities: <access denied>
>        Kernel driver in use: firewire_ohci
>        Kernel modules: firewire_ohci

I can provide the rest of that output if it's useful too.
I'm curious as to why it reports "False" for preempt (low latency) on the CCRMA kernel -- I guess I was thinking that was part of the RT patches, but apparently that isn't the case...

I see FFADO has a new version (2.2.1) out a couple months ago.  I've been thinking about trying that, but what I've read has led me to expect that this interface should work with 2.1.

I'd love to hear what others have experienced.


[*] - I'm pretty sure I built this from source, as I couldn't find it in Fedora or CCRMA repositories.  (I was kind of surprised about that, since these sndfile utilities seem quite useful.)  Anyway the rest of the system is pretty much stock, and up to date a of a couple days ago.
PlanetCCRMA mailing list
PlanetCCRMA <at>
Janina Sajka | 16 Aug 23:06 2014

Something's forcing HDMI as default ALSA device


Something about the Linux kernel appears to me to have changed sometime
after kernel-3.13.10. I'm not certain just exactly when, but all the
kernels Fedora has released since 3.13.10 force the HDMI device as the
default ALSA audio device.

3.13.10 is the last kernel release where my carefully constructed ALSA
audio device ordering identifiers, in /etc/modprobe.d/local.conf,  work as
Any kernel beyond puts the onboard hdmi device as the default ALSA
device, which is simply untenable in my setup. For me it's not even that
I have nothing hanging off my HDMI port, I need the default device for
the Speakup screen reader, and I can't affect that on the Speakup side,
regretably. So, in effect,the system becomes unusable.

I note the CCRMA kernels for Fedora 20 are now also well behind current
Fedora releases and wonder if what I'm seeing is just one part of a
number of changes relating to audio.

Anyone know anything about this? Is there possibly a bug here that
should be tagged sooner rather than later? This is a 3-month old issue





Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina <at>
		Email:	janina <at>

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,	Protocols & Formats
	Indie UI