madVR - high quality video renderer (GPU assisted)

[Joniii]

Using 1080p23 in display modes, changes to 24p even with PAL DVD's. Also using 720p50 or 1080p50 causes some occasional crashes when entering full screen or windowed.

[nevcairiel]

Originally Posted by DragonQ

Surely 2x is rarely used for luma.

Like madshi pointed out, 2x will be useful in the future when watching 1080p on a 4K display (which happens to be 3840x2160, 2x 1080p)

So it may be rarely used today, but it may gain importance in the future.

[leeperry]

and here's a practical example of why 2X/3X TV/PC conversions were necessary, that's the original untouched DVD: http://www.discogs.com/Various-Burt-...elease/2274558

and now its ffdshow histogram:

results speak for themselves:





vintage tape encodes often end up sloppy like this IME, I guess that's what happens when careless engineers work on the case..maybe these were 0-255 in the first place and went through several PC>TV conversions duh

PQ is too good to be true in deinterlaced 59.94fps / Jinc3 AR / proper gamut mapping & the right levels conversion of course

[pie1394]

Originally Posted by leeperry

Yeah I was recently wondering the same stuff as this was discussed ages ago and 16/9 1440*1080 stuff is really a GPU hog here, but I'm quite sure that madshi wouldn't force double scaling anyway.

Many terrestrial-broadcasted HDTV programs are still encoded with 1440x1080 16:9 AR mode due to channel's bandwidth allocation consideration. For those very computation intensive algorithms, I guess it won't be a waste of time to design a dedicated optimization for such 4:3 H-scaling factor on Luma and 8:3-H + 2:1-V on Chroma to be displayed at 1920x1080.


With Jinc3+AR scaling + Per-pixel-adaptive deinterlacing, GTX260+ is not even powerful enough for any content displayed at 1920x1080. I have to set madVR to use Lanczos3+AR or turn off Anti-Ring option.

The newest madVR's Jinc3+AR 2x mode performance improvement now makes GTX260+ fast enough to handle those interlaced 1920x1080i30 4:2:0 contents displayed at 1920x1080p60. Without this improvement, the GTX260+ is even not fast enough to handle such content with only Chroma Jinc3+AR scaling.

Thus I wonder how many GPUs are really powerful enough to handle the critical case with Jinc3+AR mode?

With the progressive contents, GTX260+ is still quite capable of handling various materials with Jinc3+AR. There is no need to tell about newer GPUs with similar or more stream processor units.


The GT200b's (Tesla core) CUDA unit design is not as efficient as GF1xx's (Fermi core) or GK10x's (Kepler core). I just hope such old-school GPU is still capable of handling Jinc3+AR scaling on most cases w/o sacrificing nVidia's post-processing quality on HDTV contents.

[6233638]

I don’t know that I would spend €200 on a new video card just for Jinc AR scaling, especially if something like Lanczos 3 AR is an option for you.

I think most of us with higher-end video cards probably bought them for other purposes (most likely gaming) with madVR being a secondary concern.

Who knows if the card you go out and buy for Jinc 3 will be enough for some future developments, or if madVR will get a lot more efficient in the future? (E.g. Hard-coded optimisations for common sizes like 360/480/576/720 scaling, to 1080)

[DragonQ]

Originally Posted by nevcairiel

Like madshi pointed out, 2x will be useful in the future when watching 1080p on a 4K display (which happens to be 3840x2160, 2x 1080p)

So it may be rarely used today, but it may gain importance in the future.

True.

Tis still depressing that I can't use any of the higher quality algorithms on a current generation IGP. I guess Trinity would be better, as will Haswell.

[DragonQ]

Originally Posted by pie1394

Many terrestrial-broadcasted HDTV programs are still encoded with 1440x1080 16:9 AR mode due to channel's bandwidth allocation consideration.

In which countries? I know the UK doesn't use 1440x1080 any more and, AFAIK, the US never did since they seem to prefer 720p/60 when bandwidth is limited.

[aufkrawall]

I found each seperate device for presentation and DXVA processing helpful for 4k content and DXVA decoding: Without, render queue is very unstable.
No problems with software decoding, then it can be off.

Edit: I also think presented frames in advance should be set to 8 (at least) by default, 4 is definitely too few for 4k or other heavy stuff (10 bit I444 etc).

[Mangix]

http://www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU?pid=105#pid105

It seems that even though madVR is telling D3D(or whatever) to switch to 60Hz, it ends up switching to 59Hz. Definite bug.

[DragonQ]

Pretty sure that's a Windows 8 bug.

[kerman]

It says to support with external dxva decoders, but if I enable coreavc dxva acceleration I get a full green screen... is it a bug??

[e-t172]

Originally Posted by Mangix

http://www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU?pid=105#pid105

It seems that even though madVR is telling D3D(or whatever) to switch to 60Hz, it ends up switching to 59Hz. Definite bug.

"It's not a bug, it's a feature!"

[turbojet]

