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

[Selur]

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

[Gravitator]

encoding.y4m > disable "Prefer FFmpeg" > Crash (win7x64)

[Selur]

Since y4m is just a container, which could hold different content,.. I just tested reencoding some y4m content to x264 and had no problem.
-> need more infos, read http://www.selur.de/support
(got an idea what might case a crash of the job processing, got it fixed locally)

[Gravitator]

That check

[Selur]

Reread the instructions on how to create a proper debug output.
The DebugOutput you posted contains no usable data,...

[Selur]

read your debug output from the other thread, 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 "E:\test\y4m\PARK_J~1.Y4M" | "C:\PROGRA~1\Hybrid\DivX265.exe" --input - --size 1920x1080 --bitrate 10000 -aqo 2 --interval 5 --framerate 50 -o "C:\Temp\park_22_13_13_8610_01.265"

in a command prompt window?
(+ with 'prefer ffmpeg' enabled reencoding works, right?)

[Gravitator]

(+ with 'prefer ffmpeg' enabled reencoding works, right?)

then works
Deintelace: Auto,Prefer FFmpeg-on > ok
Deintelace: Auto,Prefer FFmpeg-off > crash
Deintelace: off,Prefer FFmpeg-on > crash

[Selur]

will fix

[Gravitator]

Here are VP9-2pass

[Selur]

I know what the problem is, it has nothing to do with the encoder, so stop posting debug outputs.

[Gravitator]

ABR also not working
I had a working version, but it is a hybrid replaced by another

[Selur]

It will not work with any encoder unless I fix the bug.

[Gravitator]

Perhaps it lacks the AVX? core2duo

[Selur]

Like I wrote: I know the cause of the problem and no it has nothing to do with AVX.

[Gravitator]

I found the > problem causes 64-bit (32 bit is fine)
https://forum.videohelp.com/threads/360831-Looking-for-up-to-date-working-and-static-vp...=1#post2287227

[Selur]

The main problem is a bug in the avisynth script generation or more precise when Hybrid generates one and when not, the vpxenc not working for you is another problem.

[Selur]

Did you check the last test version I send you?
(the problem in the thread you linked to was fixed a while ago)

[Gravitator]

Y4M-fixed

[Gravitator]

use the 32bit VP9? Or refrain (although the quality is he inferior HEVC)

[Selur]

For me vpxenc 64bit works fine on all my systems, so there's nothing I can do about that.

[Gravitator]

For me vpxenc 64bit works fine on all my systems, so there's nothing I can do about that.

you have AMD?
-------
what will the holders core2duo check anyone

[deadrats]

@Selur:

the thing is that i can't really post a debug report because the encoding goes fine, it's the results that are all F'ed up and i don't believe it's the fault of hybrid, i think the problem lies with vpxenc, because i've been able to reproduce the problem with media coder, which also supports vp8/9 encoding.

in a nutshell, with interlaced input, if i choose to de-interlace and i choose vp8 encoding, the resulting picture is as if someone cut it in half vertically and spliced it back together the wrong way. in other words, assume you had a picture of a horse, the output is the frame cut in half and if the head was on the right side now it's on the left side.

but it's worse than that, the colors are all wrong also, the resulting picture is like a black/white grey scale but with a greenish tinge to it, with vertical greenish lines on either edge of the video.

with a progressive picture, the picture comes out properly oriented but the weird color problem is their.

with vp9 encoding, the encoding pretends to finish but i'm left with one of two things, depending on what container i chose: either a dummy file that can't be flayed back by any player including gom, vlc, mpc, mpc hd, pot and ffplay throws out an error message about incorrect markers or a really absurdly small file in the 20kb range that contains nothing.

i can reproduce this with both your software and media coder, the encodes seem to go fine, and in fact adding insult to injury, media coder has an active preview of the encode so you can see how it's going, during it's encode it seems that everything is going fine but...

interestingly xmedia recode which also supports vp8 (but not vp9) produces a usable output (though low quality no matter what settings i use) and the latest ffmpeg using the batch file another poster supplied produces a working vp9 file, though those results can only be played back by ffplay.

i don't know, there's something odd going on with the vpxenc binary that you and Stan use in your respective software.

it doesn't really matter, maybe one day vp9 will be mature enough with some more development and everything will be fine.

[Selur]

might a bug I fixed that a few week ago which happened due to a mess up where the vp9 guys added y4m input support but in the same patch destroyed the support for all other inputs,.. (I added a workaround, added it to the vp9 bugtracker and the dev posted that the problem on their side should now also be fixed)
-> you might want to test the latest vpxenc
(working on a new Hybrid release which fixes some avisynth mess-up)

[deadrats]

where can i get the latest vpxenc? and i assume i can just copy it into the hybrid directory and give it a shot?

[Selur]

latest Hybrid should come with the latest version (compiled yesterday using: https://github.com/jb-alvarado/media-autobuild_suite), but I messed up something related to avisynth, so the latest Hybrid version might still crash unrelated to vpxenc
(working on it)

[Selur]

uploaded a new version

[deadrats]

ok Selur, i just downloaded and tried your latest version, some funny things happened.

i loaded one of my favorite test subjects, a 32 minute clip from an adult dvd, interlaced mpeg-2 with ac3. i loaded up the file and since you mentioned about avisynth, i chose yadif de-interlace (not the avisynth version), aac audio, vp9 and mkv. i added the job, started the job and the job completed a short time later, error free, but the resulting file was just under 30mb, when it should have been about 900mb. needless to say it was a dummy file, filled with null data, i checked it with every app i could think of, there was just nothing there.

on a lark, i decided to try with avisynth de-interlacing, i chose qtgmc, otherwise same settings as above and this time it did crash according to the gui right when it tries to create the mkv file with mkv merge. i checked the temp folder and much to my surprise a complete .vp9 file was created and not only that it plays back flawlessly with mpc, i can even seek with it. and the quality is surprising, vp9 is a pretty damn good codec, i know this is liable to start a flame war in some forums but i would dare to say it's better than x264 and maybe on par with divx's hevx.

[Selur]

If you can recreate the yadif case where only a dummy file was created, please create a debug output of the whole process. (Seems like I missed some bug which I wanted to have fixed with the latest release.)

Problem with judging vp8&vp9 is that their 2pass rate control totally fails to hint any specified target.
I guess Google doesn't care that much about hitting a specific target size but both vp8 and vp9 really do a bad job in this regard.

[deadrats]

i was able to recreate the dummy file, just under 30mb, here's the debug report. i hope a level 5 debug report is good.

[Selur]

Argh, I see the problem:
Avisynth doesn't deinterlace since 'Yadif -custom' is not an avisynth deinterlacer (so far so good), the bug is that the internal flag that Avisynth is used for deinterlacing gets enabled and thus mencoder will not deinterlace the content later.
Since vpxenc doesn't support encoding of interlaced content it simply produces trash.
->will fix that tomorrow evening (since I'm out all day)