I'm in the same boat here. I want to be able to have 4K @60hz. I'm hoping for 4K 10bit HDR support soon somehow (devs must be working on library updates, don't they?). I wonder if a Ryzen 1600 would be sufficient or whether it would be helpful to raise the Ghz (Ryzen 1600x) or number of cores (Ryzen 1700). I'd like to go for the non-X Versions to keep the TDP/noise in the HTPC low if that's possible.
Also how much GPU power is needed for that? In Nvidia terms GTX 1060? 1070? Or AMD 560/570/580? Or Vega?
Since I'm coming from a mac I can't experiment much and have to buy the right hardware...

madshi wrote:
Chainik wrote:

We could ask you to add Vapoursynth processing into madVR smile You know, many people dream of SVP integrated into madVR...

I'm absolutely open to that. Not right now, too busy with other stuff, but sooner or later. Would you mind sending an email to my email account (madshi (at) gmail (dot) com), so that when I'm ready to look into that, we can talk via email, if that's alright with you? I think that would be more efficient than using the forum.

That would be SO great. Still hoping for news on that :-)

> I mean - you don't need madVR's "smooth motion" if SVP already gives video with the exact screen refresh rate (not 59.94 but something like 60.135)
But this still means SVP comes first, MadVR after, right?
(sorry for asking again, I'm on Mac platform right now and can only see SVP working pretty good with 1080p Stuff. But before I'll invest in a Windows HTPC this is a must have: 2160p24 HEVC HDR input, MadVR HDR->SDR conversion, SVP 60fps output - all in a plex friendly environment (Kodi with plugin or PMP))

Chainik wrote:

only the video renderer knows the exact vsync times
however you can set "To screen" + "Force the exact value" as a target rate in SVP

I don't know where to put this answer... is it regarding the MadVR+SVP setup?

Regarding "MadVR will always be last": seems logical because it's the renderer, but in terms of data processing having MadVR first convert HDR to SDR (or other MadVR scaling stuff etc) and then letting SVP interpolate frames seems less work than first blowing up those 24 HDR frames to 60 (which isn't possible yet as I have learned - no HDR processing) and then let MadVR convert 60 HDR frames to SDR. That's why I thought: the place where MadVR's Smooth Motion takes place would be perfect to let SVP do the frame rate conversion :-)

dlr5668 wrote:
ronny wrote:

Is there a way to have MadVR first do the HDR->SDR conversion with 2160p24 SDR output and after that letting SVP do the frame interpolation to have 2160p60 SDR (8bit or 10bit?)?

You cant do it. Madvr will always be last

:-(

It would be great if SVP could replace or supplement MadVR's "Smooth Motion" Setting. That would be a killer feature. @Chainik, maybe something to build together with Madshi? :-)

Is there a way to have MadVR first do the HDR->SDR conversion with 2160p24 SDR output and after that letting SVP do the frame interpolation to have 2160p60 SDR (8bit or 10bit?)?