WinXP: UniTrunker 1.0.0.6 thru 1.0.0.9 won't select audio adapter from list

[offsite]

System is WinXP, ICOM R8500, Sennheiser USB audio adapter (one of several present).

All UniTrunker versions work fine from retro up thru 1.0.0.5.

UniScope shows expected signal.

1.0.0.6 thru 1.0.0.9 show flat line on scope and no decoding.

Exact same config is used for all versions.

Sorry if this is old issue, Rick, but I've been using retro until today.
------------------------------------------------------------------------------------------------
OK... just gave it one more try and here's the fix!

For some reason (at least on my XP system) the new versions (1.0.0.6 and up) will not properly select a sound card input when multiple adapters are present.

But if you set the desired adapter as the default (using the PC soundcard application) then Unitrunker 1.0.0.6 and up will pick up the signal when UniTrunker input is also set to default.

All versions prior to 1.0.0.6 will allow selection of the desired adapter from the list, even when it is not the default adapter.

I'm guessing this is already an identified issue... but if not, hope this note saves somebody else the trouble to run it down...

-rb-
PS: I changed the title to reflect this "fix"

[offsite]

Hi Rick,

Just finished an afternoon of fun with 1.0.0.9!

Was able to import all the systems I previously worked up in 1.0.0.5... so that was a great help.

Here, 1.0.0.9 is now the highly stable graphics based version of "retro" I've been looking forward to!

The ability to differentiate systems in the local EDACS environment (where all systems look the same) is a total joy worth waiting for.

And the local DOD P25 system comes thru with flying colors.

Congratulations, Rick, and thanks for what I can only imagine was (is) an effort of enormous immensity for the benefit of the community!!

Thank you, thank you, thank you!

-rb-

[Unitrunker]

Originally Posted by offsite

the new versions (1.0.0.6 and up) will not properly select a sound card input when multiple adapters are present.

Weirdness ... I'll check this out. Thanks rb.

[Unitrunker]

I'm not able to recreate the problem. I don't have an external (eg. USB) audio device. I see two choices - "Microsoft Sound Mapper" and "SigmaTel Audio". I can successfully decode from either.

If you add or remove a USB device - the program might not notice. If a device is missing - click the refresh button on the Receiver toolbar. The program will ask Windows for a current list of audio input devices. The missing device should appear in the Audio Port drop-down list of selections.

[scanpprcn]

Rick, I posted this issue in another thread, but I think it got lost. I too have two sound cards in the PC running UT... Unless the sound card in my machine is selected in Windows to be the default adapter UT will not decode the data (nothing shows on the scope either). If I toggle between the cards in audio properties, each one in turn being the default sound card then I can selectively route the audio, but it effectively leaves the other one dead. I'm running XP Pro SP3. BTW, this behavior does not exists in the retro (DOS) version on the same machine (to rule out PC/Windows issues for you).

[SkipSanders]

I get the same problem, Vista 64, with one USB sound device, and one on-board sound device.

If I select the on board device before the USB device is added, it works. If USB is selected and running first, Unitrunker won't recognise the on board sound input, though you can select it. So it depends on which device had control first, looks like. If I reboot with both sound devices present, Unitrunker seems to work ok. It's a little hard to guess when it'll fail, and when it won't.

[Unitrunker]

Thanks everyone. I'll pick up an external USB audio input from Fry's on the cheap for testing.

[offsite]

Hi Rick,

Had some more time to play with the USB audio adapter ("adapter") issue to get more info that might be helpful.

From previously, if the adapter is set as default on the PC, it can be selected as default or as its own ID from the UT list of adapters. Under this configuration either choice WILL provide a signal to the scope and for decoding.

However, if the adapter is not set as default on the PC it still can be selected its own ID from the UT list of adapters, but it WILL NOT provide a signal to the scope or for decoding.

Further, if the adapter is set as default on the PC and selected as its own ID from the UT list of adapters and then removed as default on the PC, it WILL NOT provide a signal to the scope or for decoding.

While this last result is as expected, perhaps it will be in some way diagnostic.

My guess is its just another one of those quirky USB issues that plague computer systems everywhere, and probably only a factor if anyone wants to run multiple instances of UT simultaneously (is this even possible?) with inputs from various adapters.

Thanks again, Rick, for your selfless efforts for all of us out here.

-rb-

[Unitrunker]

Originally Posted by offsite

if the adapter is not set as default on the PC it still can be selected its own ID from the UT list of adapters, but it WILL NOT provide a signal to the scope or for decoding.

I found the cause ... the program was using the wrong index to select the audio device. Selecting the Microsoft Wave Mapper would give you nothing. Selecting the next device in the list would actually get you the wave mapper (default) device. If you picked a third choice, you'd actually get the second one (and so on).

I've fixed this for the next release.

[offsite]

Thanks, Rick!!