Rovi Divx 10 HEVC

[Selur]

@vhelp:

so actualy, divx265 does give progress report through piping.

using

mencoder -ovc raw -noskip -field-dominance -1 -vf scale,format=i420,yadif=0,scale,format=i420 -forcedsubsonly -nosub -nosound -mc 0 -lavdopts threads=2 -really-quiet -of rawvideo -o - -dvd-device "E:\TestDVD" dvd://1 | DivX265 -i - -s 720x576 -br 1500 -fps 25 -o "E:\Output\test_13_01_53_9310_01.265"

I see no progress indication at all
-> how did you pipe your content to DivX265 ??

[Selur]

@vhelp: can't get any progress if I feed DivX265 through pipe -> what am I missing?

[vhelp]

i see you using multiple piping commands for multiple console apps. i've never used such an sonario.

mencoder -ovc raw -noskip -field-dominance -1 -vf scale,format=i420,yadif=0,scale,format=i420 -forcedsubsonly -nosub -nosound -mc 0 -lavdopts threads=2 -really-quiet -of rawvideo -o - -dvd-device "E:\TestDVD" dvd://1 | DivX265 -i - -s 720x576 -br 1500 -fps 25 -o "E:\Output\test_13_01_53_9310_01.265"

the software behind the piping that i am using is pascal based, not c/c++ and is a dosconsole window app that accepts most command line apps and pipes the output to a memo control. as the the app is runningand sending progress info, the memo is populated. at first try, divx265 doesn't appear to be reporting anything, but after a certain number of threshold or frames, it releases what it has ( cache? ) and a set number of progress is sent out.

if i may ask, what happens when you enter dosx265 -h in hybrid ?

it should result in something similar, below.

DivX 265/HEVC Encoder (version 1.0.0.341) (c) 2000-2013 DivX, LLC (a subsidiary of Rovi Corporation).

Usage: divx265 -i <infile> -o <outfile> -br <bitrate> -s <w>x<h>  (for raw infile)
   or: divx265 -i <infile> -o <outfile> -br <bitrate>             (for .avs|.avi infile)
   or: divx265 -h  (for help)

Options:
  General:
       -h, --help Help
       -v, --verbose Verbose mode, detailed messages output.
       -q, --quiet Quiet mode, no messages output.

  Input/Output:
       -i, --input <Input file> Required. (For raw stream from stdin, use -i -)
       -o, --output <Output file> Required.
       -s, --size <height>x<width> Required for raw files. Frame dimensions (e.g. 1920x1080)
       -br, --bitrate <bitrate> Required. Target bitrate in kbps
       -I, --interval <interval> Keyframe interval. 1 to 5 seconds. Default=5
       -n, --frames <number> Maximum number of frames to encode
       -fps, --framerate Frame rate Frame rate. Default=24 Hz (raw files) or derived from file (.avs/.avi)
         Valid frame rates:
           60 Hz
           60000/1001 Hz
           50 Hz
           30 Hz
           30000/1001 Hz
           25 Hz
           24 Hz
           24000/1001 Hz

if you don't see the above in hybrid's output (assuming you have that featured in a TAB or something) then i would say it is your "piping" method for hybrid. if this is the case, then you might want to investigate other piping methods in your apps language. let me know about the above output though.,.just curious..thanks.

[Selur]

Okay, you are not doing a direct pipe but you cache headers&frames, so I guess you feed DivX265 not only the raw stream, but you feed it also some header infos.

About the output: I get exactly the output you posted.

[vhelp]

actually, this is the exact param i used when i was testing it.

divx265.exe --input "c:\dgavc.avs" --framerate 24 -br 2000 -o g:\video.divx265.hm10

[Selur]

... but there you are not piping the input you are feeding it with a file. :/

[vhelp]

oh, now i get it. sorry for the confusion, i missunderstood.

[Selur]

