2011-06-22, 21:37
So if it's a clock problem, do you mean graphic card refresh rate clock problem or internal software clock ?
TheSwissKnife Wrote:Those timecodes are complete rubbish even in remux set - way off and any software that tries to sync to them is going to have problems. What are you remuxing with? I measured 240ms out at worst case (rather than a swing of say 70ms to and thro with a constant average) - the 240ms is I think enough for xbmc to give up even with drop/dupe etc and just immediately adjust the clock, thus screwing the video sync.
My advice is get the latest version of mkvmerge, mkvextract, mkvextractgui etc.
Extract using GUI all tracks. Then drag them into mkvmerge gui (mmg) and set the video stream to forced 24/1001 fps. I am very sure you will get proper timecodes then...and I would think that should solve most of your problems.
BTW all I did was insert the timecodes into excel in column A (without the header line) and in column B use =(ROW()-1)*10.66666666666-A1 pasted all the way down (ie formula into B1 then copy and paste down column). Column B show the fluctation then from zero. You can find the max using max(B1:B11968). Now overall the timestamps seem not to be obviously drifting on a long running average so xbmc could try to improve, at least by not shifting the clock so readily on a large swing in timestamp - at least averaging over a second even when large delta but that is something to discuss with bobo1on1.
=(ROW()-1)*10.66666666666-A1