That is close on name . . . I have two that are a couple years apart, and the device names vary a bit anyhow.

#pulseaudio #linux #Kenwood #WSJTX_config

Hmmmm . . . both not working would tend to point to choosing the wrong device. I'm using a SignalLink with Pulse and all is fine (not on Ubuntu, but that is pretty irrelevant, since they diidn't write

#pulseaudio #linux #Kenwood #WSJTX_config

You still need something like NTP to smoothly manage your clock, even with a time source like that. GPS or not, if it step adjusts, you may have problems.

#Cat_RigControl #AudioIssues #Icom

Glad to hear it, and thanks for the update(s)!

#Yaesu

Have you tried any other speeds? In all the searches I have done on your combo, folks seem to be running 4800 . . . Wondering if WSJTX might be orking the higher speeds . . . Just a thought . . .

#Yaesu

Baud rate on the radio (item #32, iirc) and on the computer?

#Yaesu

Well, unless you set the compile to the same install path . . . (or remove it if you choose to install the binary blob later).

#linux

Keep in mind that most of these dependencies are due to the specific build/package being used, and not the code version itself! I have run everything from, iirc, 2.5.2 through current on an older Linu

#linux

If you see the SignaLink USB audio device in Windows, dig down and find the tests for it and see if you have signal there. Also make sure that Windows has not decided to mute the device for you, or th

#AudioIssues

Audio and control are typically not the same device - check your audio config.

#AudioIssues

Or, simply build from source and circumvent all this pre-packaged software version dependency nonsense. A compile is not locked to specific versions like a binary distribution/package is. (If loading

#raspberryPi

Bill - As a matter of curiosity, can you offer a bit more detail on the issues that you have with the MK-V? I too am running that rig (well, the FT1000 MV-V Field), but don't seem to have any problems

#frequency

I do (on Slackware), but build from source 100%, so can't help you on a repo . . . - Tim

#linux

I tend to do that, but if something in a new built does not work, the ability to revert to a prior version that did without someone elses arbitrarily imposed restrictions is nice . . .

#stopped_working

#stopped_working

That was the one I was negating . . . as soon as the "hard coded badge or identifier" was needed, it could be added to source with little effort, since what is seen on air is fully open. Binary distri

#EnhancementReqest

Not sure which that is, since you did not cc:, but if it was the one about "checking out a special build", my point is that that won't help much, since once the "identifier" (or whatever) is known, it

#EnhancementReqest

So what would stop someone from determining the key, trivially adding it to the source, and recompiling? It's not like compiling WSJTX is even minimally difficult . . .

#EnhancementReqest

Yeah, I reealize that . . . It just seems that with a request to test, an appropriate source tarball ought to be dropped as well, since that will run on anything, as opposed to the limited scope of th

#hamlib

For those of us who never use prebuilt packages, is there a link to source for this? Or is the *4.6*git.tar.gz close? Thanks, - Tim

#hamlib