STB Firewire (IEEE-1394) Support

[Bohica]

DFA -- all looks fine in debug. When changing channels -- when it does not work -- it looks in debug like it should work.

[Bohica]

Originally Posted by wad06

I keep getting the same error:

"There was a playback error in Playback. Details: sage.playbackexception: There was a problem accessing the filesystem for playback."

I can't seem to get past this.

I'm using Sage 2.2.8.
XP SP2
Moto Comcast Box

Everything works fine in VLC. I, however, can't play the dump file in windows media player (only VLC and theatertek). In WM10, it says it's a song and doesn't play it.

Any help would be appreciated.

Wad

This is all a codec problem. It must work in windows media player before it will work in sage. In my doc -- in the notes section, i list a hotfix for media player. I dont know if this will help or not. Try installing QT alternative -- google "QT Alternative" and see if that helps. Make sure of course you have installed WMP 10, and directx 9.0c. Edit... also at one point during troubleshooting -- I ran across a really cool WMP troubleshooting tool that let you look at your directshow filters for WMP -- and which ones were listed as default. It let you remove old ones. Not sure the name of it. I was googling "HD content in windows media player" or something like that... if anyone knows that tool can you post.

[DFA]

1. That would be "Windows XP Video Decoder Checkup Utility" (MSFT)

2. Search this thread for "GetFileSize". There is some history on this and related problems when Sage machine-guns these queries. For a few that were having this problem with 2.2.8, as I recall, it was finally attributed to using the Sage Service feature. I am not aware if Sage ever provided an explanation or resolved the problem (they moved on to 3.0.x anway).

I am getting rapid GFS requests on channel change (and not running the SageService). Seems to me however, these GFS requests, rapid or otherwise, should not start coming until "videoframe/network_encoding_to_playback_delay" parameter has timed out. That is why I asked Sage to confirm function on this parameter. I am not sure how SGR app responds when queried for GFS when SGR has no info yet (or old value from previous channel yet holding in register!) and the graph has not yet even started.

DFA

[AndersNolberger]

When SGR gets a question about file size and it is still waiting for the graph to start it either responds 0 or 200 depending on which dump filter is used.

If you are using my new dump filter included with SGR the answer will be 0 until something is actually written to disk.

If some other filter is used the file size is coming from the file system and it takes a while for the file system to report a file size even thought the file has in fact started growing. Therefore SGR reports 200 to let Sage start playing. That workes ok but there will be some stutter for the first second or two.

Also I have read the new guide for using firewire STB and there it states that it is important that the initial file name given to the dump filter must be in the Sage recording folder. I don't think that is necessary. SGR change the file name before the graph is started so the initial name could be anything at all. Not that important but could help understand how SGR works.

Anders

[Bohica]

Originally Posted by AndersNolberger

Also I have read the new guide for using firewire STB and there it states that it is important that the initial file name given to the dump filter must be in the Sage recording folder. I don't think that is necessary. SGR change the file name before the graph is started so the initial name could be anything at all. Not that important but could help understand how SGR works.

Anders

Dont know if it is necessary or not either - it seemed to help in the GFS messages and in channel changing for me at one point -- so I left it in.

[Bohica]

Originally Posted by DFA

1. That would be "Windows XP Video Decoder Checkup Utility" (MSFT)

DFA

Thats the one. Thanks...

[wad06]

Thank you for all of your responses.

Well, I tried installing quick time alternative player and the hotfix recommended. I still get the same error.

Then, I tried SpaceGhost's guide (using the different/longer graph). Now, I get a picture for about three seconds and then it freezes and cpu pegs.

This happens when playing in sage, and when playing the dump file in WM10.

I hate to be a pain, but I would love to figure this out if anyone has any more suggestions.

Wad

EDIT:

Well, I just tried recording with the short graph while I was out of the house. It recorded two shows perfectly that can be played in VLC or TheaterTek. But, I still can't play them in Sage or WMP10. I used the decoder utility mentioned above, and it says NVidia is the preferred decoder. The only reason it is such a big deal is for the sake of time shifting live TV. As it is now, though, it is quite usable strictly as a DVR.

[Bohica]

... but in your dumpfile -- are you using the correct dump filter -- the one that shipped with SGR? And are you naming the file .ts? And are .ts files configured to play in sage?

[wad06]

I am only using two filters, the Tuner and the dump file that was included with SGR. The output file is .ts.

I have not configured Sage to play .ts files. I'm not sure how to do this. Maybe this is the big missing step.

Again, thanks for your replies.

Wad

[TakeFlight]

I've got this set up and working like a champ right now. It's been running for several days and I've recorded probably two dozen HD shows so far with really no problems. My question is, should the file that is created be a .TS file or .MPG? I keep reading people talking about configuring Sage to play TS files so that's why I'm curious. I followed the most recent PDF instructions, and like I said it's working great. My HD shows are recording from my Motorola STB to 1920x1080 DD5.1 MPG files (confirmed in the Information tab in TheaterTek). Is this the way it should be working or should the files be .TS files? I'm not sure I care since it's working but I'm curious.

