madVR - high quality video renderer (GPU assisted)

[Nullack]

I have a Samsung UN50JU6500 UHD TV and every time MadVR changes my refresh rate to 23Hz, my TV gets kicked off of 4:4:4 at 1080p. At 1080p 60hz I can do 4:4:4 or full RGB without a problem, but when it changes to any different refresh rate, my TV no longer stays in PC mode (4:4:4). Its immediately noticeable because when it fails to pass 4:4:4 all of the image customization (RGB / White Balance) become available.

Anyone have an idea why? Does my TV only support 4:4:4 at 60hz and no other refresh rates or could this be a setting in MadVR?

Try setting the HDMI port to UHD colour mode. Read the manual for details.

[huhn]

Try setting the HDMI port to UHD colour mode. Read the manual for details.

not going to work. it's a samsung they can't do 4:4:4 outside of 60 hz and in rare cases 30 hz.

the JU6500 can't do proper 23/24p anyway so not a huge loss.

[Nullack]

My samsung does 4:4:4 from 60hz all the way down to the 30s, 24s etcetc since I enabled the UHD mode.

[Probe]

There are no specific requirements that I'm aware of. Make sure you use the latest LAV *nightly* build, but even if you don't, HDR files should still look "ok".

Please make a screenshot of the madVR Ctrl+J OSD when playing a HDR video. Don't attach it to this forum, but upload it to some image uploading/sharing host.


Thanks for the response...just before providing the OSD...I decided to play with some additional settings...I eventually resolved the issue by changing the downscale setting from Lanczos to DXVA2. I assume having the processing done by the GPU is required? I am coming from a AMD 6570 now using a gtx 960 and trying to get the consistent glitch free performance I had with the AMD...still in the experimental phase.

for the record...with the HDR feature now working I think the image at 400 nits looks great!. Thank you for your efforts.

[huhn]

sending 4:4:4 and getting 4:4:4 are two totally different things.

samsung is well know for the 60 hz limitation and for the broken 23p limitation for the not that expense screens too.

but if they fix it fine by me and about time after how many years?

[Georgel]

The source probably has a lot of source dither/grain/noise. This may be the producer's intention. Unless your screen bit depth is set really low, any of madvr's dithering algorithms shouldn't add much noise at all.

You can already turn off dither in MadVR. Rendering > Dithering > None. Use that, and compare to see if there's more or less noise. However, using no dither is always a terrible idea. You get banding and posterization artifacts.



Ordered Dithering is the lowest noise option and it is much better for Anime than rounding (None). Use Ordered Dithering, turn off "change dither for every frame", and leave on "use colored noise" for the lowest visible noise configuration. Personally I like both options off, colored noise is worse than luma noise, but the difference is subtle.

I almost always watch Anime myself.

I would be very surprised if you could see the noise from 8-bit ordered dithering with "change dither for every frame" disabled. I cannot. The noise you observed in Kaleid Liner Prisma Illya was probably not due to dithering, you don't see it in every source do you?

