USB-UIRT tuning devices not being identified?

[dvd_maniac]

Upgraded to latest beta (7.0.12) using Win7 64bit and now my usb-uirt does not see tuning devices. I went to the "Test Infrared Code" and nothing was there. I went to "Change Tuning Device" and nothing there either.
I use the Uirt to control the Hauppauge remote so I know it is functioning correctly in Windows and Sage.
I checked the Common folder and USB-UIRT Transceiver is there as well as all the pertinent IR files.
Anybody else or any ideas?

[ranger]

No help for you, just a comment that I am having the same problem. Also running Win7 64bit. I just started searching to see where the problem might be but no results so far. I had not tried the USB UIRT prior to 7.0.12

[perfessor101]

I guess I'll be submitting a bug report too ...

I'm loosing the USB-UIRT on SageTV 7.0.12.234 Client on Windows 7 Professional 64bit.

If I unplug and replug the USB-UIRT and restart SageTV Client the remote controls start working again ...

SageTV 7.0.12.234 server seems to have no trouble yet using my other USB-UIRT for tuning on Windows 7 Professional 64bit.

I just thought it was Widows being windows again ...

Bobby

[Spectrum]

I'll chime in as a third that this is happening to. My USB-UIRT just arrived and I set it up over the weekend; I got it to remedy missed recordings on my HDPVR due to the blaster flaking out.

Windows sees it fine. Sage didn't initially see it when I tried to change the tuning device for the HDPVR so I removed the HDPVR as a tuner, then added it back. It saw the USB-UIRT but then threw up an error message when when it got to the point of learning codes. Unplugging and re-plugging the USB-UIRT got me through. Now whenever I close the client and stop the service (same box) I have to restart both, then unplug and re-plug the USB-UIRT or Sage won't see it and change channels. Once I un/re-plug it, works like a champ. I just have to remember to do this EVERY time I stop/start things or I miss recordings

This is on Win7 x64 too if it matters. I went ahead and submitted a bug report too.

[Spectrum]

Apparently my problem is because I'm running Sage as a service and running the client on the same box. The beta team's response from my bug report was

This is a known issue with the USBUIRT on Vista/Win7. Their drivers don't
support using it from the service and a desktop app at the same time
reliably.

Sooooo I just bought a $50 device that can be a remote receiver OR an IR blaster but not both.

<rant>The Vista/Windows 7 architecture is here to stay; at least until it evolves into something new. Drivers written for XP are just not gonna cut it for devices intended to be used in modern systems.</rant>

I sent an email to USB-UIRT support to see if there is any update on this. If not I'll see if Sage will take the USB-UIRT back as I have no use for a device that does 1/2 of what is advertised

[Tiki]

You have a couple of options...
1. You could use a 3rd party app to control both the IR Receive and IR Blast functions of the USBUIRT. LMRemote Keymap is one that advertises the ability to do this and there is someone from that company who posts regularly on these forums. Girder or HIP may be able to do this as well.
2. You could use the USBUIRT as a blaster only and use one of the Hauppauge devices as an IR Receiver only.

Personally, I do Option 2. I'm using the USBUIRT to blast 2 cable boxes (one connected to an HD-PVR and one connected to a PVR-150), and I have the IR Receiver plugged into a HVR-2250. I just use the Hauppauge remote.

[Spectrum]

Jon from USB-UIRT responded and said they are aware of the problem and have no timetable for a fix

Originally Posted by Tiki

You have a couple of options...
1. You could use a 3rd party app to control both the IR Receive and IR Blast functions of the USBUIRT. LMRemote Keymap is one that advertises the ability to do this and there is someone from that company who posts regularly on these forums. Girder or HIP may be able to do this as well.
2. You could use the USBUIRT as a blaster only and use one of the Hauppauge devices as an IR Receiver only.

Personally, I do Option 2. I'm using the USBUIRT to blast 2 cable boxes (one connected to an HD-PVR and one connected to a PVR-150), and I have the IR Receiver plugged into a HVR-2250. I just use the Hauppauge remote.

LMRK really borks MALA (Mame launching app) which makes using the system for playing arcade games a PITA. I'll look into Event Ghost and see if that's doable.

After using the HDPVR IR blaster, I'm not letting any IR in/out of the HDPVR. The blaster has been removed and the IR port has a nice layer of gaffers tape on it. It's the only Hauppauge device I have so using that's out.

