On Wed, 29 Dec 2004, Anne Wilson wrote: > My longest chapter was left to process overnight. This morning I found: > > INFO: [mplex] rough-guess multiplexed stream data rate : 7889048 > INFO: [mplex] target data-rate specified : 10080000 > INFO: [mplex] Setting specified specified data rate: 10080000 > INFO: [mplex] Run-in Sectors = 89 Video delay = 13019 Audio delay = 16619 > INFO: [mplex] New sequence commences... > INFO: [mplex] Audio c0: buf= 4096 frame=000000 sector=00000000 > INFO: [mplex] Video e0: buf= 237568 frame=000000 sector=00000000 > **ERROR: [mplex] Failed write: /Public/Rome/ostia.mpg > > /Public/Rome/ostia.mpg exists, and plays satisfactorily in Totem or Kaffeine. > It exists but is it complete? One possibility is that the filesystem ran out of space at the very end of the multiplexing run.
> It lacks the last 10 seconds, or so, though. Is it safe to accept this file > as usable, or will there be some vital end-information missing? It will be missing the 'end of stream' info which _may_ cause a problem with DVD authoring programs - but then again it might work and the video will be a little short. If you have the elementary streams (the .m2v and .mp2) files still around you could try running mplex again after checking that there's enough space, etc. The other thing you can try, which will be a little faster and use no extra disc space, is to output to /dev/null mplex -f 8 -o /dev/null video.m2v audio.mp2 and see if the "Failed write:" still happens. Cheers, Steven Schultz ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users