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

[Selur]

@deadrats: you are not using the latest version try the 2014.01.22.1 revision. For your case Hybrid should then use: mencoder do deinterlace and ffmpeg to wrap the content into a y4m wrapper and then feed it to vpxenc.

[deadrats]

tried the latest version, with yadif the same thing happens, a 29.1mb dummy file is created, only now even choosing avisynth de-interlacers doesn't work, i start the job but it hangs with a message next to all tasks that says "waiting" meaning it never even starts.

[Selur]

Okay, strange couldn't reproduce the problem here, will do some further examination, once I get back home today.
Send you a link to the 2014.01.22.2 version, please try if that version helps.
(side note: you have to recreate the jobs and not use the old once.)

[SuperNoob28]

No clue what OS you are on, what version you downloaded,..
Also "I cannot open my hybrid app" doesn't really give much details,...

General reminder:
1st startUp after a version update or a new install always takes long since:
a. Hybrid checks for all tools
b. fontconfig which comes with mplayer might rebuild the index of all the fonts in the system
(most of the time it's mplayer/fontconfig -> simply check your taskmgr, if mplayer is working thats probably the cause)
-> so depending on your system simply wait a bit.


Cu Selur

I have OS Win 7 64bit. I have the 2013.12.6.2.SETUP.exe version.

[Selur]

a. current version is 2014.01.22.1
b. did you check if the startUp is just waiting for mplayer?

[Gravitator]

Bad work - deinterlace:Auto

[Selur]

Don't see the problem, by default Hybrid will use QTGMC(Preset="Fast"), which looks fine to me, for better results choose a slower preset for QTGMC.
No clue, what I should do with the files, since there is no explanation and debugoutput of how they were created.

[Selur]

Okay, I know where the problem is.
Your content is flagged as bottom field first, but it is progressive.
-> either run the Interlace Analyse "Filtering->(De-)Interlace/Telecine->Deinterlace/Telecine Settings->Analyse" (this way Hybrid will detect the source as progressive) or disable deinterlacing or overwrite the scan type to progressive or set deinterlacer to None.
Also note: you can tell Hybrid to automatically run the "Interlace Analyse" through: "Config->Automation->Autorun interlaced check"

=> no bug in Hybrid, buggy (wrong flagged) source

Cu Selur

Ps.: sample shows nicely what can happen if you deinterlace progressive content

[Gravitator]

No clue, what I should do with the files, since there is no explanation and debugoutput of how they were created.

Regardless of the encoder and settings

Okay, I know where the problem is.

apply by default in the next build?

[Selur]

apply by default in the next build

No, I will not change Hybrid to handle wrongly flagged files.
If you want Hybrid to automatically try to check if the interlacing flags are correct, you need to enable 'Autorun interlaced check' and save it as default.

[deadrats]

tried with Hybrid 1.22.2 and vp9 encoding with avisythn deinterlacing works again, but still with yadif a dummy file is created.

i used a smaller interlaced test file, i have attached that test sample, it's from an adult dvd but there is no sex or nudity, just a chick fully clothed talking on the phone, 39secs long, so you can test it out yourself.

ignore the discrepancy between the file name listed in the debug report and the name of teh file i uploaded, i renamed the file slightly prior to upload but same file.

[Selur]

Thanks for the feedback, just on my way to bed, but downloaded the content will look at it tomorrow and report back.

Cu Selur

Ps.: Calls look fine on a first clance:

"C:\PROGRA~1\Hybrid\ffmpeg.exe" -v -10 -i "F:\PORN\DVDVOLUME\Alicia Rio on phone.demuxed.mpg" -an -sn -r 30000/1001 -threads 8 -vf yadif=1:1,crop=706:472:4:0,scale=720:480 -vsync 0 -r 29.97 -pix_fmt yuv420p -sws_flags spline -f yuv4mpegpipe - | "C:\PROGRA~1\Hybrid\vpxenc.exe" --codec=vp9 --passes=1 --pass=1 --target-bitrate=6400 --end-usage=vbr --profile=0 --good --cpu-used=0 --undershoot-pct=0 --buf-sz=6 --buf-initial-sz=4 --buf-optimal-sz=5 --drop-frame=0 --resize-allowed=0 --kf-min-dist=0 --kf-max-dist=60 --auto-alt-ref=0 --noise-sensitivity=0 --sharpness=7 --static-thresh=0 --tile-columns=2 --tile-rows=1 --threads=16 --width=720 --height=480 -o "C:\Users\NJ\AppData\Local\Temp\Alicia Rio on phone vp9 2_17_09_52_4410_04.vp9" -

content get's decoded and deinterlaced with ffmpeg using yadif and then get fed to vpxenc.
-> I'm starting to suspect one of the vpxenc options is at fault here,... will test tomorrow

[deadrats]

just ran into another bug, i tried to redo the test encode with the sample i supplied but this time i tried to use lossless qtgmc "before resharpening", source matching "2xrefined", custom, bob and i disabled adaptive quant for vp9, when i tried to add the bob i got a pop up that said "FIX ME(22), please report,."

when i checked the job had been added but when i tried to run the job it crashed immediately.

debug attached.

[Selur]

Ah, okay, added the "FIX ME"-info to some code samples where I didn't find a way to reach the code and where if the code was reachable a bug would occur. (it's a name shortening problem after audio extraction with Mplayer)
-> will fix