Is there any way to play 2 videos simultaneously with dxva2 resizing without a bunch of dropped frames?
It's not a load issue, 2 videos with Jinc work fine on same hardware.

[pie1394]

Originally Posted by DragonQ

In which countries? I know the UK doesn't use 1440x1080 any more and, AFAIK, the US never did since they seem to prefer 720p/60 when bandwidth is limited.

You are right. it is not so widely used now...

So what format does the BBC1 HD (DVB-T2 8MHz ?) use now?

I just realized that I have not watched any BBC One HD sample made from 2012. The latest one I seen was from 2011.
It looks like all BBC HD contents have been sent in 1920x1080 format since May 30, 2012...
The experiments were made since 2011 Wimbledon...


As I can tell, the Japan (ISDB-T 6MHz), Austrilla (DVB-T 7MHz?) terrestrial programs based on MPEG-2 video, they are still 1440x1080.

About the Korea (ATSC, DMB), 1920x1080 MPEG-2...

About the China (DMB), its HDTV program is 1920x1080 although still encoded with MPEG-2 format.

About the Hong Kong (DMB-T 8MHz) and Taiwan (DVB-T 6MHz), the HDTV programs are 1920x1080 encoded with H.264.

[pie1394]

Originally Posted by michkrol

First of all, thanks for your continued hard work on MadVR. A really good piece of software.

I've encountered a rather strange bug, happens randomly and with quite specific settings. Here's how to reproduce:

1. Enable both "use separate device for presentation" and "use separate device for DXVA processing".
2. Set "DXVA2" for image up-/downscaling.
3. Play a h264 10bit file in windowed mode, while using downscaling (or upscaling).
4. The video is "jumping", as if instead of next frame, the previous frame gets rendered.
   What I mean is instead of frames 1 2 3 4, you get frames 1 2 1 4 or something.

Same file works fine with one of the "use separate device ..." options disabled or when using either other scaling algorithms or no scaling. Also other files work perfectly.

<... cut ... >

Intel HD 4000 + drivers v2875
Windows 7 (x64)
MadVR v0.85.7
MPC-HC Lite 1.6.6.6391 (32bit of course)
LAV Filters 0.54.1, but also happens if using MadVR's internal decoding

1. This issue also randomly happens to my ION system with the same setup, especially at 50% zoom window mode.
2. Driver version does not seem to matter. GeForce driver 306.97 or 310.70.
3. Not only H.264 Hi10p contents, it also happens to generic Bluray 24fps contents.
4. Same contents are repeatly verified with Bilinear luma scaling or MPC-BE64 + EVR. They just look ok.


The madVR's CPU usage is still somewhat higher than the EVR's. The difference is very obvious with the FHD H.264 Hi10p contents.

With P10 input contents, DXVA scaling causes higher CPU loading than Bilinear scaling on 1920x1080p24 --> 960x540p60 at window mode. This makes the C2D P8600@2.4GHz overloaded and it causes frame dropping. Change the Luma scaling to Bilinear, and it is about 75 ~ 90%. If MPC-BE64 + EVR is used, the CPU loading is just within 45 ~ 60% range.

Maybe the 64-bit Lav video decoder has some advantages over the 32-bit one due to compiler optimization from 8 additional GPRs in x86-64 mode.

[Mangix]

Originally Posted by e-t172

"It's not a bug, it's a feature!"

which basically means that in my case, defining a resolution of 59.94Hz and not one of 60.00Hz is the only way to "fix" this. Oh well.

[annovif]

Originally Posted by nevcairiel

Like madshi pointed out, 2x will be useful in the future when watching 1080p on a 4K display (which happens to be 3840x2160, 2x 1080p)

So it may be rarely used today, but it may gain importance in the future.

Hello, a curiosity : Do you know why the marketing tell us that 4k is four time high definition ? 1080p*4 is a highest resolution than the sony 1000 4k matrix has .

Sorry for my very bad English
Good Year, Fabio

[nevcairiel]

Originally Posted by annovif

Do you know why the marketing tell us that 4k is four time high definition ?

Because it is.
You can fit four 1080p images into one 4k image.



The sides are only 2x the size of course, but the overall image area is 4 times 1080p, which means the number of pixels increases by a factor of 4.

Do the math:
3840*2160 = 4*1920*1080

[jmone]

Consumers are so used to MegaPixel count I wish they would just stick to this as "4K" is really 8MP.

DVD = 0.3MP (NTSC) or 0.4MP (PAL)
720p = 0.9MP
1080p = 2MP
4K = 8MP

[shawkie]

I'm running MPC-HC + madVR on an HD4000. At the moment I have disabled both the internal MPEG2 decoders in MPC-HC and enabled the Intel decoders in madVR instead. I'm having a couple of problems with DVD menus. Firstly, I'm not getting any kind of highlight on the selected menu item - this is going to make it impossible to navigate the menu using a remote control. Secondly, on "The Business" (UK) the menu doesn't respond to the mouse either.