(2012-05-07 13:57)rdoac Wrote: Wanted to report back, we watched a recording last night using Mythbox git, which used cmyth for playback. The commercial skips were firing in the wrong place and jumping 7 mins. I am going to apply the patch and see if it's better. (No Commercial Skip would be better). Commercial skip fired if we clicked play or play+skip.
I'd need a log and more detail about what the wrong place means. Note that there are some advanced EDL settings that can be configured in XBMC to help clean up the sometimes dubious commercial breaks that are detected by mythcommflag (depending on the algorithm configured). I use Logo Detection only for DVB-T recordings in NZ and found that to be the most reliable for the content broadcast over here. I strongly recommend testing the different options if you have the patience. Curiously the "All available methods" algorithm was the worst performing option based on the testing I did.
For more detail see http://wiki.xbmc.org/index.php?title=Use...#.3Cedl.3E
7 minutes sounds curiously like twice the typical 3:30 commercial breaks we get over here so it's possible the frame rate for content was being guessed at half the rate when it perhaps shouldn't be. There are some heuristics applied to determine what frame rate to use to obtain the time markers from the frame markers stored in mythbackend. If the frame rate was guessed incorrectly then the positioning would be off by a factor of 2 as well. Would need a log file to see if the heuristics need adjusting.
You can find the heuristics and the log messages that should appear in the log file in the ReadEditDecisionLists() method at https://github.com/xbmc/xbmc/blob/master...er/Edl.cpp