Hi! It turned out that the "-1696" PTS offset is caused by dvbcut itself, but does not propagate into the output files. The messages were just a consequence of an incompatibility with another "broken PTS" hack that Sven added earlier: Since PTS values wrap around at 2^32 in some streams (instead of 2^33 as it should be), dvbcut ignores the broken MSB and re-generates a correct one. Unfortunately, my patch checked the uncorrected timestamp. With the new revision 4, the messages should be gone (unless something is wrong with the stream).
-- Michael "Tired" Riepe <[EMAIL PROTECTED]> X-Tired: Each morning I get up I die a little ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ DVBCUT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dvbcut-user
