That's great news Carl. Thank you for the fantastic support.
-j
On Mon, May 4, 2015 at 2:00 PM, Carl Eugen Hoyos ceho...@ag.or.at wrote:
Jeremy genericinbox at gmail.com writes:
Cropdetect seems to be broken since 2.6.
The issue (cropdetect did not work correctly
for 8 bit) should be
Jeremy genericinbox at gmail.com writes:
Cropdetect seems to be broken since 2.6.
The issue (cropdetect did not work correctly
for 8 bit) should be fixed, thank you for
the report!
Carl Eugen
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
Jeremy genericinbox at gmail.com writes:
./ffmpeg -i
/Users/jeremylk/Dev/Ruby/workspace/video_encoder_app/Breathing_5s.mov
-vf cropdetect=24:16:0 dummy.mov
Workaround for the time being is to use:
-vf format=yuv422p,cropdetect=24:16:0
(or format=yuv420p)
Note that if I understand your
Your workaround works, thank you. I'll keep that in mind.
For future questions: Please understand that you
should (and must) only test current FFmpeg git
head, nothing else is relevant here.
Understood, will do.
On Sun, May 3, 2015 at 4:30 AM, Carl Eugen Hoyos ceho...@ag.or.at wrote:
Jeremy
Sorry, I misread the original request. The command being used is :
./ffmpeg -i
/Users/jeremylk/Dev/Ruby/workspace/video_encoder_app/Breathing_5s.mov -vf
cropdetect=24:16:0 dummy.mov
On Sat, May 2, 2015 at 3:29 PM, Jeremy genericin...@gmail.com wrote:
Sure thing. Below is the output from 2.5.6
Sure thing. Below is the output from 2.5.6 (the last working version)
followed by the output for the same command / same file using 2.6, when the
behavior for cropdetect changed. Notice how the values for the 2.6 output
show no crop detected. This is consistent in everything post-2.6.
Everything
Jeremy genericinbox at gmail.com writes:
I can provide output data to support this
Please only provide your failing command line
including complete, uncut console output if
you want the issue fixed.
Carl Eugen
___
ffmpeg-user mailing list
Hi all,
Cropdetect seems to be broken since 2.6. I noticed this the other day with
a new build for my encoding app, which pulled 2.6.2. Cropdetect no longer
worked with 24:16:0 variables. Pushing the threshold variable up to 65
created different values, but they were negative an incorrect.
2.5.6
