Hello Alan,

This is an excellent idea.
I also use about 20 alsaloop and 20 vac in our project F4KJI.fr

The chain is as follows:
Redpitaya 384k I / Q => Linux station with websdr by gnuradio => ffmpeg 192k to vlc by udp / wav stream => Windows station by vac with cwskimmer and wsjtx.

we changed the alsaloop source code to 384k.

It could be very interesting to develloperate a stream standards on Cwskimmer server software (can be part of a dll) and WSJTX.

The cherry on the cake would be able to do the same time to translate frequencies, this would allow us to take for example 192k I / Q and bring back in baseband all the signals therein. Indeed on 192khz we could decode on a single audio stream most of the current digital modes in addition to the CW.

This is what we are trying to do in our project but gnuradio is very consumer in CPU.

That's why we even abandoned the udp stream gnuradio to go through vac during transport between our two stations. For example, on a I7 3,8ghz, udp transport costs 10% of cpu on each side. Go through a vac for the streamer via ffmpeg and vlc wav / upd costs us 2%.

But the most greedy is actually frequency translation and filtering.

We do not have the necessary skills to create a streaming software that would take an alsaloopback source and stream it to the cwskimmer and wsjtx programs.

But if you start the adventure, we would be happy to debug with you.

Thanks in advance, F4HTB

Le 22/03/2018 12:45, Alan Hopper a écrit :
Hi Phil and all
I am also very interested in a better way to interface sdrs to wsjtx than vac and virtual serial cables. There has been some discussion about it here https://groups.google.com/forum/#!topic/hermes-lite/ht54gu0vYuE <https://groups.google.com/forum/#%21topic/hermes-lite/ht54gu0vYuE> .

I recently discovered that Multipsk has a nicely designed protocol that allows iq data and radio control to be sent over tcp/ip, I have integrated it into my own SparkSDR software http://www.ihopper.org/radio/ and it has proven easy to use. The Multipsk interface is described here https://groups.io/g/multipsk/topic/new_release_4_34_1_of/15716260?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,15716260 .

I can see the value of using rtp and it should not be hard to pack the Multipsk packets into rtp, Phil maybe the two schemes can be combined.

I realize everyone will have a different idea as to the perfect protocol and it would be easy to get carried away trying to make it cover every use, as a first achievable target I think a simple one to one virtual audio/virtual serial cable replacement makes sense.

I'll certainly add support in Sparksdr for any protocol added to wsjtx and am happy to collaborate in any development.

73 Alan M0NNB



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to