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

[omelette]

I look forward to testing the new version.

Not sure what level of debugging needed to highlight the problem. I've just discovered that nifty feature of Hybrid's for producing video-samples, so I've attached a sample video instead. This is a re-encode of a 'standard' 25fps x264 video, and the same problem occurs - so the problem is not tied to the frame-rate.

[Selur]

A you use mkv as output. (I normally use mp4.)
I can confirm that Hybrid does not detect the video stream in the input.

This is because mplayer reports:

[mkv] Unknown/unsupported CodecID (V_MPEGH/ISO/HEVC) or missing/bad CodecPrivate

and doesn't output any ID_Video infos.
-> problem is mplayer doesn't support hevc inside mkv (since mplayer is used in a lot of places Hybrid then decides that it can't handle the input)
Can't do anything about it, this will fix itself when newer mplayer versions start supporting mkv with hevc in it.

---

Also as a general rule: unless told otherwise always stick with the default debug level and don't post stuff from the normal log since it doesn't help me at all.

Cu Selur

[Gravitator]

--dither                      Enable dither if downscaling to 8 bit pixels. Default disabled
--[no-]weightb                Enable weighted prediction in B slices. Default disabled

what use "--dither" ?

[Selur]

not useful in Hybrid, since this is already possible and done through ffmpeg
normally: allows to convert 10bit raw input to 8bit hevc adding noise (dither) to avaoid banding during the conversion

[deadrats]

@Selur:

you sure took you're sweet ass time updating your app with support for the latest divx encoder, wtf?

just kidding, thanks for adding support, downloading the latest version now to test it out.

btw, i glanced at the changelog and it says you removed support for weighted b from x265, why?

[Selur]

hups, should be under added not removed

[Gravitator]

What is the reason of failure in addition "hevc.mkv" when "hevc.mp4" accepts without complaint?

[Selur]

Sorry, but that sentence doesn't make any sense, no clue what it was ment to say.

[Gravitator]

give hevc.mkv


give hevc.mp4 and hybrid accepts/OK

[Selur]

Yes, that is a known limitation atm. because mplayer&mencoder do not know how to handle mkv(hevc), when they do, so will Hybrid.

[Gravitator]

possible to look for markers of P / B frames in viewing mode HEVC?

[Selur]

Avisynth Preview might show the b-/p-Frames if ffmpegsource identifies them.

[omelette]

A problem when re-encoding with DivX265 perhaps (with both mp4 and mkv and using default DivX265 settings) - Job queue shows the encoding-video part as "STARTED" but remains at 0%. 'DivX265.exe' has executed OK but then it just sits there, no CPU-loading, nothing.

[Selur]

What happens if you call:

"C:\PROGRA~1\Hybrid\mencoder.exe" -lavdopts threads=2 -really-quiet -of rawvideo -o - -ovc raw -demuxer lavf -vfm ffmpeg -noskip -vf scale,format=i420 -forcedsubsonly -nosub -nosound -mc 0 "F:\HOD329~3.MP4" | "C:\PROGRA~1\Hybrid\DivX265.exe" --input - --size 720x360 --bitrate 1500 -aqo 3 --interval 5 --framerate 24000/1001 -o "C:\DOCUME~1\ADMINI~1.OME\LOCALS~1\Temp\test_01_53_52_3710_02.265"

if that fails, what is the output of:

"C:\PROGRA~1\Hybrid\mencoder.exe" -lavdopts threads=2 -of rawvideo -o nul -ovc raw -demuxer lavf -vfm ffmpeg -noskip -vf scale,format=i420 -forcedsubsonly -nosub -nosound -mc 0 "F:\HOD329~3.MP4

any errors?

[Selur]

Also: you might want to update to the latest version 2014.04.04.1

[omelette]

The first one does the same - 'DivX265.exe' executes, has about 73meg of memory allocated to it, but just sits there, no output, no 'CPU' activity according to Task Manager. The second one runs normally, lots of output, maxing out the CPU.

