On 11/06/2016 20:45, Steven Franke wrote: > I am currently playing with an alternative to the current msk144 detector > (the counterpart of mskdt for jtmsk), mainly using the command-line program > msk144d. Once I’ve decided what to do there, I’ll spend some time figuring > out why I was seeing different results when calling syncmsk144 from within > wsjt-x. Or, maybe I’ll get lucky and the problem will have healed itself by > then!
Hi Steve, I am able to run simulated QSOs between two instances of WSJT-X with MSK144, the performance seems very good with very short pings decoding cleanly and reliably. The SNR numbers are suspiciously high but that may be because of the effectively noise free channel I am using, what is the SNR reporting range of MSK144? First impressions show that this is much better than JTMSK. Hopefully I can get my rotator fixed soon, I am keen to try this out on air. 73 Bill G4WJS. ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
