STB Firewire (IEEE-1394) Support - Page 95

pingmustard · #**1881** 11-10-2009, 01:54 AM

Quote:

Originally Posted by nyplayer

After beating my head against the wall

I finally got the right combination and got all my HD and SD channels working with no bad files. Make sure in w7 the legacy drivers are installed for your fire-wire card.

Below is my ini file... notice the tuning delay. The other stuff paths to channel and grf file can be changed.

[System]
Port=6969
[Graph]
FileName="C:\GRAPHEDIT\SGR1\srgts.grf"
TuningDelay=5000
UnloadGraphOnStop=1
UnloadGraphOnSwitch=0
[Girder]
UseGirder=0
GirderHost=127.0.0.1
GirderPort=1024
GirderPassword=
GirderPrefix=Channel
GirderIndividualNumbers=1
GirderInterNumberTimeSpacing=10
[ExeTuner]
UseExeTuner=1
ExeTunerPath=C:\gethd\channelw.exe -v -f 2

For the graph I use the NVIDIA TS info parser between the capture device and the SGraphRecorder dump.. the ouput of the dump I made it Dump.ts... Sage will automatically encode as mpg.

If you do not have the NVIDIA decoders installed and no info parser... you can try to leave it out. But make sure the tuning delay is set. I found that with the info parser it performs better on my system.

Is your channel surfing flawless now?

I tried using the same graph as you but still had problems switching channels (~2 of 5 channel changes lead to blanks). I'm using Motorola DCH3416. I had to bump the TuningDelay to be 7000 ( 7 seconds) in order to get it to work more reliably -- ie: it would be really annoynig to find out my recordings didn't work because of this.

However, it does create a suboptimal lag for if you're watching/channel surfing and it forces you to wait up to 7 seconds for channel change... Is there a better way to handle this so we don't have to wait so long?

nyplayer · #**1882** 11-10-2009, 03:27 AM

I totally gave up on capturing through fire-wire not worth the headache too many corrupted files. For now I just dusted off my old Hauppauge PVR USB2 and capture the SD.

Brent · #**1883** 11-12-2009, 03:48 PM

Help

A little background. I was using firewire for channel changing (not for actual capture) with my HD-PVR on a Windows XP install for a long time successfully. Then I decided to install Windows 7 - a fresh install and then re-installed SageTV with all of the old sagetv settings and folders restored back into the Windows 7 install. I have the HD-PVR, Windows 7, UAC disabled, and the SA 4250HDC cable box.

Following these instructions I happily re-set up firewire channel changing:

1. Downloaded & installed ExeMultiTuner plugin put it in my <SageTV install path>\Common folder on the server PC
2. Re-installed same drivers I was using with my XP install - the ones found here STB Firewire Drivers for Windows Vista/XP/MCE
and downloaded & installed the firest.msi from here: Timmmoore's site. All files were put in C:/STBFirewire directory
3. I rebooted the PC
4. I ran a command prompt and from the directory where the channel.exe and channelw.exe files are I typed "channel -f -a0 2 60" and like clockwork the channel on the cable box changed. Good so far right???
5. Installed the EXEMultiTunerPlugin directory with the exemultituner.reg file and the exemultitunerplugin.dll file in the common directory.
6. copied the stubdevice.ir into the exemultitunerplugin directory, renamed it to 2.ir (the device number of the panel for me is 2) and changed the 2.ir contents to be "2 38000 400 3" and saved it
7. Registry setting was changed to now say this:
c:\STBFirewire\channelw.exe -f -a0 %DEVICE% %CHANNEL%
8. Started up SageTV (in service mode as always) and added the HD-PVR as a tuner selecting EXEMultiTuner Plugin as the channel changer. Had to go back to select "2" later as it didn't do that for me.

The problem is, it won't change channels in SageTV no matter how many times I go through the instructions. Is there some step I'm missing? Is there something particular to Windows 7 I'm missing?

mcaron1234 · #**1884** 11-12-2009, 03:59 PM

Quote:

Originally Posted by Brent

Help

A little background. I was using firewire for channel changing (not for actual capture) with my HD-PVR on a Windows XP install for a long time successfully. Then I decided to install Windows 7 - a fresh install and then re-installed SageTV with all of the old sagetv settings and folders restored back into the Windows 7 install. I have the HD-PVR, Windows 7, UAC disabled, and the SA 4250HDC cable box.

