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

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

Have you checked with alsamixer to make sure nothing is muted?
73 ... Sid.

On 04/12/2019 15:46, Robert D. Bowers wrote:

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

Nothing that shouldn't be.? I've muted some of the features of the built-in audio only.? The two USB sound cards - they both are fine as far as the settings (checked with both alsamixer and QasHctl (I ran across a situation where that software found a setting that alsamixer missed - that shut down audio out in another application).

History of this problem - more recent.

I lucked into this small footprint computer and thought it would be a useful thing to have a dedicated computer running radios. (Using Ubuntu 18.04)

I first installed Quisk.? It worked.? Upgraded to gain some functions I wanted, it worked.? Then months later started having problems.? Found the one affecting the Si570... but still something a bit strange.? Then I discovered this problem. Installed Pulseaudio volume control.? That helped in diagnosing some receive issues, no reliable Tx.? Installed alsamixer, could not find anything wrong.? Updated Quisk to most recent version. Still no Tx audio to radio.? Installed QasHctl, still nothing wrong found. Finally joined here and asked for help.

If I can figure out which file is the config file for Quisk (most recent version), I'm going to look through that.? I'd activated the digital signals some time ago, but my present setup doesn't require that - and maybe there is some sort of interference there.

It's a tough one.? Very irritating and frustrating.

(Thanks for replying Sid!)

Bob

On 12/4/19 6:24 PM, Sid Boyce via Groups.Io wrote:

Have you checked with alsamixer to make sure nothing is muted?
73 ... Sid.

On 04/12/2019 15:46, Robert D. Bowers wrote:

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

Hello,

I will add a feature to the next Quisk release to show the audio level for each connected sound card. It will be on the Config/Status screen. That should help with debugging.

Jim
N2ADR

Hello,

I will add a feature to the next Quisk release to show the audio level for each connected sound card. It will be on the Config/Status screen. That should help with debugging.

Jim
N2ADR

FOUND!!!

Crazy thing.?? Since my transmit audio in won't be over 2.6K or so (JT65/FT8/PSK31/voice/etc.), I'd had the mike audio in set to 8K (one of two settings).?? I thought I read somewhere that the audio in for mike (or digital as I've been running it) didn't require the maximum bandwidth set to the same setting as the IQ bandwidth (I guess for that side of the system - the audio in and out, it could be less than the radio side).?? I changed it to 48K and now I have audio out and a signal out.?? (Signal condition/modulation - next to check!)

I also found another thing...?? Sometimes you have to play with a combination of mixers to get a mike going.?? I use the front mike of the "small footprint" computer used with the radio, and could not get any audio on the TX test.?? I messed and messed with it, without luck.?? Finally I went back to QasHctl and found that there was a single setting involving the front mikes that wasn't set.?? I changed that, went back to Alsa Mixer and found that I had to change the audio in sensitivity again, then changed the bandwidth for mike audio - and everything started working.

BTW - a small thing that might be useful - there are adjustments in the audio setup for each channel (output level and phase), but I couldn't find something that after adjusted, would adjust the transmit audio level (increase or decrease power in FM mode, for instance).?? That might be a nice option to have as one of the buttons or as a slider.

Thanks for the suggestions and "listening"!!!

Bob
N4FBZ


On 12/5/19 8:37 AM, jimahlstrom wrote:

Hello,

I will add a feature to the next Quisk release to show the audio level for each connected sound card. It will be on the Config/Status screen. That should help with debugging.

Jim
N2ADR