[Selur]

I'm having a hard time trying to reproduce the problem -> can you save you Settings (Config->Proiles->Global profile->Save global profile) and send me the settings file? Looks like it's a combination of a bunch of settings which lead the path to the problem and unless I find the right settings I can't reach it.

---
Think I foudn the problem, seems like ffmpeg ahs problems with the file, when calling:

"G:\Hybrid\ffmpeg.exe" -y -i "F:\PORN\DVDVOLUME\Alicia Rio on phone.demuxed.mpg" -an -sn -r 30000/1001 -threads 8 -vf yadif=1:1,crop=706:472:4:0,scale=720:480 -vsync 0 -r 29.97 -pix_fmt yuv420p -sws_flags spline -f yuv4mpegpipe NUL

(which is just the decoder)
ffmpeg reports:

[swscaler @ 0000000000497fe0] Warning: data is not aligned! This can lead to a speedloss
[yuv4mpegpipe @ 000000000529f8a0] Encoder did not produce proper pts, making some up.
[yuv4mpegpipe @ 000000000529f8a0] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 3003 >= 3003
av_interleaved_write_frame(): Invalid argument

-> looking into it

[deadrats]

ok, after doing more test encodes than i can shake a stick at, i've come to the following conclusion: it's an F'ed up situation that i'm not sure can ever be resolved.

as you surmised it's a combination of settings that cause problems, i can reproduce the creation of a dummy file every time if i enable the "SSIM" option in vp9 under "tune".

similarly, if i choose yadif custom, either the standard one or the avisynth version, it creates a dummy file every single time. a couple of times while testing different settings i did manage to get a crash, but i would say that with 90% of the settings combinations i have tried it works just fine.

but man, those 10% of times, it can be maddening trying to find a pattern, but the two commonalities is either yadif deinterlacing or tume SSIM.

now i'm going to start testing with a small progressive sample and various source codecs and see if i can reproduce the problem further.

[Selur]

as you surmised it's a combination of settings that cause problems, i can reproduce the creation of a dummy file every time if i enable the "SSIM" option in vp9 under "tune".

-> will try to reproduce

[Leo99]

Selur, you said that will added conversion to anamorphic content with a PAR 40:33.
Did your apps have support PAR to MP4 NTSC 16:9 (40/33) already..?
So far I know it's usually used in widescreen NTSC format 704x480 (SAR:22/15 PAR:40/33 DAR:16/9).

[Selur]

Hybrid already can convert between PAR X and PAR Y. Nothing to add.

[Leo99]

OK I see. But how about widescreen video 1920x816 (2.35:1). I can't see in your output PAR the option of 2.35:1...

[Selur]

2.35 is not a pixel but a display aspect ratio.
-> If you have NTSC content select 'MP4 NTSC 16:9 (40/33)', if you have PAL content select 'MP4 PAL 16:9 (16/11)' and leave the rest to Hybrid.
It will resize the height and set the aspect ratio so that the output will be played back properly with the width you selected.

[deadrats]

@Selur:

i've noticed something odd with the x265 settings exposed by your app; under the quantization tab, there's a drop down menu labeled rate distortion optimization. this value is set by default to 3: no info available. the no info description is also applied to values 1 through 5 inclusive. for 0 it says no rdo quantization, partial rdo during mode decision and for 6 it says full rd-based mode decision.

the odd thing is if you hover the pointer over the drop down menu it lists the following 3 options:

0:minimal
1:normal
2:full

so the obvious questions become if the value 2 is full, why does the drop down menu say 6 is full and where do the rest of the values come from. furthermore, when you hover the pointer over the drop down menu it says command line match: --rd X; default: --rd 2 yet your gui defaults to a value of 3, a value that according to your own explanation doesn't exist.

Lucy, you have some splainin to do.

[Selur]

a. I simply forgot to update the tool tip
before x265 had three rd-Levels:

--rd Level of RD in mode decision
Range of values:
 0: Least;
 1: Lightweight RDO Analysis;
 2: Full RDO Analysis (Default)

but that changed a while back.

now looking at the source:
default is 3, see: line 184
rdLevel goes from 0 to 6, see: line 495
command line too sais:

--rd                          Level of RD in mode decision 0:least....6:full RDO.

