Sage 64 Server - USBUIRT Error

[SteveW]

I currently have 9.1.8 of the server running, using the USBUIRT to control my two Bell Sat tuners with no issue.


Installed 9.2.1 64 bit in a new directory. When I get to the point to configure tuning for my HD-PVRs, I get the following attached error.


What am I missing here? If I reboot, and start only the 64 bit Sage to make sure the old version isn't hanging onto the driver, I still get the same error. I'm pretty sure I saw that USBUIRT was working in the 64 bit version. Any suggestions?

[wnjj]

The same thing happened in the beta installer (https://forums.sagetv.com/forums/sho...&postcount=238). I thought that got fixed for the final but you may have to follow the same steps Tiki did in the posts after this one.

[Tiki]

Originally Posted by wnjj

The same thing happened in the beta installer (https://forums.sagetv.com/forums/sho...&postcount=238). I thought that got fixed for the final but you may have to follow the same steps Tiki did in the posts after this one.

I was never successful at getting both transmit and receive to work simultaneously with 64-bit Sage when running Sage as a service. So, if I set up the USBUIRT to work with my remote, I would get that same error when I tried to configure the blaster to work with my cable box. If I disabled the USBUIRT remote and restarted, then I could get the blaster to work.

I could make both work if Sage was in application mode (not running the Sage service), but I would never consider running that way except as an experiment. For now I am still I using 32-bit Sage.

Apparently 1 person did report that they got this working, so I was planning to give it one more try soon. But I am skeptical (I suspect they weren’t really in service mode, or they weren’t using the transmitter and receiver at the same time). I really hope I’m wrong and it will just work if I try again.

[SteveW]

Originally Posted by wnjj

The same thing happened in the beta installer (https://forums.sagetv.com/forums/sho...&postcount=238). I thought that got fixed for the final but you may have to follow the same steps Tiki did in the posts after this one.

So reading thru the posts it sounds like there is a 64 bit driver for the usbuirt I need to install? Are they part of the install package and just not installed, or do I need to download them? I just need it to work as a blaster....

[wnjj]

Originally Posted by SteveW

So reading thru the posts it sounds like there is a 64 bit driver for the usbuirt I need to install? Are they part of the install package and just not installed, or do I need to download them? I just need it to work as a blaster....

It’s supposed to be part of the installer but something wasn’t right during the beta. I thought it was corrected but maybe not. You can try following the instructions in this post to see if it helps: https://forums.sagetv.com/forums/sho...&postcount=191

[wnjj]

Originally Posted by Tiki

I was never successful at getting both transmit and receive to work simultaneously with 64-bit Sage when running Sage as a service. So, if I set up the USBUIRT to work with my remote, I would get that same error when I tried to configure the blaster to work with my cable box. If I disabled the USBUIRT remote and restarted, then I could get the blaster to work.

I could make both work if Sage was in application mode (not running the Sage service), but I would never consider running that way except as an experiment. For now I am still I using 32-bit Sage.

Apparently 1 person did report that they got this working, so I was planning to give it one more try soon. But I am skeptical (I suspect they weren’t really in service mode, or they weren’t using the transmitter and receiver at the same time). I really hope I’m wrong and it will just work if I try again.

JustFred is quite knowledgeable and thorough so I believe him when he said it worked for him. Are you on Windows 7 still? There may be some system level security setting that matters when it comes to processes sharing hardware. I would think Jon’s work to make it Vista compatible would have carried over into the 64-bit driver code since it was so long ago.

[Denali]

I finally got 64 bit partially running but USBUIRT won't receive in Service mode like others have seen (I had to copy the files from the posted ZIP file). When using Application mode USBUIRT will work as a receiver but my Hauppauge Colossus 2 is not detected. In either Service or Application mode when selecting which airing to record both SD and HD channels for the program are displayed even though only the HD channels are enabled. Even the old analog channels show in the Record selection and their disabled also. Think I'm heading back to 32 bit version 9.1.10. May try the 32bit 9.2.1 build and see how it plays.

[jusjoken]

Originally Posted by wnjj

It’s supposed to be part of the installer but something wasn’t right during the beta. I thought it was corrected but maybe not. You can try following the instructions in this post to see if it helps: https://forums.sagetv.com/forums/sho...&postcount=191

I was never able to recreate the copy issue. My tests all succeeded and copied the 64 bit driver to the system32 folder overwriting the 32 bit one. Obviously this copy fails for some users so it needs to be manually copied. The 64 bit driver should be in the redist folder under sagetv.

k

[wnjj]

Originally Posted by Tiki

I was never successful at getting both transmit and receive to work simultaneously with 64-bit Sage when running Sage as a service. So, if I set up the USBUIRT to work with my remote, I would get that same error when I tried to configure the blaster to work with my cable box. If I disabled the USBUIRT remote and restarted, then I could get the blaster to work.

I could make both work if Sage was in application mode (not running the Sage service), but I would never consider running that way except as an experiment. For now I am still I using 32-bit Sage.

Apparently 1 person did report that they got this working, so I was planning to give it one more try soon. But I am skeptical (I suspect they weren’t really in service mode, or they weren’t using the transmitter and receiver at the same time). I really hope I’m wrong and it will just work if I try again.

Reading this super old thread (https://forums.sagetv.com/forums/showthread.php?t=45049) has me wondering about StephaneM’s idea of having the server process the IR receive since the HW is really connected there anyway. That would clear this up. I don’t know what is involved and may require a bunch of work.

[JustFred]

Originally Posted by Denali

I finally got 64 bit partially running but USBUIRT won't receive in Service mode like others have seen (I had to copy the files from the posted ZIP file). When using Application mode USBUIRT will work as a receiver

I had no problems running on Win7-x64. See my previous post here. Maybe there's some issue that's unique to Win10, which I don't use.

[wnjj]

Originally Posted by Denali

I finally got 64 bit partially running but USBUIRT won't receive in Service mode like others have seen (I had to copy the files from the posted ZIP file). When using Application mode USBUIRT will work as a receiver but my Hauppauge Colossus 2 is not detected. In either Service or Application mode when selecting which airing to record both SD and HD channels for the program are displayed even though only the HD channels are enabled. Even the old analog channels show in the Record selection and their disabled also. Think I'm heading back to 32 bit version 9.1.10. May try the 32bit 9.2.1 build and see how it plays.

Would it not receive in service mode at all or only after configuring it as a blaster first? I may have to ask Jeff if there’s any way to overhaul the receive code to be handled on the server and then forwarded to the client.

I’m guessing the channels all showing up is a configuration issue related to a new install rather than something 64-bit specific. You could try copying over your 32-bit properties file and modifying the paths to “Program Files” manually. There will likely be other users stumbling upon setup issues they haven’t worried about in years.

[Denali]

It was after configuring as blaster. Trying to configure Remote Control for receiver get error "Failed setting the Infrared Receiver Port! Please ensure the device is connected." The USBUIRT led blinks but Sage does not see it.

[Tiki]

Originally Posted by wnjj

JustFred is quite knowledgeable and thorough so I believe him when he said it worked for him. Are you on Windows 7 still? There may be some system level security setting that matters when it comes to processes sharing hardware. I would think Jon’s work to make it Vista compatible would have carried over into the 64-bit driver code since it was so long ago.

I did all my testing with the beta 9.2 on Windows 10, and am currently using the 32-bit version of the beta with no real issues. I don’t have a Windows 7 machine setup anymore. I have not tried the final 9.2.1 released version yet and am out of town at the moment so can’t experiment right now.

It’s a shame that Jon didn’t respond one way or the other - it would be nice if he could confirm whether this 64-bit driver is based on the code that fixed the problem in Vista or not.

[Tiki]

Originally Posted by wnjj

Reading this super old thread (https://forums.sagetv.com/forums/showthread.php?t=45049) has me wondering about StephaneM’s idea of having the server process the IR receive since the HW is really connected there anyway. That would clear this up. I don’t know what is involved and may require a bunch of work.

This sounds like it would be tricky and possibly messy. Sage supports multiple clients that may or may not be hosted on the same hardware as the server. You could even have multiple Virtual Machines running on the same hardware side by side and the client and server could be in different VMs.

You wouldn’t want to do this for a remote client. So I guess you would need to add logic to determine if the client was on the same hardware (or same VM) as the server.

[Denali]

Think I found solution for USBUIRT receive in Service Mode. There is a line in Sage.properties files irman_rcv_port=USB. In SageClient.properties it is irman_rcv_port=. I inserted USB to the client file and now the USB-UIRT can be selected in Setup : Detailed Setup : Commands and configured.

The disabled SD channels showing in the Record menu seems to have gone away after restart of Service.

EDIT spoke to soon,

The USBUIRT no longer transmits with this change. No longer any options to select in Change Tuning Device until USB is removed from SageClient.properties file.

[SteveW]

I'm all fixed up. uu_irsage.dll was where it should be.


The uuirtdrv.dll in the system32 directory was still the 32 bit one. Upon reflection, probably good it didn't overwrite it anyways. I have the 64 bit version installed in a new directory while I still use the 32 bot version and gradually get the settings same in the 64 bit version. If uuirtdrv.dll had been overwritten, it would have stopped channel changes from working correctly on my 32 bit production SageTV.


I just copy the 32 and 64 bit dll back and forth whenever I need tuning working on my 64 bit for testing. Eventually, the 64 bit dll will be the one left in there.


Thanks to everyone involved for their tireless work on the 64 bit version. Working great so far!

[wnjj]

Originally Posted by SteveW

I'm all fixed up. uu_irsage.dll was where it should be.


The uuirtdrv.dll in the system32 directory was still the 32 bit one. Upon reflection, probably good it didn't overwrite it anyways. I have the 64 bit version installed in a new directory while I still use the 32 bot version and gradually get the settings same in the 64 bit version. If uuirtdrv.dll had been overwritten, it would have stopped channel changes from working correctly on my 32 bit production SageTV.


I just copy the 32 and 64 bit dll back and forth whenever I need tuning working on my 64 bit for testing. Eventually, the 64 bit dll will be the one left in there.


Thanks to everyone involved for their tireless work on the 64 bit version. Working great so far!

Actually that DLL in the system32 directory should only be the 64-bit one. The 32-bit one is in there by a mistake in the original driver installer. 32-bit programs load their DLL’s from sysWOW64. You can leave the 64-bit one in system32 and still run either version.

[jusjoken]

Originally Posted by SteveW

I'm all fixed up. uu_irsage.dll was where it should be.


The uuirtdrv.dll in the system32 directory was still the 32 bit one. Upon reflection, probably good it didn't overwrite it anyways. I have the 64 bit version installed in a new directory while I still use the 32 bot version and gradually get the settings same in the 64 bit version. If uuirtdrv.dll had been overwritten, it would have stopped channel changes from working correctly on my 32 bit production SageTV.


I just copy the 32 and 64 bit dll back and forth whenever I need tuning working on my 64 bit for testing. Eventually, the 64 bit dll will be the one left in there.


Thanks to everyone involved for their tireless work on the 64 bit version. Working great so far!

If all is working right on a 64 bit system then usbuirt should use the 32 bit driver from the syswow64 folder and the 64 bit driver from the system32 folder. You should not need to move the file around.

The sagetv installer tries to do this copy because the usbuirt author created his installer to install the 32 bit driver to BOTH syswow64 and to system32

Perhaps the copy failure occurs if the usbuirt is in use??

k

[SteveW]

Originally Posted by jusjoken

If all is working right on a 64 bit system then usbuirt should use the 32 bit driver from the syswow64 folder and the 64 bit driver from the system32 folder. You should not need to move the file around.

The sagetv installer tries to do this copy because the usbuirt author created his installer to install the 32 bit driver to BOTH syswow64 and to system32

Perhaps the copy failure occurs if the usbuirt is in use??

k

Ok, I didn't realize the 32 bit drivers were coming from the the SysWOW64 directory. Good to know. The system32 directory definitely had a different version of uuirtdrv.dll compared to what the installer should have put there.


I had the 32 bit Sage shut down while the 64 bit installed, so I wouldn't think the DLL was in use, but couldn't say for sure if something else had it open. Like you said, 32 bit Sage uses a different directory, so nothing should have been holding onto the one in the system32 directory...

-S.