On Sun, Apr 04, 2004 at 10:17:21AM -0700, Steven M. Schultz wrote: > > On Sat, 3 Apr 2004, Richard Ellis wrote: > > > is sparse (actually, sparse is a bit too generous) and that the mode > > of operation for mpeg cutting is slightly non-intuitive. However, on > > Yes indeed - actually I would go further than that and say it's > very non-intuitive.
Agreed, I was trying to be kind. Once you "get" the mode, it does work, but it's very non-typical. > > a few test cut's I've made with GOPchop and LVE, it seems that > > LVE outputs a much more correct mpeg stream than GOPchop does. I > > had > > Alas, LVE chokes and dies very ungracefully when presented with HD > content. It seems to scan the file and build the index ok (but > part way thru that the main program window goes away and the a > blank preview window grows to 16:9) after the scan of the file > completes the the program segfaults. Definitely unhappy with 16:9 > 1920x1080i data. Ok, on that one I can't possibly say. The most I've presented it with is 720x480 interlaced standard NTSC from the Hauppage card. No HD content, and it does work with that. > So, it's back to the drawing board - maybe trial and error with > "dd" will work ;) Will mpgtx clip it at all? Mpgtx lets you specify time and size offsets to "clip" at. If the mpeg stream is normal otherwise beyond being 1920/1080i data, maybe mpgtx will slice and dice it enough to be useful. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Mjpeg-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mjpeg-users
