Saving logs from cmdline encoding

[salehin]

I'm using .bat file to encode. Here is one .bat file content:
x264.exe --pass 1 --bitrate 4849 --stats ".stats" --level 4.1 --ref 5 --mixed-refs --no-fast-pskip --bframes 6 --b-adapt 2 --b-pyramid --weightb --filter -3:-3 --subme 9 --trellis 1 --psy-rd 0.9:0 --partitions p8x8,b8x8,i4x4,i8x8 --8x8dct --merange 32 --threads auto --thread-input --aq-strength 0.5 --progress --no-dct-decimate --output NUL "BBCHD_720p.avs"

x264.exe --pass 2 --bitrate 4849 --stats ".stats" --level 4.1 --ref 5 --mixed-refs --no-fast-pskip --bframes 6 --b-adapt 2 --b-pyramid --weightb --filter -3:-3 --subme 9 --trellis 1 --psy-rd 0.9:0 --partitions p8x8,b8x8,i4x4,i8x8 --8x8dct --merange 32 --threads auto --thread-input --aq-strength 0.5 --progress --no-dct-decimate --output "BBCHD_720p.mkv" "BBCHD_720p.avs"

I was wondering if it's possible to save the entire encode log in a text file. Then I can see and fine tune x264 settings later

Cheers :)

[Dark Shikari]

command 2> file.txt

[smok3]

command 2> file.txt
wouldn't that produce a 'catastrophically' long file.txt?

x264 feature request:
--cutelog mini.txt
and/or
--log full.txt

(p.s. if mini.txt or full.txt exist then add stuff by default, not overwrite)

p.s.2. my typical log is only;
x264 0.65.1016M dbc5ef0
2passQuicktime (2pass) --bitrate 700 --filter "-1,-1"
Command line:
wavegain -s -y -l -f G:\zabava3dec\zabava3dec.log G:\zabava3dec\zabava3dec_vdub.wav
encoding took
13 minutes, 0 seconds

[salehin]

(Sorry dark, but this will sound very basic to you and others) So I just add in file.txt in the end like this

x264.exe --pass 1 --bitrate 4849 --stats ".stats" --level 4.1 --ref 5 --mixed-refs --no-fast-pskip --bframes 6 --b-adapt 2 --b-pyramid --weightb --filter -3:-3 --subme 9 --trellis 1 --psy-rd 0.9:0 --partitions p8x8,b8x8,i4x4,i8x8 --8x8dct --merange 32 --threads auto --thread-input --aq-strength 0.5 --progress --no-dct-decimate --output NUL "BBCHD_720p.avs"

x264.exe --pass 2 --bitrate 4849 --stats ".stats" --level 4.1 --ref 5 --mixed-refs --no-fast-pskip --bframes 6 --b-adapt 2 --b-pyramid --weightb --filter -3:-3 --subme 9 --trellis 1 --psy-rd 0.9:0 --partitions p8x8,b8x8,i4x4,i8x8 --8x8dct --merange 32 --threads auto --thread-input --aq-strength 0.5 --progress --no-dct-decimate --output "BBCHD_720p.mkv" "BBCHD_720p.avs"

encode_log.txt

[smok3]

salein, no, you would run your batch like:

mybatch.bat 2> log.txt

[akupenguin]

wouldn't that produce a 'catastrophically' long file.txt?
18 lines is catastrophically long? I know notepad chokes on files on the order of a MB, but a KB is ridiculous.

--cutelog mini.txt
What exactly would you cut from those 18 lines to get a mini log, and why should I add more modes than --quiet/normal/--verbose?

If you just don't want the --progress report in the logfile, then I could be convinced to put --progress on stderr and everything else on stdout, so they can be redirected independently. Dealing directly with files is just ugly.
If you want --verbose output on the terminal and normal summary in the logfile (or vice versa)... sorry, write a text filter or maintain your own patch, that's not going into my x264.

[smok3]

ok then :)

then I could be convinced to put --progress on stderr and everything else on stdout

that would be great (imho).