[willgill]

This setup will crash Sony Vegas Movie Studio + DVD Platinum

Guys, just a heads up. Since you're using SageTV and semi-geeked (since you're in this thread) ,I figured there's a decent possibility that some of you may be using video editing software. Right now, Pinnacle Studio 10 has some massive stability issues so many of you may be tempted to buy the currently on-sale Sony Vegas Movie Studio + DVD Platinum (VMS). VMS+D P is normally $129 but after rebates is $39 and an incredible deal and very powerful software.

VMS+D P specifically doesn't like the Motorola AV/C and Motorola Tuner AV/C that gets installed with doing this threads proceedure.

The work-around is to temporarily disable Motoroal AV/C and Motorola Tuner AV/C before you fire up Sony Vegas Movie Studio + DVD Platinum.

If you don't your computer will hard reboot. No BSOD, no program crash... hard reboot. It took me about 10 of these hard resets before I finally diagnosed the problem. I cringed everytime my computer did that and thought I may save some of you guys some headaches.

[gtd885a]

Jeez, finally had everything working well and I get hit with 5c. Pretty much anything worth watching is 5c'd (well, when 24 starts back, I guess I'll have it at least).

It was fun while it lasted (sort of). Good luck to everyone. I dunno, maybe I'll still play with it, but more than likely I'll be looking at a "commercial" solution.

This sucks.

[gtd885a]

Originally Posted by willgill

Right now, Pinnacle Studio 10 has some massive stability issues so many of you may be tempted to buy the currently on-sale Sony Vegas Movie Studio + DVD Platinum (VMS).

LOL, guess that's why I just got Pinnacle Studio 10 free after rebate. Haven't used it yet, maybe by the time I get around to using it, they'll have some bug fixes

[heffe2001]

I'm having this same thing happening, and would prefer it to output as .TS, but it seems Sage is telling it to use .mpg. This throws SA or compskip into a endless loop. If it were saving them as .ts files, I'd have the comskip that was modded to skip on TS filesrun on those, and SA run on the other files...

[Bohica]

Originally Posted by heffe2001

I'm having this same thing happening, and would prefer it to output as .TS, but it seems Sage is telling it to use .mpg. This throws SA or compskip into a endless loop. If it were saving them as .ts files, I'd have the comskip that was modded to skip on TS filesrun on those, and SA run on the other files...

Dont understand... when you configure your graph -- just set the source as the STB and use the included dump filter with SGR and name it something.ts...

[JasonJoel]

I think his issue is that it doesn't matter what you specify on the graph, Sage ALWAYS makes the extentoin MPG, regardless if you specify something.TS or not. They really are .TS files, but they get a .MPG extention no matter what.

Rename them from .MPG to .TS and you'll see they are normal .TS files.

However, since SD and HD all all have the .MPG extention for now, there is no good way for COMSKIP or SA to distinguish.And since both types of files are not support in the same program yet, it makes the commercial detection go berzerk. He'll either have to do COMSKIP by hand for a while, or wait until Jere gets Show Analyzer to support TS files - which he is actively doing right now. Might be a few more weeks though as he is rewriting some infrastructure.

Jason

Originally Posted by Bohica

Dont understand... when you configure your graph -- just set the source as the STB and use the included dump filter with SGR and name it something.ts...

[JasonJoel]

Hear anything back yet? It's been 10 days.

Jason

Originally Posted by DFA

I have shot off a support request to Sage asking for the verification of function of the Sage "videoframe/network_encoding_to_playback_delay" parameter and/or any changes to the NE protocol for which the UNE may need updating.

The issue I am addressing revolves around STB FW LiveTV viewing and channel switching.

DFA

[heffe2001]

Originally Posted by JasonJoel

I think his issue is that it doesn't matter what you specify on the graph, Sage ALWAYS makes the extentoin MPG, regardless if you specify something.TS or not. They really are .TS files, but they get a .MPG extention no matter what.

Rename them from .MPG to .TS and you'll see they are normal .TS files.

However, since SD and HD all all have the .MPG extention for now, there is no good way for COMSKIP or SA to distinguish.And since both types of files are not support in the same program yet, it makes the commercial detection go berzerk. He'll either have to do COMSKIP by hand for a while, or wait until Jere gets Show Analyzer to support TS files - which he is actively doing right now. Might be a few more weeks though as he is rewriting some infrastructure.

Jason

That's exactly my problem, Sage auto-creates the .mpg extension. Hopefully with the next release we can force .ts extensions, then I won't have to make SA skip those recordings (what really boggles my mind is I have the HD channels set to NOT comskip, but apparently it has to read the mpg before it processes the rules, would have figured it would process the rules, THEN read the mpeg if it needs to).

[Bohica]

Oops -- I never even looked at the file extensions sage creates... I see I see...

[heffe2001]

Yeah, I racked my brains trying to figure out why it was calling everything mpg when I had told it to use .ts...

I eventually just assumed it was Sage that gave it the .mpg extension.