[Csnd] help with csound+jack on Raspberry Pi

[Csnd] help with csound+jack on Raspberry Pi

Date	2013-11-28 19:03
From	Dave Seidel
Subject	[Csnd] help with csound+jack on Raspberry Pi
	Hi all, I just got a Raspberry Pi, and managed to get the Satellite CCRMA distro running on it. I was able to build Csound 6, and I can run Trapped. However, running just with "-odac", the output starts to break up fairly quickly. So I got jack fired up and ran Csound with "-+rtaudio=jack -odac:system:playback_" -- no error messages, but also no sound. Any suggestions? I'm still a jack novice, and certainly an RPi newbie. Thanks very much in advance. Also, is there a repository of RPi-specific Csound knowledge out there somewhere, like a wiki? - Dave

Date	2013-11-28 19:19
From	Steven Yi
Subject	Re: [Csnd] help with csound+jack on Raspberry Pi
	Hi Dave, Just FYI, there's some info here in Paul Batchelor and Trev Wignall's Csound Journal Article: http://www.csounds.com/journal/issue18/beagle_pi.html There were some email threads here about the RaspberryPi some time ago that discussed some audio things. I don't own one so have no further information. :P Good luck with it! steven On Thu, Nov 28, 2013 at 2:03 PM, Dave Seidel wrote: > Hi all, > > I just got a Raspberry Pi, and managed to get the Satellite CCRMA distro > running on it. I was able to build Csound 6, and I can run Trapped. However, > running just with "-odac", the output starts to break up fairly quickly. So > I got jack fired up and ran Csound with "-+rtaudio=jack > -odac:system:playback_" -- no error messages, but also no sound. Any > suggestions? I'm still a jack novice, and certainly an RPi newbie. Thanks > very much in advance. > > Also, is there a repository of RPi-specific Csound knowledge out there > somewhere, like a wiki? > > - Dave

Date	2013-11-28 19:56
From	Tarmo Johannes
Subject	Re: [Csnd] help with csound+jack on Raspberry Pi
	Hi! I was experimineting with Pi some time ago and had difficulties getting jackd work properly. Appearently you have got better luck but for any case, can you check that csound6 is registered as client by jackd and the connecions to playback_ ? Do you have qjackd installed? or you can use also jack_lsp -c for connections or aren't you using by chance dummy audio driver in jack (should be alsa)? What worked for me was to use an external usb sound interface, rtalsa and also audio worked better if I used only audio out (not duplex, ie no -iadc option in the csd). not sure, if it helps... tarmo On Thursday 28 November 2013 14:03:05 Dave Seidel wrote: Hi all, I just got a Raspberry Pi, and managed to get the Satellite CCRMA distro running on it. I was able to build Csound 6, and I can run Trapped. However, running just with "-odac", the output starts to break up fairly quickly. So I got jack fired up and ran Csound with "-+rtaudio=jack -odac:system:playback_" -- no error messages, but also no sound. Any suggestions? I'm still a jack novice, and certainly an RPi newbie. Thanks very much in advance. Also, is there a repository of RPi-specific Csound knowledge out there somewhere, like a wiki? - Dave

Date	2013-11-28 20:17
From	Richard Dobson
Subject	Re: [Csnd] help with csound+jack on Raspberry Pi
	I haven't had time to work on the Pi very much, but having had similar issues getting jack to build/work, I can confirm that doing (if necessary, definitely was on my relatively early model) a complete sudo apt-get upgrade followed by installation of the Sonic Pi software (also via apt-get) results in a working Jack (they install their own custom build - best to uninstall anything already there first). See: http://www.cl.cam.ac.uk/projects/raspberrypi/sonicpi/index.html Richard Dobson On 28/11/2013 19:56, Tarmo Johannes wrote: > Hi! > > I was experimineting with Pi some time ago and had difficulties getting > jackd work properly. Appearently you have got better luck but for any > case, can you check that csound6 is registered as client by jackd and > the connecions to playback_ ? Do you have qjackd installed? or you can > use also > ...

