Kodi Community Forum

Full Version: tvheadend - 30s timecode offset?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Folks -

I've wittered about this before, but it's time to raise it again simply because it's buggering up my workflow when trimming adverts/leading credits/etc. I use tvheadend 3.2 (3.2.18~g40a8920~oneiric) on XBMCBuntu (Oneiric/11.10), although I've had this problem on various other variations. Recording is from multiple USB DVB-S2/T/T2 tuners to mkv containers on a local SSD.

Simply put, everything has about a 30s timecode offset. Open a file in XBMC and immediately call up the properties, and it'll tell you that it's about 30s in as soon as it starts.

Some other media players see the same - VLC before early 2.x releases did, but not later ones; mkvmerge sees the same; MPC doesn't.

So here's the irritation: I play the file in VLC (on XP or Win7) to see where the preamble stops and the programme proper starts. I make a note of that timecode, plus the equivalent at the other end of the broadcast. I feed these into mkvmerge GUI as cut points, and I promptly slice the file in the wrong place. Creating EDL files for XBMC has the same effect - you have to manually tune the values to the right place with a binary split around "approximately 30s from where you think you should be", which is an utter waste of my life.

The only ways around it I've found is:

1. To use an old release of VLC to find the cut points since that sees the offset in the same way as mkvmerge. However, VLC 1.11.x crashes more often than I care to mention, and I'd rather only have a single version installed anyway.

2. To run the file through Handbrake before cutting. This corrects a multitude of errors, included the timecode offset, so the file now tells everyone that it genuinely begins at 00:00:00. However, I'd rather re-encode as a last resort (it's not strcitly necessary on an H.264 HD broadcast anyway, as well as taking forever) - and, if I do have to do it, I'd rather do it last, since it maintains file integrity (chopping up an H.264 stream can play havoc with seek times).

Any thoughts, anyone? Does anyone else see this, does anyone have a different editing workflow that gets around it?
No-one else? Everyone else has tvheadend files that always start at 00:00:00 for every application?

I've just watched Comskip get the ad breaks horribly wrong, partly because of this, so I can't even manually skip over the commercials and save all that cutting and re-processing.

I'm taking this personally, tvheadend hates me. Does the season of goodwill extend to code, do you think? :-(
happens with vlc 2.0.5 for me
Thank you - that at least makes me believe that it's not *just* me!

The next question is what to do about it, though...
I am now using comskip that cbxbiker61 has posted and have the same issue...

The edl file seems correct but when playing the file it is constantly 30 off.

All,

This has now been reported as a bug and I believe I understand the basic problem. But I need to get John to take a look as I think he's best placed to look into it.

Adam