Please do not use "None", it makes me sad when people disable dithering. :(



Thanks for all the help!

I do not observe the noise in every anime I watch, but in some there is some noise, and it becomes visible, and kind of distracts me, because I enter a thinking mode where I ask myself if it could not be repaired.

Then I think that it was the original design that had the noise in there.

About the bit depth of the material, it is either 8 or 10 bit, where my monitor, LG Display LP173WF4-SPF1 is 10 bit (I think I remember reading this in a review (?) ).

It is totally true that some anime do not show even the least amount of noise with error diffuse 2, but Fate series seem to have quite a big amount of noise in some scenes (why?).

Thanks for all the help!

[huhn]

they simply add noise because they wanted to let a scene looks noisy.

and are you sure it is a LP173WF4-SPF1 ?
that would mean it is a 700 CR 6 bit AH IPS panel (first 6 bit IPS i have ever heard of)

http://www.panelook.com/LP173WF4-SPF1_LG%20Display_17.3_LCM_parameter_21056.html

you are maybe able to reduce the noise by setting the bit deep to 6 in madVR and you may avoid double dithering but maybe not.

edit: and yeah a 6 bit panel can look a lot more noisy in dark scene than a 8 bit panel.

[CarlosCaco]

It doesn't really matter: they are all 6bit+FRC :)


So what is the correct setting option should i put? native bit depth 6 or 8?
a i can see difference with better quality at 8 but maybe i´m wrong
what FRC doe?

[Asmodian]

1. In DX9 mode, I can't use the exclusive mode since once I able exclusive mode, the full screen is just going to be black screen.

2. Instead of the increasing of dropped frame in DX11 mode, DX9 mode increases presentation glitches a lot, one completely movie might have 200 more presentation glitches.

Again, just a reminder, I am using a laptop with 3630QM+970M, do you think this can be a problem?

This might be a problem that I hope can be fixed in the next version.
Also, could you please tell me what is the benefit of setting it to DX11? Does the graphics looks better or it's mean to be more efficient?

There are some screen shots that might give you some information
Madshi, hope this can be helpful and not boring you.

Do not use FSE if it makes something not work, the only reason for it is to improve stability so if it hurts it leave it off.

Same for DX11, no image changes, just another software path that may or may not work better.

Have you tried Windowed Oveay? (Requires both FSE and DX11 disabled).

[huhn]

So what is the correct setting option should i put? native bit depth 6 or 8?
a i can see difference with better quality at 8 but maybe i´m wrong

only testing will tell you this. i guess 6 bit will be better. seeing a difference shouldn't be really hard.

what FRC doe?

it's a version of dithering.
i have only one screen with FRC and it does a poor job with it.

[Asmodian]

So what is the correct setting option should i put? native bit depth 6 or 8?
a i can see difference with better quality at 8 but maybe i´m wrong
what FRC doe?

In my testing I preferred madVR set to 6-bit on a 6-bit panel but I am sure it depends on the display.

FRC flickers the pixel color between different 6-bit values in order to look like an 8-bit color the panel cannot display. This is not the cause of the noise you see (that is in the source) but it can make it more visible.

[py930828]

Do not use FSE if it makes something not work, the only reason for it is to improve stability so if it hurts it leave it off.

Same for DX11, no image changes, just another software path that may or may not work better.

Have you tried Windowed Oveay? (Requires both FSE and DX11 disabled).

I tried windows overlay, mpc shows "creating Direct3D device failed (8876087b), I disable both FSE and DX11

[enphenate]

It's Samsung "feature" :(

not going to work. it's a samsung they can't do 4:4:4 outside of 60 hz and in rare cases 30 hz.

the JU6500 can't do proper 23/24p anyway so not a huge loss.

sending 4:4:4 and getting 4:4:4 are two totally different things.

samsung is well know for the 60 hz limitation and for the broken 23p limitation for the not that expense screens too.

but if they fix it fine by me and about time after how many years?
Dang that sucks, my 4 year old LG 37LD450 passed 4:4:4 at all of the lower refresh rates :(

So what is my best option for watching movies with MadVR? I know the UN50JU6500 does have 24p judder but I dont notice it.

Should I play all files at 60hz while passing 4:4:4 without MadVR changing the refresh rates, or do I let MadVR choose the proper refresh rate and dealing with not passing 4:4:4? Again this is all in 1080p.

My main concern about it not passing 4:4:4 at 23hz is that I am calibrating my screen and creating a 3D LUT for MadVR, so Im trying to decide what best screen mode to create it with. Either not passing 4:4:4 at 23hz and have full control of my color and white balance, or passing 4:4:4 at 60hz in PC mode but having little control over fine tuning the screen.

Im just trying to get the best overall experience with what I can work with.

[huhn]

Dang that sucks, my 4 year old LG 37LD450 passed 4:4:4 at all of the lower refresh rates :(

So what is my best option for watching movies with MadVR? I know the UN50JU6500 does have 24p judder but I dont notice it.

Should I play all files at 60hz while passing 4:4:4 without MadVR changing the refresh rates, or do I let MadVR choose the proper refresh rate and dealing with not passing 4:4:4? Again this is all in 1080p.

My main concern about it not passing 4:4:4 at 23hz is that I am calibrating my screen and creating a 3D LUT for MadVR, so Im trying to decide what best screen mode to create it with. Either not passing 4:4:4 at 23hz and have full control of my color and white balance, or passing 4:4:4 at 60hz in PC mode but having little control over fine tuning the screen.

Im just trying to get the best overall experience with what I can work with.
think about 60 hz only with smooth motion.

if you didn't notice the judder issue at 23p than you shouldn't notice it at 60 hz because it is the same so you could disable smooth motion but i would get crazy without it.

[enphenate]

think about 60 hz only with smooth motion.

if you didn't notice the judder issue at 23p than you shouldn't notice it at 60 hz because it is the same so you could disable smooth motion but i would get crazy without it.

Im still confused at what the best option would be to use with MadVR? 4:4:4 60hz with limited calibration ability or 23hz with full calibration ability but not passing 4:4:4.

[Asmodian]

Only you can judge. What looks better to you?

[ryrynz]

Can someone give me a heads up on how filepath is used? Can it be used to cover all files under that directory and all sub directories? Also does it work with network shares? If not I'd like to have support for those.

If (filepath = "c:\users\admin\desktop") "profile" Using the above I can't get the profile doesn't activate when launching a file located in that directory. What's wrong?

[SweetLow]

Can someone give me a heads up on how filepath is used? Can it be used to cover all files under that directory and all sub directories? Also does it work with network shares? If not I'd like to have support for those.

If (filepath = "c:\users\admin\desktop") "profile" Using the above I can't get the profile doesn't activate when launching a file located in that directory. What's wrong?
RTFM ;)
filePath, fileName, fileExt e.g. "c:\movie.mkv", "movie.mkv", "mkv", _wildcards_ supported

so use if (filepath = "c:\users\admin\desktop\*.*") "profile"

[ryrynz]

RTFM ;)
filePath, fileName, fileExt e.g. "c:\movie.mkv", "movie.mkv", "mkv", _wildcards_ supported

so use if (filepath = "c:\users\admin\desktop\*.*") "profile"

I did. I think I had the network share typed wrong when I tried that the first time because adding \ and *.* were the very first things I tried when it didn't work.

[SweetLow]

i test both network and local paths - all working fine.
p.s. \*.* - shall not be the spaces between backslash and asterisk (and before backslash too)
p.p.s. and no success with non ascii symbols in path! - to madshi

[chros]

On a side note, did anyone with a '8-bit + FRC' panel make some tests displaying 10-bit with madVR with dithering disabled to compare panel's dithering to that of madVR?
Well, since panel dithering is always on you can't really compare them. But I can't see any difference between 10 bit without madvr dithering and 8 bit with madvr dithering from 10 cm (usual viewing distance is 3m :) )
And, is madVR's Ordered dithering enough to smooth out the gradients of a dithered 10-bit on a 8-bit panel or is Error Diffusion required?
Again, I don't see any difference from 10cm, so Ordered dithering would be fine.