b. the level do not all have descriptions, since the x265 folks didn't give any names or explanation any level aside from zero and six.
I asked about this in the mailing list, see:
https://mailman.videolan.org/pipermail/x265-devel/2013-December/002909.html
Steve replied that they are doing a lot of work on it atm. and that there should be some detailed infos inside x265.h in the future.
Since there wasn't any additional info when I released the latest Hybrid version, I didn't update the toolTip and the dropDown shows 'no info available' for all the options where there is no info available.
-> will update the toolTip once the x265 team adds some info.

Cu Selur

[z-machine95]

hello everyone! i need a way to save the progression of a job paused, even if i shut down the pc. i can't do ibernation... i have windows 7

[Selur]

Hybrid can only postpone upcoming subjobs, it can't 'stop' a running subjob and then restart from the same position.
This would only work if similar to hibernation a complete memory dump of all connected applications were possible.
-> since I have no clue how to archive this, I doubt Hybrid will ever be able to do this

[z-machine95]

Hybrid can only postpone upcoming subjobs, it can't 'stop' a running subjob and then restart from the same position.
This would only work if similar to hibernation a complete memory dump of all connected applications were possible.
-> since I have no clue how to archive this, I doubt Hybrid will ever be able to do this

Thanks for reply, Ok... The problem is hybrid take more than a day to encode 4 h long video into x265 with slow preset at 1500kbps... I try to split into parts the video but it seem that the result is more blocky and have less quality than the encoding of the entire video. Can this be possible, lost of quality if source is split? During the encoding I have pause for more than an 1 h, can this be the cause of quality loss? Another thingnwhen I resume a paused job from the 4 fps performance encoding rate it passes to 1.09 fps... After 2 h it returns slowly to original performance.. Why this performance drop?


Thanks you so much for this incredible software!

[Selur]

• Yes, splitting a source can change the bit rate distribution and thus the output quality. For x264 this effect isn't noticeable that much, but for x265 it might be. If it does or not also depends on the source content and a bunch of other parameters. (in example if openGop is used or not, which encoding mode is used, etc.)
• When Hybrid pauses an encoding it simply suspends the decoder. The encoder then automatically pauses too since it's waiting for new frames or a finished signal from the decoder.
• Hybrid only shows the speed output that x265 indicates, my guess is that x265 might not be really slower, but might simply taking the whole processing time into account. So it might be showing an average fps over the encoding time (pausing doesn't stop the encoding time) and not just over the last 100 frames or so. -> if there actually is a performance drop you need to ask the x265 folks about it.
• Personally, I wouldn't use any H.265 encoder for archiving atm. . Simply looking at the x265 commits from the last month or so indicates that there is still a lot of work to be done and to call x265 anything near stable. -> using an unstable encoder not just for testing encodes seems like a bad idea.

Cu Selur

[z-machine95]

• Yes, splitting a source can change the bit rate distribution and thus the output quality. For x264 this effect isn't noticeable that much, but for x265 it might be. If it does or not also depends on the source content and a bunch of other parameters. (in example if openGop is used or not, which encoding mode is used, etc.)
• When Hybrid pauses an encoding it simply suspends the decoder. The encoder then automatically pauses too since it's waiting for new frames or a finished signal from the decoder.
• Hybrid only shows the speed output that x265 indicates, my guess is that x265 might not be really slower, but might simply taking the whole processing time into account. So it might be showing an average fps over the encoding time (pausing doesn't stop the encoding time) and not just over the last 100 frames or so. -> if there actually is a performance drop you need to ask the x265 folks about it.
• Personally, I wouldn't use any H.265 encoder for archiving atm. . Simply looking at the x265 commits from the last month or so indicates that there is still a lot of work to be done and to call x265 anything near stable. -> using an unstable encoder not just for testing encodes seems like a bad idea.

Cu Selur

I agree, but my first try has been really successfull.. I converter 14 Mbps film ( the fellowship of the ring) into x265 and the result is a very good quality video in a very low space.. 2,67 gb for a 1500 Kbps 4 h film, and the quality is very good, very near the source...

Here is my x265 film: http://forum.tntvillage.scambioetico.org/index.php?showtopic=382466

[Selur]

Happy you like x265 (and Hybrid), btw. you might want to replace the x265 binaries with the latest from x265.cc since a few bugs were fixed since the build of the x265 binaries which came with Hybrid. Noteworthy especially a problem when openGop was disabled.

[z-machine95]

Happy you like x265 (and Hybrid), btw. you might want to replace the x265 binaries with the latest from x265.cc since a few bugs were fixed since the build of the x265 binaries which came with Hybrid. Noteworthy especially a problem when openGop was disabled.

Thank you very much.... Yeah... I am very happy! It's a Good codec, Good quality at low Gb. But should i download mingw or vp12 version? 32-bit or 64-bit... It's supported the 64-bit by hybrid?