STB Firewire (IEEE-1394) Support

[TakeFlight]

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.Jason

I assumed this was the case. I just wanted to make sure I wasn't missing something. I verified they were indeed TS files because I renamed them to .TS and the HDTVtoMPEG2 utility recognizes them as TS files. Plus, the fact that they aren't always the same exact size for a 1 hour show means they must be the "untouched" original transport stream. It's not like I thought Sage was re-encoding them. It would be more convenient if they were TS files but I don't use the commercial skip myself so really it doesn't matter to me.

Thanks for the clarification.

[JasonJoel]

I agree that it would be nice if Anders put the option in the network encoder to dump as .TS (if he can).

The .MPG extention is confusing to many.

Jason

[AndersNolberger]

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.

Originally Posted by JasonJoel

I agree that it would be nice if Anders put the option in the network encoder to dump as .TS (if he can)

Sage sends a command to SGR about starting to record a program. It either sends a SWITCH or START command. With that command there is a parameter of what Sage expects the name of the file to be (this can be seen in the debug window).

SGR responds by searching the graph for the dump filter and setting its file name to that exact name. It then starts the graph. Therefore it does not matter what the file name for the dump filter is to begin with, it is always changed and to a file name that Sage has decided.

The dump filter is writing the actual file to disk and that file is never changed in any way by Sage. Sage only use that file for playback. If SGR would change the file name Sage would not find it and playback would never start.

Anders

[TakeFlight]

I always used to run Sage in service mode. I like running it that way because I feel it's a safer way to run it. If the interface were to crash, the service would still be running and recording shows. Ever since I set up the firewire connection to my cable box I've turned service mode off because of the known "get file size' issues.

Is there anybody running in service mode (regardless of the get file size issue) and not having any problems? I'd really like to start running in service mode again because I've had Sage crash on me twice now since I stopped using service mode. I'm not saying using service mode would make it so Sage wouldn't crash, but at least the service would still be running if the interface did crash. Apparenly there is no fix for the get file size issue, but is there anybody just using service mode anyway and not experiencing any performance issues?

[dvsing]

Yea.. it's always been a gripe of mine since SGraphRecorder came into being that I was unable to run in service mode AND watch live HDTV at the same time. I used to just stay in service mode and watch all of my HDTV after it was done recording, but as of a few weeks ago I turned off service mode and I'm just crossing my fingers that the UI doesn't crash and take down anything that's currently recording with it.

It matters less now since one can pretty much obtain any mainstream TV show online if they know where to look =) I've had to do this on more than on occasion if SageTV has a scheduling "oops".

-Dan

[TakeFlight]

Originally Posted by dvsing

Yea.. it's always been a gripe of mine since SGraphRecorder came into being that I was unable to run in service mode AND watch live HDTV at the same time. I used to just stay in service mode and watch all of my HDTV after it was done recording, but as of a few weeks ago I turned off service mode and I'm just crossing my fingers that the UI doesn't crash and take down anything that's currently recording with it.

Maybe I missed this very obvious point. Are you saying that the get file size issue is only an issue if you are trying to watch live HDTV? I assumed it was always an issue regardless of what you were actively doing. Honestly, I haven't tried running it in service mode yet. I just read here that it was an issue and turned service mode off when I was setting up firewire support. I rarely (basically never) have a reason to watch live HDTV via Sage. My main reason for setting Sage up to record HD via firewire is to archive music performances on the various late night shows, SNL and the random concert shows on PBS. I don't need to watch these live. I have a Comcast DVR in another room I can use for that. So, you are saying "other than watching live HDTV" you were able to use service mode without a problem?

[dvsing]

Yea.. in my experience the "GET_FILE_SIZE" problem only occurs when you try to watch an HDTV recording that has not yet finished (ie, delayed live). Interestingly, if for some reason the file gets divided into two segments due to a sage stop/start or whatever, you can watch the first segment even when the second segment is still recording and not get the GET_FILE_SIZE error... so, to be very specific, the problem only occurs when SGraphRecorder is recording to the same file that the UI is playing back.... and only in service mode.

-Dan

[TakeFlight]

Originally Posted by dvsing