Didn't know the latest update had been updated already! Will get it when my 3G connection improves, it sucks at the moment.

PS - forgot you asked for the output. No errors that I can see.

[Selur]

Seems like the decoding works fine -> looks like some restriction in DivX265,.. maybe it not only support just a few frame rates, but also only a few resilutions.

[gonca]

According to their website, Divx265 encodes as per their profiles. Combinations of FPS and resolution. i.e. different resolutions support different FPS

[Selur]

looking at the DivX Profiles
The profiles only set upper limits, so "--size 720x360 --bitrate 1500 -aqo 3 --interval 5 --framerate 24000/1001" should work

I know that when mencoder is used as decoder, there is no progress indication since DivX265 doesn't have any, but it should not ' just sits there, no CPU-loading, nothing'. It should use near 100% cpu usage during encoding.
-> tried to reproduce the problem using:

mencoder -lavdopts threads=8 -really-quiet -of rawvideo -o - -ovc raw -demuxer lavf -vfm ffmpeg -noskip -vf scale,format=i420,scale=720:320,scale,format=i420 -sws 10 -forcedsubsonly -nosub -nosound -mc 0 "F:\TESTCL~1\test.avi" | DivX265 --input - --size 720x320 --bitrate 1500 -aqo 5 --interval 5 --framerate 25 -o "H:\Temp\test_09_13_36_5710_01.265"

but here it works,... no problem.

[omelette]

Selur, first off, I have really no idea what that line is supposed to be doing - all those options make my head spin! Running it, I get a problem regarding the paths. Changing both paths to "c:\", so that it becomes;

mencoder -lavdopts threads=8 -really-quiet -of rawvideo -o - -ovc raw -demuxer lavf -vfm ffmpeg -noskip -vf scale,format=i420,scale=720:320,scale,format=i420 -sws 10 -forcedsubsonly -nosub -nosound -mc 0 "c:\test.avi" | DivX265 --input - --size 720x320 --bitrate 1500 -aqo 5 --interval 5 --framerate 25 -o "c:\test_09_13_36_5710_01.265"

it runs ok - meaning 'DivX265.exe' executes, then sits there doing nothing. I tried putting a valid 'test.avi' video at c:\ but it still does the same - so I guess that test.avi is not being used as an input-file. If you're confused, think how I feel!!! Probably redundant, but a little video of what I am seeing is attached.

[Selur]

What happens if you simply call (in a command prompt) the DivX265.exe inside the Hybrid folder?
Do you get the normal DivX help output?

To check if the decoding works fine, try calling:

mencoder -lavdopts threads=8 -of rawvideo -o nul -ovc raw -demuxer lavf -vfm ffmpeg -noskip -vf scale,format=i420,scale=720:320,scale,format=i420 -sws 10 -forcedsubsonly -nosub -nosound -mc 0 "c:\test.avi"

this should throw an error if mencoder has some problem decoding the file.

[omelette]

Everything appears normal when I try both of those things (see pic).

[Selur]

strange,..
I send you a 32bit Windows build of my development version, which includes an additional ffmpeg passthrough to show progress during DivX265 encoding, did you try if that version helped?

[omelette]

Sorry, didn't notice your PM. After replacing the Hybrid.exe file with the new one, I get strange(r) results! First, I get a "disabled avisynth support... need to update avisynthExtension AddOn" message - probably 'cos it's a development version. Now DivX265.exe actually does something, but only for 3% of the sample-video (1min of x264, 25fps), before going into hibernation-mode again!

For what it's worth, to rule out a problem with my XP install, I created a fresh virtual-XP partition using a different & updated XP ISO to the one I used to create my old virtual-XP partition (which was a stripped-down to the bare-essentials version). It made no difference - which really didn't surprise me as Wine-XP has the same problem as well. Has me wondering if this could be a 32-bit/64-bit issue?!?!?

[Selur]

need to update avisynthExtension AddOn