only testing will tell you this. i guess 6 bit will be better. seeing a difference shouldn't be really hard.
In my testing I preferred madVR set to 6-bit on a 6-bit panel but I am sure it depends on the display.
Just checked on my laptop display (6bit+FRC, advertised as 16.02 million colors) with the 16 bit gradient test png image (dithering set to none in madvr): you can definitely see the difference between 6 and 8 bit output (but not above 8). So use 8bit output and ordered dithering.

Dang that sucks, my 4 year old LG 37LD450 passed 4:4:4 at all of the lower refresh rates :(
Really? How? With which refresh rates? With which hdmi port? Using dvi-hdmi? What's your graphics card?
I have the big brother but (no matter what I did) I didn't managed to get 4:4:4 with any combination that I've tried. I have to say I use hdmi-hdmi from my laptop. And this review also says that they couldn't make it work: http://www.hdtvtest.co.uk/news/lg-32ld450-42ld450-20101120901.htm
Im still confused at what the best option would be to use with MadVR? 4:4:4 60hz with limited calibration ability or 23hz with full calibration ability but not passing 4:4:4.
"with limited calibration ability" : if you have a meter than just create a 3dlut so you won't miss any of the calibration settings of your tv.
The 23hz vs 60hz is a different matter, just try it out how it looks.

Btw: do you know any display device (tv or projector) that can do 4:4:4 via hdmi-hdmi AND 23hz or 24hz???

[SweetLow]

my 4 year old LG 37LD450 passed 4:4:4 at all of the lower refresh rates



Btw: do you know any display device (tv or projector) that can do 4:4:4 via hdmi-hdmi AND 23hz or 24hz???
don't comment last post only, view the full thread :p

[Nullack]

Help please.

* Reducing GPU buffers reduces the GPU memory footprint which with just 2GB on 4K material is good for my setup especially given the need to run copyback DXVA 2 with madVR. Is there any practical problem with running just 4?

* Since I run 64bit builds of LAV, MPC-BE and madVR, and I have ample system ram at 16GB, I see no reason to change cpu decoding buffers from default. Does more of less than default decoding buffers have any practical impact?

* Whats with present frames in advance? Why do this? If it is a good thing, how many should be done? Whats the relevant factors with deciding on this setting?

Thanks

[chros]

don't comment last post only, view the full thread :p
Errr ... What do you mean? He was talking about the Samsumg tv latter on not the LG.

[ShadyCrab]

Not sure what part of the chain is the problem here, but the exact same video is being detected as having BT.601 primaries on one opening and BT.709 on the next. I've noticed this bug on other videos too. Whats worse, is that it actually changes the color of the video (mainly in the greens). Is this a video encode bug or an actual bug in madVR/LAV's detection code (also using) xySubFilter and MPC-HC). So far its only on videos were instead of the matrix being 'best guess' its 'upstream' for the matrix and 'bitstream' for the primaries (on videos were in the mediainfo just the matrix has been set as BT.709, leaving the primaries guess to the chain).

http://i.j2.io/9EM0.png
http://i.j2.io/8T2O.png
(size difference is due to poor screenshot lossless PNG crop, not due to different frame. Color difference is there on madVR itself).

[nevcairiel]

Not sure what part of the chain is the problem here, but the exact same video is being detected as having BT.601 primaries on one opening and BT.709 on the next. I've noticed this bug on other videos too. Whats worse, is that it actually changes the color of the video (mainly in the greens). Is this a video encode bug or an actual bug in madVR/LAV's detection code (also using) xySubFilter and MPC-HC). So far its only on videos were instead of the matrix being 'best guess' its 'upstream' for the matrix and 'bitstream' for the primaries (on videos were in the mediainfo just the matrix has been set as BT.709, leaving the primaries guess to the chain).

http://i.j2.io/9EM0.png
http://i.j2.io/8T2O.png
(size difference is due to poor screenshot lossless PNG crop, not due to different frame. Color difference is there on madVR itself).

If this info would be present in the bitstream, than it would also be coming from upstream LAV, and not leave madVR having to get it from the bitstream itself. Sounds like a bug in madVR to me. A sample video that shows this problem will be required, however.

[madshi]

I don't know why a soft telecine DVD remux oder vob is treated as progressive but played back at 29p by default.

that looks pointless to me.
If it's *soft* telecine then it should be played at 23p if deinterlacing is disabled. Are you sure it's 29p? If it is, then it's probably not soft telecined.

a soft telecine source is flagged progressive that's why deinterlacing isn't used.
Because HD DVDs and D-Theater captures are soft telecined and play perfectly with deinterlacing disabled. There are even some (rare) Blu-Rays with this mode. But if you want deinterlacing to be used for such sources, simply change your madVR settings to "if in doubt, activate deinterlacing". That's what that setting is for.

I'm aware that you don't necessarily share the opinion that everything must be open, which is totally fine as I agree that intellectual property should be valued. But is there a chance that you explain at some point how sharpen edges works?
Sorry, but no. It's also not necessarily the final version yet. It's a work in progress. I already have some plans to further improve it, at least the anti-ringing part of it.

should I add MADVR into NVIDIA control panel? Since so far, I only set MPC-HC run by NVIDIA graphics card but not MADVR, I don't know what application I should choose to put into the control panel.
Your media player.

These two pictures, when I was in windows mode, the render and present queue is full, but if I am in fullscreen, the queue drop to 2, and the present time is really really long.
Don't attach pictures to this forum, they often don't get approved, or with very long delays.

I found the problem!!! The reason why the render queue and the present queue drop is because of DX11, if I set it to DX9 in "general setting", the queue will get back to full, and the presenting time goes back from 16ms to 2ms(in full screen case). However, there are two problems that I have found so far:

1. In DX9 mode, I can't use the exclusive mode since once I able exclusive mode, the full screen is just going to be black screen.

2. Instead of the increasing of dropped frame in DX11 mode, DX9 mode increases presentation glitches a lot, one completely movie might have 200 more presentation glitches.

Again, just a reminder, I am using a laptop with 3630QM+970M, do you think this can be a problem?
Is that an Optimus laptop? Those are known to have certain problems. You could try installing a different driver version, maybe it helps.

There are some screen shots that might give you some information
I can't even see them because they're not approved (see above).

@madshi: the OSD font size (and maybe the font itself) changed a lot with the latest version. Is this intentional?
Yes. Forgot to mention it in the changelog.

Hi Madshi, if you choose "use half frame rate for deinterlacing", the frame time on the OSD does not change. This is with DXVA deinterlacing.
It does for me. It says: "vsync 16.68ms, frame 16.68ms" with (DXVA) deinterlacing active and "vsync 16.68ms, frame 33.37ms" if I manually disable deinterlacing.

