STB Firewire (IEEE-1394) Support

[davefred99]

Originally Posted by MeInMaui

You have to go to the correct directory via the command line.

Open the command window
type cd c:\firewire [Enter]
type msiexec /i firestb.msi IDENT="1" [Enter]

or I think you can just type

c:\firewire\msiexec /i firestb.msi IDENT="1" [Enter]

It should do the same thing. (I need to blow the dust off my old DOS skills )

I got it running and posted a reply to the everyone over in that thread for all to read.
I gotta say its still not an easy thing to set up but Thanks to this forum I was able to figure it out.
Thanks, Dave

[jpaddock3000]

OK, so I'm having the hardest time getting sage to change my channels. When I using sgraphrecorder or command line, no problem. I have the registry key in the correct location. I make sure to have the service off. I'm able to see that sage sees the new multituner plugin. I make a file called 2.ir in the correct directory and replace stub device with the number 2. I even added the path to the channelw.exe file in windows' path and changed the registry key to just say "channelw.exe %DEVICE% %CHANNEL%". I have even tried "channelw.exe -f -a4 2 %CHANNEL%" thinking that might work. Still no success. This seems to be a very easy process, but for some reason, it isn't working for me. Please assist me. How is %DEVICE% recongnized by the system? Where is that defined? Also, what does the numbers in 2.ir mean? Why aren't I putting the -f -a4 2 in there instead?

Thanks

[MeInMaui]

Originally Posted by jpaddock3000

OK, so I'm having the hardest time getting sage to change my channels. When I using sgraphrecorder or command line, no problem. I have the registry key in the correct location. I make sure to have the service off. I'm able to see that sage sees the new multituner plugin. I make a file called 2.ir in the correct directory and replace stub device with the number 2. I even added the path to the channelw.exe file in windows' path and changed the registry key to just say "channelw.exe %DEVICE% %CHANNEL%". I have even tried "channelw.exe -f -a4 2 %CHANNEL%" thinking that might work. Still no success. This seems to be a very easy process, but for some reason, it isn't working for me. Please assist me. How is %DEVICE% recongnized by the system? Where is that defined? Also, what does the numbers in 2.ir mean? Why aren't I putting the -f -a4 2 in there instead?

Thanks

After setting up the encoder to use the ExeMultiTuner plugin in the SageTV source setup, did you go into sage.properties and add the panel number for that STB (looks like 2 in your case) to the mmc/encoders/.../device_name property? (make sure you shut down SageTV first or the changes won't take.

Aloha,
Mike

[jpaddock3000]

Yes I did. Sorry I forgot to put that on the above post. I changed stub device to 2

[Opus4]

Originally Posted by MeInMaui

After setting up the encoder to use the ExeMultiTuner plugin in the SageTV source setup, did you go into sage.properties and add the panel number for that STB (looks like 2 in your case) to the mmc/encoders/.../device_name property? (make sure you shut down SageTV first or the changes won't take.

BTW: you should be able to do this from the Source Details screen: select Tuner Control, Change Tuning Device, then choose from the list. If it isn't there, then something isn't configured properly.

- Andy

[Opus4]

jpaddock3000: what is the name of the directory you are using below the Common\RemoteCodes directory? It should be "EXEMultiTunerPlugin", not "EXEMultiTuner" -- see my post here.

- Andy

[jpaddock3000]

Andy, I did make sure to have the correct directory name. Once that wasn't working, I renamed that directory to the instructions in the pdf document and when I turned on sage, it automatically created the correct directory again and made a 2.ir file. The file was blank, so I put in the correct information. To me it seems like sage understands that it needs to use that directory, but I'm not having any luck.

[jpaddock3000]

Does anybody have any other ideas? Also, where is %device% defined? Is that in the dll file? How does the dll know to type channelw.exe -f -a4 2 <channel>?

Thanks

[Opus4]

I don't know what is happening... what is the exact name of the registry path/entry you are using? What are its contents? In my registry, EXEMultiTunerPlugin has an item titled 'command' with a string as "<full path to channelw.exe> -f -a4 -n %DEVICE% %CHANNEL%" -- %DEVICE% and %CHANNEL% are substituted with the appropriate values by the plugin.

%DEVICE% comes from your .ir file -- what is its exact path & its contents?

In Source Details, what does it list on the Tuner Control button?

I would go back through the instructions for EXEMultiTunerPlugin & double check all the settings.

- Andy

[jpaddock3000]

Originally Posted by Opus4

I don't know what is happening... what is the exact name of the registry path/entry you are using? What are its contents? In my registry, EXEMultiTunerPlugin has an item titled 'command' with a string as "<full path to channelw.exe> -f -a4 -n %DEVICE% %CHANNEL%" -- %DEVICE% and %CHANNEL% are substituted with the appropriate values by the plugin.

%DEVICE% comes from your .ir file -- what is its exact path & its contents?

In Source Details, what does it list on the Tuner Control button?

I would go back through the intructions for EXEMultiTunerPlugin & double check all the settings.

- Andy

My registry command is:
D:\Software\SageTV\Firewire\channelw.exe -f -a4 %DEVICE% %CHANNEL%

My path to my .ir file is:
C:\Program Files\SageTV\Common\RemoteCodes\EXEMultiTunerPlugin\2.ir
The contents of the file are:
2 38000 400 3

When I go to setup video sources, for tuner control it says:
EXEMultiTunerPlugin 2

Andy,
Did you put quotes in your registry key?

Thanks

[gjvrieze]

Originally Posted by jpaddock3000

My registry command is:
D:\Software\SageTV\Firewire\channelw.exe -f -a4 %DEVICE% %CHANNEL%

My path to my .ir file is:
C:\Program Files\SageTV\Common\RemoteCodes\EXEMultiTunerPlugin\2.ir
The contents of the file are:
2 38000 400 3

When I go to setup video sources, for tuner control it says:
EXEMultiTunerPlugin 2

Andy,
Did you put quotes in your registry key?

Thanks

I know you were asking towards Andy, but he has not yet responded, and yes in fact, mine has the quotes, the easiest way to get it right, is just to use the reg file and change it to resolve your path.....

[jpaddock3000]

OK I just put this in the registry
"D:\Software\SageTV\Firewire\channelw.exe -f -a4 %DEVICE% %CHANNEL%"
I restarted the sage service and still no luck.

Any other ideas.

Also, I just re-built my system and put Vista on it after having all this trouble. I got everything up and running that was on XP, but for some reason can't get sage to change channels via firewire in XP or Vista.

Also, I did use the reg file to import the settings and I did just change the path.

[Opus4]

I don't see quotes in my reg entry. What is the path to the key?

Is that really the path to channelw.exe? If you use that path at a command prompt, does it work?

Try changing the reg entry to use notepad.exe instead & see what error message you get -- you may need to change the service to interact with the dekptop or try it in non-service mode.

- Andy

[jpaddock3000]

Originally Posted by Opus4

I don't see quotes in my reg entry. What is the path to the key?

Is that really the path to channelw.exe? If you use that path at a command prompt, does it work?

Try changing the reg entry to use notepad.exe instead & see what error message you get -- you may need to change the service to interact with the dekptop or try it in non-service mode.

- Andy

Yes, that really is the path. Yes, if I run this command from the command line, it works fine. Just for some reason, it doesn't work in Sage.

Also, I don't get any error message when typing in notepad in the registry and restarting the service.

If it might help, here is a section of my sage.properties file:
mmc/encoders/551195576/2/1/available_channels=
mmc/encoders/551195576/2/1/brightness=116
mmc/encoders/551195576/2/1/contrast=121
mmc/encoders/551195576/2/1/device_name=2
mmc/encoders/551195576/2/1/hue=128
mmc/encoders/551195576/2/1/last_channel=108
mmc/encoders/551195576/2/1/provider_id=962144708217
mmc/encoders/551195576/2/1/saturation=113
mmc/encoders/551195576/2/1/sharpness=63
mmc/encoders/551195576/2/1/tuning_mode=
mmc/encoders/551195576/2/1/tuning_plugin=C\:\\Program Files\\SageTV\\Common\\EXEMultiTunerPlugin.dll
mmc/encoders/551195576/2/1/tuning_plugin_port=0
mmc/encoders/551195576/2/1/video_crossbar_index=1
mmc/encoders/551195576/2/1/video_crossbar_type=2

Please let me know if that looks correct.

Thanks

[Opus4]

As I said above, I don't really know what is happening. The last thing I'll suggest is to check that EXEMultiTunerPlugin.dll is really there and/or redownload it.

- Andy

[fiatmonkey]

Opus4 et all;

I am sorry if someone has asked/posted this before but has anyone created firewire integration with sagetv and cable STB support for linux?

Thanks!

[jpaddock3000]

So I have re-downloaded the file and restarted the machine with no success. Are there any other methods to do firewire tuning via sage besides exemultituner plugin? I was able to have firewire tuning work great with the sgraphrecorder. Does anyone know how to setup a graph to work with the PVR 500?

Thanks

[evilpenguin]

Originally Posted by fiatmonkey

Opus4 et all;

I am sorry if someone has asked/posted this before but has anyone created firewire integration with sagetv and cable STB support for linux?

Thanks!

Do some digging in the linux sub-forum. IIRC that's an experimental feature built into the linux version and you can enable it just by setting a property.

[Endymion]

Well, it appears that I have 2 instances of SGR AND Sage all running as services!

So far testing has revealed no excessive GET_FILE_SIZE messages on either instance of SGR, and Sage is working great. I'm running all 3 as Local System account with Interact with Desktop checked. I get icons for both SGR instances, so I can look at the debugger windows.

Anyone else doing this? Run into any issues? Would anyone like a short writeup on how to set it up?

[evilpenguin]

Originally Posted by Endymion

Well, it appears that I have 2 instances of SGR AND Sage all running as services!

So far testing has revealed no excessive GET_FILE_SIZE messages on either instance of SGR, and Sage is working great. I'm running all 3 as Local System account with Interact with Desktop checked. I get icons for both SGR instances, so I can look at the debugger windows.

Anyone else doing this? Run into any issues? Would anyone like a short writeup on how to set it up?

I'm curious why you need 2 Sage instances, I thought you could setup multiple SGR's in Sage by just adjusting the port numbers.