Following these instructions I happily re-set up firewire channel changing:

1. Downloaded & installed ExeMultiTuner plugin put it in my <SageTV install path>\Common folder on the server PC
2. Re-installed same drivers I was using with my XP install - the ones found here STB Firewire Drivers for Windows Vista/XP/MCE
and downloaded & installed the firest.msi from here: Timmmoore's site. All files were put in C:/STBFirewire directory
3. I rebooted the PC
4. I ran a command prompt and from the directory where the channel.exe and channelw.exe files are I typed "channel -f -a0 2 60" and like clockwork the channel on the cable box changed. Good so far right???
5. Installed the EXEMultiTunerPlugin directory with the exemultituner.reg file and the exemultitunerplugin.dll file in the common directory.
6. copied the stubdevice.ir into the exemultitunerplugin directory, renamed it to 2.ir (the device number of the panel for me is 2) and changed the 2.ir contents to be "2 38000 400 3" and saved it
7. Registry setting was changed to now say this:
c:\STBFirewire\channelw.exe -f -a0 %DEVICE% %CHANNEL%
8. Started up SageTV (in service mode as always) and added the HD-PVR as a tuner selecting EXEMultiTuner Plugin as the channel changer. Had to go back to select "2" later as it didn't do that for me.

The problem is, it won't change channels in SageTV no matter how many times I go through the instructions. Is there some step I'm missing? Is there something particular to Windows 7 I'm missing?

Did you go into sage.properties and change the line similar to the one below:

From:

Quote:

mc/encoders/1642691032/3/0/device_name= StubDevice

To:

Quote:

mc/encoders/1642691032/3/0/device_name=2

As instructed in meinmaui's fire wire channel change instructions found here?

Hope this helps,

Matt

Brent · #**1885** 11-12-2009, 04:04 PM

Quote:

Originally Posted by mcaron1234

Did you go into sage.properties and change the line similar to the one below:

From:

To:

As instructed in meinmaui's fire wire channel change instructions found here?

Hope this helps,

Matt

I checked it and it was already changed to 2

Quote:

device_name=2

- I think this is done automatically now when you select the "2" in the input setup

reggie14 · #**1886** 11-12-2009, 04:14 PM

Brent-

Have you tried babgvant's FWChannelProxy? The setup is pretty easy and maybe it will just work.

Brent · #**1887** 11-12-2009, 04:18 PM

Quote:

Originally Posted by reggie14

Brent-

Have you tried babgvant's FWChannelProxy? The setup is pretty easy and maybe it will just work.

I did. Unfortunately that didn't work either. My fwchannelproxy log had this to say:

Code:

DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
CanMacroTune
MacroTune 2
LoadLibrary 114229248
-f 2 2
HR = 1
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
CanMacroTune
MacroTune 2
LoadLibrary 130613248
-f 2 2
HR = 1
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
CanMacroTune
MacroTune 7
LoadLibrary 26607616
-f 2 7
HR = 1
CanMacroTune
MacroTune 6
LoadLibrary 26607616
-f 2 6
HR = 1
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH
DLL_PROCESS_ATTACH

JerryB · #**1888** 11-12-2009, 04:22 PM

Quote:

Originally Posted by Brent

7. Registry setting was changed to now say this:
c:\STBFirewire\channelw.exe -f -a0 %DEVICE% %CHANNEL%

Is there some step I'm missing? Is there something particular to Windows 7 I'm missing?

I don't know if it is something particular to Win 7 but I ended up hard coding the device number into the registry setting

C:\Firewire\channelw.exe -f -a0 2 %CHANNEL%

and it's working for me.

Brent · #**1889** 11-12-2009, 04:30 PM

Quote:

Originally Posted by JerryB

I don't know if it is something particular to Win 7 but I ended up hard coding the device number into the registry setting

C:\Firewire\channelw.exe -f -a0 2 %CHANNEL%

and it's working for me.

I've tried it with the 2 instead of the %DEVICE% in the registry and it doesn't seem to make a difference.

Brent · #**1890** 11-12-2009, 04:35 PM

It's strange that I can change channels with that command using channel.exe in the command prompt, but not within SageTV using channelw.exe I'm sure I'm missing something - just pulling my hair out trying to figure out what...

