ExeMultiTuner

[wayner]

If I remember correctly it goes in lieu of the device number. I think it does go in the Properties file but it actually may go in the Windows registry, but I am not 100% sure as I am going with my memory from years ago. Post back if you can't find it - and I will try to find it when I get home tonight in a couple of hours.

[tvmaster2]

Originally Posted by wayner

If I remember correctly it goes in lieu of the device number. I think it does go in the Properties file but it actually may go in the Windows registry, but I am not 100% sure as I am going with my memory from years ago. Post back if you can't find it - and I will try to find it when I get home tonight in a couple of hours.

thanks - I’ll keep poking around in here. arggg. lol.

[wayner]

Open up the properties file in a text editor and search for the unique id - as in b4c876f0

[wnjj]

Originally Posted by tvmaster2

UPDATE - I had to change my cable set top box due to a broken jack. I have the same model as a replacement (Cisco 4742HD), but my Sage setup wouldn't recognize channel change anymore.
I used Timmoore's command line prompt and was able to force a channel change with 'channel -f -a [device number] [channel number], but can't get Sage to change channels.
It's been so long since I had to set this up - does every set top have a unique ID that has to be entered into Sage Properties somewhere? Anyone know what the missing step is?
In the 'Common' dir, I was using FWchannelproxy2 as the HDPVR's tuning device.
Stumped

Is your .ir file named the same as the [device number] you used when you ran TimMoore's command line?

[wayner]

SO the unique ID is in the device name in the properties file like this:
mmc/encoders/-431556906/90/0/device_name=c6f0ad921600

My ir file also uses the unique id, as in c6f0ad921600.ir

This is in the EXE folder, as in: C:\Program Files\SageTV\Common\RemoteCodes\EXEMultiTunerPlugin or something like that.

This is all from backup files as I just realized that my Windows SageTV servers don't have working connections to firewire as my main server is on unRAID and that uses a different firewire tuning process.

[jpwegas]

Originally Posted by wayner

I think the Tim Moore website is now gone.

If anyone needs it for reference, it appears that the Internet Archive still has an intact copy (including the MSI files):

https://web.archive.org/web/20151002...ire/readme.htm

[tvmaster2]

Originally Posted by jpwegas

If anyone needs it for reference, it appears that the Internet Archive still has an intact copy (including the MSI files):

https://web.archive.org/web/20151002...ire/readme.htm

would you happen to have a way back link to the babvgant files? Those links seem to be key instruction info, and they're all dead:

http://babgvant.com/files/folders/sa...ntry11740.aspx

[tvmaster2]

Originally Posted by wayner

SO the unique ID is in the device name in the properties file like this:
mmc/encoders/-431556906/90/0/device_name=c6f0ad921600

My ir file also uses the unique id, as in c6f0ad921600.ir

This is in the EXE folder, as in: C:\Program Files\SageTV\Common\RemoteCodes\EXEMultiTunerPlugin or something like that.

This is all from backup files as I just realized that my Windows SageTV servers don't have working connections to firewire as my main server is on unRAID and that uses a different firewire tuning process.

Here's what Timmoore channel returned:

Unique ID 484df2665f38

Vendor ID 385f66

Model ID 1286

[wayner]

Do you have the EXEMultituner instructions. If I remember correctly someone did a word document on this. I think I might have posted some revisions to this when I first did this config something like 13 years ago. It was on the file section of this forum.

[wayner]

So I found the page but the file is gone. https://forums.sagetv.com/forums/dow...do=file&id=157

[tvmaster2]

I’ve been reading forum posts all day, maybe I have? Problem is, some of the documents referred to the most are long gone. I’m searching through some backup drives. I don’t remember it being this difficult originally - so something is either corrupted or missing.

[tvmaster2]

Originally Posted by wayner

So I found the page but the file is gone. https://forums.sagetv.com/forums/dow...do=file&id=157

that’s happening a lot lately. I wish all these linked help files weren’t linked but were imbedded. Now that Opus, Narflex and Fuzzy seem to have left the scene, it would be great if help info hadn't disappeared as well...

[wayner]

I found the doc.

[wayner]

And here is a post describing how to use the unique ID https://forums.sagetv.com/forums/sho...07&postcount=8

