Normally when I need to know all the available audio devices on a system 
I try something like csound blabla.csd -devaudio99 which results in 
Csound listing all available devices and then telling me device 99 is 
out of range. This time, with an RME Fireface 800 I can't get that list 
as no matter what device number I opt for Csound works away like normal, 
only I can't hear anything! I just tried -odevaudio 199 and still no 
errors about the device being out of range? Any ideas on how to find the 
right devices? I can write a simple utility for outputting available 
devices but there must easier way?

Rory.

Thanks Steven. I installed a newer version and it runs now, although I 
am still having some difficulty in getting things going. I was only 
running 5.04, I have so many machines with Csound installed it's hard to 
keep up!



Steven Yi wrote:
> Hi Rory,
> 
> blue has code that detects possible outputs and shows the user using a
> dropdown list.  I'm wondering if you could try that if it would work
> for you or not.
> 
> Otherewise, I use "-o dac999" with Csound when doing detection on
> Windows.  On Linux, I query /proc/asound/pcm to get device numbers
> (cat /proc/asound/pcm) with Alsa and with Jack the code is a little
> more complicated as it uses Csound bu iterates through a number of
> different sample rates to find the connection.
> 
> Hope that helps!
> steven
> 
> On 10/19/07, Rory Walsh  wrote:
>> Normally when I need to know all the available audio devices on a system
>> I try something like csound blabla.csd -devaudio99 which results in
>> Csound listing all available devices and then telling me device 99 is
>> out of range. This time, with an RME Fireface 800 I can't get that list
>> as no matter what device number I opt for Csound works away like normal,
>> only I can't hear anything! I just tried -odevaudio 199 and still no
>> errors about the device being out of range? Any ideas on how to find the
>> right devices? I can write a simple utility for outputting available
>> devices but there must easier way?
>>
>> Rory.
>> --
>> Send bugs reports to this list.
>> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
>>

It might be nice if we made this a bona fida feature instead of an error
message when the number is out of range.  Adding something like a
--list-devices command option to parallel the --list-opcodes flag.  It
should run, list the devices, and then exit Csound.

Also, a --list-utilities would be nice now too since new utilities can be
added via plugins.  I implemented a feature like this in the MacOS 9 front
end (there is an API function to get a list of utilities and descriptions):

The available utilities are:
  atsa        Soundfile analysis for ATS opcodes
  cvanal      Soundfile analysis for convolve
  dnoise      Removes noise from a sound file
  ...

I could probably implement the latter of these ideas pretty easily.

Anthony Kozar
anthonykozar AT sbcglobal DOT net
http://anthonykozar.net/

Rory Walsh wrote on 10/19/07 12:33 PM:

> Any ideas on how to find the
> right devices? I can write a simple utility for outputting available
> devices but there must easier way?
> 
> Rory.

I would love to see this *featured* added to Csound.

I would like to know audio in/out and midi devices and their ID's


-dB

On Oct 19, 2007, at 2:08 PM, Anthony Kozar wrote:

> It might be nice if we made this a bona fida feature instead of an  
> error
> message when the number is out of range.  Adding something like a
> --list-devices command option to parallel the --list-opcodes flag.  It
> should run, list the devices, and then exit Csound.
>
> Also, a --list-utilities would be nice now too since new utilities  
> can be
> added via plugins.  I implemented a feature like this in the MacOS  
> 9 front
> end (there is an API function to get a list of utilities and  
> descriptions):
>
> The available utilities are:
>   atsa        Soundfile analysis for ATS opcodes
>   cvanal      Soundfile analysis for convolve
>   dnoise      Removes noise from a sound file
>   ...
>
> I could probably implement the latter of these ideas pretty easily.
>
> Anthony Kozar
> anthonykozar AT sbcglobal DOT net
> http://anthonykozar.net/
>
> Rory Walsh wrote on 10/19/07 12:33 PM:
>
>> Any ideas on how to find the
>> right devices? I can write a simple utility for outputting available
>> devices but there must easier way?
>>
>> Rory.
>
> -- 
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk