USB-UIRT in Win10 64 bit - confusion on copying DLLs

[VCRUser]

Originally Posted by wnjj

Look in the SageTV/Common/RemoteCodes/USB-UIRT Transceiver directory for the .ir files. That is where the codes are saved. You should be able to copy those directly over from your existing system.

I did copy those over, but aren't those just for the codes the USBUIRT sends to the cable box? (I don't have that set up as a source yet for the new system, as it's in use by the old one, so can't easily test at the moment). I'm trying to set up the USBUIRT to receive commands from the Hauppauge remote that currently sends commands for playback, navigating menus, etc.. That seems to be done from the menu I described, according to the manual:

SageTV can directly receive codes from an infrared remote control. Like keystrokes, these infrared codes can be assigned to commands in Detailed Setup by using the option to link an infrared code to a command. See:
Link Infrared/Keystroke to SageTV Command [...]
After choosing a command for key/IR code assignment, SageTV will display instructions for you to press the key or remote button to be assigned to the shown command. Any keyboard input at this point is considered to be a key assignment. You can cancel this process by clicking on the
Cancel button with the mouse.

That's what I was trying without success to accomplish. I'd press the remote button but get no response from Sage. If I press a key to map it to a command, Sage responds as expected.
UPDATE: After the system had been shut down and then restarted today, I tried the exact same thing and it's working as expected. Go figure...

[wnjj]

Originally Posted by VCRUser

I did copy those over, but aren't those just for the codes the USBUIRT sends to the cable box? (I don't have that set up as a source yet for the new system, as it's in use by the old one, so can't easily test at the moment). I'm trying to set up the USBUIRT to receive commands from the Hauppauge remote that currently sends commands for playback, navigating menus, etc.. That seems to be done from the menu I described, according to the manual:


That's what I was trying without success to accomplish. I'd press the remote button but get no response from Sage. If I press a key to map it to a command, Sage responds as expected.
UPDATE: After the system had been shut down and then restarted today, I tried the exact same thing and it's working as expected. Go figure...

You’re right. It’s been awhile since I looked at any of this.

Looking through the code, I believe the receive mappings are stored in the properties file under “ui/rc_mappings/*”.

[VCRUser]

Originally Posted by VCRUser

UPDATE: After the system had been shut down and then restarted today, I tried the exact same thing and it's working as expected. Go figure...

So now it's back to not working.

Whether I try to use the remote I already trained, to use it based on copying the settings from the previous installation (same remote, older USBUIRT), or setting up the USBUIRT for tuning, Sage just isn't seeing the USBUIRT. (I get the "Not connected or being used by another application" message). It also isn't displaying the commands mapped to infrared/keystrokes - that is, when I select "link infrared/keystroke to sage tv command," each command shows the standard keyboard mappings but none of the infrareds.

Am I using the correct drivers? After it didn't work initially, I followed & was successful with the advice I found in a post, which I think came from here:

https://forums.sagetv.com/forums/showthread.php?t=63009

• On the 64 bit version USBUIRT install may not complete fully and you may need to perform the following manual steps AFTER the install completes.
o Copy uuirtdrv.dll from "SageTV\redist\usbuirt\amd64" folder into your Windows\System32 directory. Note that there will already be one there from the USB-UIRT driver install, but it is the 32-bit one and shouldn't be there anyway (the 32 bit one will be in SysWOW64 folder). Warning: If you reinstall the USB-UIRT driver for any reason it may replace this file with the 32-bit one.
 32 bit file dated 7/22/2012
 64 bit file dated 7/8/2011

Should there be some other files somewhere? My previous Sage installation has a USBUIRT folder under the Sage folder; my new one doesn't. Should I copy over that folder? It does have a usbuirt folder in sagetv/redist.

I didn't do anything outside of Sage to install the USBUIRT drivers - I don't recall that that is needed, but if it is, I can't find any installation files or instructions.

Windows itself does recognize the USBUIRT, as indicated by Lrnhelper's behaving as expected. I also checked in Control Panel, which shows it and gives the following details on drivers:
c:\\windows\system32\drivers\ftdbus.sys
c:\\windows\system32\drivers\ftd2xx.dll [ver 3.01.19]
c:\\windows\system32\drivers\uuitdrv.dll [ver 2.6.9.9]
c:\\windows\syswow64\drivers\ftd2xx.dll [ver 3.01.19]
c:\\windows\syswow64\drivers\uuitdrv.dll [ver 2.7.0.0]

Under "Events," it says (both showing today's date and around the time I booted the machine today)
"Device configured (oem4.inf)"
Device Started (FTDIBUS)"

[JustFred]

It's best to always reboot your computer after manually moving/copying/replacing any of the .dll's. Without the reboot, Windows might continue to access/use the previous dll (it might still be loaded in memory), causing quite a bit of confusion.

[VCRUser]

It had been powered down after I did that, with no dlls changed in the interim.

[VCRUser]

Originally Posted by JustFred

It's best to always reboot your computer after manually moving/copying/replacing any of the .dll's. Without the reboot, Windows might continue to access/use the previous dll (it might still be loaded in memory), causing quite a bit of confusion.

As noted, rebooting changes nothing in my case. I did, though, find an older post from you suggesting a different dll might be needed?

https://forums.sagetv.com/forums/sho...32&postcount=3

I'm not trying to run anything but Sage with the usbuirt, and the post linked above is about EventGhost, which I'm not using.

[Tiki]

I was never able to get USBUIRT to work as both a transmitter and receiver at the same time with Sage 64bit in Service mode.

Someone else said they got it working, but I suspect they were not using Sage in Service mode. In Service mode, Sage is like 2 different programs: the Sage service wants to use the USBUIRT as a transmitter to blast channels to your cable box, while the Sage UI wants to use the USBUIRT as a receiver to accept commands from your remote control.

My experience was that whichever one tried to access the USBUIRT first got control and blocked the other. I gave up on Sage64 and went back to 32-bit Sage for that reason.

[VCRUser]

Originally Posted by Tiki

My experience was that whichever one tried to access the USBUIRT first got control and blocked the other. I gave up on Sage64 and went back to 32-bit Sage for that reason.

Disappointing, after I put a good bit of effort into setting up Sag64. On the other hand, I found in my rubble an old Cyberlink remote (possibly intended for Windows Media Center) with a USB dongle to work with a PC. Initial tests are promising, and I plan to test further today, along with setting up and testing at least one source to be controlled by the usbuirt. I'll report back here after the further testing, since similar remotes (generic models sent the slow way from China) may provide the same functionality. They're under $10, so I have one on order to have a spare - and hope it and the Cyberlink both prove adequate.

Otherwise I'll have to install Sage32. What happens if you have both 32 and 64 installed? Presumably you want only the one you intend to use to be active and start up whenever the system does. Do you uninstall the other? If not, how do you disable the unused one (presumably keeping it around just in case, to assist with the installation of the 2nd version by matching settings, etc.)?

[Tiki]

Originally Posted by VCRUser

Otherwise I'll have to install Sage32. What happens if you have both 32 and 64 installed? Presumably you want only the one you intend to use to be active and start up whenever the system does. Do you uninstall the other? If not, how do you disable the unused one (presumably keeping it around just in case, to assist with the installation of the 2nd version by matching settings, etc.)?

You can install both side by side, but you should only run one at a time.
By default, they install in different locations and have separate registry settings. They each also will have their own .properties files and wiz.bin files. You can copy wiz.bin from one to the other.

As I said, there was at least one person who posted claiming they got it working correctly in 64-bit Sage, but I could not, and I’ve seen a handful of others post that they could not either. It seems that the people who are happy either don’t run Sage as a service or don’t use the USBUIRT to both send and receive.

[VCRUser]

Originally Posted by Tiki

You can install both side by side, but you should only run one at a time.

So, is the method for stopping one of them from running at startup just to go into setup/detailed/server and disable the server? Would that mean that that instance would start up only if manually invoked? Or is there an additional setting needed to prevent the ui from starting at boot (which then seems to start the server) - something in .properties or in Windows settings? This won't be needed if I can get the alternative remote to work, but would be good to know if I can't.

[VCRUser]

As an update, my Cyberlink remote works well enough, but I can't seem to map buttons that don't already affect sage to commands: the method of pointing the remote at the receiver to learn the command isn't operational. I'm guessing that's because I had to set the remote to something other than USBIRT (I used Windows Media Center). Maybe there's another way to do it, but enough of the buttons work for most of my purposes.

[wnjj]

Originally Posted by VCRUser

So, is the method for stopping one of them from running at startup just to go into setup/detailed/server and disable the server? Would that mean that that instance would start up only if manually invoked? Or is there an additional setting needed to prevent the ui from starting at boot (which then seems to start the server) - something in .properties or in Windows settings? This won't be needed if I can get the alternative remote to work, but would be good to know if I can't.

Use the SageTVServiceControl.exe program in each of the installed directories to disable/enable the service from running.

[SHS]

Originally Posted by Tiki

I was never able to get USBUIRT to work as both a transmitter and receiver at the same time with Sage 64bit in Service mode.

Someone else said they got it working, but I suspect they were not using Sage in Service mode. In Service mode, Sage is like 2 different programs: the Sage service wants to use the USBUIRT as a transmitter to blast channels to your cable box, while the Sage UI wants to use the USBUIRT as a receiver to accept commands from your remote control.

My experience was that whichever one tried to access the USBUIRT first got control and blocked the other. I gave up on Sage64 and went back to 32-bit Sage for that reason.

That right SageTV will not work in service mode with USBUIRT but enable reg auto load at startup to fix under sagetv setting

[VCRUser]

Originally Posted by SHS

That right SageTV will not work in service mode with USBUIRT but enable reg auto load at startup to fix under sagetv setting

Could you expand on that a bit? I think you're saying that:

1. It is possible to have sageTV autoload at startup, which would enable clients, place-shifters, extenders, etc. - while keeping service mode off.

2. Doing so would enable usbuirt to both transmit & receive. Does that also enable Neilm's web interface?

If so, while I know I can disable the server in the service manager app, I've found that when I then start SageTV it turns on the service anyway and the USBUIRT won't receive IR. Am I missing a setting?

I've found a workaround by using another remote control that has its own dongle, but haven't been able to assign commands to additional buttons without the USBUIRT being able to receive the IR. It would be preferable to get the USBUIRT to do both transmit & receive.

[SHS]

Originally Posted by VCRUser

Could you expand on that a bit? I think you're saying that:

1. It is possible to have sageTV autoload at startup, which would enable clients, place-shifters, extenders, etc. - while keeping service mode off.

2. Doing so would enable usbuirt to both transmit & receive. Does that also enable Neilm's web interface?

If so, while I know I can disable the server in the service manager app, I've found that when I then start SageTV it turns on the service anyway and the USBUIRT won't receive IR. Am I missing a setting?

I've found a workaround by using another remote control that has its own dongle, but haven't been able to assign commands to additional buttons without the USBUIRT being able to receive the IR. It would be preferable to get the USBUIRT to do both transmit & receive.

See below

[VCRUser]

I think this is working, but I'm having trouble with off-site placeshifter passwords in the Android miniclient on my phone. I probably need to post this question somewhere else though. I set up a password & the miniclient won't connect when I turn off wifi to simulate connecting from away.