so, to be very specific, the problem only occurs when SGraphRecorder is recording to the same file that the UI is playing back.... and only in service mode.

I'm glad I asked. This is good to know. I will give it a shot and see what happens.

[TakeFlight]

Originally Posted by TakeFlight

I'm glad I asked. This is good to know. I will give it a shot and see what happens.

OK, I just connected to my HTPC from work so I could switch it to service mode. No point in waiting until I get home. I've now got it running in service mode again and I've got the debugger window open and started a recording on an HD channel and so far so good. Just one get file size message which is what I would expect. I'm going to let this show continue recording and keep the debugger log enabled and see what happens. I'll test further when I'm at home.

[Homebuilder]

Hi, my next box to build is a client for my HD tv that has a motorola HD with firewire.

I want to record via firewire, but still use that box as a client.

Can I get a normal client license from sage and record through my client to my server?

Will my server sage "See" the network encoder for the firewire on my client?

[AndersNolberger]

How is this working with 4.1. There should be some changes in how 4.1 handles HDTV files and different sound formats.

Anders

[da_gringo]

i have 4.1.3.7, and it does not freeze up on the channel change anymore.
I havent tried service mode yet

[Bohica]

Originally Posted by Homebuilder

Hi, my next box to build is a client for my HD tv that has a motorola HD with firewire.

I want to record via firewire, but still use that box as a client.

Can I get a normal client license from sage and record through my client to my server?

Will my server sage "See" the network encoder for the firewire on my client?

If I understand correctly -- the answer is yes. The client license will just affect Sage Client... no license needed for SageGraphRecorder -- it just acts as a network encoder in this configuration...

[heffe2001]

Still getting a ton of GET_FILE_SIZE messages when watching HD (sage NOT in service mode) on a Client PC. Averages about 40ish per second, but I watch without any problems on the client...

Just wanted to post that after watching about 30-45 minutes, I started getting stuttering bad, and totally lost video/audio after trying to skip back 10 seconds. Locks with a spinning sage logo. BUT I've had that problem with another machine on the network since the 4.0 upgrade too, but not on HD content.

[WellThen]

Hi All,

New to Sage, and just got Firewire recording working. Just want to clarify, in addition to recording, should I be able to watch live TV via Firewire in HD? I'm getting an error when I try this, and just wanted to confirm whetherthis should work.

Thanks!

[JasonJoel]

Ok, firewire recording has been working pretty well for me.

Only weird thing is that sometimes the resulting files won't play in anything other than a PC. They won't play on my Buffalo Link Theater, my XBOX 360, etc. But MOST of the time they will.

I am GUESSING it is errors in the TS file itself.

So, here are some questions to you smart people:
1. Is there a decent program to fix errors in TS files?
2. Would it be more reliable if I did not just Go 6200 -> TS file, and instead did it the old way and go through the more complex graph dumping to PS file?
3. Are there any good TS -> MPEG convertors that will work with these 'abnormal' TS files? The couple programs I tried didn't seem to want to process any of the Sage TS files (even the ones that play correctly on all my devices).

Thanks for any thoughts/suggestions you have!

Jason

[Kirby]

Hi folks,

Spent the better part of today getting my Sage HTPc setup, as well as the FW connection to my DCT6200. I'm using the latest and greatest SageTV right now, 4.1.3.67, and everything seems to be working as far as channel changes over firewire, recordings, etc. However I am unable to watch a show that is recording, or live TV from the firewire connection. I do get the GFS errors, example:

START Motorola DCT-6200 1394|787|2272342303660|E:\SageTV\VerticalLimit-127283-1.mpg|Great 10:05:51 PM
Running: C:\GetHD\channelw.exe -v 2 787
GET_FILE_SIZE E:\SageTV\VerticalLimit-127283-1.mpg 10:05:53 PM
GET_FILE_SIZE E:\SageTV\VerticalLimit-127283-1.mpg 10:05:53 PM
GET_FILE_SIZE E:\SageTV\VerticalLimit-127283-1.mpg 10:05:53 PM
NOOP 10:05:53 PM
NOOP 10:05:53 PM
GET_FILE_SIZE E:\SageTV\VerticalLimit-127283-1.mpg 10:05:53 PM
GET_FILE_SIZE E:\SageTV\VerticalLimit-127283-1.mpg 10:05:54 PM
GET_FILE_SIZE E:\SageTV\VerticalLimit-127283-1.mpg 10:05:54 PM
GET_FILE_SIZE E:\SageTV\VerticalLimit-127283-1.mpg 10:05:54 PM
GET_FILE_SIZE E:\SageTV\VerticalLimit-127283-1.mpg 10:05:54 PM
GET_FILE_SIZE E:\SageTV\VerticalLimit-127283-1.mpg 10:05:54 PM
VERSION 10:07:15 PM
NOOP 10:07:15 PM
NOOP 10:07:15 PM

