Network Recorder Thanks and a Question

[mikeh49]

First, thanks Martin for an absolutely solid program. I have been using it relentlessly this summer to record from the cable box via Sage GraphRecorder and firewire. Not a single problem. In the year it has been out, I think I have had only one problem recording, and I think that was trashy stream from the cableco. So, a big two thumbs up. This is a great way to record HD from the cable box if you have firewire, are willing to stay with 32 bit Windows, and your cableco does not flag everything as do not copy. In addition to Network Recorder and Sage Graph Recorder, the timmoore firewire drivers are rock solid.

Now, the question. If you recall several months ago, I asked about live TV problem on a "remote" system where the second rolling buffer file could not be written, thus stalling live TV. This is where a second box on the network running NPVR and Network Recorder is accessing SageGraphRecorder on a remote box. If I set Rolling File to false in the network recorder config.xml, there seems to be no problem. Any thoughts? Is there a significant drawback to not using the rolling file? When I researched this earlier, there was a difference in the file ownership between live TV on the main box and the remote box. I can provide the details if that would help.

Also, FWIW, I have poor skipping on either live TV or in progress recordings on the remote system; seems similar to what others have reported. Not a show stopper at the moment, though.

[mvallevand]

I'm glad it's working for you, it's a shame more NextPVR users haven't reported on trying firewire recording, it is a good choice where it works. I wish my cableco had a few more 5C free channel. It's not just a 64bit thing anymore, it's getting harder to buy motherboards with built-in firewire.

The setting to use the rolling file basically just passes a special filename to the graph which TSWriter uses to break live tv into chunks. AFAIK it adds zero value to live tv in NextPVR and is more trouble thank it is worth. Since you are using the NextPVR TSWriter.ax on the remote machine don't forget to update it when new versions come out.

When you are recording from a remote PC and streaming to a client that is a double network hop, that might be why you are having problems. I doubt it is a Network Recorder issue.

Martin

[Karyudo]

[I]t's a shame more NextPVR users haven't reported on trying firewire recording, it is a good choice where it works. I wish my cableco had a few more 5C free channel. It's not just a 64bit thing anymore, it's getting harder to buy motherboards with built-in firewire.

I know this is an old-ish thread, Martin, but I've just discovered NPVR this week, and I think I've got pretty much everything I need to try Network Recorder: I've got 32-bit Windows 7, a pair of Motorola DCT-6200 cable boxes (on Shaw in Vancouver) with 1394 out, and NPVR running on an aging motherboard with onboard 1394 ports.

Think you could give me the quick rundown on how best to set up Network Recorder with this equipment? I am unfamiliar with Sage, and although my brother recorded stuff from his DCT-6208 (first-gen HD PVR) using the timmoore drivers somehow, I never did. So I'd appreciate a bit of a boost to get me over the first hump in the learning curve...

[mvallevand]

Ultimately Network Recorder depends on the Timmmoore drives so if they don't work for you standalone you won't have much luck. You should first find out what firewire channels are available 5C in your area. Here on Rogers in Ottawa, there isn't much of note. The digitalhome.ca forums would be a good place to start.

Also the quality of 1394 chipset can make a big difference too, if you get bad quality with lots of pixelization you might need a better chipset. I found even the cable made a difference especially trying HD.

Martin

[mikeh49]

Here's some how to:

Original timmmoore page on setting up drivers and channel changin:

http://home.comcast.net/~timmmoore/firewire/readme.htm

Updated info from exdeus with better .inf file for installer and lots of good info:

http://home.comcast.net/~exdeus/stbfirewire/

You can go into the diagnostics on your stb to check the 5C status of each channel.

For Win7, you have to downgrade to the legacy firewire driver in device manager for your firewire device (search for win7 legacy firewire for more info) prior to installed the timmmoore drivers. You also may need to reboot the stb (unplug) to get it to be recognized. The capdvhs program is a quick way to check if the firewire input is working. Neat little program, too bad there is no command line interface.

I have used this system on two computers, one with a firewire pci card and one with internal firewire, and both worked fine. Don't know what chipset they are. Cable from monoprice worked great.

For channel changing, I'd recommend the sagechanger.exe which is an enhancement of timmmoore's channel.exe. The advantage of sagechanger is that it can turn on the stb if it is off. I've been using for a month or so, and works fine. You can google to find it on the sage forums. You'll need a batch file called from sagegraphrecorder to change channels as sagegraphrecorder cannot handle as many command line parameters as needed.

You'll need graphedit to create a capture graph. Three filters: firewire capture device (panel or tuner, can't remember) -> NPVR TSMon -> NPVR file writer

The npvr wiki should get you going with Martin's network recorder.

[epelic]

Martin and Mike were a great help in my recent setup of firewire recording with NextPVR. I'm running Windows XP so the driver issue / challange did not exist for me. You might want to review the following for some additional background, ideas, etc.:

http://forums.nextpvr.com/showthread.php...Experience