After reading so many good things about the USB-UIRT I'm really disappointed. I thought it would make this seamless, instead it just introduced more problems into my config.

[wayner]

Channel changing on 64 bit OSes seems to be a real issue as there are no firewire drivers for 64 bit.

[StephaneM]

Originally Posted by Spectrum

LMRK really borks MALA (Mame launching app) which makes using the system for playing arcade games a PITA.

LM RKM is not doing anything that could prevent any application to work correctly, except for one thing: the OSD.

The LM RKM OSD use transparent WPF windows. So when overlaid over some software that make use of DirectX it can cause issues (usually screen flicker, frame rate drop)

At this point you have two solutions: disable the LM RKM OSD (it is mainly used for displaying volume) or try to see if a graphic card driver update or directx settings can improve things if you need the LM RKM OSD.

Regards,
Stéphane.

[Spectrum]

Originally Posted by StephaneM

LM RKM is not doing anything that could prevent any application to work correctly, except for one thing: the OSD.

The LM RKM OSD use transparent WPF windows. So when overlaid over some software that make use of DirectX it can cause issues (usually screen flicker, frame rate drop)

At this point you have two solutions: disable the LM RKM OSD (it is mainly used for displaying volume) or try to see if a graphic card driver update or directx settings can improve things if you need the LM RKM OSD.

Regards,
Stéphane.

The last time I had LMRK installed it prevented my Xbox 360 controllers from sending commands to Mala; controllers worked fine everywhere else, just not in Mala. Shutting down LMRK allowed things to function correctly. I'm not sure exactly what is going on in Mala as it's a pretty old Delphi app that is semi-maintained by someone who is not the original author It works really well for what it does and although configuration is a royal pain, once it's done it just works and is agnostic about OS installs as long as it lives in the same location. Really hacked me off too because I liked LMRK and had to live w/o some of the features.

I got another email last night from Jon and there may be a solution for the USB-UIRT working natively. I'm waiting with fingers crossed! If this doesn't work out I'll dig a little deeper into LMRK and see if I can make it coexist with Mala.

I do realize I'm asking for a lot in terms of system integration here. It seems to be one of those things that in theory should just work. Unfortunately Murphy has way of sneaking up and inserting gremlins into the system that prevents everything from playing nicely.

[Spectrum]

Originally Posted by wayner

Channel changing on 64 bit OSes seems to be a real issue as there are no firewire drivers for 64 bit.

Yep, firewire would be great but I'm not going back to 32bit just for that

[StephaneM]

Originally Posted by Spectrum

The last time I had LMRK installed it prevented my Xbox 360 controllers from sending commands to Mala; controllers worked fine everywhere else, just not in Mala.

Well in this case don't use the wording "borks Mala", but "prevent Xbox 360 controller from working with Mala"...

As the Xbox 360 controller is most presumably a HID device, it is possible that LM RKM can receive (and discard) messages from it. Though IF and ONLY IF you set up LM RKM to use a HID remote (MCE remotes, Firefly Mini...) and NOT if you set up LM RKM to use the USB-UIRT as both a remote and blaster...

You must not have seen the "Technical Support..." button in LM RKM, otherwise I'm sure the issue you have could have been solved promptly.

Regards,
Stéphane.

[Spectrum]

Originally Posted by StephaneM

Well in this case don't use the wording "borks Mala", but "prevent Xbox 360 controller from working with Mala"...

Semantics, but point taken

Originally Posted by StephaneM

As the Xbox 360 controller is most presumably a HID device, it is possible that LM RKM can receive (and discard) messages from it. Though IF and ONLY IF you set up LM RKM to use a HID remote (MCE remotes, Firefly Mini...) and NOT if you set up LM RKM to use the USB-UIRT as both a remote and blaster...

Not sure about the XB360 controller being an HID device, but you hit the nail on the head with the MCE remote. That's exactly what I had set up at the time.

Originally Posted by StephaneM

You must not have seen the "Technical Support..." button in LM RKM, otherwise I'm sure the issue you have could have been solved promptly.

Totally missed it! Of course I tend to do these things late at night

[Spectrum]

Jon has made a beta driver available that straightened everything out. Just thought I'd point it out in case it applies to anyone paying attention to this thread