madVR - high quality video renderer (GPU assisted)

[huhn]

same RGB range question for my old AMD laptop. in the video settings under colour there is the setting dynamic range. the options here are full, limited or leave this option unticked. unticked appears to be the same as full though. not sure if theres really a difference here. I unticked all video & quality options in the AMD settings just to be sure drivers dont mess with the content. so should I leave the dynamic range option as well unticked or set it to full?
these setting shouldn't have na effect on madVR but you can use defaults.

with crimson you should think about using custom.

madvr: is currently set to display expects PC levels (default).

with my panasonic plasma (VT60) I can choose HDMI range normal (default setting) or full. when I set it to full though then black becomes gray. but according to "(1) Display wants 0-255. GPU and madVR are consequently also both set to 0-255." setting it to full range should be right, shouldnt it?

if your GPU is set to full range RGB yes.

but there are 3 point with levels.
madVR, GPU and TV screen. so make sure your GPU is set to the correct output type too.

[x7007]

I have an issue with Madvr + Potplayer + Exclusive mode D3D11 10bit . I'm using Lav Filter 0.67 and CUVID 970GTX

Randomly if I go exclusive mode and back to windowed the frames goes on but repeat themselfs, it's like shaky video that you see the frame before, and madvr ctrl+j shows numbers that goes back and forward fast. I tried many things to fix the issue, it happens in windows 10 . I can't find the reason it happens. I try prerender 3-4-6 and such , nothing helps. Nvidia Control panel set to Prerender 3 for Potplayer. Decoder Queue , Upload Queue, Render queue, present queue, all goes lower .
Normally when it works fine
Decoder 16-16 / 16
upload ueue 12-12 /12
render queue 12-12 /12
present queue 3-4 /4

when it doesn't
14-16
10-12
1-2
1-4 randomly can be 2-4 too

There are 10-15 dropped frames every sec.


Can someone please help me understand the issue ?

EDIT

Changing the Display bit from 10 bit to 8 bit fix the issue .. what can be the problem with the 10 bit ?

EDIT 2 :
I used Potplayer 32 bit taking the settings from old installation every time. So I've installed the 64bit and set it from start. the stuttering doesn't happen but I'm getting Render queue 2-4 /12 present queue 1-3 /3 only in exclusive mode. windowed mode works fine with the right queues .

EDIT 3 :
Ha never mind I forgot that I have set 1 prerender in the NVCP for all programs and I didn't have the potplayer x64 to the list for 3 . so that's why

EDIT 4
What does it mean if I have Async Reader in Grey in the Filters menu where Lav Filters and Madvr are showing ? For some reason Potplayer doesn't show me the Chapters lines on the media player bar with little marks, only if I reinstall and not using my old INI and registry files they appear, anyone know what could it be and if I can restore them after I use my settings ?

EDIT 5
Using Prenderer in NVCP 2 and not 3 fix the issue it seems. should the NVCP Prenderer be lower than the MADVR prerender ?

The async I mean is in the picture including the little Chapters bars , you can see I have only one, there should be more, every movie I have one or none, but madvr does detect them and I can choose them from the madvr try icon, with the time.

http://0.t.imgbox.com/Wnu1E6Gg.jpg (http://imgbox.com/Wnu1E6Gg)

[Razoola]

If you set madvr to sending 16-235 and GPU driver to sending 0-255 then you will be sending 16-235 (16 reference black and 235 reference white, plus BTB&WTW). So your TV have to be set to accept 16-235. Desktop will be wrong levels.

I get a better picture using full range on my panel. The desktop being wrong is not an issue as I don't use the panel for desktop application. If I use the setting as you suggest there I get a washed out picture.

[Thunderbolt8]

but there are 3 point with levels.
madVR, GPU and TV screen. so make sure your GPU is set to the correct output type too.how can I do that when its not the setting in madVR and not that one in CCC?

edit: found this here https://pcmonitors.info/articles/correcting-hdmi-colour-on-nvidia-and-amd-gpus/
in that picture there is a "my digital flat panels" tab which I dont have with my drivers (I use laptop drivers from leshcatlabs)

[iSeries]

I thought you were upscaling DVDs? This would be a 2x to 2.25x resize, no?

Isn't SD to 1080p a 5x upscale? (PAL has a total pixel resolution of 414720, 1080p has 2073600). 720p to 1080p would be 2.25x?

[nevcairiel]

Isn't SD to 1080p a 5x upscale? (PAL has a total pixel resolution of 414720, 1080p has 2073600). 720p to 1080p would be 2.25x?

Scale factor relates to the horizontal/vertical dimensions, not the overall pixel count. 1080p -> 4K is a 2x/2x upscale in that sense, and 720p > 1080p is 1.5x
This is generally handled this way because algorithms like NNEDI exactly double the resolution in one dimension per run, so running NNEDI once would double the vertical resolution (and its internally just run twice to double both dimensions).

[iSeries]

Scale factor relates to the horizontal/vertical dimensions, not the overall pixel count. 1080p -> 4K is a 2x/2x upscale in that sense, and 720p > 1080p is 1.5x
This is generally handled this way because algorithms like NNEDI exactly double the resolution in one dimension per run, so running NNEDI once would double the vertical resolution (and its internally just run twice to double both dimensions).

Thanks - although still a little confused lol So 576p to 1080p is only around 1.9x? . I have doubling set to activate for =>1.5x upscales and quadrupling to activate for =>3x upscales. I think these are the defaults? Anyway, I'm pretty sure quadrupling is activated when playing SD with these settings.

[Manni]

with crimson you should think about using custom.


Unless I missed it, Crimson doesn't allow to set the dynamic range, even when using custom (or tools like RadeonMod, which don't support this in Crimson either).

That's why I went back to Catalyst 14.12, as the only way to get the correct levels with both MadVR and PowerDVD (which I use when I need full BD menus or 3D) was to set the driver to RGB Limited, which isn't recommended for MadVR, as it means the GPU is converting levels after MadVR.

Not an issue if you only use MadVR obviously, as Crimson can be set to RGB Full and MadVR to whatever gives the correct levels on your display.

[mawen1250]

With the latest version (v0.89.19), the matrix of YCgCo video is recognized as BT.709 and results in wrong color.

[huhn]

Unless I missed it, Crimson doesn't allow to set the dynamic range, even when using custom (or tools like RadeonMod, which don't support this in Crimson either).

That's why I went back to Catalyst 14.12, as the only way to get the correct levels with both MadVR and PowerDVD (which I use when I need full BD menus or 3D) was to set the driver to RGB Limited, which isn't recommended for MadVR, as it means the GPU is converting levels after MadVR.

Not an issue if you only use MadVR obviously, as Crimson can be set to RGB Full and MadVR to whatever gives the correct levels on your display.

i have no clue what you are even doing with the dynamic range.
the GPU output can still be changed.

[livache]

