开云体育

I tried different combinations - none would put out an audio signal that could be detected (if it was there, it was below the sensitivity of my scope - which is more or less usual for decent moderate cost scopes).?? Some settings, of course, wouldn't work at all... no receive and Quisk would even crash on trying to transmit. The reliable combination that always reliably received a signal (sometimes - but not often, I'd have to reset the Softrock if I made some changes) was using hw:0 and hw:1 (0 being the built-in audio, 1 being the USB audio).?? I know the audio works - the 'test' feature in Ubuntu setup was reliable in outputting a signal that the scope could detect (and could be heard in headphones).?? I've checked everything I know to check, which was rather comprehensive.?? It's something between Quisk and the USB port (changing ports didn't make a difference either), and 'feels' to be on the software side (maybe an update to Ubuntu?).

I've even looked into the update idea a bit, but what I found either didn't apply or didn't make a difference.

It's got me really frustrated.?? I've been trying to get on 2m ssb for many years, but don't have the money to buy something (unemployed and disabled - although that may change as I may finally have a job I can handle starting next year).?? Getting this going again would also open up some other possibilities on HF as well.?? (I may even try to scrounge parts - I've always been rather good at that - to build a 6m transverter.)

Bob
N4FBZ

On 12/4/19 7:02 AM, Nick wrote:

On 03/12/2019 20:47, Robert D. Bowers wrote:

Any suggestions on where to check next? It doesn't seem to be hardware related at all... something between Quisk and the digital signal going into the USB audio devices!

I have experienced similar problems with Linux Mint 19.2 (Ubuntu 18.04 based).

Have you selected the right pulseaudio devices in your sound settings?

73
Nick
G3VNC