Hybrid(Windows/Linux/Mac): Input -> x264/x265/Xvid/VP8/VP9

[deadrats]

the divx people have updated their cli encoder, this time there are 64 and 32 bit builds:

http://labs.divx.com/divx265

you might also be interested in knowing that they are promoting your software:

http://labs.divx.com/tools-for-divx265

[Selur]

Thanks for the info, didn't know about any of those two infos.

---

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 .

Does anyone know if it now works on Windows XP (since the runtime works on XP) -> no, it doesn't
Any why didn't they compile it statically? (sadly their forum is 'down for maintenance from June 26th to July 10th. ' otherwise I would have asked about plans regarding a static release)

[Gravitator]

DivX265 version 1.3.74 - Really speed increased to 3x and improved image quality

[Gravitator]

Can we expect Psy-RD from DivX? - it is a private or open technology / patent?

[Selur]

it is a private or open technology / patent?

There is no fixed meaning to psy-rd (= psycho visual rate-distortion) other than it is an adjustment to the bit rate distribution to enhance the quality.
Since quality is vague term, so is the was how to implement psy-rd. It's basically an implementation of some quality metric and the tuning of the bit rate distribution to enhance the image based on that quality metric. So depending on how the designers choose to define their internal psycho visual quality metric they might or might not violate patents.

Can we expect Psy-RD from DivX?

Best ask someone who works for DivX Networks.

Cu Selur

[Wringst]

[quot

Problems in the newest version after installation!





and



So the application doesn't start!

[Selur]

Wild guess, some dll from the Visual C++ Redistributable Packages for Visual Studio 2013 is required, with the amount of information you provided I can't reproduce the problem, read http://www.selur.de/support.

[blud7]

I have the same problem, Hybrid isn't able to pull a version number from the 64 bit divX encoder, replacing it with the 32 bit version works fine.

[Selur]

@blud7: Can you please try if the 64bit version works if you place the attached dll next to it?
(If Hybrid starts up with the dll without a problem, also please reset the tool cache (Config->Tools->Clear...) and restart Hybrid to see if it interferes with another tool. Thanks!)

[Selur]

Argh, seems like:
a. Kvazaar need the Visual C++ 2010 runtime installed (it's not enough to put the dlls next to it)
b. DivX265 need the Visual C++ 2013 runtime installed (it's not enough to put the dlls next to it)
-> considering to remove support for both.

[deadrats]

for those that don't know DivX mpeg-4 asp had psychovisual enhancements before x264 did, if someone wanted to use the x264 psy-rd algorithms said algorithms would have to be released under the gpl along with the binary as would any improvements, but there's nothing stopping anyone from implementing their own psy-rd, nero avc has their own (that encoder is based on the Ateme encoder).

honestly, i consider most psy optimizations to be more fluff than substance and i usually avoid them like the plague.

[deadrats]

@Selur: is the fps encoding speed reported with the DivX265 encoder accurate? because if it is it's crazy how much faster those guys managed to get their encoder. i'm currently doing a 1440x1080 4:3 pixels 8mb/s vc-1 to 1920x1080 square pixel 8mb/s encode at a sustained 18fps with the balanced setting. with x265 with the ultrafast setting i'm lucky if i see close to 10fps and this is with the exact same hardware that i have been using for all my tests, even the same OS install.

i'm wondering if the encoder is misreporting the encode speed, if the divx people really managed to optimize the crap out of the encoder or if that new vc run time that's required is somehow optimizing the run time calls for optimum performance.

either way, if the reported speed is true, then bravo to the divx people.

[Selur]

fps is taken from the output of the DivX264 binary, so my guess is that the speed is accurate.
(using c11++ should only give a few percent speed improvement at best,..)

Cu Selur

[Selur]

Small correction fps is taken from ffmpegs output, but it should still be accurate.

[deadrats]

it's accurate alright, i just double checked with by keeping an eye on encoding time and manually calculating it. edit: i was wrong, my my non-wpp test was flawed, i forgot that i was cutting something with free video editor.

the speeds with both wpp and no-wpp are about the same. regardless, you need to keep this encoder in Hybrid, distribute the vc run time if you have to, the way divx265 runs now it effectively negates the need to upgrade to expensive hexacore and octocore setups, a decent quad core will do the job nicely.

based on my rough estimates, that means that at the highest quality settings, a current gen intel hexacore should be able to achieve and sustain very acceptable frame rates. i wonder what they could do if they gpu accelerated their encoder.

on more thing, there are both 64 bit and 32 bit builds of the new cli but i don't see any options for choosing which encoder is used, does Hybrid automatically detect which OS it's being installed on and automatically just install the appropriate version or is this an oversight on your part?

[Selur]

Hybrid does the following:

1. extract the 32bit tools
2. check if the OS is 64bit
3. replace the 32bit tools with their 64bit counterparts, assuming they exist. Mplayer and mencoder are treated special. On 64bit systems Hybrid uses both the 32bit and the 64bit versions depending if Avisynth is used. Whenever Avisynth is used the 32bit versions get used otherwise the 64bit versions.

Cu Selur

[blud7]

@blud7: Can you please try if the 64bit version works if you place the attached dll next to it?
(If Hybrid starts up with the dll without a problem, also please reset the tool cache (Config->Tools->Clear...) and restart Hybrid to see if it interferes with another tool. Thanks!)

It works. Sorry for the late reply, but I see you have found the issue...

[gonca]

Using latest hybrid. DivX265 crashes everytime

Edit
x264 also crashes

Edit 2
Corrupt input file, never mind

[Wringst]

Hybrid does the following:[list=1][*]extract the 32bit tools[*]check if the OS is 64bit[*]replace the 32bit tools with their 64bit counterparts, assuming they exist. Mplayer and mencoder are treated special. On 64bit systems Hybrid uses both the 32bit and the 64bit versions depending if Avisynth is used. Whenever Avisynth is used the 32bit versions get used otherwise the 64bit versions.

Cu Selur

The newest version of Hybrid (July 04) has php format. How can I install it on a windows system?

[Selur]

fixed layout of post #1156

To install Hybrid (rev 2014.07.03.1) on Windows:

• uninstall your old Hybrid version (normally not needed, but due to recent changes, it is recommend this time)
• install Hybrid (using the installer)
• add optional additions: aac encoders, codecs for mplayer/mencoder, custom misc.ini, custom style sheets

so only change is that you should deinstall any previous Hybrid version before installation

Cu Selur

[Gravitator]

Thank you for the installation progress for DivX

Whether to hybrid obey the rule profile DivX1080p@30?

[Selur]

Whether to hybrid obey the rule profile DivX1080p@30?

Translator screwed up.

Not sure what you want to ask.
Atm. Hybrid only checks that
a. the selected DivX-Resolution-Profile matches to the output resolution
b. that only frame rate supported by DivX265 are used.
it doesn't check the combinations mentioned on page 6 of http://labs.divx.com/system/files/DivX_HEVC_Profiles.pdf

The 4K profile targets CE devices supporting 4K display resolutions up to 60 fps.
1080p targets devices supporting 1080p resolution up to 60 fps.
720p targets mobile devices with up to 720p resolutions up to 30 fps.

and looking at these restrictions 1080p encodes are not limited to 30fps.
(will add a check to validate that the output obeys these combination restrictions)

-> Can you rephrase that question?

Cu Selur

[Gravitator]

Table write 1080p@50 and 1080p@60 that is not supported for 1080p profile

[Selur]

you are right, will adjust next Hybrid version accordingly to check that width * height <= MaxLumaPS and width * height *fps <= MaxLumaSR

[Gravitator]

At DivX Converter comes trickier, if feed him 1920x1080@50 then output it produces 1536x848@50 under 1080p profile (they seem to have a calculator for compromise).

[Selur]

Works fine in Hybrid using park_joy_1080p.y4m as source:

ffmpeg -y -loglevel fatal -r 5000000/100000 -i "H:\park_joy_1080p50.y4m" -an -sn -threads 8 -vsync 0 -r 5000000/100000 -pix_fmt yuv420p -f rawvideo - | DivX265 --input - --size 1920x1080 --bitrate 8000 -aqo 3 --interval 5 --framerate 50 -o "H:\Temp\park_joy_1080p50_14_03_35_2310_01.265"

the output is fine.

-> no clue, what DivX Converter does and why it does what it does, but that is not a restriction of DivX265 itself so no reason for Hybrid to randomly* lower the resolution. (* there probably is a reason, but you best ask for support in the official DivX forum)

Cu Selur

[Gravitator]

Put "park_joy_1080p50.y4m" in the DivX Converter (profile 1080p) and you will see that it changes the resolution but leaves the frame rate. - ?
(Can reduce the frame rate but leave the resolution of <or> to reduce the resolution but leave the frame rate)

[Selur]

Don't care about DivX Converter,...

[Gravitator]

Don't get so upset
Chief Engineer will come to work after 5 hours, then enlighten all

[Wruckler]

Don't care about DivX Converter,...

HI Selur!

Hybrid does not start.

The error message: