Hi, Andrew Jeffery wrote: > The first was with mplayer and it's time detection problems in > MPEG-TS streams - commercial detection wasn't working as mplayer > seemed to randomly get the starting time position in the video wrong > (i.e. hit play on a video and mplayer reckoned it was 13 hours or so > in - comfortably missing all the edl time values)
Mplayer (and Xine) have the big problem that they can not seek correctly on MPEG-TS files. Unlike AVI a TS has no Index. Xine for example checks the bitrate at the beginning and calculates everything based on that bitrate. As a result while watching a recording in Freevo 2.0 the elapsed time information on my LCD goes up one second every two seconds. Mplayer does not have that bug, but seeking 10 seconds can result in a 30 second seek or even more. THE ONLY way for correct TS seeking is looking at the timestamp in the TS frame. That is how kaa.metadata detects the length of the file: read the first and the last timestamp. Maybe the whole commercial detection based on mplayer and edl values is wrong. Hans-Juergen (Cc) started porting noad (the VDR commercial detection) to something more generic. IMHO the best encoding server would use gstreamer and a gstreamer commercial detection. Maybe Zaheer (also Cc) knows if something like this is already work in progress. > an hour long episode of Kitchen Nightmares USA was supposedly 2973 > minutes. What does mminfo say? Dischi -- Work is the greatest thing in the world, so save some for tomorrow. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel