I'm having similar difficulties, but I did find something of a workaround.
First of all, the linked post above suggests:
"vlc INPUT --file-logging --logfile file_log.txt"
but aren't the rules on Windows that you must use the "--option=value" syntax, not "--option value" ?
Anyway, I tried all variations and the only way I can get a log file is to use the following combo:
""C:\Program Files\VideoLAN\VLC\vlc" P1000098.mov --extraintf=logger --verbose=2 ..."
This causes a log file named vlc-log.txt to be written in the current directory, as well as a log screen to be displayed during the processing. I have not found a way to give it a different name (not that I care).
What is more interesting/concerning, though, is that this file (vlc-log-txt) does not contain ALL the info shown on the screen. Even with --verbose=2 (or 3), I get a lot of 'main debug: ...' lines, etc, but what I DON'T get, and what is relevant to my current troubleshooting exercise, are entries such as this:
Code: Select all
[00000477] avcodec encoder debug: libavcodec already initialized
[00000477] avcodec encoder warning: libfaac doesn't support this output format!
(libfaac@0187EDA0)
[00000477] avcodec encoder error: cannot open encoder
[00000477] main encoder debug: TIMER module_Need() : 70.000 ms - Total 70.000 ms
/ 1 intvls (Avg 70.000 ms)
[00000403] stream_out_transcode stream out error: cannot find audio encoder (mod
ule:any fourcc:mp4a)
(I copied these from the screen log)