I finally got around to installing the tuner in my wife's car ... If I had known how easy it was, I would have done it years ago. The only weird part was that the antenna connector didn't match what was on the back of the tuner, but a little wire cutting, stripping, and electrical tape and you can make just about anything fit together

So my question is whether it's possible to manually tune the tuner? I can get it to seek, but one station in particular wasn't coming in well enough, apparently, for seeking to stop, but I couldn't figure out how to tune by a frequency at a time. I was finally able to play the reaction-speed game where you start the seek and hit the button again to stop it at just the right frequency, but there must be a better way, right?

You can dial in an exact frequency if you hit the search button.

the antenna connector didn't match what was on the back of the tuner

The adaptor that does that costs peanuts in Europe and silly prices in the US, mind you, The one that I posted to Rob Riccardelli a year ago is still floating round the postal system to this day.

Yeah. I appreciate you sending it Boxer, but It still hasn't shown up. Weird.

but I couldn't figure out how to tune by a frequency at a time.

Known bug in 2.0 final. As Roger said, you can direct-input frequencies using the remote, but that's still not ideal. 3.0 alpha doesn't have this bug IIRC.

Yes, you can manually tune it.

Use the Hijack "KnobSeek" function for this purpose (available as a "virtual button" for remapping, and also pre-programmed in the default PopUp0 menu -- use the Hijack menu to assign this to the Knob).

Cheers

Since when did this work around the bug? And how?

I don't remember the "bug", other than that there is/was one with some particular s/w version. But KnobSeek works just fine with my tuners. Currently using v2final, I think.

Cheers

Why aren't you using the V3Beta? Is there a showstopping bug?

Repeat after me. "There is no V3 Beta."

Oopps, I mean V3Alpha7

I don't remember the "bug", other than that there is/was one with some particular s/w version.

I checked it last night, and I'd remembered it backwards. Knobseek of course works perfectly. The bug wasn't with individual frequency tuning, the bug was with scanning for the strong signals. I'd forgotten that was the bug. We tried to fix it by using Kenwood remote IR translations, but those didn't actually work.

Remapping the IR codes has worked well enough for me... I can 'browse' the frequencies O-K, but if I know where I'm trying to get to, the search works best.

Brilliant! And... it works! (mostly)

[ir_translate]
PrevTrack.LT=b9460c.L
NextTrack.LT=b9460d.L

From this thread where Tony and Mark have a disturbingly similar conversation... maybe this issue is due for a FAQ: "Manually tune the radio workaround for version 2.0"

Right, that's the one I was thinking of. That translation isn't for browsing the frequencies, it's supposed to let you seek to the next strong signal, and we were told it doesn't work for that purpose.