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: https://bugzilla.kernel.org/show_bug.cgi?id=70941,  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 Sourceforge.com. 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> ccrma.stanford.edu
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” (<http://lwn.net/Articles/572740/>). 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
(<http://www.phoronix.com/scan.php?page=news_item&px=MTU3Njk>), 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> ccrma.stanford.edu
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> asterisk.rednote.net
		Email:	janina <at> rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,	Protocols & Formats	http://www.w3.org/wai/pf
	Indie UI			http://www.w3.org/WAI/IndieUI/
Brian Fay | 15 Aug 16:00 2014

Fedora 20 real time kernel crashes


I'm wondering if anybody else frequently experiences crashes/hangs running the real time kernel on Fedora 20? I'm using the default nouveau driver, and I can't seem to use the kernel reliably.

I'm almost guaranteed to get a crash when waking up from suspend - I'll see a display and I'll be able to move the mouse, but the system will be otherwise unresponsive (no capslock light).

Or, occasionally during a desktop session the screen will freeze and I will be unable to interact at all (audio still seems to play for a while).

Is anybody experiencing similar issues, and are there any thoughts on solutions?

Brian Fay
PlanetCCRMA mailing list
PlanetCCRMA <at> ccrma.stanford.edu
Tom Poe | 30 Jul 14:00 2014

which Centos5 distro to use?

Hello:  I have a Dell c521 desktop computer that I would like to install 
planetccrma on.  Seems like the Centos5 distro is best suited for this 
purpose, but there are several versions of the Centos5 iso to choose 
from.  Can anyone recommend which one to download, place on a 
thumbdrive, and install on the desktop?
Thanks, much
Nils Tonnätt | 30 Jun 19:05 2014

recent version of linuxsampler


I noticed that the version of linuxsampler in PlanetCCRMA is outdated. 
What is needed to get a more recent version in the repository? I hope 
that some bugs with my samples are already fixed.

Best regards,
Nils Tonnätt
Donald Steven | 30 Jun 18:24 2014


I've installed faust, llvm and a number of  related software, but I 
can't find libfaust.a without which I can't seem to enable the faust 
opcodes in csound6 or csound6-devel.

1. Are the faust opcodes required by csound in order for faust to work?  
(I'm just new to faust and would like to try it)?
2. How do I get cmake to enable the faust opcodes?  I'm using: #cmake 
-DFAUST_LIBRARY=$HOME/lib/faust/libfaust.a ./

The $HOME/lib/faust/libfaust.a is a non-issue.  There is no file 
libfaust.a anywhere on my system.

3. How do I get libfaust.a successfully installed in /usr/lib or 

Many thanks for any help anyone can provide.

Thierry Coduys | 26 Apr 14:36 2014

LoMus 2014 | Submissions was extended to 02 May 2014

Submissions was extended to 02 May 2014

Appel à contribution / Call for participation
Désolé en cas d’envois multiples / Sorry for possible crossposting

LoMus 2014

À la recherche des logiciels libres pour la création sonore et intermédias

Pour sa cinquième édition, LoMus 2014 s’adresse à tous ceux qui développent des logiciels libres musicaux ou qui peuvent contribuer au processus de la création musicale.

Un prix sera remis aux logiciels qui font preuve non seulement d’innovation, mais notamment d’inventivité face aux enjeux actuels de la création musicale.

31 mars 2014 - Appel à soumissions
02 mai 2014 - Date limite de soumission des logiciels
16 mai 2014 - Notification d'acceptation
23 mai 2014 - Remise du prix lors des JIM 2014

LoMus 2014

In search of open-source software for musical and intermedia creation

For its fifth edition, LoMus 2014 invites music and audio open-source software creators to submit original projects that either directly or indirectly contribute to musical creation.

A prize will be awarded to open-source sofware that proves to be not only innovatory but also inventive in the present context of music and audio creation.

Mars 31, 2014 - Call for submissions 
May 02, 2014 - Submission deadline 
May 16, 2014 - Admission notification 
May 23, 2014 - JIM Awards Ceremony 2014
PlanetCCRMA mailing list
PlanetCCRMA <at> ccrma.stanford.edu