Development of Sagetv v9

[EnterNoEscape]

Originally Posted by Fuzzy

even if run as a new segment, comskip is supposed to deal with segmented files just fine.

I get that. I was thinking we were adding data to the start of the file (not just a segment), but after I thought about it, that would be absurd. I would prefer to keep whole files when possible instead of creating segments even though it could be more storage efficient if recordings could share segments.

[lewispm]

Could you just treat it like a commercial and create a file that has a start/stop location for the padding which happens to be located in another file?

Can the playback play one file for say 3 mins of padding then seamlessly switch to the actual recording by just reading a text file with the filename and times?

Also, regarding segments, when a recording is interrupted, it creates a -0 and a -1 (iirc) file and the playback seamlessly plays both. Why not just have the "shared" padding time be a segment that is appended or prepended to both recordings. It sounds like just a symlink after the recording is complete. Or maybe that is what y'all have already discussed.

[tmiranda]

Originally Posted by Fuzzy

even if run as a new segment, comskip is supposed to deal with segmented files just fine.

To clarify: comskip.exe only deals with one file at a time. The STV and any supporting code must stitch together multiple files into one "recording".

[trallyus]

If someone needs motivation to update the tuners problem with SageTV , then they really should create a kickstarter project as well as I can't program worth crap but I can help fund those that can and it would be worth having my tuners working full force instead of only 1/2 of them due to the way sage tv sees non supported tuners.