http://sourceforge.net/projects/project-x
I've found that re-syncing and bad sections of the captured file are handled very well by this utility. I typically run it against every capture as a step in preparing a DVD to record. Note: I had to modify the source to run it without GUI even though it's parms say it should. quick CL usage: Note: CL doesn't load the GUI components, except with switch [-gui] <without options> ...starts the GUI switches and inputfiles can be in any order options: [-ini <path + inifile>] ..use that specified iniFile instead of the standard [-dvx1] ..create a .d2v ProjectFile on demux [-dvx2] ..create a .d2v ProjectFile + .ac3.wav (RIFF WAVE Header) [-dvx3] ..create a .d2v ProjectFile + .mpa.wav (RIFF WAVE Header) [-dvx4] ..create a .d2v ProjectFile + .ac3.wav + mpa.wav (RIFF WAVE Header) [-out <path>] ..use that specified directory for output [-name <filename>] ..use that specified filename for output [-cut <file>] ..use that text based file as cutpoint list [-chp <file>] ..use that text based file as chapterpoint list [-id <tokens>] ..use only these (P)IDs, separated by comma "," [-gui] ..display the GUI using all given CLI options [-log] ..write the normal logfile [-saveini] ..save changes made bei CLI in active .ini [-split <xxx>] ..split output at xxx MB [-demux, -tom2p, -topva, -tovdr, -tots, -filter] ..action types On Sun, 2007-03-04 at 00:48 -0500, [EMAIL PROTECTED] wrote: > I have a large number of ivtv-generated files, some of which were > corrupted by a MythTV bug that's finally been fixed. I'd like to > quickly identify which ones so they can be scheduled for rerecording. > > The bug caused Myth to stop emptying ivtv buffers for 5-25 seconds, > leading to visible glitches in the recordings (sudden jumps and > typical blocky mpeg artifacts). Is there some way to detect this > in the file? > > I tried pulling down ivtv 0.10.1 and compiling -just- the util > directory (since I'm still running kernel 2.6.12), then trying > ps-analyzer foo.mpg | grep -2 Unknown > as advised in some traffic to ivtv-devel around Jan 30. > > Unfortunately, a file with a known glitch in it didn't produce any > output except "end of file". > > Any suggestions? Presumably there must be -some- tool that can notice > that keyframes aren't where they're supposed to be, or something like > that, at some point in the stream. > > Thanks! > > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users -- Richard Hendershot <[EMAIL PROTECTED]>
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
