Re: Re: gsoc2013 octave audio system

[Pantxo Diribarne]

Le 22/04/2013 17:54, Mike Miller a écrit :

Well, for one there is some disrepancy, I think, between what matlab
> calls an audio device and what portaudio calls an audio device. I
> don't have access to matlab right now but I'm pretty certain they mean
> physical devices while portaudio enumerates things like "pulse",
> "jack", "default", "system default", etc. as devices.

I had access to Matlab on a linux mint box and here is what I obtain from ML:
>> ai = audiodevinfo ();
>> ai.input(:).Name
ans =
HDA Intel PCH: ALC887-VD Analog (hw:0,0) (ALSA)
ans =
HDA Intel PCH: ALC887-VD Analog (hw:0,2) (ALSA)
ans =
sysdefault (ALSA)
ans =
pulse (ALSA)
ans =
default (ALSA)

From octave:
octave:16> ai = audiodevinfo ();
octave:17> ai.input(:).Name
ans = HDA Intel PCH: ALC887-VD Analog (hw:0,0)
ans = HDA Intel PCH: ALC887-VD Analog (hw:0,2)
ans = sysdefault
ans = pulse
ans = default


The number and the name of the input and output devices are identical in your implementation and in matlab. The only differences I see are :

•  in ML the host api is appended at the end of the name in the form "nameofthedevice (hostapi)".
  
•  the DriverVersion  field contains the host api name which you can retrieve using the "name" field of a PaHostApiInfo structure.
• the struct arrays are 1-by-nin(out)put and not nin(out)put-by-1
  

I can see "pulse" in the list of my input devices. As I undersatnd, pulseaudio is a hardware abstraction layer and not a host API (like ALSA or jack). It is the same for sysdefault which actually points to one of my hardware devices.

Pantxo