Yes, seems like you mistook feeding DivX265 through a pipe with grabbing DivX265s output.

[DarrellS]

I tried the newest DivX265.exe command line encoder and it looks like the clear winner in HEVC encoding. It has a width limit of 4096 for 4k encodes. I encoded a 3200x1800 animation at 7 fps. This is compared to Multicoreware's x265.exe encoder at 2 fps for the same input file. I'll try a 4k encode and report back on my results.

Here is the new DivX265.exe encoder...

DivX HEVC Encoder v1.2.24 (3-14-2014) http://download.divx.com/hevc/DivX265_1.2.24.exe

-aqo <1-5> Algorithm quality optimized for: 1:fastest speed 2:fast 3:balanced(*) 4:higher quality 5:highest quality.

Command line argument for Virtualdub external encoder...

-i - -s %(width)x%(height) -br 4000 -aqo 1 -o "%(tempvideofile)"

[deadrats]

I tried the newest DivX265.exe command line encoder and it looks like the clear winner in HEVC encoding.

of course it's the clear winner, did anyone ever really believe that the clown crew at MCW would be able to compete in any meaningful way.

[DarrellS]

I didn't think that DivX Labs would upgrade their command line encoder. They never upgraded their H264 command line encoder. I never was able to get it to work with Virtualdub's external encoder.

[racer-x]

I tried the newest DivX265.exe command line encoder and it looks like the clear winner in HEVC encoding. It has a width limit of 4096 for 4k encodes. I encoded a 3200x1800 animation at 7 fps. This is compared to Multicoreware's x265.exe encoder at 2 fps for the same input file. I'll try a 4k encode and report back on my results.

Here is the new DivX265.exe encoder...

DivX HEVC Encoder v1.2.24 (3-14-2014) http://download.divx.com/hevc/DivX265_1.2.24.exe

-aqo <1-5> Algorithm quality optimized for: 1:fastest speed 2:fast 3:balanced(*) 4:higher quality 5:highest quality.

Command line argument for Virtualdub external encoder...

-i - -s %(width)x%(height) -br 4000 -aqo 1 -o "%(tempvideofile)"

Tried it out and the speed was very fast for hevc, however the quality sux real bad. Changing bitrate to -br 8000 or -aqo 3 has litle effect on quality. Do you know the command line argument for CRF using Virtualdub External Encoder? Maybe that might help.

[DarrellS]

Here is the usage text for the updated divx265 encoder...

