Page 1 of 2

Compatibility report

PostPosted: Sun Feb 22, 2015 1:37 pm
by ks1h
Managed to download the whole thing this morning. Runs with no errors BUT:
1) panadapter area is white and blank although I can click around and get freq to change
2) S signal changes as I click around so it is receiving something
3) I get about 50ms of real audio when I start the app but then horrible digital noise and then no audio
4) When I start the app, I get an additional audio mixer (i.e., in addition to speaker mixer) which has Line(Peaberry Radio) and Peaberry CW application. Nothing useful happens if I switch from Line (Peaberry Radio) to Speakers.
5) I can cancel the app and reload HDSDR with no problems.

I looked at the system event viewer and didn't see anything obvious.

Any ideas???

73
Ken KS1H

Re: Compatibility report

PostPosted: Mon Feb 23, 2015 3:53 am
by AE9RB
Older Intel video drivers for Windows are known to have problems. I'm waiting on a framework update to fix this.

The extra mixers are a Windows thing. You might not see them in other applications that use the older APIs.

What sound card do you have? Did you try the eventSpeaker=false option as described in the readme?

Re: Compatibility report

PostPosted: Mon Feb 23, 2015 11:58 am
by ks1h
It's a Lenovo Thinkpad T60 running 32bit Windows 7. Soundcard seems to be "Soundmax Integrated Digital HD Audio". I tried eventSpeaker=false but it had no effect.

I'll try another computer today.

73 Ken KS1H

Re: Compatibility report

PostPosted: Mon Feb 23, 2015 6:06 pm
by ks1h
Tried it on a fairly new desktop today (Windows 7 64bit). Now I get a spectrum (no freq scale on horizontal axis, though) and can change frequencies appropriately. Same audio problem. A flash of real audio, then digital noise, then nothing. This computer has AMD High Definition Audio built into the motherboard. Also tried changing eventSpeaker = false with no change.

HDSDR works OK.

73 Ken KS1H

Re: Compatibility report

PostPosted: Mon Feb 23, 2015 7:24 pm
by AE9RB
OK, found it. The weird audio is a bug on a fresh install. Just change the AGC once and you'll be set.

Re: Compatibility report

PostPosted: Mon Feb 23, 2015 9:24 pm
by ks1h
Yep, that fixed the audio problem, although I have to put my phones on only after I toggle the AGC. :lol:

I assume that if we want to use an external keyer (like the Iambino) we put it in through the ring of the Key jack and set for "bug"?

Ken KS1H

Re: Compatibility report

PostPosted: Mon Feb 23, 2015 9:30 pm
by W4MMP
Hi,
I had the same question in a different thread.

Set the keyer speed to zero (0). This make the tip work like a straight key connection.

Re: Compatibility report

PostPosted: Mon Feb 23, 2015 11:57 pm
by kb3cuf
Setting keyer speed to zero also allows for tx balance- you can send carrier and monitor while adjusting the sliders- and I found you can get a deep null, indeed. As credit to David and the choice of high quality sound card IC, the null points are quite close to the center on the upper set, and no big difference on the bottom set.

My method is to null, then "margin" by picking the center of the range once the carrier is audible on another RX.

say audible at 30 and then again at 50, I'd be at 40. (a blind setting in the center)

Larry
KB3CUF

Re: Compatibility report

PostPosted: Tue Feb 24, 2015 12:30 pm
by ks1h
Setting the keyer speed to 0 (indicating keyer "off") only partially works for me. I'm using the Iambino keyer. If I send a string of dits at 11wpm, the Peaberry does OK on the first few but then starts to extend the dits into longer durations (as indicated by the PeaberryCW internal sidetone and RF power out, which follows the sidetone). The same happens for dahs, although it seems to take a longer string for this to happen.

Ken KS1H

Re: Compatibility report

PostPosted: Tue Feb 24, 2015 6:49 pm
by AE9RB
I can't reproduce this unless I don't turn the keyer off.