>>>>> On Tue, 11 Aug 2009 11:04:49 +0200, Erik Jakobsen <eja at urbakken.dk> >>>>> said:
> Stelios Bounanos wrote: >>>>>>> On Tue, 11 Aug 2009 05:20:53 +0200, Erik Jakobsen <eja at urbakken.dk> >>>>>>> said: >>> --------------------------------------- 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 ?. Well, VAC pretends to be an audio device because this is what it does... I don't know why it's giving you trouble, only that your previous email contains an fldigi log that shows an error while trying to access the "Virtual Cable 2" DirectSound input device. > 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. PowerSDR uses PortAudio, like fldigi, (though I believe they have their own version forked from PortAudio mainline many months ago). Concerning VAC, the PowerSDR manual says that "with most digital software MME will work well". So I suggest that you go with MME both in PowerSDR and fldigi. In fldigi, the PortAudio capture and playback menus contain devices names that appear twice. The device that appears in the main capture or playback menu is the MME device, and the corresponding DirectSound device in in a submenu. BTW, PowerSDR supports PortAudio backends that fldigi does not. We cannot build ASIO support into the win32 fldigi binary because the ASIO license is totally incompatible with the GPL. The WDM-KS backend I could never get to work and in any case it requires a huge SDK download from MS (unless one downloads the headers from somewhere else, not good). I mention this because I don't know if VAC is capable of speaking to its client programs via different backends, e.g. MME to PowerSDR and DirectSound to fldigi. To be safe use the same backend (Driver) in both. >> 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 ?. I don't see why fldigi would not work with Flex radios, if VAC does what it says on the tin :-) Also, Brian has got it working. -- 73, Stelios, M0GLD.
