Re: [Sugar-devel] [Csnd] Re: Re: Re: Re: csound on Fedora 11 and rawhide
On Tue, Sep 8, 2009 at 4:23 PM, Art Hunkinsabhun...@uncg.edu wrote: Victor, I understand you to be saying that pulseaudio exhibits more latency than ALSA. If this is so, why are we making pulseaudio the default for SoaS - where most audio will be realtime? Because that's what Fedora and most other distros are moving to. Also it does add more latency but not enough that most users will notice. Even if you use alsa it will connect to the alsa pulse audio provider which will basically add even more latency Csound - PA alsa provider - PA - ALSA - kernel. It works fine in most cases even for VoIP. What requires such low latency as to be an issue in an environment such as a learning one. Will the children notice a few milliseconds? Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Csnd] Re: Re: Re: Re: csound on Fedora 11 and rawhide
peter wrote: On Tue, Sep 8, 2009 at 4:23 PM, Art Hunkinsabhun...@uncg.edu wrote: Victor, I understand you to be saying that pulseaudio exhibits more latency than ALSA. If this is so, why are we making pulseaudio the default for SoaS - where most audio will be realtime? Because that's what Fedora and most other distros are moving to. Also i think using pulseaudio on a distro which is almost by definition aimed at under-powered machines is a mistake. it's a very expensive subsystem, performance-wise. i seem to recall seeing it take 10% of a 1Ghz system. paul it does add more latency but not enough that most users will notice. Even if you use alsa it will connect to the alsa pulse audio provider which will basically add even more latency Csound - PA alsa provider - PA - ALSA - kernel. It works fine in most cases even for VoIP. What requires such low latency as to be an issue in an environment such as a learning one. Will the children notice a few milliseconds? Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel =- paul fox, p...@laptop.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Csnd] Re: Re: Re: Re: csound on Fedora 11 and rawhide
I've finally got sound, out of my Asus EeePC900 (Linux) - wonderful. I'm also in a position to comment on much of what has been communicated over the last few hours. 1) The pulseaudio module *must* be downloaded/installed for Csound to work at all. Pulseaudio-libs is not required. 2) Pulseaudio works with either -+rtaudio=pulse, or nothing (I guess that means it is patched). 3) As long as the separate pulseaudio module is present, ALSA also works (via -+rtaudio=alsa). ALSA is obviously in the main package already (apparently as part of pulseaudio). 4) Portaudio is indeed completely absent; if you specify -+rtaudio=pa [or portaudio], Csound crashes. 5) IMPORTANT: Pulseaudio latency is very poor; at the end of random envelopes, it even gives a short additional burst of sound (as if needing to empty an old buffer). ALSA (-+rtaudio=alsa), OTOH, is very responsive and totally satisfactory. Bottom line: if I had my druthers, I'd vote for ALSA as the default. Nonetheless, I agree with Victor; there is no real problem - as long as we remember to specify -+rtaudio=alsa, and install the pulseaudio module. (I do admit this seems a bit convoluted, but such is life and Csound.) As an aside: I'm still working on getting sound from my Windows box. Art Hunkins - Original Message - From: victor.lazzar...@nuim.ie To: cso...@lists.bath.ac.uk Sent: Tuesday, September 08, 2009 11:48 AM Subject: [Csnd] Re: Re: Re: Re: csound on Fedora 11 and rawhide But there is no problem then, we just have to install the csound-alsa package (possibly if the alsa module is not in the main package) and use -+rtaudio=alsa. Victor - Original Message - From: Felipe Sateler fsate...@gmail.com Date: Tuesday, September 8, 2009 4:45 pm Subject: [Csnd] Re: Re: Re: csound on Fedora 11 and rawhide To: cso...@lists.bath.ac.uk AFAIK, yes, it was patched. The thing is that apparently the SoaS package is exactly the same one as in fedora. In fedora it might make sense to use pulseaudio (since pulseaudio will be running anyway and lots of soundcards/drivers do not allow multiple applications writing to them at the same time). I agree that pulseaudio in Sugar does not make much sense, but as long as it's the same package as in fedora, I think it will keep being pulse. On Tue, 2009-09-08 at 08:01 +0100, victor wrote: Well, you can try adding -+rtaudio=pulse. If Csound was not patched, it would still look for portaudio. Was it patched to find pulseaudio by default? My only misgiving about this is that pulseaudio is very high-latency. Victor - Original Message - From: Art Hunkins abhun...@uncg.edu To: Peter Robinson pbrobin...@gmail.com; Felipe Sateler fsate...@gmail.com Cc: cso...@lists.bath.ac.uk Sent: Tuesday, September 08, 2009 1:46 AM Subject: [Csnd] Re: csound on Fedora 11 and rawhide I'm really excited that Csound now seems to be working on Sugar-on-a-Stick. I'm getting sound written to -odac, but unfortunately am still not hearing audio. I imagine my problem is my audio setup. My CsOptions are: -odac -m0d --expression-opt -b128 -B2048 This set of options work fine on the XO-1, which is of course Csound5.08 with alsa as default rtaudio. SoaS default is now Pulseaudio, about which I know nothing; my log shows it is being used, as expected. I noted that there were also updates available for pulseaudio and pulseaudio-libs. (I don't believe they were part of Soas Strawberry.) Not knowing whether these are now needed, I installed them as well. Still no audio. FWIW, I'm on my WindowsXP system, which has several audio drivers installed on it along with a specified (Windows) default. I've no idea if this matters. What am I missing? I assume it's something in CsOptions. I'm hoping that for purposes of my Sugar activity, that the additional pulseaudio files will not need to be installed. For kids and their teachers and support people, the less that needs to be done the better. Art Hunkins - Original Message - From: Peter Robinson pbrobin...@gmail.com To: Art Hunkins abhun...@uncg.edu; Felipe Sateler fsate...@gmail.com Cc: cso...@lists.bath.ac.uk; Sugar devel sugar-devel@lists.sugarlabs.org Sent: Sunday, September 06, 2009 5:12 PM Subject: csound on Fedora 11 and rawhide Hi All, I think (with the help of Felipe) and after around a million test recompiles :-) I've finally fixed the issues with the csound python bindings on Fedora. The build is now in rawhide and fedora- testing for Fedora 11 as of today. The build that your after is 5.10.1- 12. For me at least it seems to work OK on Fedora 11 rawhide. PulseAudio is set as the default. I would like to know how it looks to everyone else. Cheers, Peter Send bugs reports to this list. To unsubscribe, send email
Re: [Sugar-devel] [Csnd] Re: Re: Re: Re: csound on Fedora 11 and rawhide
Followup: I've now got audio with SoaS on my Windows box. (I think I used a differently prepared stick, probably one that was updated *correctly*). All results were as described below on my Asus EeePC900. My remaining problem is MIDI input. Here are my CsOptions: -odac -+rtaudio=alsa -+rtmidi=alsa -M hw:1,0 -m0d --expression-opt -b128 -B2048 -+raw_controller_mode=1 (It seems that *both* -+rtaudio=alsa and -+rtmidi=alsa are required here.) No sound, and the log shows real confusion on the MIDI front. Here is the relevent portion: ALSA lib rawmidi_hw.c:233:(snd_rawmidi_hw_open) open /dev/snd/midiC1D0 failed: No such file or directory ALSA: error opening MIDI input device *** error opening MIDI in device: -1 (Unknown MIDI error) Seems like there is something missing for alsa MIDI. BTW, both -+rtmidi=pulse and -+rtmidi=portmidi fail; apparently these options don't exist. Art Hunkins - Original Message - From: Art Hunkins abhun...@uncg.edu To: cso...@lists.bath.ac.uk; pbrobin...@gmail.com Cc: sugar-devel@lists.sugarlabs.org Sent: Tuesday, September 08, 2009 2:10 PM Subject: Re: [Csnd] Re: Re: Re: Re: csound on Fedora 11 and rawhide I've finally got sound, out of my Asus EeePC900 (Linux) - wonderful. I'm also in a position to comment on much of what has been communicated over the last few hours. 1) The pulseaudio module *must* be downloaded/installed for Csound to work at all. Pulseaudio-libs is not required. 2) Pulseaudio works with either -+rtaudio=pulse, or nothing (I guess that means it is patched). 3) As long as the separate pulseaudio module is present, ALSA also works (via -+rtaudio=alsa). ALSA is obviously in the main package already (apparently as part of pulseaudio). 4) Portaudio is indeed completely absent; if you specify -+rtaudio=pa [or portaudio], Csound crashes. 5) IMPORTANT: Pulseaudio latency is very poor; at the end of random envelopes, it even gives a short additional burst of sound (as if needing to empty an old buffer). ALSA (-+rtaudio=alsa), OTOH, is very responsive and totally satisfactory. Bottom line: if I had my druthers, I'd vote for ALSA as the default. Nonetheless, I agree with Victor; there is no real problem - as long as we remember to specify -+rtaudio=alsa, and install the pulseaudio module. (I do admit this seems a bit convoluted, but such is life and Csound.) As an aside: I'm still working on getting sound from my Windows box. Art Hunkins - Original Message - From: victor.lazzar...@nuim.ie To: cso...@lists.bath.ac.uk Sent: Tuesday, September 08, 2009 11:48 AM Subject: [Csnd] Re: Re: Re: Re: csound on Fedora 11 and rawhide But there is no problem then, we just have to install the csound-alsa package (possibly if the alsa module is not in the main package) and use -+rtaudio=alsa. Victor - Original Message - From: Felipe Sateler fsate...@gmail.com Date: Tuesday, September 8, 2009 4:45 pm Subject: [Csnd] Re: Re: Re: csound on Fedora 11 and rawhide To: cso...@lists.bath.ac.uk AFAIK, yes, it was patched. The thing is that apparently the SoaS package is exactly the same one as in fedora. In fedora it might make sense to use pulseaudio (since pulseaudio will be running anyway and lots of soundcards/drivers do not allow multiple applications writing to them at the same time). I agree that pulseaudio in Sugar does not make much sense, but as long as it's the same package as in fedora, I think it will keep being pulse. On Tue, 2009-09-08 at 08:01 +0100, victor wrote: Well, you can try adding -+rtaudio=pulse. If Csound was not patched, it would still look for portaudio. Was it patched to find pulseaudio by default? My only misgiving about this is that pulseaudio is very high-latency. Victor - Original Message - From: Art Hunkins abhun...@uncg.edu To: Peter Robinson pbrobin...@gmail.com; Felipe Sateler fsate...@gmail.com Cc: cso...@lists.bath.ac.uk Sent: Tuesday, September 08, 2009 1:46 AM Subject: [Csnd] Re: csound on Fedora 11 and rawhide I'm really excited that Csound now seems to be working on Sugar-on-a-Stick. I'm getting sound written to -odac, but unfortunately am still not hearing audio. I imagine my problem is my audio setup. My CsOptions are: -odac -m0d --expression-opt -b128 -B2048 This set of options work fine on the XO-1, which is of course Csound5.08 with alsa as default rtaudio. SoaS default is now Pulseaudio, about which I know nothing; my log shows it is being used, as expected. I noted that there were also updates available for pulseaudio and pulseaudio-libs. (I don't believe they were part of Soas Strawberry.) Not knowing whether these are now needed, I installed them as well. Still no audio. FWIW, I'm on my WindowsXP system, which has several audio drivers installed on it along with a specified (Windows) default. I've no idea if this
Re: [Sugar-devel] [Csnd] Re: Re: Re: Re: csound on Fedora 11 and rawhide
On Tue, Sep 8, 2009 at 7:10 PM, Art Hunkinsabhun...@uncg.edu wrote: I've finally got sound, out of my Asus EeePC900 (Linux) - wonderful. Good news. finally YAY! I'm also in a position to comment on much of what has been communicated over the last few hours. 1) The pulseaudio module *must* be downloaded/installed for Csound to work at all. Pulseaudio-libs is not required. Which module in particular? 2) Pulseaudio works with either -+rtaudio=pulse, or nothing (I guess that means it is patched). Correct. 3) As long as the separate pulseaudio module is present, ALSA also works (via -+rtaudio=alsa). ALSA is obviously in the main package already (apparently as part of pulseaudio). well not as part of pulse audio but both options are compiled. 4) Portaudio is indeed completely absent; if you specify -+rtaudio=pa [or portaudio], Csound crashes. Correct. Is there a demand for it? Between pulseaudio and alsa we cover the vast majority of audio in Fedora. 5) IMPORTANT: Pulseaudio latency is very poor; at the end of random envelopes, it even gives a short additional burst of sound (as if needing to empty an old buffer). ALSA (-+rtaudio=alsa), OTOH, is very responsive and totally satisfactory. Bottom line: if I had my druthers, I'd vote for ALSA as the default. Nonetheless, I agree with Victor; there is no real problem - as long as we remember to specify -+rtaudio=alsa, and install the pulseaudio module. (I do admit this seems a bit convoluted, but such is life and Csound.) Well I've defaulted it to pulse because that's the default for Fedora. There's also quite a bit of tweaking that can be done on the application side of things. I use it with VoIP which is very sensitive to latency so I suspect there's some improvements that can be done on both the csound side as well and possibly the PA config as well. Cheers, Peter As an aside: I'm still working on getting sound from my Windows box. Art Hunkins - Original Message - From: victor.lazzar...@nuim.ie To: cso...@lists.bath.ac.uk Sent: Tuesday, September 08, 2009 11:48 AM Subject: [Csnd] Re: Re: Re: Re: csound on Fedora 11 and rawhide But there is no problem then, we just have to install the csound-alsa package (possibly if the alsa module is not in the main package) and use -+rtaudio=alsa. Victor - Original Message - From: Felipe Sateler fsate...@gmail.com Date: Tuesday, September 8, 2009 4:45 pm Subject: [Csnd] Re: Re: Re: csound on Fedora 11 and rawhide To: cso...@lists.bath.ac.uk AFAIK, yes, it was patched. The thing is that apparently the SoaS package is exactly the same one as in fedora. In fedora it might make sense to use pulseaudio (since pulseaudio will be running anyway and lots of soundcards/drivers do not allow multiple applications writing to them at the same time). I agree that pulseaudio in Sugar does not make much sense, but as long as it's the same package as in fedora, I think it will keep being pulse. On Tue, 2009-09-08 at 08:01 +0100, victor wrote: Well, you can try adding -+rtaudio=pulse. If Csound was not patched, it would still look for portaudio. Was it patched to find pulseaudio by default? My only misgiving about this is that pulseaudio is very high-latency. Victor - Original Message - From: Art Hunkins abhun...@uncg.edu To: Peter Robinson pbrobin...@gmail.com; Felipe Sateler fsate...@gmail.com Cc: cso...@lists.bath.ac.uk Sent: Tuesday, September 08, 2009 1:46 AM Subject: [Csnd] Re: csound on Fedora 11 and rawhide I'm really excited that Csound now seems to be working on Sugar-on-a-Stick. I'm getting sound written to -odac, but unfortunately am still not hearing audio. I imagine my problem is my audio setup. My CsOptions are: -odac -m0d --expression-opt -b128 -B2048 This set of options work fine on the XO-1, which is of course Csound5.08 with alsa as default rtaudio. SoaS default is now Pulseaudio, about which I know nothing; my log shows it is being used, as expected. I noted that there were also updates available for pulseaudio and pulseaudio-libs. (I don't believe they were part of Soas Strawberry.) Not knowing whether these are now needed, I installed them as well. Still no audio. FWIW, I'm on my WindowsXP system, which has several audio drivers installed on it along with a specified (Windows) default. I've no idea if this matters. What am I missing? I assume it's something in CsOptions. I'm hoping that for purposes of my Sugar activity, that the additional pulseaudio files will not need to be installed. For kids and their teachers and support people, the less that needs to be done the better. Art Hunkins - Original Message - From: Peter Robinson pbrobin...@gmail.com To: Art Hunkins abhun...@uncg.edu; Felipe Sateler fsate...@gmail.com Cc: cso...@lists.bath.ac.uk; Sugar devel
Re: [Sugar-devel] [Csnd] Re: Re: Re: Re: csound on Fedora 11 and rawhide
On Tue, Sep 8, 2009 at 10:00 PM, Art Hunkinsabhun...@uncg.edu wrote: Followup: I've now got audio with SoaS on my Windows box. (I think I used a differently prepared stick, probably one that was updated *correctly*). All results were as described below on my Asus EeePC900. Great. My remaining problem is MIDI input. Here are my CsOptions: -odac -+rtaudio=alsa -+rtmidi=alsa -M hw:1,0 -m0d --expression-opt -b128 -B2048 -+raw_controller_mode=1 (It seems that *both* -+rtaudio=alsa and -+rtmidi=alsa are required here.) I've not actually used midi recently (recently being not in over 5 years), I played around with it years ago in the SoundBlaster era. No sound, and the log shows real confusion on the MIDI front. Here is the relevent portion: ALSA lib rawmidi_hw.c:233:(snd_rawmidi_hw_open) open /dev/snd/midiC1D0 failed: No such file or directory ALSA: error opening MIDI input device *** error opening MIDI in device: -1 (Unknown MIDI error) Seems like there is something missing for alsa MIDI. Does the sound card midi require sound fonts or samples to be loaded, or even support midi? I think a lot of the newer cheap mother board sound cards like the Intel HDA audio don't even support it. Can you get it working using one of the other midi packages? There's a list in Fedora here https://fedoraproject.org/wiki/SIGs/AudioCreation#Packages_Accepted_into_Fedora BTW, both -+rtmidi=pulse and -+rtmidi=portmidi fail; apparently these options don't exist. It won't, I don't believe either support midi in any form. Regards, Peter Art Hunkins - Original Message - From: Art Hunkins abhun...@uncg.edu To: cso...@lists.bath.ac.uk; pbrobin...@gmail.com Cc: sugar-devel@lists.sugarlabs.org Sent: Tuesday, September 08, 2009 2:10 PM Subject: Re: [Csnd] Re: Re: Re: Re: csound on Fedora 11 and rawhide I've finally got sound, out of my Asus EeePC900 (Linux) - wonderful. I'm also in a position to comment on much of what has been communicated over the last few hours. 1) The pulseaudio module *must* be downloaded/installed for Csound to work at all. Pulseaudio-libs is not required. 2) Pulseaudio works with either -+rtaudio=pulse, or nothing (I guess that means it is patched). 3) As long as the separate pulseaudio module is present, ALSA also works (via -+rtaudio=alsa). ALSA is obviously in the main package already (apparently as part of pulseaudio). 4) Portaudio is indeed completely absent; if you specify -+rtaudio=pa [or portaudio], Csound crashes. 5) IMPORTANT: Pulseaudio latency is very poor; at the end of random envelopes, it even gives a short additional burst of sound (as if needing to empty an old buffer). ALSA (-+rtaudio=alsa), OTOH, is very responsive and totally satisfactory. Bottom line: if I had my druthers, I'd vote for ALSA as the default. Nonetheless, I agree with Victor; there is no real problem - as long as we remember to specify -+rtaudio=alsa, and install the pulseaudio module. (I do admit this seems a bit convoluted, but such is life and Csound.) As an aside: I'm still working on getting sound from my Windows box. Art Hunkins - Original Message - From: victor.lazzar...@nuim.ie To: cso...@lists.bath.ac.uk Sent: Tuesday, September 08, 2009 11:48 AM Subject: [Csnd] Re: Re: Re: Re: csound on Fedora 11 and rawhide But there is no problem then, we just have to install the csound-alsa package (possibly if the alsa module is not in the main package) and use -+rtaudio=alsa. Victor - Original Message - From: Felipe Sateler fsate...@gmail.com Date: Tuesday, September 8, 2009 4:45 pm Subject: [Csnd] Re: Re: Re: csound on Fedora 11 and rawhide To: cso...@lists.bath.ac.uk AFAIK, yes, it was patched. The thing is that apparently the SoaS package is exactly the same one as in fedora. In fedora it might make sense to use pulseaudio (since pulseaudio will be running anyway and lots of soundcards/drivers do not allow multiple applications writing to them at the same time). I agree that pulseaudio in Sugar does not make much sense, but as long as it's the same package as in fedora, I think it will keep being pulse. On Tue, 2009-09-08 at 08:01 +0100, victor wrote: Well, you can try adding -+rtaudio=pulse. If Csound was not patched, it would still look for portaudio. Was it patched to find pulseaudio by default? My only misgiving about this is that pulseaudio is very high-latency. Victor - Original Message - From: Art Hunkins abhun...@uncg.edu To: Peter Robinson pbrobin...@gmail.com; Felipe Sateler fsate...@gmail.com Cc: cso...@lists.bath.ac.uk Sent: Tuesday, September 08, 2009 1:46 AM Subject: [Csnd] Re: csound on Fedora 11 and rawhide I'm really excited that Csound now seems to be working on Sugar-on-a-Stick. I'm getting sound written to -odac, but unfortunately am still not hearing audio. I imagine my problem is my audio setup. My CsOptions are: -odac
Re: [Sugar-devel] [Csnd] Re: Re: Re: Re: csound on Fedora 11 and rawhide
- Original Message - From: Peter Robinson pbrobin...@gmail.com To: Art Hunkins abhun...@uncg.edu Cc: cso...@lists.bath.ac.uk; sugar-devel@lists.sugarlabs.org Sent: Tuesday, September 08, 2009 5:38 PM Subject: Re: [Csnd] Re: Re: Re: Re: csound on Fedora 11 and rawhide My remaining problem is MIDI input. Here are my CsOptions: -odac -+rtaudio=alsa -+rtmidi=alsa -M hw:1,0 -m0d --expression-opt -b128 -B2048 -+raw_controller_mode=1 (It seems that *both* -+rtaudio=alsa and -+rtmidi=alsa are required here.) No sound, and the log shows real confusion on the MIDI front. Here is the relevent portion: ALSA lib rawmidi_hw.c:233:(snd_rawmidi_hw_open) open /dev/snd/midiC1D0 failed: No such file or directory ALSA: error opening MIDI input device *** error opening MIDI in device: -1 (Unknown MIDI error) Seems like there is something missing for alsa MIDI. Does the sound card midi require sound fonts or samples to be loaded, or even support midi? I think a lot of the newer cheap mother board sound cards like the Intel HDA audio don't even support it. Can you get it working using one of the other midi packages? There's a list in Fedora here https://fedoraproject.org/wiki/SIGs/AudioCreation#Packages_Accepted_into_Fedora MIDI is essential to realtime Csound. Portmidi has long been the MIDI standard in Csound. I note it's on the list you cite. Any reason it can't be used? OTOH, alsa was used (on the XO-1) for rtmidi. Can't it continue? (My activities are meant both for the XO-1 and SoaS; so as much consistency/continuity as possible would be helpful to me. [The XO-1 used alsa for both audio and midi.] Otherwise, I think separate versions will be required, unfortunately.) Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Csnd] Re: Re: Re: Re: csound on Fedora 11 and rawhide
Does the sound card midi require sound fonts or samples to be loaded, or even support midi? I think a lot of the newer cheap mother board sound cards like the Intel HDA audio don't even support it. Can you get it working using one of the other midi packages? There's a list in Fedora here https://fedoraproject.org/wiki/SIGs/AudioCreation#Packages_Accepted_into_Fedora MIDI is essential to realtime Csound. Portmidi has long been the MIDI standard in Csound. I note it's on the list you cite. Any reason it can't be used? I don't plan on compiling it into csound on Fedora as its not the default sound platform on Fedora. There's alsa and pulseaudio support compiled in so that gives you two options. Also it was never supported in the previous release of olpcsound used on the XO. To add to this I barely have time to support csound with 2 sound options compiled in, I certainly don't have the time to support 3. If you want to step up and assist in supporting csound in Fedora I might reconsider the option. OTOH, alsa was used (on the XO-1) for rtmidi. Can't it continue? Sure, I haven't disabled it but looking at all the devices I have on hand and digging out the XO-1 I don't see a single device that has hardware midi (including 2 laptops, a netbook, another geode based desktop system and a couple of other desktops) so I suspect if it was working it was emulated in software. I have no idea how any of that works so I have no idea what's broken but I don't have any way to debug it. Feel free to submit patches that fix the issue though. (My activities are meant both for the XO-1 and SoaS; so as much consistency/continuity as possible would be helpful to me. [The XO-1 used alsa for both audio and midi.] Otherwise, I think separate versions will be required, unfortunately.) As mentioned it must have been software midi as I don't see HW midi on the XO-1 using the old 802 release that's running on XO-1 that was closest to hand. I don't see what could have broken as looking at the olpcsound build config (included below) the only audio option that was used was alsa. In the current build we actually have significantly more things enabled. Are you sure that midi is working on your machines? have you tested another application to see if they work? Can you include (as mentioned by Felipe the output of ls -al /dev/snd ?) Peter if env['buildOLPC'] == '1': env['pythonVersion']= '2.5' env.Prepend(CPPFLAGS= ['-DOLPC']) env.Prepend(CPPFLAGS= ['-DENABLE_OPCODEDIR_WARNINGS=0']) if util.getPlatform() != 'linux': print Build platform is not linux # Set other options?? env['useGettext'] = '1' env['useDouble']= '0' env['usePortAudio'] = '0' env['useJack'] = '0' env['buildCsoundAC']= '0' env['buildCsound5GUI'] = '0' env['useDouble']= '0' env['usePortMIDI'] = '0' env['useALSA'] = '1' env['useFLTK'] = '0' env['buildCsoundVST'] = '0' env['buildCsoundAC']= '0' #'buildCsound5GUI' env['buildLoris'] = '0' env['buildStkOpcodes'] = '0' env['useOSC'] = '1' env['buildFluidOpcodes']= '0' env['prefix'] = '/usr' env['buildUtilities'] = '0' ##env['gcc4opt']= '1' env['useLrint'] = '1' env['Word64'] = '0' env['Lib64']= '0' env['buildPDClass'] = '0' env['buildDSSI']= '0' env['buildVirtual'] = '1' env['buildInterfaces'] = '1' env['buildSDFT']= '0' env['buildJavaWrapper'] = '0' env['buildNewParser'] = '0' env['buildvst4cs'] = '0' env['buildImageOpcodes']= '1' env['dynamicCsoundLibrary'] = '1' ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