with my panasonic plasma (VT60) I can choose HDMI range normal (default setting) or full. when I set it to full though then black becomes gray. but according to "(1) Display wants 0-255. GPU and madVR are consequently also both set to 0-255." setting it to full range should be right, shouldnt it?

On my EU ST50 I don't have an option to select full range for HDMI inputs. It only shows for DVI->HDMI.
And if I set 16-235 in madvr and 0-255 output on my nvidia gpu I can see 236-255 passing through. 0-15 don't.
0-255 in madvr and 16-235 on GPU is fine.
From the little information I could gather about this, it seems the full range option for HDMI inputs is only present on US models of these plasmas.


another thing: with my TV theres also an option called HDMI content type from which I can choose Auto (default), graphics, foto or off. which is the recommended setting here when watching movies? auto, graphic and foto look all the same, that setting is a little bit brighter than off.

HDMI content type just switches the viewing preset on the TV based on what I set in the nvidia driver if the feature is enabled on the TV. I have it in the menu in Setup/ Link Settings /HDMI Content type [AUTO/off].

Setting Games in nvidia driver switches the TV to Game preset.
Movies -> Cinema preset
Full Screen Videos -> True Cinema
Desktop Programs -> True Cinema
Photos -> True Cinema
Auto Select -> True Cinema

[MistahBonzai]

Unless I missed it, Crimson doesn't allow to set the dynamic range, even when using custom (or tools like RadeonMod, which don't support this in Crimson either).


AMD Radeon settings > Display > Additional Settings (Old Radeon menu pops-up here) > My Digital Flat Panels > Pixel Format > Select "(Full RGB)

Got that? ;)

[x7007]

Hi , I really want help about the situation , I know I fixed it but I want to know the reason or what is the setting you guys are using . it was working always good before, so I'm not sure what changed.

http://forum.doom9.org/showthread.php?p=1752157#post1752157

If you can answer all the questions please, but importantly.

Should the NvCP Prerender should be less than the setting in Madvr ?

Exclusive mode + 8 bit + NVCP Pre -3 + Madvr 3 or 4 there are no issues
Exclusive mode + 10 bit + NVCP Pre -3 + Madvr 3 or 4 there are issues
Exclusive mode + 10 bit + NVCP Pre -2 + Madvr 3 or 4 there are no isues

If Nvidia prerender have Max Prerender of 4 , is that what you select ? or even so if it's 3 , what do you select in Madvr ? because if I select too high 6 or 8 the Render Queue is not filling and Prerender is at 1 and not full too.

How do I know which is the best setting because no one said their settings.

So is the thing in potplayer that only after fresh installation I can see the chapters marks on the movie, and while using my old INI file there is only 1 mark but madvr does show all chapters from the tray icon. i'm not sure what setting control that.

[Asmodian]

On my EU ST50 I don't have an option to select full range for HDMI inputs. It only shows for DVI->HDMI.
And if I set 16-235 in madvr and 0-255 output on my nvidia gpu I can see 236-255 passing through. 0-15 don't.
0-255 in madvr and 16-235 on GPU is fine.
From the little information I could gather about this, it seems the full range option for HDMI inputs is only present on US models of these plasmas.

Setting 0-255 in madVR and 16-235 on the GPU cannot send BtB or WtW. The GPU compresses 0-255 to 16-235 and there is nothing above 255 or below 0 to compress into 236-255 or 0-15. When set the other way around (madVR 16-235, GPU 0-255) there isn't anything clipping 0-15.