Which is why I think if there was an option to delay playback until decoder queue is full, then there be no problem. This is a capture source. If this capture source is to be reliable to capture at full framerate all the time, the computer must be fast enough and compress it fast enough, else there be drop frames. I can trust my computer can capture fine and that once the decoder queue is full, would stay full even if it can't deliver frames faster than realtime.

Edit: I just realized, why isn't the render queue delayed until full? When I first start playback, it isn't like the render queue is full then slowly goes down to 0-2. It's 0-2 from the start.
Your source filter simply doesn't deliver frames. I've told you before, the source filter should push frames until madVR blocks. But your source filter does not. There is NOTHING I can do to make the queues fill. It's the responsibility of your source filter. The key problem is that madVR's "delay" feature waits for frames to come from the source filter while the graph is still in paused mode. And in that mode it seems that your source filter doesn't send more than 1-2 frames. It only starts sending frames when playback in unpaused, and it never sends frames fast enough ("in advance") to allow the queues to fill.

I actually thought he had done that in this version.
I was just about to write up a post asking about the GUI changes because I find them difficult to read on my 1080p screen.
With this build I'm now seeing a big proportionally spaced and anti-aliased font (http://abload.de/img/new-osd-full20oi4.png) (with bad keming (https://en.wikipedia.org/wiki/Kerning)) vs the old monospaced bitmap font (http://abload.de/img/old-osd-fullv6ohk.png).
It's worse in a window because the new stats (http://abload.de/img/new-stats-window6aoph.png) now scale with the window size and get a lot smaller than the old ones (http://abload.de/img/old-stats-windowxboxi.png).
I'm scaling the font size with the window/screen size now. I've tried many different fonts and spent many hours on this, trying to find a good solution. The biggest problem is that most fonts don't support grayscale anti-aliasing at smaller font sizes. The fonts must be rather big for them to start supporting grayscale AA. ClearType AA is supported at small font sizes, but looks terrible when transparently blended over the video frame as madVR does. So the font I'm not using (which is actually the Windows default GUI font) was the "best" compromise I could find. It's one of the VERY few fonts which supports anti-aliasing at smaller font sizes. Most other fonts look very thin and are thus also hard to read at smaller font sizes.

It's true that the font size is now allowed to get smaller if your playback window is very small. The purpose of that is to fit more of the stats into the window. If I didn't do that, the font size would be bigger which is easier to read, but a lot of the OSD content would then be cut off.

It's possible (and i use it more then decade already - to increase monitor luminance on the fly to view video and pictures :) ), but, AFAIK, there is no standard user mode API to access this feature under Win platform.
Ok, but how many displays, especially how many TVs support that?

Thanks for the response...just before providing the OSD...I decided to play with some additional settings...I eventually resolved the issue by changing the downscale setting from Lanczos to DXVA2.
Makes no sense to me that this would change anything related to HDR.

no success with non ascii symbols in path! - to madshi
You mean chinese or russian characters? Or what do you mean?

* Reducing GPU buffers reduces the GPU memory footprint which with just 2GB on 4K material is good for my setup especially given the need to run copyback DXVA 2 with madVR. Is there any practical problem with running just 4?
Bigger is better, but 4 should work ok, too.

* Since I run 64bit builds of LAV, MPC-BE and madVR, and I have ample system ram at 16GB, I see no reason to change cpu decoding buffers from default. Does more of less than default decoding buffers have any practical impact?
Higher CPU/decoder queue means more protection against CPU spikes causing the decoder queue to get empty. But usually the default should be fine.

* Whats with present frames in advance? Why does this? If it is a good thing, how many should be done? Whats the relevant factors with deciding on this setting?
That's the size of the present queue. If your GPU queue is set to 4 frames, probably it would make sense to reduce the present queue size to 4, too, except if you're using smooth motion FRC. The frame presented in advance are frames which madVR has already sent to Direct3D for presentation. So they're out of madVR's hands, and even out of the responsibility of the media player process. Usually this increases reliability against frame drops.

It would be good if you could make up your mind if you want support for your specific playback problems in this thread, or in your own thread, because if you ask in both threads, questions and answers might overlap, causing me more support work. Thanks.

[madshi]