I figured it out - four steps.
Find the Unique ID by running channel -v from a command prompt in the folder that this file is installed (my unique ID is 74bf21471900)
Run regedit and change "channelw.exe %DEVICE%" to "channelw.exe -n %DEVICE%"
Add a new .ir file with your unique ID - copy the exist file (i.e. 2.ir) to a new file and change the 2 to your unique ID - in my case 74bf21471900.ir
Fully shutdown Sage and change the device_name property to your unique ID - in my case 74bf21471900 so - mmc/encoders/1642691032/3/0/device_name= 74bf21471900

I did this on my old PC (I guess now my test environment) and it seems to work. Hopefully it is using the unique ID rather than the old device number - I think it must be.

[jpwegas]

Originally Posted by tvmaster2

would you happen to have a way back link to the babvgant files? Those links seem to be key instruction info, and they're all dead:

http://babgvant.com/files/folders/sa...ntry11740.aspx

That link was truncated when it got posted but I can see a lot of the pages and files here:

https://web.archive.org/web/20180816...ant.com/files/

A lot of things seem to be there but I didn't check whether all the pages and downloads work.

--John

[wayner]

And here is a post describing how to use the unique ID https://forums.sagetv.com/forums/sho...07&postcount=8

This is from that thread post on Jan 7, 2009

Originally Posted by wayner

I figured it out - four steps.
Find the Unique ID by running channel -v from a command prompt in the folder that this file is installed (my unique ID is 74bf21471900)
Run regedit and change "channelw.exe %DEVICE%" to "channelw.exe -n %DEVICE%"
Add a new .ir file with your unique ID - copy the exist file (i.e. 2.ir) to a new file and change the 2 to your unique ID - in my case 74bf21471900.ir
Fully shutdown Sage and change the device_name property to your unique ID - in my case 74bf21471900 so - mmc/encoders/1642691032/3/0/device_name= 74bf21471900

I did this on my old PC (I guess now my test environment) and it seems to work. Hopefully it is using the unique ID rather than the old device number - I think it must be.

[tvmaster2]

Awesome sleuthing, thanks. I will be sure to save these for myself. Will let you know the results. I’m still partially concerned Windows isn’t properly relating to the new 1394 connection, but I CAN force a Firewire channel change with -f

[wayner]

Originally Posted by tvmaster2

Awesome sleuthing, thanks. I will be sure to save these for myself. Will let you know the results. I’m still partially concerned Windows isn’t properly relating to the new 1394 connection, but I CAN force a Firewire channel change with -f

Then hopefully you are good. I had the occasional issue where causing channel changes could cause the PC to crash if you tried to force it and you used the wrong parameters.

[tvmaster2]

Originally Posted by wayner

Then hopefully you are good. I had the occasional issue where causing channel changes could cause the PC to crash if you tried to force it and you used the wrong parameters.

Time will tell. Maybe it’s time to investigate USB-UIRT

[tvmaster2]

Originally Posted by wayner

And here is a post describing how to use the unique ID https://forums.sagetv.com/forums/sho...07&postcount=8

I figured it out - four steps.
Find the Unique ID by running channel -v from a command prompt in the folder that this file is installed (my unique ID is 74bf21471900)
Run regedit and change "channelw.exe %DEVICE%" to "channelw.exe -n %DEVICE%"
Add a new .ir file with your unique ID - copy the exist file (i.e. 2.ir) to a new file and change the 2 to your unique ID - in my case 74bf21471900.ir
Fully shutdown Sage and change the device_name property to your unique ID - in my case 74bf21471900 so - mmc/encoders/1642691032/3/0/device_name= 74bf21471900

I did this on my old PC (I guess now my test environment) and it seems to work. Hopefully it is using the unique ID rather than the old device number - I think it must be.

OK, now that I'm awake.....
Step one: finished
Step two: where does channelw.exe show up in regedit? It doesn't show up anywhere in mine.
Step three: where does the new .ir file get added, SageTV Common dir?
Step four: change the device_name? That's in Sage Proerties/appropriate encoder line?

Actually, I'm concerned there's something wrong with how Windows is recognizing this 1394 device.