DivX 10 HEVC/H265 implementation

[birdie]

I have quite an intense video clip (MJPEG, 640x480@30fps) of a stormy weather with the furious rain and wind, and even at the highest possible bitrate for this resolution (2850Kbit/sec) the resulting video in HEVC still misses a lot of details. Maybe my source isn't exactly compressible, who knows?

What's your experience with DivX HEVC implementation?

[fumoffu]

IMO HEVC (or at least divx and Strongene encoders) aren't doing too good in SD resolutions. My theory is this has something to do with how deblocking and/or SAO works, but I'm definitely not an expert. Generally HEVC has much softer look than h264 which looks nice in 720p or more but SD clips has to be up-scaled almost 3 times it's size on FullHD monitor and that soft look turns into way too much blur.

[burfadel]

HEVC is new that is why. Has the standard even been finalised yet? HEVC now is probably where h264 was in say, 2005. It still has a long, long way to go in terms of improvement. No doubt in a couple of years time it will look better than h264 even at low bitrates, because it should!

[phate89]

I tried to encode a piece of the video they use to show the encoder (if they use it they think it works well with that video right?).
I took the 4k tears of steel, downscaled to full hd and encoded in h264 with my usual setting ( --level 4.1 --preset placebo --pass 2 --bitrate 1700 --deblock -2:-1 --bframes 4 --ref 4 --vbv-bufsize 50000 --vbv-maxrate 50000 --qcomp 0.8 --merange 32 --subme 10 --psy-rd 1.0:0.15) and h265 divx with the (only) profile available. I keep the bitrate low intentionally.
h265 speed was slightly better than x264 placebo, but in quality x264 is better
h264 1700 kbps http://www.putlocker.com/file/4A0AEA1BD09D3818
h265 1700 kbps http://www.putlocker.com/file/387BC8E4DAD298B5
h264 3000 kbps http://www.putlocker.com/file/5B300A3220091974
h265 3000 kbps http://www.putlocker.com/file/4758CAE945380DBD

[JEEB]

I have quite an intense video clip (MJPEG, 640x480@30fps) of a stormy weather with the furious rain and wind, and even at the highest possible bitrate for this resolution (2850Kbit/sec) the resulting video in HEVC still misses a lot of details. Maybe my source isn't exactly compressible, who knows?

What's your experience with DivX HEVC implementation?

Just FYI, the DivX implementation was already brought up here (http://forum.doom9.org/showthread.php?p=1642883#post1642883). And yes, the results haven't been too mind-blowing yet. That said, I wonder how much more information, settings and other things can be picked out of the actual MainConcept encoder included (mc_enc_hevc.dll) that is used in the background. After all, it does export some functions and I wouldn't be surprised if with some code you would be able to encode without the DivX application itself in the middle :) .

HEVC is new that is why. Has the standard even been finalised yet? HEVC now is probably where h264 was in say, 2005.
Yes, the HEVC standard has been finalized. ISO/IEC is just taking it slow for whatever reason and thus they still don't have the spec ratified on their side, but ITU-T has already ratified it in April as H.265 (spec (http://www.itu.int/rec/T-REC-H.265-201304-I)). Bit stream was more or less frozen in January. And yes, both sides are ratifying the exact same document ^^; .

And it's more like 2003. Or possibly 2004, since the implementations are maturing somewhat faster than with AVC/H.264 :) .

[Doobie]

I downloaded the Divx HVEC moments after it was available for download. First, kudos to Divx for getting this out!

The HEVC results look good, and tighter than anything I've seen before (I haven't tried Google's newest video codec, yet).

Anything else I have to say is about the Divx encoder. Does it not have variable bitrate encoding? It won't retain anamorphic structure of the source. It doesn't decode AC3. And, it was so slow.

[fumoffu]

Does it not have variable bitrate encoding?

Well, I'm pretty sure it uses ABR which is somewhat variable but I guess you meant something like CRF in x264 or CQP? and unless there is some undocumented option hidden in dll which I doubt then no.
Yes 2-pass would be nice, hopefully with fast first pass ;)

[xooyoozoo]

Encoded some raw test seqs and a short clip from the Paperman short in Divx HEVC 1080p. Target ABR bitrate was set to lowest allowed, 1600 kbps, to show Divx in the best possible light. QP is flat within a frame, which means no AQ and no psy features, so it would definitely not compare well at more luxurious bitrates.

