Hi from #ffmpeg-devel <Daemon404> im not doing any fixes today though, im beat. ... <Daemon404> michaelni, if im not around mail me them, or putthem on github or something
i found another regression, thought "here" is a good "something" that way more people can search for and fix regressions heres one regression: ./ffmpeg -i Broadway-5.1-48khz-448kbit.ac3 -t 10 out.wav ./ffmpeg-codecpar-2016-0331-23 -i Broadway-5.1-48khz-448kbit.ac3 -t 10 out-codecpar.wav ls -alF out-codecpar.wav out.wav -rw-r----- 1 michael michael 6681702 Apr 1 01:38 out-codecpar.wav -rw-r----- 1 michael michael 5760102 Apr 1 01:38 out.wav the codecpar case also fills the screen with Non-monotonous DTS in output stream 0:0; previous: 75264, current: 66048; changing to 75264. This may result in incorrect timestamps in the output file warnings not yet rebased onto origin tree used for the testing: https://github.com/dwbuiten/FFmpeg/tree/codecpar PS: i suggest to wait at least 48h with no new regressions being found before this is pushed, its a exceptionally large merge -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Never trust a computer, one day, it may think you are the virus. -- Compn
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
