Hi, Am Samstag, 12. August 2006 18:45 schrieb Michael Riepe: > Hi! > > Quick analysis: > > The stream is *not* damaged (at least not the part I got). But dvbcut is > acting strange anyway, in particular if both start and stop frames are > I-frames. If the (excluded) stop frame is not an I-frame, the error goes > away. Might be an off-by-one error somewhere.
I can not confirm this... but found another strange thing... When I'm cutting from 0(I) to 476(B) the errors start at: Muxer problem: 00:00:14.910/86 > 00:00:14.910/47 (dts:00:00:14.929/61) s->getbuffree():214870 up to the end of the stream. The same happens if I stop at 472 which is an I-Frame! But it's different when I'm starting at a B frame (5)... in that case it even happens from the very beginning of the stream ... independent from the stop frame. Of course, nothing at all happens if both start and stop frames lie before minute 14.9! ciao Ralph -- ------------------------------------------------------ Ralph Glasstetter Rueppurrer Str. 62 0721 / 359166 76137 Karlsruhe [EMAIL PROTECTED] ------------------------------------------------------ ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ DVBCUT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dvbcut-user