x264 was then bitrate matched to Divx's actual ABR output. Psy-rd was manually lowered to 0.4:0 (same as tune-animation) to acknowledge that it's a liability in bitrate starved situations: x264 --preset veryslow -I 120 --psy-rd 0.4:0 -B $b --pass $n

The outputs were cut and recomposed to form side-by-side comparisons and were reencoded for transparency (CRF 10). I also included the demuxed Divx bitstreams and the x264 mkvs. You can find everything here (https://drive.google.com/folderview?id=0BzAA-H5x8NKTNU9mel8xQl8yQjQ&usp=sharing).

If you don't care to download the clips,

Cactus: Divx clear winner
DucksLegs: Tossup. Divx's ratecontrol ruins the middle half of the clip
Paperman: Tossup
VenueVu: x264 slight winner

Overall, I can't shake the feeling that this is mostly moving sideways or, at best, marginally forward while still losing out on backwards compatibility. If there was a clear indication of Divx 10 being only a rough demonstration (a la x265), I'd understand and be much less disappointed. I think that, as is, this release is reminiscent of the early AVC encoders: capable but forgettable.

[turbojet]

It's a big improvement over Divx's avc encoder but don't expect them to be competitive as far as quality goes. Their hevc encoder blurs a lot, I'd take x264 over it on all those samples except maybe VenueVu which is blurry to begin with and x264 has more noise. x264 is probably closer to the source, if that's the case it's a sweep.

[dukey]

Give it some time, it's pretty early days with regards to HEVC implementations.

[Kurtnoise]

There is a command line tool available now (http://labs.divx.com/node/127927)...

[fumoffu]

Very nice of them, definitely step in the right direction. Unfortunately, for now command line barely adds anything useful :/
The difference from GUI version is you can set frame rate, keyframe interval and number of frames to encode.
Was hoping for some quality/speed advanced options or different encoding mode...

[Sagittaire]

available command line are:

target_cc max_layers max_dpb_depth max_buffering min_buffering bit_depth_luma bit_depth_chroma device_idx device_mode src_width src_height calc_stat calc_hash calc_quality cpu_opt num_threads gop_max_len gop_min_len adapt_b idr_period fixed_i_position use_scd max_reordering HEVC Layer %04d write_pic_par_set profile level width height log2_max_poc sei_msg_flags snr_infer_split log2_min_cu_size log2_max_cu_size log2_min_tu_size log2_max_tu_size max_tu_depth_inter max_tu_depth_intra max_cu_depth_inter max_cu_depth_intra constrained_ipred intra_partitioning strong_intra_smoothing use_me subpel_mode num_ref_frames_l0_p num_ref_frames_l0_b num_ref_frames_l1 search_range out_of_pic_mvs max_num_merge_cand deblock_mode beta_offset tc_offset sao_luma sao_chroma rc_mode quant_i quant_p quant_b quant_min quant_max avr_br hss_rate cpb_size use_nal_hrd use_vcl_hrd cpb_fullness cpb_fullness_trg cpb_fullness_units cb_offset cr_offset sign_data_hide transform_skip lambda_I lambda_P lambda_B flags sar_idc pic_ar_x pic_ar_y sar_width sar_height overscan_appr_flag time_scale num_units_in_tick fixed_frame_rate frame_based_timing bit_rate_scale cpb_size_scale annexb stream_type write_au_delimiters write_seq_end_code write_single_sei write_vid_par_set write_seq_par_set write_id_stamp

certainely with .ini or .cfg file. Anyway I don't find way to use it. Perhaps desactived in this exe file.

[Selur]

+ command line version does not have any progress indication if input comes in via pipe :/

[Marchand]

Using DivX HEVC Encoder

The DivX HEVC encoder [BETA] is a command line tool that is now capable of encoding HEVC content.

Download the binaries here. http://labs.divx.com/node/127927

Usage

DivX H.265/HEVC Encoder

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)

Example Usage

from a raw file (yuv/raw, assumes IYUV/I420 colorspace):

C:\DivX265.exe -i content_in.yuv -o content_out.hevc -br 3000 -s 1280x720

Piping from stdin through another command line tool:

C:\ffmpeg.exe -i content_in.avi -s 1280x720 -f rawvideo -pix_fmt yuv420p - | DivX265.exe -s 1280x720 -br 4000 -i - -o content_out_50frames.hevc

from an AVS file (make sure AVISynth is installed):

DivX265.exe -i content_in.avs - o content_out.hevc -br 3000/li>

from an AVI file:

DivX265.exe -i content_in.avi - o content_out.hevc -br 3000/li>

Options

http://i.imgur.com/S7KXRNF.png

Notes

For more information on bitrate, keyframe intervals, etc., please refer to the DivX HEVC Video Profiles (DRAFT, May 2013).
http://labs.divx.com/node/127903

The default colorspace for encode is assumed to be IYUV or I420

Tested and some did not work? See the image below:

http://i.imgur.com/zRIgzQY.jpg

DOWNLOAD VIDEO TEST: https://shared.com/c7ct6nhm2u

[Selur]

Does anyone know if there will be updated versions of DivX265 or was it a one time thing?

[birdie]

Try to e-mail DivX developers.

[Kurtnoise]

There is a benchmark (http://labs.divx.com/node/127935) in the DivX labs regarding their hevc encoder/decoder from the 10.1 beta bundle since few days...


btw, is there a way to use their hevc decoder outside their player ?

[Selur]

Does the 10.1 beta still come with a command line encoder?

[Kurtnoise]

I don't think so...

[SeeMoreDigital]

At 79.5MB their 'DivX 10.1 4K Beta' application is pretty big...

[Kurtnoise]

A new beta has been released concerning their command line tool... (http://labs.divx.com/node/127927)


What's new:

Improved encoding efficiency
New options:
-aqo [1-4] specifies one of the 4 encoding modes: 1 - fastest, 2 - balanced (default) 3 - higher quality (experimental) 4- highest quality (experimental)
-F turns off scene change detection, results in fixed intervals between keyframes
--no-wpp turns off Wavefront Parallel Processing
--start [frame_number] allows encoding from [frame_number] frame


Known issues:
-aqo 3 and -aqo 4 sometimes result in a crash when encoding 4K contents.

[birdie]

When trying to download "DivX HEVC Encoder v1.1.18 (12-4-2013)" all I get is:

OK

[filler56789]

When trying to download "DivX HEVC Encoder v1.1.18 (12-4-2013)" all I get is:

OK

What browser did you use? :confused:

[mindwin]

Any test samples please?

It's too slow on my machine. :(

New options:
-aqo [1-4] specifies one of the 4 encoding modes: 1 - fastest, 2 - balanced (default) 3 - higher quality (experimental) 4- highest quality (experimental
Very interesting.

http://labs.divx.com/node/127941
Some tests.

[Selur]

When trying to download "DivX HEVC Encoder v1.1.18 (12-4-2013)" all I get is:

OK
Same here with latest Firefox, Chrome and Internet Explorer 11

[mindwin]

Selur
Same here with latest Firefox, Chrome and Internet Explorer 11
Firefox 26, works fine. (from Ukraine, Kharkov)

http://ivanvolkov.ru/HEVC/DivX265_1.1.18.exe
Mirror. :)

[Sagittaire]

Well I read that:
http://labs.divx.com/node/127941

really interessing test for these reasons:

1) first at all, DivX labs use x264 for H264 codec reference. why not use their own H264 codec? DivXInc admit just here that the x264 codec is better than their own H264 implementation codec ... :D

2) For this test DivXInc use "1 pass bitrate" crappy and useless encoding Rate Control mode. The conclusion is just that 1 pass bitrate method for DivX HEVC is really better than the unoptimized x265 1 pass bitrate mode. In my test x265 in crf mode produce really better quality than DivX HEVC in 1 pass bitrate mode and by far.

3) The DivX HEVC codec is certainely a good codec but only "1 pass bitrate" mode is accessible. Impossible to make encoding even with simple 1 pass at fix quantizer. For me at this time DivX HEVC codec is useless just because the rate control mode is crappy.

[x265_Project]

These results don't match our x265 test results. DivX used a build of x265 from 2 weeks ago, before we optimized our presets. x265's speed and efficiency is much better than what is shown in these graphs.

From ftp://ftp.kw.bbc.co.uk/hevc/hm-11.0-anchors/cross-check/bb/hm-11.0__vs__hm-10.0.xls the HM 11 encoder results for RA-Main should be...
Bitrate Global PSNR
17,370.83 40.46
6,017.99 38.80
2,811.22 37.03
1,475.79 35.26
Note that Global PSNR = (6*YPSNR + UPSNR + VPSNR) / 8
If you simply take an average of Y, U and V PSNR, your quality will appear to be better than it is.

No worries. We'll be happy to repeat these tests using exactly the same settings as the DivX team suggests. It looks like it will take a while (on a Core i74700HQ with a RAMdisk)...

We can't test the high quality data point with DivX...DivX265_1.1.18 --input d:\BasketballDrive_1920x1080_50.yuv -s 1920x1080 -br 17371 -I 5 -n 500 -aqo 4 -o d:\DivX41.hevc
Value is outside DivX HEVC Profile: Bitrate. Must not exceed 12000
For help: DivX265_1 -h
OK... now we're running...
>DivX265_1.1.18 --input D:\BasketballDrive_1920x1080_50.yuv -s 1920x1080 -br 6018 -I 5 -n 500 -aqo 4 -o d:\DivX42.hevc
0:27:56 Frame 290 of 500 encoded @ 0.17 fps
And then, it crashed, blaming the user...
>DivX265_1.1.18 --input d:\BasketballDrive_1920x1080_50.yuv -s 1920x1080 -br 6018 -I 5 -n 500 -aqo 4 -o d:\DivX42.hevc
0:41:44 Frame 427 of 500 encoded @ 0.17 fps
Encoding aborted by user

>DivX265_1.1.18 --input d:\BasketballDrive_1920x1080_50.yuv -s 1920x1080 -br 2811 -I 5 -n 500 -aqo 4 -o d:\DivX43.hevc
0:00:02 Frame 1 of 500 encoded @ 0.49 fps
Encoding aborted by user

DivX265_1.1.18 --input d:\BasketballDrive_1920x1080_50.yuv -s 1920x1080 -br 1476 -I 5 -n 500 -aqo 4 -o d:\DivX44.hevc
0:00:01 Frame 1 of 500 encoded @ 0.61 fps
Encoding aborted by user

[x265_Project]

DivX reports...
https://sslproxy.getsatisfaction.com/sslproxy/SWhAdDNLMG5zdGFuVGlWeni9VoUrMeElpIiHaKLM6dTOqeWyLCu-oLdN-CpG4-VtgcG7TXyXQ2eYXfZyxsaBXg==.png
My tests show the x265 results should look like this...
http://x265.org/img/x265DivxChallenge.png

Medium
FPS Bitrate Global PSNR Version
2.75 17513.3 39.999 0.6+1-6b7550eed359
3.54 6031.25 37.963 0.6+1-6b7550eed359
4.09 2757.34 35.785 0.6+1-6b7550eed359
4.67 1444.69 33.357 0.6+1-6b7550eed359
Veryslow
FPS Bitrate Global PSNR Version
0.12 17691.51 40.437 0.6+1-6b7550eed359
0.39 6051.88 38.416 0.6+1-6b7550eed359
0.57 2808.56 36.414 0.6+1-6b7550eed359
0.71 1417.32 33.72 0.6+1-6b7550eed359

You can repeat these tests. My batch file looks like this (D is my RAMdisk)...
del d:\*.* /Q
copy c:\testx265\BasketballDrive_1920x1080_50.yuv d:\*.*
set SEQUENCE=d:\BasketballDrive_1920x1080_50.yuv
set RESOLUTION=1920x1080
set FPS=50
set FRAMES=500
x265 --input %SEQUENCE% --input-res %RESOLUTION% --fps %FPS% -f %FRAMES% -o d:\MEDIUM1.hevc --csv %CSV% --bitrate 17371 -p medium --no-progress --tune psnr
x265 --input %SEQUENCE% --input-res %RESOLUTION% --fps %FPS% -f %FRAMES% -o d:\MEDIUM2.hevc --csv %CSV% --bitrate 6018 -p medium --no-progress --tune psnr
x265 --input %SEQUENCE% --input-res %RESOLUTION% --fps %FPS% -f %FRAMES% -o d:\MEDIUM3.hevc --csv %CSV% --bitrate 2811 -p medium --no-progress --tune psnr
x265 --input %SEQUENCE% --input-res %RESOLUTION% --fps %FPS% -f %FRAMES% -o d:\MEDIUM4.hevc --csv %CSV% --bitrate 1476 -p medium --no-progress --tune psnr
x265 --input %SEQUENCE% --input-res %RESOLUTION% --fps %FPS% -f %FRAMES% -o d:\VERYSLOW1.hevc --csv %CSV% --bitrate 17371 -p veryslow --no-progress --tune psnr
x265 --input %SEQUENCE% --input-res %RESOLUTION% --fps %FPS% -f %FRAMES% -o d:\VERYSLOW2.hevc --csv %CSV% --bitrate 6018 -p veryslow --no-progress --tune psnr
x265 --input %SEQUENCE% --input-res %RESOLUTION% --fps %FPS% -f %FRAMES% -o d:\VERYSLOW3.hevc --csv %CSV% --bitrate 2811 -p veryslow --no-progress --tune psnr
x265 --input %SEQUENCE% --input-res %RESOLUTION% --fps %FPS% -f %FRAMES% -o d:\VERYSLOW4.hevc --csv %CSV% --bitrate 1476 -p veryslow --no-progress --tune psnr

[Kurtnoise]

you should post also a graph about speed encoding...with x264 as anchor :D

[Selur]

btw. DivX Converter does come with a command line encoder named 'DivXEngine' (inside the 'DivX Transcode Engine'-folder):
Usage:
DivXEngine <options>
-i <input media file(s)> : set input media file(s)
-o <output media file> : set output media file
[-v <video bitrate (kbps)>] : set video bitrate, don't use with -f option
[-a <audio bitrate (kbps)>] : set audio bitrate, don't use with -f option
[-x <custom resolution width>] : set custom resolution width
[-y <custom resolution height>] : set custom resolution height
[-f <file size limit (MB)>] : set filesize limit (in MB), don't use neither with -v -a options
[-t] : enable audio pass through
[-p <output profile>] : possible values are:
m - Mobile
ht - HomeTheater (default)
hd720 - HD720
hd1080 - HD1080
phd - DivXPlusHD
p4k - DivXPlus4K
hevc720 - HEVC720
hevc1080 - HEVC1080
hevc4k - HEVC4K
iphone - MP4 AVC for iPhone
ipad - MP4 AVC for iPad
[-k] : enable trick-play (for DivXPlusHD(phd) profile only and one input media file!)
[-s] : enable video 2 pass encoding
[-d] : enable profile detector
[-b] : enable burn subtitle
[-l] : enable logging and specify (optionally) output directory
[-q] : Set DivXLogger logging level
DIVX_ALL_MSG = (1 << 0), // 2 ^ 0 = 1 all message types
DIVX_CRITICAL_MSG = (1 << 1), // 2 ^ 1 = 2 Critical error
DIVX_ERROR_MSG = (1 << 2), // 2 ^ 2 = 4 Error
DIVX_WARNING_MSG = (1 << 3), // 2 ^ 3 = 8 Warning
DIVX_INFO_MSG = (1 << 4), // 2 ^ 4 = 16 Information
DIVX_HEADER_MSG = (1 << 5), // 2 ^ 5 = 32 Heading, usually marks start of group of related messages
DIVX_DEBUG_MSG = (1 << 6), // 2 ^ 6 = 64 Debug message
DIVX_PROGRESS_MSG = (1 << 7) // 2 ^ 7 = 128 Some progress
[-w] : disable WPP(Wavefront Partitioning Processing), works in case of HEVC profiles only
[-u <output profile>] : HEVC quality level, works in case of HEVC profiles only. Possible values are:
fastest - HEVC Quality level: fastest
fast - HEVC Quality level: fast
balanced - HEVC Quality level: balanced
better - HEVC Quality level: better
best - HEVC Quality level: best
[-h] : help
It is a lot faster than DivX265, supports Avisynth input (but, sadly doesn't support input via pipe/std::In).
Using
DivXEngine.exe -i test.avs -v 5000 -x 1920 -y 1080 -p hevc1080 -q 128 -u fastest -o test.265
encoding a 10:53min 1920x1080p clip (Elephants Dream) took 10:34min, so since the frame rate of the clip was 24fps the encoding speed with the fastest profile should also be ~24fps.
Haven't done any further testing since the missing 'pipe-input'-support, is a deal-breaker for me, but since I hadn't read about it here I thought I should mention it.

Cu Selur

[Kurtnoise]

It's not really new...that's their GUI uses as a frontend.

[Selur]

didn't knew it could be used through a command line interface, never saw that anyone posted about it here in the forum, so for me it was new :)

[Sagittaire]

It's not really new...that's their GUI uses as a backend.

[-s] : enable video 2 pass encoding

this parameters is a really new. 2 pass encoding will produce really better quality than 1 pass bitrate mode.

[Kurtnoise]

Well...this has been introduced when they have jumped in the AVC content, in 2009-2010 ?!!

[Sagittaire]

btw. DivX Converter does come with a command line encoder named 'DivXEngine' (inside the 'DivX Transcode Engine'-folder):
Usage:
DivXEngine <options>
-i <input media file(s)> : set input media file(s)
-o <output media file> : set output media file
[-v <video bitrate (kbps)>] : set video bitrate, don't use with -f option
[-a <audio bitrate (kbps)>] : set audio bitrate, don't use with -f option
[-x <custom resolution width>] : set custom resolution width
[-y <custom resolution height>] : set custom resolution height
[-f <file size limit (MB)>] : set filesize limit (in MB), don't use neither with -v -a options
[-t] : enable audio pass through
[-p <output profile>] : possible values are:
m - Mobile
ht - HomeTheater (default)
hd720 - HD720
hd1080 - HD1080
phd - DivXPlusHD
p4k - DivXPlus4K
hevc720 - HEVC720
hevc1080 - HEVC1080
hevc4k - HEVC4K
iphone - MP4 AVC for iPhone
ipad - MP4 AVC for iPad
[-k] : enable trick-play (for DivXPlusHD(phd) profile only and one input media file!)
[-s] : enable video 2 pass encoding
[-d] : enable profile detector
[-b] : enable burn subtitle
[-l] : enable logging and specify (optionally) output directory
[-q] : Set DivXLogger logging level
DIVX_ALL_MSG = (1 << 0), // 2 ^ 0 = 1 all message types
DIVX_CRITICAL_MSG = (1 << 1), // 2 ^ 1 = 2 Critical error
DIVX_ERROR_MSG = (1 << 2), // 2 ^ 2 = 4 Error
DIVX_WARNING_MSG = (1 << 3), // 2 ^ 3 = 8 Warning
DIVX_INFO_MSG = (1 << 4), // 2 ^ 4 = 16 Information
DIVX_HEADER_MSG = (1 << 5), // 2 ^ 5 = 32 Heading, usually marks start of group of related messages
DIVX_DEBUG_MSG = (1 << 6), // 2 ^ 6 = 64 Debug message
DIVX_PROGRESS_MSG = (1 << 7) // 2 ^ 7 = 128 Some progress
[-w] : disable WPP(Wavefront Partitioning Processing), works in case of HEVC profiles only
[-u <output profile>] : HEVC quality level, works in case of HEVC profiles only. Possible values are:
fastest - HEVC Quality level: fastest
fast - HEVC Quality level: fast
balanced - HEVC Quality level: balanced
better - HEVC Quality level: better
best - HEVC Quality level: best
[-h] : help
It is a lot faster than DivX265, supports Avisynth input (but, sadly doesn't support input via pipe/std::In).
Using
DivXEngine.exe -i test.avs -v 5000 -x 1920 -y 1080 -p hevc1080 -q 128 -u fastest -o test.265
encoding a 10:53min 1920x1080p clip (Elephants Dream) took 10:34min, so since the frame rate of the clip was 24fps the encoding speed with the fastest profile should also be ~24fps.
Haven't done any further testing since the missing 'pipe-input'-support, is a deal-breaker for me, but since I hadn't read about it here I thought I should mention it.

Cu Selur

well don't work here. It's a new update? Because my divxconverter up to december and "check update" say no new update available?

[Selur]

Simply downloaded it from the official homepage a day before I posted, installed it inside a VM and copied the 'DivX Transcode Engine' folder to my main system for the testing.

[Shevach]

Are there binaries of divx265 for Linux (Linux32 and Linux64)?

[DarrellS]

Surprised that nobody has mentioned the updated DivX265 encoder. It has a new fastest setting and also constant quantizer settings.

DivX265 is almost twice as fast at new fastest setting (1) as x265 at ultrafast preset.

http://labs.divx.com/divx265

[Slitheen]

Surprised that nobody has mentioned the updated DivX265 encoder. It has a new fastest setting and also constant quantizer settings.



Where can these CQ settings be found?

Also, why are the HEVC profiles MKV only I wonder.

[Kurtnoise]

Where can these CQ settings be found?
http://labs.divx.com/divx265
http://labs.divx.com/node/127929

Also, why are the HEVC profiles MKV only I wonder.
Because the marketing chosen by DivX was to create DivX Plus HD format (http://en.wikipedia.org/wiki/DivX_Plus_HD) where the container selected for this was Matroska. So, they keep it the same for HEVC contents I guess...

[Slitheen]

I see. Thanks.


I tried out the Divx10 encoder, using the 720p HEVC profile with an H264 file I'd encoded in handbrake. Impressive reduction of size with reasonable quality but I keep getting what seems to be a juddery stuttery framerate with the output.

[Kurtnoise]

A new version has been released (http://labs.divx.com/divx265) :

DivX265 version 1.3.74
What's new:

Faster encoding, up to 3 times faster (balanced mode)
64 bit and 32 bit version
New options wrt signalling colorspace properties: -709, --colour-primaries, --transfer-characteristics, --matrix-coefficients

Note that this requires the VC 2013 runtime .
It is recommended to use the 32 bit version with AviSynth.

Known issues:

XP is not supported

[Kurtnoise]

A new version has been released (http://labs.divx.com/divx265) few days ago :

DivX265 version 1.4.21

What's new:

Support for Main 10 (10 bit) in addition to Main (8 bit).
Additional 10 bit raw input formats (yuv420p10le, v210)
Improved encoding speed and efficiency
Linux version
Signalling of BT.2020
New options:
-10 --main10 Selects Main 10 (10 bit) profile
--format (yuv420p, yuv420p10le, yuv422p10le, I420, V210) Raw pixelformat
--psnr Calculation psnr metrics
It is recommended to use the 32 bit version with AviSynth.

Known issues:

Statistics Linux version incorrect.

[Kurtnoise]

DivX265 version 1.5

What's new:

Supports DivX HEVC temporal scalability.
New options:
-ts, --temporal-scalability Enable two layer temporal scalability, where the frame rate of the baselayer is reduced by 2
Known issues:

Statistics Linux version incorrect.
32 bit version cannot encode main 10 at 4K resolutions, use 64 bit version.


DivX HEVC temporal scalability

DivX265 version 1.5 can create dual frame rate streams. For example, it can create 4K60/30 dual layer streams which can be played back on DivX HEVC 4K Certified devices that support 60Hz or 30 Hz. This makes it possible to play 4K@60 content on DivX HEVC file-based certified devices that cannot meet the playback requirements for 4K@60. It requires a mux which puts the DivX Tag (unregistered userdata) in "Codec Private". For example the DivX MKV mux from github jaya (https://github.com/jaya-divx/mkvtoolnix) will do this. The DivX Tag contains a random asset number and layer specific details.


http://labs.divx.com/divx265

[foxyshadis]

Is every other frame just a non-ref B (or P even)? That would be the most sensible way to put something like that in a single file, then you could ignore every other frame with no change to the video.

[mademoisellesocal]

Is every other frame just a non-ref B (or P even)? That would be the most sensible way to put something like that in a single file, then you could ignore every other frame with no change to the video.

The odd frames are indeed non-reference frames and are not required for decoding the base layer.

[birdie]

ffmpeg -i source.avi -f rawvideo -pix_fmt yuv420p pipe:1 | ./DivX265_1_5_8 -fps 15 -s 1024x768 -i - -aqo 5 -br 4000 -o dest.hevc
Value is outside DivX HEVC Profile: Frame rate. Must be a value listed in the profile

I'm confused. What does the encoder want?

Edit: fps 15 is not supported. Sigh. Since this encoder outputs raw video I wonder why any limitations exist at all.

[mademoisellesocal]

ffmpeg -i source.avi -f rawvideo -pix_fmt yuv420p pipe:1 | ./DivX265_1_5_8 -fps 15 -s 1024x768 -i - -aqo 5 -br 4000 -o dest.hevc
Value is outside DivX HEVC Profile: Frame rate. Must be a value listed in the profile

I'm confused. What does the encoder want?

Edit: fps 15 is not supported. Sigh. Since this encoder outputs raw video I wonder why any limitations exist at all.

DivX guarantees that all streams created with DivX tools in compliance with DivX profiles can be played back on DivX certified devices.

Valid frame rates for DivX HEVC:
60 Hz
60000/1001 Hz
50 Hz
48 Hz
30 Hz
30000/1001 Hz
25 Hz
24 Hz
24000/1001 Hz

15 fps is an odd frame rate for content distribution so it's not supported. Is there a particular reason you prefer that framerate?