How are you testing? Are you using the AVS-HD test patterns (http://www.avsforum.com/forum/139-display-calibration/948496-avs-hd-709-blu-ray-mp4-calibration.html)?

If you cannot set your TV to accept full range you still do not care about being able to send BtB or WtW information. On a properly calibrated display 0-16 is all 0% brightness or 100% black and 235-255 is all the same 100% brightness. This means that even if everything below 16 gets clipped you don't care because you cannot see it.

Maybe it is your TV doing the clipping? Is it calibrated such that 0-16 is 0% white but 235 is less than 100% white? Maybe it pushes the brightness past a nominal 100% white for WtW information? Plasmas don't have a well defined 100% white in my experience. E.g. A full screen area of 100% white will be much less bright compared to a 15% screen area of 100% white.

[Asmodian]

Should the NvCP Prerender should be less than the setting in Madvr ?

Prerender should be on "Application Controlled"

How do I know which is the best setting because no one said their settings.

There are no "best" settings for everyone, if there were madshi would remove all the other options. Also rule 12. :p

So is the thing in potplayer that only after fresh installation I can see the chapters marks on the movie, and while using my old INI file there is only 1 mark but madvr does show all chapters from the tray icon. i'm not sure what setting control that.

This is something with PotPlayer, not madVR.

[GCRaistlin]

without OSD screenshots it's hard to judge.
OK, I've performed some investigations.
MPC-HC settings:
Video Renderer: madVR
Audio Renderer: ReClock
ReClock settings:
[x] PAL SpeedDown (force to 24fps)
madVR settings:
list all display modes madVR may switch to: 1080p24, 1080p25, 1080p30, 1080p50, 1080p60
[x] treat 25p movies as 24p (requires Reclock or VideoClock)
All other settings are at their defaults, unless noted otherwise for the particular case.

PAL

http://i68.tinypic.com/2ce2r07.jpg
madVR doesn't switch the display to 24 Hz.
madVR:
[ ] treat 25p movies as 24p (requires Reclock or VideoClock)
The display refresh rate set to "24 Hz (Interlaced)".
http://i66.tinypic.com/65reqa.jpg
Interlacing is visible, lot of dropped frames... madVR seemed to be right not switching the display to 24 Hz.
madVR:
[x] disable automatic source type detection (.) force film mode
http://i64.tinypic.com/11ttrep.jpg
LAV Video:
[x] Enable YADIF Deinterlacing (.) 50p/60p (Video)
http://i65.tinypic.com/2uehb46.jpg
As far as I understand YADIF deinterlacing in video mode doubles the frame rate - ReClock reports "50 fps". madVR, though, still considers 24 Hz as the appropriate video mode. That's where dropped frames came from. Bug?
BTW it is only true by madVR's "(.) if in doubt, deactivate deinterlacing". By "(.) if in doubt, activate deinterlacing" madVR switches the display to 50 Hz and the result looks like the next case.
madVR:
[x] disable automatic source type detection (.) force video mode
http://i67.tinypic.com/2l9gq5u.jpg

NTSC

http://i63.tinypic.com/242u7w1.jpg
The picture looks bad.
madVR:
[x] disable automatic source type detection (.) force video mode
http://i64.tinypic.com/28rrdf.jpg
The picture still looks bad.
madVR:
[x] disable automatic source type detection (.) force film mode
http://i65.tinypic.com/2wp49om.jpg
The picture looks better but interlacing is still visible.
madVR:
(.) if in doubt, activate deinterlacing
[x] disable automatic source type detection (.) force film mode
http://i68.tinypic.com/8wbi8z.jpg
The picture is the same as in the previous case but the display is 24 Hz.
LAV Video:
[x] Enable YADIF Deinterlacing (.) 50p/60p (Video)
http://i66.tinypic.com/dh9tnn.jpg
The picture looks even better but madVR switched the display to the wrong mode again so we have lot of dropped frames.
LAV Video:
[x] Enable YADIF Deinterlacing (.) 25p/30p (Film)
http://i65.tinypic.com/2jg1pih.jpg
The picture is the same as in the previous case but no dropped frames.


So let's sum up:

madVR doesn't take into account doubled frame rate when YADIF deinterlacing is enabled.
YADIF deinterlacing seems to be better than madVR's.


but the NTSC SD file is 60 HZ and should be watched at that.
As you can see above, it can be played perfectly at 30 Hz, too.

[x7007]

Prerender should be on "Application Controlled"



There are no "best" settings for everyone, if there were madshi would remove all the other options. Also rule 12. :p



This is something with PotPlayer, not madVR.


obviously understood. but what about the issue with 10 bit ? it didn't happened before and it only happens when I try to use prerender 3 in the nvidia or some kind mix that the NVidia prerender is higher than Madvr. what can be the cause ?

And no matter what prerender I put I don't have the issue with 8 bit. it just happens with 10 bit. I tested MPDN and 10 bit works fine there. I just try to find the issue, if it's madvr or potplayer.

And what is Async Reader filter ?

Btw, should I use Lav Splitter or Lav Splitter Source ?


Somehow I don't know, I had my Display in Madvr Ctrl+J showing always 100.00000HZ steady, but I changed stuff and updated drivers and now it's 100.000355-361HZ not steady as before. does anyone knows what can possibly change the Display HZ ? I have laptop G751JT with 970GTX , using windows 8.1, I didn't change nvidia drivers, just updated Chipset drivers , Madvr , Potplayer. and some windows update hotfixes which I don't know if it happened before it or after.
Should it be best if Display and Composition rate would be 1:1 with no clock deviation ? cause that's what I had before some changes.

Can Gsync work in potplayer or MPDN ? cause trying to enabling it the Render queue is 4-12 /12 and Present queue 0-4 /4


http://forum.doom9.org/showthread.php?p=1752157#post1752157

http://forum.doom9.org/showthread.php?p=1752157#post1752157

EDIT 2 :

I figured what was the problem with the Chapters bookmark
while the movie playing I went to right click > Playback > Chapters/Bookmark > Clear all marked . now I have all the chapters marked correctly.


EDIT 3 :
If I am using in Nvidia control panel Prerender Use the default or 3 , it causing the issue to appear straight away at the 2nd full screen entering.


EDIT 4 :
On my laptop using NVCP prerender application default (3) and Madvr Pre Render 4 works fine. windows 8.1 Render queue 12-12 /12
But on my desktop NVCP prerender application default (3) and Madvr Pre Render 4 Render queue 2-4 /12 and present queue 3-4 /4 , why is the render queue cut ? and what could have issue when the issue seems to happens when actually the Render is full.

MPDN 10 bit works fine,

[huhn]

OK, I've performed some investigations.
MPC-HC settings:
Video Renderer: madVR
Audio Renderer: ReClock
ReClock settings:
[x] PAL SpeedDown (force to 24fps)
madVR settings:
list all display modes madVR may switch to: 1080p24, 1080p25, 1080p30, 1080p50, 1080p60
[x] treat 25p movies as 24p (requires Reclock or VideoClock)
All other settings are at their defaults, unless noted otherwise for the particular case.

PAL

http://i68.tinypic.com/2ce2r07.jpg
madVR doesn't switch the display to 24 Hz.
madVR:
[ ] treat 25p movies as 24p (requires Reclock or VideoClock)
The display refresh rate set to "24 Hz (Interlaced)".
http://i66.tinypic.com/65reqa.jpg
Interlacing is visible, lot of dropped frames... madVR seemed to be right not switching the display to 24 Hz.
madVR:
[x] disable automatic source type detection (.) force film mode
http://i64.tinypic.com/11ttrep.jpg
LAV Video:
[x] Enable YADIF Deinterlacing (.) 50p/60p (Video)
http://i65.tinypic.com/2uehb46.jpg
As far as I understand YADIF deinterlacing in video mode doubles the frame rate - ReClock reports "50 fps". madVR, though, still considers 24 Hz as the appropriate video mode. That's where dropped frames came from. Bug?
BTW it is only true by madVR's "(.) if in doubt, deactivate deinterlacing". By "(.) if in doubt, activate deinterlacing" madVR switches the display to 50 Hz and the result looks like the next case.
madVR:
[x] disable automatic source type detection (.) force video mode
http://i67.tinypic.com/2l9gq5u.jpg

NTSC

http://i63.tinypic.com/242u7w1.jpg
The picture looks bad.
madVR:
[x] disable automatic source type detection (.) force video mode
http://i64.tinypic.com/28rrdf.jpg
The picture still looks bad.
madVR:
[x] disable automatic source type detection (.) force film mode
http://i65.tinypic.com/2wp49om.jpg
The picture looks better but interlacing is still visible.
madVR:
(.) if in doubt, activate deinterlacing
[x] disable automatic source type detection (.) force film mode
http://i68.tinypic.com/8wbi8z.jpg
The picture is the same as in the previous case but the display is 24 Hz.
LAV Video:
[x] Enable YADIF Deinterlacing (.) 50p/60p (Video)
http://i66.tinypic.com/dh9tnn.jpg
The picture looks even better but madVR switched the display to the wrong mode again so we have lot of dropped frames.
LAV Video:
[x] Enable YADIF Deinterlacing (.) 25p/30p (Film)
http://i65.tinypic.com/2jg1pih.jpg
The picture is the same as in the previous case but no dropped frames.


So let's sum up:

madVR doesn't take into account doubled frame rate when YADIF deinterlacing is enabled.
YADIF deinterlacing seems to be better than madVR's.



As you can see above, it can be played perfectly at 30 Hz, too.

pal
1. of cause it doesn't switch to 24p is has 50 FPS in this case.
2. you should never switch to 24p if video deinterlacing is used.
3. madVR has now 25 FPS so it is working
4. madVr is missing or ignoring the information that the stream is 50/60p. could be an lavfilter problem or could be a problem in madVR
5. working as intended

NSTC

1. what GPU driver and settings are used? the AMD driver settings alter deinterlancing which can easily result in a terrible picture.
2. it should look the same but it doesn't. nothing has change it is still using the same AMD DXVA deinterlacer.
3. source is for sure true interlaced so film mode can't work.
4. film mode should alwasy switch to 24p so not sure about 3.
5. madVr is missing or ignoring the information that the stream is 50/60p. could be an lavfilter problem or could be a problem in madVR
6. working as intended

madVR doesn't have an deitnerlacer it is using the DXVA deinterlancer for your video card. which is pretty broken on crimson...

25/30 deinterlacing should be avoided under any cost. madVR can use 25/30 DXVA interlacing the option can be found under trade quality for performence and yeah shouldn't be used.

edit: there is no need to add 1080p30 if 1080p60 is flawless same for 1080p25 if 1080p50 exist.

[x7007]

It seems the fix is using NVCP Pre renderer 3 and use Exclusive mode 3 as long as use Exclusive mode + 10 bit. Can someone help me with the other questions ? Async Reader , Lav Splitter or Lav Splitter Source ?

And all the rest of the questions are in the posts below.


http://forum.doom9.org/showthread.php?p=1752157#post1752157

http://forum.doom9.org/showthread.php?p=1752157#post1752157

http://forum.doom9.org/showthread.php?p=1752242#post1752242

[Manni]

AMD Radeon settings > Display > Additional Settings (Old Radeon menu pops-up here) > My Digital Flat Panels > Pixel Format > Select "(Full RGB)

Got that? ;)

Yes, and that has nothing to do with the ability to delect a different dynamic range once you have selected the pixel format at driver level. :)

In Catalyst, once you select the pixel format (say RGB Full, which is the best option for MadVR) you can also select, separately, a dynamic range option (16-235 or 0-255) for other software like PowerDVD which use windows rendering, unlike MadVR. This allows to get the right video levels for both MadVR and PowerDVD, especially when you use a display set to HDMI standard (16-235) to work with other video sources, like a bluray player or a satellite box.

That's the option that's gone in Crimson, so the only way to get the correct levels for both MadVR and PowerDVD is to set the driver to RGB Limited, which isn't ideal for MadVR as it means the driver is changing the levels behind its back.

This level issue is more difficult to solve with PowerDVD due to a levels mismatch between 2D and 3D in RGB Full, but that's a different issue (and one I'm struggling to get past the first level support of Cyberlink as they don't understand it).

Also Crimson crushes white in 3D (it only resolves up to 230 irrespective of the pixel format) with PowerDVD, which is another reason why I switched back to Catalyst 14.12.

Got that? ;)

[Marsu42]

Personally, I hate NLS, in any configuration. Try a movie with a horizontal camera pan. It looks totally aweful IMHO. Which is why this feature has very low priority for me.

Right, I guess I have to stick with ffdshow - as most 4:3 clips are sd resolution, it doesn't require *that* much cpu power.

As for the NLS look: I didn't try it on a lot of series yet, but i depends on the style they're shot in. At least with "Start Trek DS9", people amazingly stand in the middle of the frame most of the time - i.e. no distortion. To the edges, there's always some sci-fi station, planet or shuttle stuff that looks stretched just like before. And they almost never do panning, but cuts just like legacy Star Trek. I guess a lot of 4:3 sitcoms or older series with lots of talking are the same way, i.e. you can extend them to 16:9 w/o major annoyances.

[x7007]

Yes, and that has nothing to do with the ability to delect a different dynamic range once you have selected the pixel format at driver level. :)

In Catalyst, once you select the pixel format (say RGB Full, which is the best option for MadVR) you can also select, separately, a dynamic range option (16-235 or 0-255) for other software like PowerDVD which use windows rendering, unlike MadVR. This allows to get the right video levels for both MadVR and PowerDVD, especially when you use a display set to HDMI standard (16-235) to work with other video sources, like a bluray player or a satellite box.

That's the option that's gone in Crimson, so the only way to get the correct levels for both MadVR and PowerDVD is to set the driver to RGB Limited, which isn't ideal for MadVR as it means the driver is changing the levels behind its back.

This level issue is more difficult to solve with PowerDVD due to a levels mismatch between 2D and 3D in RGB Full, but that's a different issue (and one I'm struggling to get past the first level support of Cyberlink as they don't understand it).

Also Crimson crushes white in 3D (it only resolves up to 230 irrespective of the pixel format) with PowerDVD, which is another reason why I switched back to Catalyst 14.12.

Got that? ;)

When you watch PowerDVD in 3D mode do you use different profile in the TV to compensate for the 3D mode darker display , what I mean in 3D it's more dark and you need to level the brightness by 5-4

[Manni]

When you watch PowerDVD in 3D mode do you use different profile in the TV to compensate for the 3D mode darker display , what I mean in 3D it's more dark and you need to level the brightness by 5-4

Yes of course you adjust levels in the display in 3D (I use a separate user mode for 2D and 3D anyway), but it would be nicer if the levels matched between 2D and 3D in PowerDVD as it would make is easier to find a way to match levels with MadVR.

Irrespective of that, you still can't resolve 230-235 in Crimson in 3D, the contrast settings on the display does nothing, above 230 is just hard clipped by the driver in 3D. You can change the brightness setting in Crimson, but that affects both brightness and contrast, so it's pretty much useless.

Not sure if this is a Crimson issue or a PowerDVD issue with Crimson, as TMT seems to have the same issue in 3D (white crush in Crimson) I'd say it's a Crimson issue that's not been picked up by Cyberlink yet.

Anyway, pretty much OT in a MadVR thread :)

[KoD]

I find the above posts somewhat confusing. Some parts sound right, some parts sound wrong. If it were me reading them, I would not know what to do.

