Thread Installationsproblem mit FFmpeg::Command auf Win7 (18 answers)
Opened by bianca at 2017-08-29 19:19

Linuxer
 2017-09-08 18:56
#187381 #187381
User since
2006-01-27
3870 Artikel
HausmeisterIn

user image
Ich würde es mal mit der ffmpeg-Option -report versuchen?

Damit bräuchte es dann keinen Redirect des STDERR-Kanals mehr.

Siehe http://ffmpeg.org/ffmpeg.html#toc-Generic-options

""
-report

Dump full command line and console output to a file named program-YYYYMMDD-HHMMSS.log in the current directory. This file can be useful for bug reports. It also implies -loglevel verbose.

Setting the environment variable FFREPORT to any value has the same effect. If the value is a ’:’-separated key=value sequence, these options will affect the report; option values must be escaped if they contain special characters or the options delimiter ’:’ (see the “Quoting and escaping” section in the ffmpeg-utils manual).

The following options are recognized:

file

set the file name to use for the report; %p is expanded to the name of the program, %t is expanded to a timestamp, %% is expanded to a plain %

level

set the log verbosity level using a numerical value (see -loglevel).

For example, to output a report to a file named ffreport.log using a log level of 32 (alias for log level info):

FFREPORT=file=ffreport.log:level=32 ffmpeg -i input output

Errors in parsing the environment variable are not fatal, and will not appear in the report.
meine Beiträge: I.d.R. alle Angaben ohne Gewähr und auf Linux abgestimmt!
Die Sprache heisst Perl, nicht PERL. - Bitte Crossposts als solche kenntlich machen!

View full thread Installationsproblem mit FFmpeg::Command auf Win7