Not sure what part of the chain is the problem here, but the exact same video is being detected as having BT.601 primaries on one opening and BT.709 on the next. I've noticed this bug on other videos too. Whats worse, is that it actually changes the color of the video (mainly in the greens). Is this a video encode bug or an actual bug in madVR/LAV's detection code (also using) xySubFilter and MPC-HC). So far its only on videos were instead of the matrix being 'best guess' its 'upstream' for the matrix and 'bitstream' for the primaries (on videos were in the mediainfo just the matrix has been set as BT.709, leaving the primaries guess to the chain).

http://i.j2.io/9EM0.png
http://i.j2.io/8T2O.png
(size difference is due to poor screenshot lossless PNG crop, not due to different frame. Color difference is there on madVR itself).
If this info would be present in the bitstream, than it would also be coming from upstream LAV, and not leave madVR having to get it from the bitstream itself. Sounds like a bug in madVR to me. A sample video that shows this problem will be required, however.
^

Yep - sample, please! I need to be able to reproduce this on my PC.

[madshi]

SUBTITLES - HELP

Today I wanted to look into the problem of moving subtitles into black bars not always working as expected. It has been reported to me that e.g. moving SRT subtitles into the black bars stops working if the SRT contains <i>italic</i> subtitles. So I've tried to reproduce that just now, but can't!

Does anybody have any sample with which I can reproduce that moving subtitles into the black bars works at first, but then stops working at some point?

[KoD]

I tried windows overlay, mpc shows "creating Direct3D device failed (8876087b), I disable both FSE and DX11
If you are having issues with DX9 mode, maybe you don't have the DirectX 9 runtime installed? Run the web installer from here (https://www.microsoft.com/en-gb/download/details.aspx?id=35&e6b34bbe-475b-1abd-2c51-b5034bcdd6d2=True) just to make sure.

[chros]

If you are having issues with DX9 mode, maybe you don't have the DirectX 9 runtime installed? Run the web installer from here (https://www.microsoft.com/en-gb/download/details.aspx?id=35&e6b34bbe-475b-1abd-2c51-b5034bcdd6d2=True) just to make sure.
Or is it an optimus system?

[SweetLow]

Ok, but how many displays, especially how many TVs support that?

TVs? Almost none, AFAIK (and see IRL). Only monitors - and i use this on monitors (first Samsung 959NF, then Dell 2707WFP) at my primary PC (to view short videos), not theater PC.


You mean chinese or russian characters? Or what do you mean?

Russian(Cyrillic). But - ANSI CP is 1251 (and OEM 866) on my PC - and if you internally use AnsiStrings - it shall not be a problem, i assume.

[aufkrawall]

Sorry, but no.
No problem. I'm glad we have it in madVR though.

Different issue:
I'm instantly getting lots of dropped frames when I enable black bar detection for a HEVC 10 bit 4k 50fps video. Neither GPU nor CPU load is at max, so probably performance can be improved?
The video plays fine without it (except of some weird high bitrate locations).
CPU is a 4770k@4.1Ghz and GPU 780 Ti@1.2Ghz.

[huhn]

If it's *soft* telecine then it should be played at 23p if deinterlacing is disabled. Are you sure it's 29p? If it is, then it's probably not soft telecined.

yes i'm sure it is soft telecine and the reported fps is 29.90 fps says source filter even with "if in doubt, activate deinterlancing".

some extra informations.
software decoding with IVTC sees 3:2.
quiicksync decoding with IVTC sees 2:2 (no repeat flags)

and there is no combed file in the whole source.

and ffmpegsource uses 23p for it.

[madshi]

Russian(Cyrillic). But - ANSI CP is 1251 (and OEM 866) on my PC - and if you internally use AnsiStrings - it shall not be a problem, i assume.
Should be unicode, but I'll check.

I'm instantly getting lots of dropped frames when I enable black bar detection for a HEVC 10 bit 4k 50fps video. Neither GPU nor CPU load is at max, so probably performance can be improved?
Yes, I'm aware of the problem. It will be fixed soon(ish).

yes i'm sure it is soft telecine and the reported fps is 29.90 fps says source filter even with "if in doubt, activate deinterlancing".
That's just what the decoder reports, but not what madVR actually draws. Try frame stepping again, you should be seeing 24fps not 30fps.

[huhn]

That's just what the decoder reports, but not what madVR actually draws. Try frame stepping again, you should be seeing 24fps not 30fps.

the issue is that madVR isn't switching to 23p if possible and madVR isn't using smoothmotion at 60 hz with these sources.

[dansrfe]

OSD upscaling works great, however the text is hard to read when height is less then ~630px or within the smallest OSD size range.

Should peak luminance be set to 265nit for a 300nit (measured) display?