Date	2013-11-29 04:03
From	Dave Seidel
Subject	Re: [Csnd] help with csound+jack on Raspberry Pi
	Thanks to all, many useful suggestions, all helpful. With the holiday events, I haven't had the time to dig any deeper yet into jack configuration, but I find the "-+rtaudio=alsa" works, which may be sufficient or maybe even preferable. And Trapped may not be the ideal test under these circumstances, as I don't expect it's been optimized for realtime performance on a system like this. I intend to use the RPi in the context of a compact but versatile performance rig, as described here[1] and here[2], though the details will of course evolve. The RPi is headless, and operated/controlled via ssh from my Android tablet. I'll be using Csound as a realtime component, running on either the tablet or the RPi (or both), and I plan to control it on the RPi from hardware using the Auduino (which is an Arduino with several programmable knobs and buttons -- I've done this before with Csound via pd and csoundapi~) and/or the rePatcher (assuming I can figure out how to interface with it). The RPi will also be used to program the Shnth[3], which is a really cool digital instrument I recently acquired. BTW Richard, Sonic Pi is apparently already installed as part of Satellite CCRMA (along with pd and SuperCollider, and a bunch of other stuff), but I've not had a chance to look into it yet. This is still my first day with the device, so I have much to learn. - Dave [1] http://daveseidel.tumblr.com/post/67979351933/little-boxes [2] http://daveseidel.tumblr.com/post/68309253856/diagram [3] http://shbobo.net On Thu, Nov 28, 2013 at 3:17 PM, Richard Dobson <richarddobson@blueyonder.co.uk> wrote: I haven't had time to work on the Pi very much, but having had similar issues getting jack to build/work, I can confirm that doing (if necessary, definitely was on my relatively early model) a complete sudo apt-get upgrade followed by installation of the Sonic Pi software (also via apt-get) results in a working Jack (they install their own custom build - best to uninstall anything already there first). See: http://www.cl.cam.ac.uk/projects/raspberrypi/sonicpi/index.html Richard Dobson On 28/11/2013 19:56, Tarmo Johannes wrote: Hi! I was experimineting with Pi some time ago and had difficulties getting jackd work properly. Appearently you have got better luck but for any case, can you check that csound6 is registered as client by jackd and the connecions to playback_ ? Do you have qjackd installed? or you can use also ... Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2013-11-29 04:27
From	Dave Seidel
Subject	Re: [Csnd] help with csound+jack on Raspberry Pi
	I should also mention that I was able to generate a WAV file for "Trapped" and play it back with no problems at all on the RPi. On Thu, Nov 28, 2013 at 11:03 PM, Dave Seidel <dave.seidel@gmail.com> wrote: Thanks to all, many useful suggestions, all helpful. With the holiday events, I haven't had the time to dig any deeper yet into jack configuration, but I find the "-+rtaudio=alsa" works, which may be sufficient or maybe even preferable. And Trapped may not be the ideal test under these circumstances, as I don't expect it's been optimized for realtime performance on a system like this. I intend to use the RPi in the context of a compact but versatile performance rig, as described here[1] and here[2], though the details will of course evolve. The RPi is headless, and operated/controlled via ssh from my Android tablet. I'll be using Csound as a realtime component, running on either the tablet or the RPi (or both), and I plan to control it on the RPi from hardware using the Auduino (which is an Arduino with several programmable knobs and buttons -- I've done this before with Csound via pd and csoundapi~) and/or the rePatcher (assuming I can figure out how to interface with it). The RPi will also be used to program the Shnth[3], which is a really cool digital instrument I recently acquired. BTW Richard, Sonic Pi is apparently already installed as part of Satellite CCRMA (along with pd and SuperCollider, and a bunch of other stuff), but I've not had a chance to look into it yet. This is still my first day with the device, so I have much to learn. - Dave [1] http://daveseidel.tumblr.com/post/67979351933/little-boxes [2] http://daveseidel.tumblr.com/post/68309253856/diagram [3] http://shbobo.net On Thu, Nov 28, 2013 at 3:17 PM, Richard Dobson <richarddobson@blueyonder.co.uk> wrote: I haven't had time to work on the Pi very much, but having had similar issues getting jack to build/work, I can confirm that doing (if necessary, definitely was on my relatively early model) a complete sudo apt-get upgrade followed by installation of the Sonic Pi software (also via apt-get) results in a working Jack (they install their own custom build - best to uninstall anything already there first). See: http://www.cl.cam.ac.uk/projects/raspberrypi/sonicpi/index.html Richard Dobson On 28/11/2013 19:56, Tarmo Johannes wrote: Hi! I was experimineting with Pi some time ago and had difficulties getting jackd work properly. Appearently you have got better luck but for any case, can you check that csound6 is registered as client by jackd and the connecions to playback_ ? Do you have qjackd installed? or you can use also ... Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2013-11-29 11:05
From	Bernt Isak Wærstad
Subject	Re: [Csnd] help with csound+jack on Raspberry Pi
	Working on the COSMO Project, we had trouble getting jack to run too and just stuck with ALSA instead. What would be the benefits of switching to jack in terms of performance? We also had huge problems with dropouts until we found out that our interface was USB 1.1 and the USB controller on the Pi was USB 2.0. Here is a explanation how to force the USB to 1.1 (that helped us): Force USB port to USB 1.1 (needed to prevent dropouts) The RPi has a USB2.0 controller that apparently can cause issues with USB1.1 audio interfaces. The solution is to force the controller to use USB1.1 mode. You can do this by adding the following kernel parameter to your /boot/cmdline.txt file on your RPi: dwc_otg.speed=1 You cannot edit this file from the Raspberry itself (through ssh) since it is a read-only file on a protected boot partition (sudo will not help). Instead power down the PI, extract the SD card and put it into your machine. On the SD card partition you will find the cmdline.txt file and be able to edit it so it will look something like this: dwc_otg.lpm_enable=0 dwc_otg.speed=1 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait Save the file, eject the SD card and put it back into your PI. On Fri, Nov 29, 2013 at 5:27 AM, Dave Seidel <dave.seidel@gmail.com> wrote: I should also mention that I was able to generate a WAV file for "Trapped" and play it back with no problems at all on the RPi. On Thu, Nov 28, 2013 at 11:03 PM, Dave Seidel <dave.seidel@gmail.com> wrote: Thanks to all, many useful suggestions, all helpful. With the holiday events, I haven't had the time to dig any deeper yet into jack configuration, but I find the "-+rtaudio=alsa" works, which may be sufficient or maybe even preferable. And Trapped may not be the ideal test under these circumstances, as I don't expect it's been optimized for realtime performance on a system like this. I intend to use the RPi in the context of a compact but versatile performance rig, as described here[1] and here[2], though the details will of course evolve. The RPi is headless, and operated/controlled via ssh from my Android tablet. I'll be using Csound as a realtime component, running on either the tablet or the RPi (or both), and I plan to control it on the RPi from hardware using the Auduino (which is an Arduino with several programmable knobs and buttons -- I've done this before with Csound via pd and csoundapi~) and/or the rePatcher (assuming I can figure out how to interface with it). The RPi will also be used to program the Shnth[3], which is a really cool digital instrument I recently acquired. BTW Richard, Sonic Pi is apparently already installed as part of Satellite CCRMA (along with pd and SuperCollider, and a bunch of other stuff), but I've not had a chance to look into it yet. This is still my first day with the device, so I have much to learn. - Dave [1] http://daveseidel.tumblr.com/post/67979351933/little-boxes [2] http://daveseidel.tumblr.com/post/68309253856/diagram [3] http://shbobo.net On Thu, Nov 28, 2013 at 3:17 PM, Richard Dobson <richarddobson@blueyonder.co.uk> wrote: I haven't had time to work on the Pi very much, but having had similar issues getting jack to build/work, I can confirm that doing (if necessary, definitely was on my relatively early model) a complete sudo apt-get upgrade followed by installation of the Sonic Pi software (also via apt-get) results in a working Jack (they install their own custom build - best to uninstall anything already there first). See: http://www.cl.cam.ac.uk/projects/raspberrypi/sonicpi/index.html Richard Dobson On 28/11/2013 19:56, Tarmo Johannes wrote: Hi! I was experimineting with Pi some time ago and had difficulties getting jackd work properly. Appearently you have got better luck but for any case, can you check that csound6 is registered as client by jackd and the connecions to playback_ ? Do you have qjackd installed? or you can use also ... Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" -- Mvh. Bernt Isak Wærstad