Well as I managed to inject some signal gen. into the SR40 running
under Rocky 1.001 (or whatever the newer version is) and it overloads
very early (- 70 dbm or s9 approx (on the other programs I can go to -
25 dbm before I get the overload and harmonics/spurs all over)) on 96
khz it is the same problem!

I checked to make shure the level of input on the card remained the
same in the mixer but it did. Tried it again on PowerSDR and it work
OK as before.


73 de Joe








Yahoo! Groups Links

I downloaded V 1.01, but pressing View | Settings the panel that opens
shows no entries for the Input Device and for the Output Device.

In addition, under File the choice Start Radio is grayed out.
Exiting from the program Windows complains about an Address Violation
at address 00403D6E, caused by a Read of address 00000004.

Running Windows XP SP1, with three sound cards :
Delta 44
Terratec Aureon Sky
nVidia nForce Audio on the mainboard

Thanks for a very nice program

73 Alberto I2PHD

Hi Alberto,
Thank you for testing Rocky!
As you know, Rocky talks directly to the WDM driver of the audio card. This
is the most promising but least explored method of audio streaming on the
Windows platform. AFAIK, no other SDR program currently uses this method
because WDM streaming is very poorly documented. There is some documentation
on the MS web site that explains how to write WDM drivers - but not how to
use them in applications.
[snip]

Hi Alex,

congratulations ! V1.02 works without problems on my PC, the sound cards
are identified correctly and the program runs smoothly.
You must also be commended for having had the courage to take the WDM route...
I adventured just through the WMME and the ASIO ones, but felt the WDM
was lacking the documentation I needed to feel at my ease, as you have
pointed out.

I like also the auto balancing feature, something I will have to study
in detail...:-)

TNX es 73 Alberto I2PHD

Hi Alberto,

Thank you for testing Rocky!

As you know, Rocky talks directly to the WDM driver of the audio card. This is the most promising but least explored method of audio streaming on the Windows platform. AFAIK, no other SDR program currently uses this method because WDM streaming is very poorly documented. There is some documentation on the MS web site that explains how to write WDM drivers - but not how to use them in applications.
However, WDM audio streaming is so attractive that someone has to find a way of using it. This is exactly what I am trying to do. Due to lack of documentation, this is to some degree a trial and error process, and I depend heavily on the user feedback since the program works fine on all of my own computers.

I have just uploaded v.1.02 of Rocky to , this may have fixed the problem that you described. Please try the new version and see if the problem if now fixed.

Also, I have written a utility that displays properties of all WDM audio devices on the system, this should help me to figure out what is going on on the systems where Rocky is not working properly. If the device list in Rocky is still blank, I will ask you and all other users who experience the same problem to run the utility and send me the report that it generates. The program is at .


73 Alex VE3NEA

Alex:

It would be a fantastic thing if you shared this technology in some
way. I struggled on and off for weeks on end before giving up. I just
have too much else to do. I would drop PortAudio completely and ASIO
forever if I could get WDM-KS to work consistently and across all WDM-KS
drivers! ASIO is just too restrictive with its restrictions to one
device per system. I just finished virtual audio to connect to
applications without wires (I have been running MMSSTV and MMTTY without
wires for a few days). We have jack that does this beautifully on
Linux. Virtual Audio Cable, with the facilities just built into the
PowerSDR release about to come out, will do the job for it. But it
would be much lower latency and much less overhead if all of these
devices were opened in WDM-KS. I attempted for quite a while to get
MSVAD (WDM-KS) virtual sound cables (in the Windows DDK) to work before
giving up and using VAC and MME through PortAudio. I did not want to
do the latter because it costs $40. However, it is better than not
having the facility at all.

Bob
N4HY




Alex, VE3NEA wrote:

Hi Alberto,

Thank you for testing Rocky!

As you know, Rocky talks directly to the WDM driver of the audio card. This
is the most promising but least explored method of audio streaming on the
Windows platform. AFAIK, no other SDR program currently uses this method
because WDM streaming is very poorly documented. There is some documentation
on the MS web site that explains how to write WDM drivers - but not how to
use them in applications.
However, WDM audio streaming is so attractive that someone has to find a way
of using it. This is exactly what I am trying to do. Due to lack of
documentation, this is to some degree a trial and error process, and I
depend heavily on the user feedback since the program works fine on all of
my own computers.

I have just uploaded v.1.02 of Rocky to
, this may have fixed the
problem that you described. Please try the new version and see if the
problem if now fixed.

Also, I have written a utility that displays properties of all WDM audio
devices on the system, this should help me to figure out what is going on on
the systems where Rocky is not working properly. If the device list in Rocky
is still blank, I will ask you and all other users who experience the same
problem to run the utility and send me the report that it generates. The
program is at .


73 Alex VE3NEA

--
Laziness is the number one inspiration for ingenuity. Guilty as charged!





Yahoo! Groups Links

Hi Bob,

I have emailed my WDM code to you. Please see if you can make use of it.

73 Alex VE3NEA

Alex:

It would be a fantastic thing if you shared this technology in some
way. I struggled on and off for weeks on end before giving up. I just
have too much else to do. I would drop PortAudio completely and ASIO
forever if I could get WDM-KS to work consistently and across all WDM-KS
drivers! ASIO is just too restrictive with its restrictions to one
device per system. I just finished virtual audio to connect to
applications without wires (I have been running MMSSTV and MMTTY without
wires for a few days). We have jack that does this beautifully on
Linux. Virtual Audio Cable, with the facilities just built into the
PowerSDR release about to come out, will do the job for it. But it
would be much lower latency and much less overhead if all of these
devices were opened in WDM-KS. I attempted for quite a while to get
MSVAD (WDM-KS) virtual sound cables (in the Windows DDK) to work before
giving up and using VAC and MME through PortAudio. I did not want to
do the latter because it costs $40. However, it is better than not
having the facility at all.

Bob
N4HY

?

?

?

o,

Thank you for the good news. I really appreciate you testing the new version
at 1 AM your local time!

73 Alex VE3NEA

?