"Moving" an HDHR from one Sage Server to another

[wayner]

I want to remove an HDHR from one Sage Server and use the tuner in a new Sage server. Can I just remove the source on the old Sage server and then just set it up on the new Sage server?

Can I have one of the two tuners in my HDHR associated to the old Sage server and one associated to the new Sage server, at least while I am in the transition phase.

Is Sage and/or the HDHR smart enough to not allow you to associate the same HDHR tuner with two PCs simultaneously?

[gplasky]

I believe the HDHR device is sharable in such a way as you can point multiple and different applications at them and be able to use them. But it is first come, first serve. So in SageOld you could configure for HDHR1tuner1 and in SageNew configure HDHR1tuner2. And one could be OTA and the other QAM. As long as one doesn't step on the same device the other is trying to use. You could have both tuners associated with both Sage servers but it wil be first come first serve so one of the recordings will error out. You would need to pay special attention to what server is recording what and which tuner has the priority on which server. Probably easier to split devices and/or tuners between the two.

Gerry

[wayner]

Thanks Gerry but no unencrypted QAM from Rogers cable except for music channels.

[gplasky]

Bummer. Regardless the HDHR supports different configuration for the tuner on a single device. And remember the HDHR is a network device so an appliction (SageTV, WMC, etc) doesn't "grab" the device like it does a physical device attached to the server. The BDA drivers talk to the HDHR.

Gerry

[jasonl]

The Windows BDA drivers do lock the tuners when in use to prevent other PCs or other applications on the same PC from taking over, and the dynamic tuner allocation feature will automatically map requests to a different available HDHomeRun tuner if the one the application tries to use is in use elsewhere. Won't help if you're running SageTV on Linux/Mac of course, but on the Windows side it's all transparent to the application in the normal configuration. The answer to all of the questions in the first post is "yes".