Microsoft Windows XP [Version 6.1.7600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Tools\DivX265>DivX265.exe -h
DivX 265/HEVC Encoder (version 1.2.0.24) (c) 2000-2014 DivX, LLC (a subsidiary of Rovi Corporation).

Usage: DivX265 -i <infile> -o <outfile> -br <bitrate> -s <w>x<h> (for raw infile)
or: DivX265 -i <infile> -o <outfile> -br <bitrate> (for .avs|.avi infile)
or: DivX265 -h (for help)

Options:
Encoder:
-br, --bitrate <bitrate> Target bitrate in kbps
-qp <1-51> constant quantizer. Note: creates potential non-compliant DivX HEVC Profile streams
-I, --interval <interval> Keyframe interval. 1 to 5 seconds. Default=5
-F, --fixed-gop-length Disable scene change detection, results in fixed gop length.
-aqo <1-5> Algorithm quality optimized for: 1:fastest speed 2:fast 3:balanced(*) 4:higher quality 5:highest quality.
--no-wpp Disable WPP

General:
-h, --help Help
-v, --verbose Verbose mode, detailed messages output.
-q, --quiet Quiet mode, no messages output.

Input/Output:
-i, --input <Input file> Required. (For raw stream from stdin, use -i -)
-o, --output <Output file> Required.
-s, --size <height>x<width> Required for raw files. Frame dimensions (e.g. 1920x1080)
-n, --frames <number> Maximum number of frames to encode
--start <number> First frame to encode
-fps, --framerate Frame rate Frame rate. Default=24 Hz (raw files) or derived from file (.avs/.avi)
Valid frame rates:
60 Hz
60000/1001 Hz
50 Hz
30 Hz
30000/1001 Hz
25 Hz
24 Hz
24000/1001 Hz

DivX265 -i - -o <outfile> -br <bitrate> -s <w>x<h>

Virtualdub command argument...

-i - -s %(width)x%(height) -br 4000 -aqo 1 -o "%(tempvideofile)"


Try...

-i - -s %(width)x%(height) -qp 18 -aqo 1 -o "%(tempvideofile)"

For some reason, the multiplexor fails so I have to save as hevc and mux manually with mkvmerge 6.8.0.

[racer-x]

Try...

-i - -s %(width)x%(height) -qp 18 -aqo 1 -o "%(tempvideofile)"

For some reason, the multiplexor fails so I have to save as hevc and mux manually with mkvmerge 6.8.0.

That produced much better quality, but my 1080p export was 33 Mb/s, almost as much as original 4k mp4 file. Setting -qp 26 results in 8617 Kb/s, but quality really suffers badly....

I get much better results exporting x265 out of AviUtl, although speed is only about 1.5 fps versus 6.5 fps using Virtualdub/DiviX265. Then again no sense exporting poor quality.

[DarrellS]

I've spent the last three days trying to figure out why the newer version (1.2.0.24) of DivX265.exe encoder refused to encode anything over DivX 4K 2560 x 1920 using either -aqo, qp or -br. It seemed to me that -aqo 1 was just too fast to make the encoder try to encode picture resolutions that high (with only 4GB of memory) so I lowered it to aqo 2 and it encoded all the 4K resolutions with no problem and at speeds almost as high as x264.exe at resolutions that high.

Here is the command line that I used to encode upper 4K resolution files with Virtualdub External Encoder...

-i - -s %(width)x%(height) -qp 24 -aqo 2 -o "%(tempvideofile)" -v

(-v is to show all messages)

DivX265 (version 1.2.0.24)
[i] VideoEnc: DivX 265/HEVC Encoder (version 1.2.0.24)
[i] VideoEnc: Profile: DivX 4K
[i] VideoEnc: Encoding
[i] VideoEnc: Format: ................. Main@5.0, 4096x2160 1:1
[i] VideoEnc: Number of coded frames .. 375
[i] VideoEnc: Total encoding time ..... 62219 ms
[i] VideoEnc: Pure encoding time ...... 45602 ms
[i] VideoEnc: Average time per frame .. 165.917 ms
[i] VideoEnc: Average speed achieved .. 6.0 fps
[i] VideoEnc: Average CPU load ........ 93.8 % (4 pictures, 8 threads)
[i] VideoEnc: Peak memory usage ....... 1296.570 Mb
[i] VideoEnc: Average bitrate ......... 317.37 kbit/sec @ 24.000 Hz (Const QP)

...or from a script...

DivX265.exe -i input.avi -qp 24 -aqo 2 -o output.hevc -v
pause

(for some reason, the script ran faster than through Virtualdub External Encoder)

C:\Tools\DivX265>DivX265.exe -i input.avi -qp 24 -aqo 2 -o output.hevc -v
Size: ................... 4096 x 2160
Framerate: .............. 240000/10000 (24.000)
FourCC: ................. BGR3
Frame count:............. 375
Profile: ................ DivX 4K
Encoding...
0:00:54 Frame 375 of 375 encoded @ 6.88 fps
Format: ................. Main@5.0, 4096x2160 1:1
Number of coded frames .. 375
Average speed achieved .. 6.9 fps
Average CPU load ........ 92.1 % (4 pictures, 8 threads)
Peak memory usage ....... 1310.945 Mb
Average bitrate ......... 367.03 kbit/sec @ 24.000 Hz (Const QP)