As soon as I select a current recording, or watch live TV on an HD channel, I get a debug similar to the one above, and the SageTV app crashes. The above event occured when I went into the program guide from the main menu, and tried to "watch" a particular channel (787- FOX HD). I am not running as a service. Is this the expected behavior right now, or shouldnt my SageTV app be crashing?

Also, I dont know if it means anything or not, but I noticed on the DCT-6200's front panel, when I tried to "watch" this live program above, the channel changed very slowly, took about 3 seconds for the 3 digits to be entered. However, I then restarted and viewed the main guide, and set the program to record, and the channel change display on the DCT-6200 took about 1/2 second.

I also just noticed that the file created by my recording above, never stopped being written to. The graph I am using for SGR is just two filters, my AV/C Tuner Device output into the SBDARecorderDump (output to .TS file).

I've also noticed now, that after I add all the lines to sage.properties, and run my device setup, it lists the DCT6200 as false for functioning and for live TV. When I close down Sage again, and re-edit the file, all my added lines are gone. How can I stop that? Do I need to also edit the sage.properties.default file, or do something with the autoback file somehow? Figure I missed something in one of the two PDF howto's, but I cant find it...

[Bohica]

ok -- couple of things. Dont know why you cant watch live. Can you watch a previously recorded HD program? It has been my experience that crashes with HD where Sage errors out and closes is almost always codec related. Try setting different audio codecs for mpeg2 playback in the settings. Sage Mpeg Default, or try other codecs like AC3, or for me -- I reinstalled WinDVD and used the intervideo decoders. I say reinstall because sage 4 corrupted my previous encoders from WinDVD -- and everytime I tried to use them it crashed sage. Could also be video codecs... so play there as well...

As for the last question, if you are not using the tuner for live playback at the time -- it will say it is functioning for live as false. Does not mean it is not working...

[Kirby]

I can play recorded TS files, as well as WMV and XviD encodings that I encoded, however, none of those originated from a recording made by SageTV. Not sure if that matters, they were made using MyHD or r5000 devices.

As for the DCT tuner right now, if I select a HD channel from the program guide, and "Watch Now", it tells me "ERROR (-10): No encoders can tune the selected station".

The DCT is listed in the Source setup page, its details look correct, and I have deleted it, and re-added, with no change in the above error. Viewing the sage.properties file, all the extra lines of code I manually added "mmc/encoders" stuff, is gone. I have tried to delete the DCT from the video sources page, closed sagetv app, verified its thread was closed, re-modified sage.props file, and re-added the device per the instructions, and same results.

While just checking everything I did notice that the "mmc/encoders" lines from the 2 PDF howto's are very different. I was using the lines from the 2nd howto, I will try it with the 1st and see what happens.

*edit* changing the mmc/encoders lines to those in the first PDF file didnt help either. In fact, when I did that, and added the device, selected 1394 input, it then asked me for an audio input on the device. I guess tomorrow will be a good day for me to reinstall sage from scratch.

Could an update to the Java VM from Sun have caused issues? I know at some point in the middle of setting up everything I accepted a Java update. Also, I have been using ac3filter for ac3 audio, as it seemed to be the only thing to make my encodings playback correctly. Any known issues with ac3filter and Sage?

[jimwhite]

"The DCT is listed in the Source setup page, its details look correct, and I have deleted it, and re-added, with no change in the above error. Viewing the sage.properties file, all the extra lines of code I manually added "mmc/encoders" stuff, is gone."

sounds like you're running the server mode and not shutting down the service...