my bad, should have refused to look at the issue until you updated to the latest version.
-> clear the tools cache (under Config->Tools), deinstall Hybrid, download and install the latest version and replace the Hybrid.exe binary with the development version, then try again

[omelette]

UPGRADE COMPLETE!!!

Replaced Hybrid.exe.with the development version. Identical result, DivX265.exe goes to sleep after 3% has been completed, CPU-load dropping to zero.

PS Just tried it with a longer video (45min x264 25fps) - it immediately goes to sleep, with 0% complete, so the 3% thing might be just an aberration.

[Selur]

Found the problem, the new DivX265.exe (version 1.2.0.24) doesn't encode on Windows XP any more, the old version (version 1.1.0.18) works fine.
So my best adwise is:
a. report to DivX that their latest DivX265 doesn't work on Windows XP
I wrote a post in their forum about it: https://forums.divx.com/divx/topics/latest_divx265_doesnt_work_on_windows_xp.
Depending on their feedback, I will deactivate DivX265 in Hybrid on Windows XP (when 1.2+ is used).
b. replace the DivX265.exe with an older version an make sure you don't use aqo 5 or constant quantizer encoder, since both were introduced with version 1.2.

[omelette]

Aww, poor XP is being abandoned. Never thought I'd feel nostalgic about that POS - the reason I switched to Linux to begin with! I'd contemplate switching to Sys7 if there was an advantage in doing so, but my brief couple of months playing with it showed it to be much slower and more bloated than XP on my setup - almost 8gig just for a bare-bones install if memory serves, compared to the 3.4gig it took for the new install of XP over the weekend. Never mind, all x265 encoding is just for curiosity-sake on my ancient hardware anyway. Need to think about upgrading more than just my OS.

Appreciate you taking the time to solve this mystery.

[DarrellS]

Found the problem, the new DivX265.exe (version 1.2.0.24) doesn't encode on Windows XP any more, the old version (version 1.1.0.18) works fine.
So my best adwise is:
a. report to DivX that their latest DivX265 doesn't work on Windows XP
I wrote a post in their forum about it: https://forums.divx.com/divx/topics/latest_divx265_doesnt_work_on_windows_xp.
Depending on their feedback, I will deactivate DivX265 in Hybrid on Windows XP (when 1.2+ is used).
b. replace the DivX265.exe with an older version an make sure you don't use aqo 5 or constant quantizer encoder, since both were introduced with version 1.2.

I had no problem using DivX265.exe version 1.2.0.24 with Windows XP before switching to Windows 7. I announced DivX265.exe the clear winner at the time since the encode speeds were much faster than x265.exe and didn't need the high memory and CPU usage that x265.exe needs.

DivX265.exe is a lot more strict about video resolutions than x265.exe since they have to fall into their profiles.

[omelette]

I've just tried versions 1.0.341 and 1.1.18 of DivX265. 1.0.341 crashes, 1.1.18 works! It got interested again on hearing that DivX265 was significantly faster at encoding. That might be true for the latest version (which I can't use) but not for 1.1.18. In fact my sample-video (1:05sec, x264, 25fps) takes more than twice as long to encode with DivX265 when using the default settings with both encoders. On my hardware that about 0.2fps versus 0.4fps - so I won't be encoding complete movies anytime soon!

PS: Hmmm, just checked the files-sizes - sample video=3.7meg, x265-encode=2meg, DivX265-encode=12.7meg!!! I guess selecting default settings (1 pass) for both doesn't produce similar results. DivX265 is encoding at a bit-rate of 1500kb/s, whereas x265 just has a 'constant bit-rate' setting.

PPS: Booo, just realised that I can no longer encode with x265 either on XP after upgrading(!) to the latest Hybrid - on the day M$ officially stopped supporting XP as well, go figure. The above tests were done on Wine-Hybrid which was still the old 4.2.1 version where x265 still works. So basically Hybrid no longer supports any flavour of x265 with XP now. I guess playtime stop here until I upgrade my Linux.