Home > Ffmpeg Error > Ffmpeg Fix Timestamps
Ffmpeg Fix Timestamps
I have fought this battle and sort of won. The ffmpeg version is 0.5.2-bluehat and the full output is below -FFmpeg version 0.5.2-bluehat, Copyright © 2000-2009 Fabrice Bellard, et al. Visit the Trac open source project athttp://trac.edgewall.org/ [FFmpeg-user] "error, non monotone timestamps" Rhodri James rhodri at kynesim.co.uk Tue Oct 30 20:25:11 CET 2012 Previous message: [FFmpeg-user] "error, non monotone timestamps" Next Where are your bug reports? > So, the solution is to explicitly code both streams, not using "copy". check over here
This is an open source project, anyone can submit patches. comment:8 Changed 5 years ago by cehoyos Component changed from FFmpeg to avformat Keywords mkv av_interleaved_write_frame added; monotone timestamp removed Resolution set to fixed Status changed from open to closed The I solved my problem, but unfortunately my skills are not enough to supply a bug-fix. Upon every move in the scenevarious blocks appear around the borders of moving and not moving areas.Anyone got a clue how to handle this?RegardsAndre MtTracer 2008-08-05 17:17:18 UTC PermalinkRaw Message Post
Ffmpeg Fix Timestamps
For reference the ffmpeg command used is -ffmpeg -i PATH_TO_CURRENT_FILE.flv -acodec libfaac -ab 96k -ac 2 -vcodec libx264 -vpre hq -vpre ipod320 -threads 0 -crf 22 PATH_TO_NEW_FILE.mp4ThanksBen Back to top Report This will be a huge shock. *whispers* (You could ignore the error and continue coding with the sync params from before the error and it would work just fine! The primary one is to use '-vsync 1'. Carl Eugen _______________________________________________ ffmpeg-user mailing list [hidden email] http://ffmpeg.org/mailman/listinfo/ffmpeg-user « Return to FFmpeg-users | 1 view|%1 views Loading...
The error message is wrong. I just googled the Internets for "groidism," and the only thing I'm coming up with is "Groid: Slang, slightly demeaning term for black guy. This is not a solution at all. it's probably unattractive, but you can always manually map them, which will just extend your commandline even more though.
We have now changed to FMS and, although the files are now perfectly synced when in .flv format, we are still getting the error when converting to mp4. Ffmpeg Non-monotonous Dts In Output Stream Therefore the source file plays fine indifferent media players including those using ffmpeg and CoreAVC libraries.My first try was to emulate the timestamps with linearly ascending values. The complete output from ffmpeg is: FFmpeg version SVN-r25837, Copyright (c) 2000-2010 the FFmpeg developers built on Nov 28 2010 13:59:29 with gcc 4.4.3 configuration: --enable-gpl --enable-version3 --enable-nonfree --enable-postproc --enable-libfaac --enable-libopencore-amrnb https://ffmpeg.org/pipermail/ffmpeg-user/2012-October/010796.html Watching H.264 (and other) videos using CUDA/D...
Fixed it again. Download in other formats: Comma-delimited Text Tab-delimited Text RSS Feed Powered by Trac 1.0.1 By Edgewall Software. perhaps open a new thread for it. [FFmpeg-user] "error, non monotone timestamps" Zarathustra leelacade at centurylink.net Tue May 28 00:43:32 CEST 2013 Previous message: [FFmpeg-user] Macroblock artifact detection.
Ffmpeg Non-monotonous Dts In Output Stream
I had googled the term, but since most of the first page linked to this thread I gave up. I wondered if it was related to "grody", which I haven't heard in over a decade, but apparently not. > It's called testing. Ffmpeg Fix Timestamps this the first mention of them. The problem appears to be damaged input files.
What on earth is a "non monotone timestamp" or for that matter a "monotone timestamp" and how do I fix this problem? http://bashprofile.net/ffmpeg-error/ffmpeg-error-code-5.html There is really scant error handling for cases where parameters *aren't* specified. Thank you for the quick and exhaustive answer!I tried to reorder the frames by their pts values to achieve the correctpresentation order. Thanks for explaining that neologism, that's always a good idea on a mailing list where many of the most frequent contributors don't have English as their first language.
- Lazy groidism is > rampant.
- This "follow our inane rules or you don't exist" is what "extreme groidism" means.
- Wouldn't you?
- Upon request I can provide some streams with multiple audio that are not convertable because of this.
- I tried to do a normal encode: ffmpeg -i 'Infile.mov' -vcodec copy -acodec libfaac -ab 320k -ar 48000 -ac 2 'Outfile.mp4' Which lead to my "error, non monotone timestamps" problem. _______________________________________________
What what? The error message is wrong. There is > really scant error handling for cases where parameters *aren't* > specified. > Thousands waste hours every day because of it and all you care is that > your http://bashprofile.net/ffmpeg-error/ffmpeg-error-code-1.html This worksfine, if passed pts values are in presentation order and aligned perfectly (aconstraint which the video stream I used didn't fulfill).Post by Luca AbeniIn the original email, you wrote that
Previous message: [FFmpeg-user] Macroblock artifact detection. I worked on that crap from version 0.1 in 1981 until the late '80s and what I'm seeing in the Linux community now feels like we're going exactly the same way. This is how MS works.
If you don't want to put the work in to give us a bit of context, that's fine, but then you can hardly expect the rest of us to
So, the solution is to explicitly code both streams, not using "copy". Previous message: [FFmpeg-user] Tons of error-messages when decoding h.264 Next message: [FFmpeg-user] "error, non monotone timestamps" Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Originally Posted by blazerqb11 Remuxing with MKVtools seems to have solved the problem, it's the right tool Originally Posted by blazerqb11 however I am still having playback issues still? That's the essence of "groidism".
That was me. it's probably unattractive, but you can always manually map them, which will just extend your commandline even more though. As I understood thereordering of packets AND frames is done completely by libav itself.That's why frames decoded by avcodec_decode_video() may not come fromthe packet you used for decoding. have a peek at these guys As it stands the error handler closes the file and the caller says, "Oh, can't write to file" and exits.
This "follow our inane rules or you don't > exist" is what "extreme groidism" means. Yeah, it's different. If you're going to throw everything up in the air and quit, then explain why.