[huhn]

set it to what's looks best to you.

[Marsu42]

Is there some non-linear stretch option with MadVR I'm not finding in the various options ... i.e. like ffdShow warped resize or Cyberlink PanoVision(tm)(r)(c)(wtf)?

If not, would it be possible to implement this - the various tv sets all seem to have a 4:3->16:9 non-linear stretch feature as it's so convenient for watching older content on a newer wide-screen display. The catch with ffdShow is that it's software-only and is stuttering esp. when enabling other post filters.

[py930828]

If it's *soft* telecine then it should be played at 23p if deinterlacing is disabled. Are you sure it's 29p? If it is, then it's probably not soft telecined.


Because HD DVDs and D-Theater captures are soft telecined and play perfectly with deinterlacing disabled. There are even some (rare) Blu-Rays with this mode. But if you want deinterlacing to be used for such sources, simply change your madVR settings to "if in doubt, activate deinterlacing". That's what that setting is for.


Sorry, but no. It's also not necessarily the final version yet. It's a work in progress. I already have some plans to further improve it, at least the anti-ringing part of it.


Your media player.


Don't attach pictures to this forum, they often don't get approved, or with very long delays.


Is that an Optimus laptop? Those are known to have certain problems. You could try installing a different driver version, maybe it helps.


I can't even see them because they're not approved (see above).


Yes. Forgot to mention it in the changelog.


It does for me. It says: "vsync 16.68ms, frame 16.68ms" with (DXVA) deinterlacing active and "vsync 16.68ms, frame 33.37ms" if I manually disable deinterlacing.


Your source filter simply doesn't deliver frames. I've told you before, the source filter should push frames until madVR blocks. But your source filter does not. There is NOTHING I can do to make the queues fill. It's the responsibility of your source filter. The key problem is that madVR's "delay" feature waits for frames to come from the source filter while the graph is still in paused mode. And in that mode it seems that your source filter doesn't send more than 1-2 frames. It only starts sending frames when playback in unpaused, and it never sends frames fast enough ("in advance") to allow the queues to fill.


I'm scaling the font size with the window/screen size now. I've tried many different fonts and spent many hours on this, trying to find a good solution. The biggest problem is that most fonts don't support grayscale anti-aliasing at smaller font sizes. The fonts must be rather big for them to start supporting grayscale AA. ClearType AA is supported at small font sizes, but looks terrible when transparently blended over the video frame as madVR does. So the font I'm not using (which is actually the Windows default GUI font) was the "best" compromise I could find. It's one of the VERY few fonts which supports anti-aliasing at smaller font sizes. Most other fonts look very thin and are thus also hard to read at smaller font sizes.

It's true that the font size is now allowed to get smaller if your playback window is very small. The purpose of that is to fit more of the stats into the window. If I didn't do that, the font size would be bigger which is easier to read, but a lot of the OSD content would then be cut off.


Ok, but how many displays, especially how many TVs support that?


Makes no sense to me that this would change anything related to HDR.


You mean chinese or russian characters? Or what do you mean?


Bigger is better, but 4 should work ok, too.


Higher CPU/decoder queue means more protection against CPU spikes causing the decoder queue to get empty. But usually the default should be fine.


That's the size of the present queue. If your GPU queue is set to 4 frames, probably it would make sense to reduce the present queue size to 4, too, except if you're using smooth motion FRC. The frame presented in advance are frames which madVR has already sent to Direct3D for presentation. So they're out of madVR's hands, and even out of the responsibility of the media player process. Usually this increases reliability against frame drops.

It would be good if you could make up your mind if you want support for your specific playback problems in this thread, or in your own thread, because if you ask in both threads, questions and answers might overlap, causing me more support work. Thanks.

Madshi, what is the difference between using DX11 or DX9? Does DX11 works better or?

[Stereodude]

That's just what the decoder reports, but not what madVR actually draws. Try frame stepping again, you should be seeing 24fps not 30fps.
Okay, so why does madVR not change the refresh rate to 24/1.001Hz or engage smooth motion (on a 60Hz display)? Forcing deinterlacing & film mode where it detects a 3:2 pattern on the clip seems to be the only way to get it to actually treat it like p23.976 content.

[Warner306]

Improving the anti-ringing of sharpen edges would be welcome. At 1080p -> 1080P, I like to use a small amount of sharpening to keep the appearance of the image consistent across all resolution profiles. I find sharpen edges looks the best when used alone because it doesn't alter image brightness, but it shimmers during panning scenes due to its ringing. It is really my last request after a year and a half of using madVR. Super sampling or another sharpening algorithm that resembles SuperRes would also be welcome.

