Search options (Page 2 of 2)

YES! i got my svptube working again i would have been really sad if i lost it

Ok, i will try again maybe i was just stupid for installing the 2017 64 bit VC......
Maybe i will need to restart when i am fucking around with VC ++ setups.

EDIT

Ok if i use VC 2015 64 bit, svptube refuses to load.
If i use the 2015 x86 version it runs normally.

Maybe that is why some svp users can't get svptube to work.

Anyway for now i have to go back to the x86 version because i really like and need svptube, maybe you know how to go from here.

EDIT2

Ok, now it seems i can install the x86 version and the x64 version together and svptube works again with the x64 2015 installed together with the x86 version .
I don't know what was fucking with my installation before i suspect my old 2015 x86 version was of another revision. And when i used the same revision of x64 and x86 it worked fine

Ok back to checking if that fixed my vapoursynth problems.......

Sorry, no such luck.
But at least i have a working svptube and a working VC++ 2015 x86 and x64 installation now, it sounded like i should need that.

And i still can't get the inbuilt mpv working with vapoursynth scripts from svp. And that is really strange since mpc-gt can find it inside mpv64 but mpv itself can't find vaporsynth's script that is inside its own directory.....weird.
Or maybe it can find them but not start them for some reason.

I am guessing that "VS - Could not initialize VapourSynth scripting." error is happening in the mpc-gt case also but the log isen't printing it out or picking up that it is happening.

Here is the log from the svp mpv

Some more testing trying to figure this out.......

When i run echo %PATH% & echo %PYTHONPATH% in cmd the path show up like they should.

If install python 3.6 installer and vapoursynth i can run vapoursynth from the python client app.
And if i install phyton embedded plus vapoursynth portable in a directory together that works as it should.

But why don't SVP's mpv vapoursynth work.....i don't get it.
Python works on my system with vapoursynth alone, but not through svp and mpv i mean they are right there in the same directory together why can't it start properly

If i remove mpv-1.dll it dosen't start at all for me, it just gives an error message asking for that file.

I am guessing that indicate that my path/phytonpath environment variables didn't work, right?
Because otherwise mpc-qt without the mpc-1.dll should read that from the mpv64 directories i think.

But something is wrong.......

No Madvr dosen't yet support HDR output.
What it does support is a very high quality HDR to SDR conversion, so you can watch HDR clips on a non HDR connection with some retained quality enhancement to the SDR version of the clip. If you crank up your backlight(for LCD screens)/OLED light setting and tune madvr's HDR conversion setting for it.

But for some reason madvr and LAV filter dosen't pick up the HDLeaders releases as being HDR BT.2020 files, as it does work with the various demo-uhd3d.com files correctly. I don't know why.
The right media info metadata seems to be included in the mkv.
The HDLeader releases is reported to work on LG HDR 4k and Samsung HDR 4k screens inbuilt players.
One tricky thing is that some releases have ATMOS audio, and at least the LG's can't play that so you will have to remux in som lesser & supported audio track from another release.

As far as i think it works is, HDLeader uses Zeus BT.709 WCG 4k releases and then reinserts the HDR curve with the SMPTE ST2086 static metadata in the mkv somehow.
But i really don't know how he does it, he reveal some info if you read the comments in the 1337x site, but it is really not much to go on.

I don't have access to a real UHD-BR discs or a player, but i have tested a HDR BT.2020 HDLeader release and a "normal" 4k BT.709 Zeus release of the same movie (Mad Max).
And.......it looks AMAZING

The HDR mkv does activate the HDR function on a compatible LG TV and it does look better (much more intense from the HDR on anything bright and much wider colour palette from the WCG features) than the straight 4k 10 bit 4:2:0 BT.709 Zeus rip. And just the straight Zeus rip looks already more than great. But HDR + WCG on top of that is an whole other level.

I have checked out several of the releases and i think it is legit as far as 4k HDR UHD Rip. Of course i can't compare with the real disc.

The day madvr or another renderer/player with high grade chroma upsampling & 3D lut support + SVP supports HDR output through the new HDR windows 10 interface/API, it will look better than any UHD-BR standalone player can offer
And I still hold a hope that madshi will add vaporsynth interface one day to madvr.

So bottom line, if you have a HDR screen and no UHD-BR disc or player.
YOU have to try it out it will blow you away Of course depending on how good the screen is though.

The general consensus seems to be, anything LG 4K OLED panel based (LG/Loewe/Panasonic) is the best, then the various high end Samsung and Sony FALD LCD screens and then everything less begins to be less impressive for maximum HDR dynamic range impact.
In terms of maximum contrast and highest light output that the screens can support.

*********
EDIT update

I checked these HDLeder 4K BT.2020 with HDR releases some more.

And unfortunately there is some problems with them.
He has used Zeus normal BT.709 4k UHD release and reinserts the HDR curve with the SMPTE ST2086 static metadata in the mkv.

But he also expands the normal compressed BT.709 gamut to WCG DCI BT.2020.
And the result is over saturated colors

On an LG TV you can switch the Color gamut to standard from wide and it will look right again but still with glorious HDR.
This should be possible in madvr if madvr support HDR output in the future also.