Stelios Bounanos wrote:
>>>>>> On Tue, 11 Aug 2009 05:20:53 +0200, Erik Jakobsen <eja at urbakken.dk> 
>>>>>> said:
>>>>>>             
>
>   
>> Stelios Bounanos wrote:
>>     
>
>   
>>> That input device looks like an output device to me :)
>>>
>>> Let's take a closer look at those virtual cable devices.  Please run the
>>> program below and send me the output file (pa_devs_out.txt) that it
>>> generates.
>>>
>>> http://download2.berlios.de/pub/fldigi/alpha/pa_devs.exe
>>>       
>
>   
>> Ok Stelios, here's the ouput file:
>>     
>
> [...]
>
>
>   
>> --------------------------------------- device #9
>> Name                        = Virtual Cable 2
>> Host API                    = Windows DirectSound
>> Max inputs = 8, Max outputs = 0
>> Default low input latency   =    0.000
>> Default low output latency  =    0.000
>> Default high input latency  =    0.000
>> Default high output latency =    0.000
>> Default sample rate         =     0.00
>> Supported standard sample rates
>>  for half-duplex 16 bit 8 channel input =
>>      8000.00,  9600.00, 11025.00, 12000.00,
>>     16000.00, 22050.00, 24000.00, 32000.00,
>>     44100.00, 48000.00, 88200.00, 96000.00,
>>     192000.00
>>     
>
> This is Virtual Audio Cable masquerading as a DirectSound device.  This
> is the input device that gives you the error.
>
>   
Because of it's masquerading ?.
>> --------------------------------------- device #7
>> Name                        = Virtual Cable 2
>> Host API                    = MME
>> Max inputs = 0, Max outputs = 2
>> Default low input latency   =    0.200
>> Default low output latency  =    0.200
>> Default high input latency  =    0.400
>> Default high output latency =    0.400
>> Default sample rate         = 44100.00
>> Supported standard sample rates
>>  for half-duplex 16 bit 2 channel output =
>>      8000.00,  9600.00, 11025.00, 12000.00,
>>     16000.00, 22050.00, 24000.00, 32000.00,
>>     44100.00, 48000.00, 88200.00, 96000.00,
>>     192000.00
>>     
>
> This is the same device accessed via the MME API.
>
>
>   
Ok.
> Please try again with the MME devices for both capture and playback,
> i.e., not the "Virtual Cable 2" devices that are under the "Windows
> DirectSound devices" submenus.
>
>   
Do you mean still using the VAC, or make a change in the set up in the 
SDR itself, here ?

http://www.urbakken.dk/MME.jpg
and
http://www.urbakken.dk/MME2.jpg

and try running this or ?

http://www.urbakken.dk/windowsdirectsound.jpg

I'm not quite sure what to try.
> If this works we'll have to assume that VAC doesn't work well under
> DirectSound, or that there's a bug in PortAudio's DirectSound backend.
>
>   
We'll see it when I have it explained what to do :-)
> I think what Brian achieves by forcing the sample rate is to avoid the
> problem where fldigi tries to set a sample rate of 0.0 (the default rate
> reported by PortAudio for VAC/DS).  The toggle to "File I/O" and back
> must be a way to reinitialise PortAudio.  If you save the settings and
> restart fldigi you shouldn't have to do this.
>
>   
I understand.
> I'm not sure why PortAudio reports 0.0 for the VAC DSound device, or how
> fldigi should handle this.
>
>
>   
Maybe it's totally a fail to try to get Fldigi to run with Flex radios ?.

73s-Erik-OZ4KK

Reply via email to