[Warner306]

Also, I mentioned earlier that peak luminance should have a disclaimer next to this setting to the effect: "For HDR content mapping." Most people, like me, won't even know where to begin and would assume this applies to all content.

[foozoor]

Improving the anti-ringing of sharpen edges would be welcome. At 1080p -> 1080P, I like to use a small amount of sharpening to keep the appearance of the image consistent across all resolution profiles. I find sharpen edges looks the best when used alone because it doesn't alter image brightness, but it shimmers during panning scenes due to its ringing. It is really my last request after a year and a half of using madVR. Super sampling or another sharpening algorithm that resembles SuperRes would also be welcome.

I agreed, supersampling is the best for sharpening.
This is why I still use avisynth at the moment.

@ madshi
I think it could be interesting to use upscaling refinement even without upscaling or add a similar option for post sharpening.

[Kirk Lazarus]

I guys,
I'm running madVR 0.89.17 on a Pc with Win7 64bit.

I use this HTPC on an OLED UHD LG TV.
This tv do not support directly 0-255 levels so I set madVR to work in 16-235.

I've done a simple test...

I used Calman 5 and madTPG like pattern generator and measured a full 21 steps grey scale. the result is this:

https://dl.dropboxusercontent.com/u/62605175/trk_mad.jpg

After that I turned back in madvr >> "color & gamma"

and I set brightness to +50.

When I set +50 I've madvr displaying a near black flashing bar test pattern.
The +50 have an evident effect on the flashing bars ...

I turned back in madTPG and with Calman I performed another grey scale read ...

the result is identical like before!!

Maybe I found a bug?

or it is normal that a brightness setting do not effect the patches reproduced in madTPG ???

thank you all for any clarification.

[Aktan]

Your source filter simply doesn't deliver frames. I've told you before, the source filter should push frames until madVR blocks. But your source filter does not. There is NOTHING I can do to make the queues fill. It's the responsibility of your source filter. The key problem is that madVR's "delay" feature waits for frames to come from the source filter while the graph is still in paused mode. And in that mode it seems that your source filter doesn't send more than 1-2 frames. It only starts sending frames when playback in unpaused, and it never sends frames fast enough ("in advance") to allow the queues to fill.

Ah, I think I finally got it. Thanks for being patient with me. Also seems like setting an audio delay in MPC-HC doesn't help :(

[ashlar42]

Is there some non-linear stretch option with MadVR I'm not finding in the various options ... i.e. like ffdShow warped resize or Cyberlink PanoVision(tm)(r)(c)(wtf)?

If not, would it be possible to implement this - the various tv sets all seem to have a 4:3->16:9 non-linear stretch feature as it's so convenient for watching older content on a newer wide-screen display. The catch with ffdShow is that it's software-only and is stuttering esp. when enabling other post filters.madshi mentioned in the past that it might arrive but that it's not a priority for him. Personally I think that a configurable solution, as Lumagen scalers offer, can produce acceptable results by combining NLS with some cropping.

[hubblec4]

[code]
* fixed: DVD aspect ratio wasn't always shown correctly when using MPC-HC


Thanks a lot, it works now again.

[bran]

Hi guys, I have a question semi-related to madVR;

I have the flagship 65" JS9505 TV from Samsung, 10bit panel. Using HDMI via a Marantz SR6010 receiver and GTX980Ti so 10-bit and/or 4:4:4 RGB is supported.

However, seems like the current standard does not accept 4K @ 60Hz and RGB 4:4:4 coupled with 10-bit? At least I can't choose it in the nvidia control panel. If I go 4:2:2 I can choose 10 or 12bit.

What would your recommendations be? Go with 4K 60Hz RGB 4:4:4 8bit or Ycbcr 4:2:2 12bit (10bit in madVR)?
Not much (any) 10-bit content nowadays but in the future when HDR rec2020 comes, will that change the preferred settings?

[nevcairiel]

HDMI doesn't have enough bandwidth for 4K RGB 4:4:4 in 10-bit, only 8-bit, or lower refreshrate, or lower chroma.

Unless movies actually start being 60Hz or something at some point, using 24p in 10-bit is probably best.
Speaking of, I wonder if this is a viable setup and the resolution switcher can actually deal with it.... Switching between 60Hz 8-bit and 24Hz 10-bit automatically.