JerryB · #**1891** 11-12-2009, 05:51 PM

Just for debugging purposes, have you tried changing channels while running SageTV in non-Service mode?

gplasky · #**1892** 11-13-2009, 05:31 AM

Quote:

Originally Posted by Brent

Help

The problem is, it won't change channels in SageTV no matter how many times I go through the instructions. Is there some step I'm missing? Is there something particular to Windows 7 I'm missing?

64 bit or 32 bit Windows 7? AKAIK there are no 64 bit firewire drivers.

Gerry

Brent · #**1893** 11-13-2009, 07:54 AM

32 bit Windows 7. Keep in mind I can change channels via firewire using the command prompt - just not via SageTV

evilpenguin · #**1894** 11-18-2009, 03:44 PM

Hey All,

I just finished a successfully install of Firewire recording on Win7 (32-bit only, 64-bit WILL NOT WORK) so I thought i'd share my steps...

1) Reverted to Win7 Firewire Legacy Drivers as per nyplayers advice.
2) Downloaded these STB drivers
3) Plugged in STB Firewire into computer and pointed it the drivers I downloaded in step #2.

NOTE: If you want to record over firewire, continue using these instructions. If all you want to do is change channels, jump to step #4 in this post.

4) Followed these instructions *very carefully* - Its got all of the download links you need.
5) Worked on the first try!

-EP

kmp14 · #**1895** 11-18-2009, 04:17 PM

Quote:

Originally Posted by evilpenguin

Hey All,

I just finished a successfully install of Firewire recording on Win7 (32-bit) so I thought i'd share my steps...

1) Reverted to Win7 Firewire Legacy Drivers as per nyplayers advice.
2) Downloaded these STB drivers
3) Plugged in STB Firewire into computer and pointed it the drivers I downloaded in step #2.
4) Followed these instructions *very carefully* - Its got all of the download links you need.
5) Worked on the first try!

-EP

EP,

I got everything working too, except that about 20% of the recordings would not play. It was random. The resulting files looked like the right size but were not playable. I gave up. Hopefully you don't have the same problem.

reggie14 · #**1896** 11-18-2009, 11:24 PM

Quote:

Originally Posted by kmp14

I got everything working too, except that about 20% of the recordings would not play. It was random. The resulting files looked like the right size but were not playable. I gave up. Hopefully you don't have the same problem.

I'm just using WinXP x32, but my experiences might be relevant:

Were you trying to play them on a software client (or on the server itself)? To get things to reliably play back on anything besides the HD extenders, I had to modify the recording graph by adding Sage's tssplitter so it would record to a program stream instead of a transport stream.

nyplayer · #**1897** 11-19-2009, 12:35 AM

Quote:

Originally Posted by reggie14

I'm just using WinXP x32, but my experiences might be relevant:

Were you trying to play them on a software client (or on the server itself)? To get things to reliably play back on anything besides the HD extenders, I had to modify the recording graph by adding Sage's tssplitter so it would record to a program stream instead of a transport stream.

Reggie,

Would you be able to post a screen shot of your graph?

evilpenguin · #**1898** 11-19-2009, 01:07 AM

Quote:

Originally Posted by nyplayer

Reggie,

Would you be able to post a screen shot of your graph?

I'm curious how you did that too, i've never been able to find a combination of filters to make Transport Stream -> Program Stream work reliably.

kmp14 · #**1899** 11-19-2009, 07:00 AM

Quote:

Originally Posted by reggie14

I'm just using WinXP x32, but my experiences might be relevant:

Were you trying to play them on a software client (or on the server itself)? To get things to reliably play back on anything besides the HD extenders, I had to modify the recording graph by adding Sage's tssplitter so it would record to a program stream instead of a transport stream.

The bad recordings would not play anywhere. Hd200, PC, etc. Further investigation revealed that the files were simply not valid MPEG files. Not sure what they were.

reggie14 · #**1900** 11-19-2009, 10:31 AM

Quote:

Originally Posted by nyplayer

Reggie,

Would you be able to post a screen shot of your graph?

Sure, I can try to remember to do that later today when I'm home. In the meantime, here's a link the a post by Qian (donkey) that basically told me how to do it.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)