Changed ffmpeg verbosity semantics #14582
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
tf.contrib.ffmpeg.decode_*
andtf.contrib.ffmpeg.encode_*
functions are extremely verbose and make it nearly impossible to see other printed messages.Corresponding methods for image such as
tf.image.decode_png
produce no output under normal conditions, and it would be nice for audio/video methods to align with this.FFmpeg on valid MP3 file with
-loglevel info
and without-hide_banner
(old semantics)FFmpeg on valid MP3 file with
-loglevel error
and with-hide_banner
(new semantics)FFmpeg on text file (invalid) with
-loglevel error
and with-hide_banner
(new semantics)$ ffmpeg -loglevel error -nostats -i in.txt -acodec pcm_s16le -ar 44100 out.wav -hide_banner Output file #0 does not contain any stream