| Certainly, if you do it before you run the orchestra. Also, in order to do
this, you have to store the orc, sco, and options inside CppSound and then
call CppSound.exportForPerformance before running Csound.
Alternatively, you can load a CSD in a CsoundFile object, call setCommand to
reset the CsOptions element, and then save the CSD again.
Hope this helps,
Mike
----- Original Message -----
From: "Art Hunkins"
To:
Cc:
Sent: Tuesday, September 15, 2009 9:39 PM
Subject: [Csnd] Getting around the device assignment problem in SoaS
> For SoaS (Fedora Linux), there remains the problem of device assignment
> involving audio out and MIDI in.
>
> Basically, if you boot SoaS then plug in a MIDI controller, audio is
> assigned C0D0; and MIDI, C1D0 (this is as expectesd). If you plug in a
> MIDI controller and then boot SoaS, MIDI gets C0D0 and audio C1D0 (this is
> *not* as expected!)
>
> It will be necessary to either do something either in Sugar, its Csound
> module, or in the python script that runs Csound to work with this issue.
>
> My question is this: With respect to the python option, is it possible
> (through the API) to pass queried values for audio and MIDI devices to
> in order to specify the correct device "numbers" to Csound?
>
> Art Hunkins
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" |