Let's recap:
- desktop / games / images / anything computer generated luma and color info is stored as RGB values and uses the entire range of values [0, 255] for each color channel: a RGB triplet of (0, 0, 0) is black, and a triplet of (255, 255, 255) is white;
- in case of movies and TV material, the image info is usually stored with the luma and color information encoded not as RGB values but as YCbCr / YV12 / YUY2 (or similar) values; the normal content (in between a full white screen and a completely black one) does not get encoded using the entire range of values allowed by this luma/color encoding scheme, but only part of it; if they exist, values outside the range used by normal content is what we call the BtB (blacker than black) and WtW (whiter than white) info
- if you try to convert the original YCbCr / YV12 / YUY2 or whatever values to RGB values, you can use two approaches:
1. do the conversion so that normal content ends up using the [16-235] range of values for each of the R / G / B color channels (it's what we call the "limited" range)
2. or do the conversion so that normal content ends up using the [0-255] range of values for each of the R / G / B color channels (it's what we call the "full" range)

- for option 1, if you really want, you may perform the color conversion to RGB so that some of the BtB and WtW data might get passed through as values below 16 and above 235; and in this case the actual RGB output might really have some values outside the [16-235] range;
- however, BtB and WtW data is not supposed to be visible, so any of the info beyond [16-235] is in fact supposed to be discarded
- moreover, in case of option 1, something that is supposed to be absolute black in the movie, ends up as a (16, 16, 16) RGB triplet, so it's a darker shade of gray, not the black that you get for (0, 0, 0); similar, something that is supposed to be absolute white in the movie, ends up as a (235, 235, 235) RGB triplet, which is a grayish white, not the white which is (255, 255, 255)
- so, not surprisingly, option 1 is not the one used to view movies on a PC

- when using madVR with the default setting of "display expects PC range", the color conversion from YV12/ etc to RGB and the color range conversion in option 2 are performed at the same time; the movie black ends up as a RGB value of (0, 0, 0), the movie white ends up as a value of (255, 255, 255), and the BtB and WtW info is discarded as it should be (well, I simplify here and I'm considering the case where no additional color space conversions and corrections are being done by madVR)

- at this point you have madVR outputing image info as RGB using the entire range of values [0-255] per color channel (a "black" in your movie is shown just as black as "black" on your desktop, in your games, in a photo, etc), and you need to send this to your display

- and this is where your display input limitations get involved, and you have to make a choice according to what was said in previous posts on this thread:
-- if you know your display doesn't accept a full range RGB signal at its inputs, then you have to make your GPU take that [0-255] output from madVR as well as everything else that is displayed on your PC, compress it to a range of [16-235] values where black is now (16, 16, 16) and white is (235, 235, 235), and send this color range compressed signal to your TV; and you instruct your GPU to do this by selecting the output as "limited" in your video card driver settings; then the TV will take this range-compressed input and will properly show what was at (16, 16, 16) as black and what was at (235, 235, 235) as white and everything in between too; and this is how both movie files and PC "native" content gets displayed with the proper colors on the TV;
-- if you know your display accepts a full range RGB signal at its inputs, then all is perfect - just make sure the GPU setting is indeed to send the signal as "full" range, and your TV properly auto-detects this (or you help it by manually setting that port as "full range" in the TV settings)


As a word of caution, when testing if everything looks fine there is indeed one thing to be aware of: the TV might not be properly calibrated, and it might crush blacks and/or whites, as Asmodian has suggested. In other words, the brightness / contrast / RGB controls are so configured that it makes some range of input values all show as black or as white, even though the TV internal processing does in fact see the [0-16] and [235-255], and would be able to properly display them if the TV would be calibrated.

Just for fun, these are some color patches I made for myself to test the visibility of the extremities of the RGB range. Each square is a solid color, in case of darker patches they are (0,0,0), (1,1,1) and so on, and for whites they are (255,255,255), (254, 254,254) and so on. They are useful not only to see if the desktop PC colors are all visible, but also to see if there are no nasty casts on dark and light grays after performing a color calibration: Test patches.7z (http://www61.zippyshare.com/v/skwO2MSX/file.html)

[GCRaistlin]

1. of cause it doesn't switch to 24p is has 50 FPS in this case.
Because of deinterlacing? ReClock reports "25 fps".
4. madVr is missing or ignoring the information that the stream is 50/60p. could be an lavfilter problem or could be a problem in madVR
ReClock can see that the stream is 50 fps. Does it mean that this is a madVR problem?
5. working as intended
Yes but it requires manual change of the default madVR's deinterlacing configuration. What's even worse is that YADIF deinterlacing gives worse result in this case: http://i65.tinypic.com/30kxfkk.jpg
1. what GPU driver and settings are used? the AMD driver settings alter deinterlancing which can easily result in a terrible picture.
HD5770, Catalyst 14.4, WinXP SP3.
2. it should look the same but it doesn't. nothing has change it is still using the same AMD DXVA deinterlacer.
My fault, here is the new screenshot for "NTSC 1" case: http://i63.tinypic.com/sfi168.jpg
You can see that it differs both from "NTSC 2" and "NTSC 3".
3. source is for sure true interlaced so film mode can't work.
madVR's deinterlacing film mode differs from YADIF deinterlacing film mode? "NTSC 6" does work, and you said that it works as expected.
4. film mode should alwasy switch to 24p so not sure about 3.
Maybe it was temporary issue 'cause next time I checked it switched to 24p.

madVR doesn't have an deitnerlacer it is using the DXVA deinterlancer for your video card.
So should I always enable YADIF deinterlacing? But, as I wrote above, for PAL (at least for my sample) it gives worse result than madVR's deinterlacing forced film mode.
Does it all mean that for best results I should have:

madVR deinterlacing set to (.) force film mode - always.
YADIF deinterlacing enabled and set to film mode - when playing a NTSC SD video.
YADIF deinterlacing disabled - when playing a PAL SD video.

?

25/30 deinterlacing should be avoided under any cost
25/30 deinterlacing = film mode?

madVR can use 25/30 DXVA interlacing the option can be found under trade quality for performence and yeah shouldn't be used
Are you talking about "use half frame rate for DXVA deinterlacing"? It is unchecked (as it is by default).

[nevcairiel]

DXVA deinterlacing is a DXVA2 feature, and DXVA2 is not officially supported on Windows XP, hence your results may vary from anyone running an OS where DXVA2 is actually officially available.
How much of it actually works on XP depends on many various factors, so you may not be getting the highest quality deinterlacing your GPU can do.

[GCRaistlin]

So lack of DXVA2 support in WinXP is the actual reason of bad madVR deinterlacing results?

[huhn]

Because of deinterlacing? ReClock reports "25 fps".
it is 50 FPS because of deinterlacing. so yes. no sure what's wrong with reclock.

ReClock can see that the stream is 50 fps. Does it mean that this is a madVR problem?
not sure. maybe maybe not. reclock doesn't see 50 FPS if madVR is deinterlancing

Yes but it requires manual change of the default madVR's deinterlacing configuration. What's even worse is that YADIF deinterlacing gives worse result in this case: http://i65.tinypic.com/30kxfkk.jpg

HD5770, Catalyst 14.4, WinXP SP3.
it should be decent. not sure what is wrong maybe the source is to bad.
My fault, here is the new screenshot for "NTSC 1" case: http://i63.tinypic.com/sfi168.jpg
You can see that it differs both from "NTSC 2" and "NTSC 3".
i need more time to check this.
madVR's deinterlacing film mode differs from YADIF deinterlacing film mode? "NTSC 6" does work, and you said that it works as expected.

yes totally. YADIF is a deinterlancer film mode is an IVTC algorithm.
it tries to restore the orginal frmae rate and onyl works on telecine source not interlanced sources.
So should I always enable YADIF deinterlacing? But, as I wrote above, for PAL (at least for my sample) it gives worse result than madVR's deinterlacing forced film mode.
Does it all mean that for best results I should have:

madVR deinterlacing set to (.) force film mode - always.
YADIF deinterlacing enabled and set to film mode - when playing a NTSC SD video.
YADIF deinterlacing disabled - when playing a PAL SD video.

?
not sure what you should do normally DXVA deitnerlancing works totally fine.

best is to use film mode for "film" and deinterlancing for videos. automatic detection doesn't work.
25/30 deinterlacing = film mode?

Are you talking about "use half frame rate for DXVA deinterlacing"? It is unchecked (as it is by default).
just don't use it. it's more for slow hardware.
as said before it is not the same as film mode IVTC.

[David]

- for option 1, if you really want, you may perform the color conversion to RGB so that some of the BtB and WtW data might get passed through as values below 16 and above 235; and in this case the actual RGB output might really have some values outside the [16-235] range;
- however, BtB and WtW data is not supposed to be visible, so any of the info beyond [16-235] is in fact supposed to be discarded
- moreover, in case of option 1, something that is supposed to be absolute black in the movie, ends up as a (16, 16, 16) RGB triplet, so it's a darker shade of gray, not the black that you get for (0, 0, 0); similar, something that is supposed to be absolute white in the movie, ends up as a (235, 235, 235) RGB triplet, which is a grayish white, not the white which is (255, 255, 255)
- so, not surprisingly, option 1 is not the one used to view movies on a PC

Wrong.

(16,16,16) is black when TV is in limited range (TV levels, 16-235) and brightness is adjusted in the TV to show 16 as black.

When madvr is set to 16-235 and GPU output to RGB 0-255 (PC Levels, Full range) then levels range is not converted so 16 is black. Your TV must show 16 as black so you have to adjust brightness for that. This is the same as with a standalone bluray player when speaking about range levels.

The problem with that configuration comes with desktop, pictures, etc. as them have (1,1,1) as black and your TV show 16 as black then 0-15 range will be show as black too.

[huhn]

why do you have to change anything at your TV for that?

as long as the TV thinks it is limited range everything should be fine.

[Thunderbolt8]

I tried using lots of versions of CCC, old and new, original AMD (even the original HP laptop driver) and those from leshcatlabs and no matter which version I choose I do not have the "My digital flat pannels" tab in CCC (laptop: HP pavilion m6 1000-sg with 7670M and windows 7 64-bit). meaning I cannot change the RGB levels range that way. Does anyone know if a kind of toggle exists for that? A toggle which would let me switch between PC and TV levels for that display which is connected to my laptop via HDMI.

[Manni]

I tried using lots of versions of CCC, old and new, original AMD (even the original HP laptop driver) and those from leshcatlabs and no matter which version I choose I do not have the "My digital flat pannels" tab in CCC (laptop: HP pavilion m6 1000-sg with 7670M and windows 7 64-bit). meaning I cannot change the RGB levels range that way. Does anyone know if a kind of toggle exists for that? A toggle which would let me switch between PC and TV levels for that display which is connected to my laptop via HDMI.

If you use catalyst, try RadeonMod, it has an option to change the dynamic range, unfortunately it doesn't work with Crimson.

[David]

why do you have to change anything at your TV for that?

as long as the TV thinks it is limited range everything should be fine.

You have to adjust brightness in your TV with test patterns to be sure it is showing 16 as black. If brightness is not correct black could be shown in the range (0-15) and you get washed picture or it could be shown above 16.

[nevcairiel]

So lack of DXVA2 support in WinXP is the actual reason of bad madVR deinterlacing results?

Who knows, but its certainly a possibility that it won't function properly.
Unless you can do a direct comparison on similar hardware on a newer OS, its hard to judge what exactly is causing your issues.

[Thunderbolt8]

If you use catalyst, try RadeonMod, it has an option to change the dynamic range, unfortunately it doesn't work with Crimson.had a look at it but cant really find a clear option for that. the only thing I could spot was DynamicRange_DEF and DyanmicRange_ENABLE_DEF in the DXVA tab. but since its the DXVA tab I dont know if that will work with madVR (would it if I use LAVVideo with copy back?). Also, I dont seem to be able to configure the display or connection for which I want this.

edit: setting the first one to PC and activating the 2nd one seem to have worked. when I now watch content on my TV then normal/limited range devours shadow detail while it looks correct with full range.

[KoD]

Wrong.

(16,16,16) is black when TV is in limited range (TV levels, 16-235) and brightness is adjusted in the TV to show 16 as black.

When madvr is set to 16-235 and GPU output to RGB 0-255 (PC Levels, Full range) then levels range is not converted so 16 is black. Your TV must show 16 as black so you have to adjust brightness for that. This is the same as with a standalone bluray player when speaking about range levels.

The problem with that configuration comes with desktop, pictures, etc. as them have (1,1,1) as black and your TV show 16 as black then 0-15 range will be show as black too.
David, there's nothing wrong with what I said. You are interpreting it from the point of view of someone who does not care if the desktop and everything else looks right, and choses to configure the GPU output as "full" range while his TV is expecting "limited range". This is not what I do, as it does not make any sense to me. And if you do this, you are very likely not getting the gamma curve right anyway either. Your issues with "making sure the black is at 16" are stemming from this also.

[David]

KoD, since this is a madvr thread it does not make any sense to me sending limited range (TV levels) when TV is expecting full range (PC levels). This is why that configuration is not cosidered when speaking about madvr and range levels:


My recommendation is always to set configure your display so that it expects PC levels (full range). This has 2 important benefits: (1) Levels will be correct for everything, including games, photos, applications and video playback. (2) There should be no problem with image quality.

If your display can't do PC levels, or if you have good reasons for not using this solution, then you have 2 alternative solutions:

(a) Either set the GPU to limited range and madVR to PC levels. This means madVR will render to PC levels and the GPU will afterwards stretch the madVR output (and desktop, games, applications, photos etc) to limited range. Using this approach still has the benefit of having correct levels everywhere. But image quality might suffer because the GPU usually uses a rather bad stretching algorithm, which can introduce banding artifacts.

(b) Or set the GPU to fullrange and madVR to TV levels. This will result in good image quality (no artifacts) and correct levels for video playback. However, desktop, games, applications and photos will have wrong levels.

madshi (http://forum.doom9.org/showpost.php?p=1635534&postcount=19433)


madVR handles the input levels automatically, you don't need options or anything for them. You can override it on a per-file basis, but its only useful if madVR detects the wrong input level. The input level is defined by the file, not any setup in your display chain.

For the level settings, there is basically 3 combinations of settings:

(1) TV accepts PC/Full levels: Set madVR to PC/Full, set GPU to PC/Full - This is usually considered the better option, if your TV can do it.

(2) TV accepts only TV/Limited levels:
(a) Set GPU to PC/Full and set madVR to TV/Limited
(b) Set GPU to TV/Limited and set madVR to PC/Full
In the second case, both a and b have small drawbacks.
With (a), you get crushed black/white on the desktop, but everything is perfect in madVR.
With (b), you get proper colors everywhere, except that the GPU is doing the PC range -> TV range conversion, which may not be the highest quality and end up in banding.

NEVER set both madVR to TV/Limited AND GPU to TV/Limited, you get double range compression.

Because of these drawbacks with either a or b, its usually recommended to use (1) if your TV accepts it. Its only "downside" is that BTB/WTW are lost, but its arguable if those are even worth keeping. If you insist on WTW/BTB, the 2a setting is probably the next best for video quality, if you can live with crushed black/white on the Desktop.

However you set it up, the test patterns should only show 16-235 after calibration.

nevcairiel (http://forum.doom9.org/showthread.php?p=1678269#post1678269)


If your display supports 0-255, then setup is easy - set everything to 0-255 and you don't have to think about it.
If your display does not support 0-255, you probably should not output 0-255 from the video card (using madNvLevelsTweaker.exe) and will have to compromise.

The first option is to have everything set to 0-255, except for the video card output, so that on the output stage it is being converted to 16-235. This means that all content is kept at the same levels (desktop & video) but the conversion to 16-235 on output may introduce banding. If you are using your PC for more than just video playback, this is the setup you have to use.

However, if you are going to be using the computer exclusively for watching videos through madVR, you have a second option. What you can do is set the video card output to 0-255, and set madVR to 16-235.

This will avoid the potential banding from having the video card compress the output levels to 16-235. But it will make anything that is not video look terrible, as anything on the desktop will still be outputting 0-255, and all values above 235 and below 16 will be clipped. (very high contrast image with no shadow/highlight detail)

I would only suggest doing this if your are only using the PC for video playback, and are seeing banding from the video card outputting 16-235.

6233638 (http://forum.doom9.org/showpost.php?p=1620589&postcount=18062)

[Plutotype]

I neither have any such content nor any technical spec. Also there are no decoders available for that. But my best guess is that it might be compatible to "conventional" HDR. I don't really know, though.

2.2.3.3.5.2 Dolby Vision
The Dolby Vision video stream is composed of a BDMV HDR video stream and a Dolby Vision enhancement layer video stream. The enhancement layer is an HEVC video stream with embedded Dolby Vision metadata. The Dolby Vision is characterized by the followings:

color primaries: BT.2020 with non-constant luminance
EOTF(Electro-Optical Transfer Function): SMPTE 2084
Bit depth: 12bit (combination of BDMV HDR video stream and Dolby Vision enhancement layer)
Enhancement layer video stream: 1920x1080 resolution, same frame rate with the BDMV HDR video stream, 100Mbps or lower together with the BDMV HDR video stream


http://www.blu-raydisc.com/assets/Downloadablefile/BD-ROM_Part3_V3.0_WhitePaper_150724.pdf

[livache]

Setting 0-255 in madVR and 16-235 on the GPU cannot send BtB or WtW. The GPU compresses 0-255 to 16-235 and there is nothing above 255 or below 0 to compress into 236-255 or 0-15. When set the other way around (madVR 16-235, GPU 0-255) there isn't anything clipping 0-15.

How are you testing? Are you using the AVS-HD test patterns (http://www.avsforum.com/forum/139-display-calibration/948496-avs-hd-709-blu-ray-mp4-calibration.html)?

If you cannot set your TV to accept full range you still do not care about being able to send BtB or WtW information. On a properly calibrated display 0-16 is all 0% brightness or 100% black and 235-255 is all the same 100% brightness. This means that even if everything below 16 gets clipped you don't care because you cannot see it.

Maybe it is your TV doing the clipping? Is it calibrated such that 0-16 is 0% white but 235 is less than 100% white? Maybe it pushes the brightness past a nominal 100% white for WtW information? Plasmas don't have a well defined 100% white in my experience. E.g. A full screen area of 100% white will be much less bright compared to a 15% screen area of 100% white.

You read it wrong. I wrote that setting 0-255 in madvr and 16-235 on GPU produces correct output.
It's 16-235 madvr and 0-255 gpu that's problematic.
And yes, the display is perfectly calibrated.
The pictures thunderbolt posted are mine.


he made some pictures using the AVSHD calibration disc:

madvr 16-235, GPU 0-255: http://someimage.com/TIY4nz2
madvr 0-255, GPU 16-235: http://someimage.com/uy1kWWj

[e-t172]

http://www.blu-raydisc.com/assets/Downloadablefile/BD-ROM_Part3_V3.0_WhitePaper_150724.pdf

That's a very interesting link you got there, thanks. I'm taking the liberty of posting a few quotes that I found quite insightful:

This format defines three types of HDR video formats: BDMV HDR, Dolby Vision and Philips HDR. The BDMV HDR is the HDR video format which is mandatory for player in this specification. The Dolby Vision and Philips HDR are the optional HDR video technologies for players and discs.

Regarding BDMV HDR:

HDR content for Ultra HD Blu-ray will be created while considering the authoring guideline that over 1000 cd/m² should be limited to specular highlights which are expected to be a small percentage of the picture area
MaxFALL indicates the maximum value of the frame average light level. HDR content for Ultra HD Blu-ray will be created while considering the authoring guideline that the MaxFALL should not exceed 400 cd/m².

Apparently, Dolby Vision is a separate layer on top of BDMV HDR, meaning that even if a player doesn't support Dolby Vision, it would still be able to display HDR content from the BDMV HDR stream in a Dolby Vision enabled disc. It's not clear to me what improvements Dolby Vision is supposed to bring compared to just using BDMV HDR alone.

Philips HDR, on the other hand, is supposed to help with the perilous task of correctly displaying HDR content on a monitor that might not be able to reach the required peak luminance:

The Philips HDR SEI messages is a metadata to control down-conversion of the dynamic range of the BDMV HDR video stream to a dynamic range of the connected display.

Section 2.2.3.3.6 pretty much states that regarding HDR to SDR conversion, it's a mess and almost nothing is standardized; the current recommendation is for authors to package an SDR stream alongside the HDR one if they want accurate SDR presentation.

[GCRaistlin]

it is 50 FPS because of deinterlacing
Deinterlacing in video mode, wrong auto-detected, right? As in "PAL 4" case?

YADIF is a deinterlancer film mode is an IVTC algorithm.
it tries to restore the orginal frmae rate and onyl works on telecine source not interlanced sources.
But madVR's deinterlacing film mode does work in "PAL 3" case. It gives the better result (http://i63.tinypic.com/sfi168.jpg) than madVR's deinterlacing video mode (http://i68.tinypic.com/x7nva.jpg). Is the source telecine?

I tried YADIF deinterlacing in ffdshow - madVR recognizes double frame rate. So the problem is perhaps in LAV. Also, the picture I got with it for PAL is the same I got with LAV (worse than I got with madVR's film mode deinterlacing). Does it mean that YADIF deinterlacing algorythm is objectively worse in this case and the bug report will be senseless?

[huhn]

Deinterlacing in video mode, wrong auto-detected, right? As in "PAL 4" case?
if i'm not mistaken than madVr doesn't have a working auto detection for film oder video mode deinterlancing.
i don't think so anymore it should be a problem with lavfilter. it is working with ffdshow so it is very unlikely a problem in madVR and the automatic detection should have anything to do with it. madVR gets an progressive stream from lav when yadif is used so this detection shouldn't be used what so ever.


But madVR's deinterlacing film mode does work in "PAL 3" case. It gives the better result (http://i63.tinypic.com/sfi168.jpg) than madVR's deinterlacing video mode (http://i68.tinypic.com/x7nva.jpg). Is the source telecine?

i don't think so. a short sample will tell me.

I tried YADIF deinterlacing in ffdshow - madVR recognizes double frame rate. So the problem is perhaps in LAV. Also, the picture I got with it is the same I got with LAV (worse than I got with madVR's film mode deinterlacing). Does it mean that YADIF deinterlacing algorythm is objectively worse in this case and the bug report will be senseless?

it is impossible to use SVP on a interlanced stream so YADIF is very important for AMD user and CUVID is broken on windows 10 and has some other limitations so there is currently "only" yadif for SVP.

[GCRaistlin]

madshi, 2 feature requests:

The possibility to choose constant OSD background color. When the video sample has too bright background (like the sky) it's really hard to read OSD from a distance (on the projector).
The delay before madVR switches the display to the appropriate mode. When I try to drop the player's window to the second monitor it often gets dropped back on the primary one because of immediate mode switch.

[GCRaistlin]

i don't think so anymore it should be a problem with lavfilter. it is working with ffdshow so it is very unlikely a problem in madVR and the automatic detection should have anything to do with it. madVR gets an progressive stream from lav when yadif is used so this detection shouldn't be used what so ever.
We're still talking about "PAL 1" case (http://forum.doom9.org/showthread.php?p=1752240#post1752240), aren't we? YADIF is off for it. So I'm not sure what LAV problem you're talking about.

i don't think so. a short sample will tell me.
PAL from http://forum.doom9.org/showthread.php?p=1752069#post1752069

it is impossible to use SVP on a interlanced stream so YADIF is very important for AMD user and CUVID is broken on windows 10 and has some other limitations so there is currently "only" yadif for SVP.
What is SVP?
YADIF is very important, yes, but, as I said above, sometimes it gives worse results than madVR's film mode: http://i66.tinypic.com/15yk9c.jpg (compare it to madVR's deinterlacing screenshots here (http://forum.doom9.org/showthread.php?p=1752369#post1752369)). Is it the issue it is worth to report of?

[nussman]

madVR film mode can (nativ progressive content) restore the original frames. Result is perfect.
Don't know which mode LAV uses for yadif, but I dont think there is an auto film/video detection and so it is in "video mode"?
"Video Deinterlacer" do not give you always a perfect results for film content.
Imho this works as it should.

[Plutotype]

That's a very interesting link you got there, thanks.

Regarding Dolby Vision, here is a very good info:
http://hdguru.com/dolby-vision-tries-to-set-bar-for-hdr/
http://www.dolby.com/us/en/technologies/dolby-vision/dolby-vision-white-paper.pdf

Will it be technically possible to achieve accurate playback of the UHD BD mastered in Dolby Vision using MPC-HC/LAVfilters/madvr?

[x7007]

so if I understand correctly if I have philips 7007 which doesn't support full . should I select limited in the nvcp and madvr full ? what about setting in potplayer or mpdn. ? I get crushed black when I use that . black is too black

[x7007]

Hi, I experience lots of dropped frames after switching between fullscreen and windowed modes, the way I describe below:

What I do is this: start playback-> all is fine, go fullscreen -> everything is still fine, then go back to windowed mode -> all still fine -> go back to full screen -> now lots of frames dropped, it does not recover itself unless I pause the video, and then resume. With 0.88.12 it was enough to pause once, and then playback would be smooth again after resuming; with 0.88.19 once is often not enough, I have to pause twice. It looks like the render queue does not recover staying at 1-3 or 2-3, even though the decoder, subtitle and upload queues fill up to their normal stats. The present queue also ends up with the same fill status as the render queue.

Some details: I'm using MPC, with its internal filters for h264 playback of mkvs, it happens on both 8 bit and 10 bit content, irrespective of whether I use software or hardware decoding. Happens only when using D3D11 and fullscreen exclusive mode. If I use full screen windowed mode, or I use the D3D9 renderer, all is fine.

I happen to have a Sony TV which accepts 12 bit color input. When using D3D11 and fullscreen exclusive mode, the TV receives 12bit per channel input (I can see this by pressing the Info key on the remote).

Have not changed the graphics drivers since a long time ago, it's still version 347.25 on a GTX980 for me.

I have this same issue but usually it doesn't happen in 8 bit, it seems only with 10 bit, in my laptop windows 8.1 it doesn't happen with same settings, only in windows 10 .

[huhn]

so if I understand correctly if I have philips 7007 which doesn't support full . should I select limited in the nvcp and madvr full ? what about setting in potplayer or mpdn. ? I get crushed black when I use that . black is too black

most philips support fullrange RGB in PC mode if it isn't to old.

[x7007]

most philips support fullrange RGB in PC mode if it isn't to old.


If I use Full-Range I get crushed black, everything just become like what's called black crush, shadows just doesn't shown as shadows anymore.

Another question about Exclusive mode :

When entering and exiting FSE , frame dropped suppose to happen and shown in madvr OSD Statistics ? Because when entering and exiting FSE those frame dropped becomes and issue when the video try to reset itself and play the video like it is lagging behind and I have repeating frames over and over again while the render queue is dropping. even the Madvr OSD is repeating itself with the numbers you can see the numbers before in an instant while everything is stuttering. it happens as long as D3D11 FSE is enabled no matter if it's 8 bit or 10 bit. The only thing that fix it is using "Delay playback start until render queue is full" and "delay playback start after seeking too" which shows that the issue is with the render queue like I said before. but what is causing this issue only in windows 10 with D3D11 FSE ? can someone please help with this, I've been trying older madvr version , but nothing changed. Even with Delay both selected I still have dropped frames while entering FSE and exiting. I'm using CPU queue size : 16 and GPU queue size : 12 , would other numbers fix the issue ? or what could the render queue settings should I focused on. I tried to play with the prerender but 3 suppose to be the best.

pretty please someone , it was working great before , I didn't need to enable delay playback and delay after seek . I don't know what changed. I even tried older nvidia driver which didn't fix the issue. MPDN D3D11 FSE have no issues at all going and exiting.

In the end it could be an bug in potplayer, but why would same version works fine in windows 8.1 and not windows 10 ?

someone else had the same issue : https://www.doom9.org/showthread.php?p=1730672#post1730672

as a check to the post withe the Cpu and Gpu queue https://www.doom9.org/showthread.php?p=1730558#post1730558

http://forum.doom9.org/showthread.php?p=1752242#post1752242
http://forum.doom9.org/showthread.php?p=1752157#post1752157