madVR - high quality video renderer (GPU assisted)

[huhn]

i don't know i mean do you even care about HDR output aren't you using a PJ?

[x7007]

i don't know i mean do you even care about HDR output aren't you using a PJ?

I have Epson 9400 projector, it supports HDR.


But I also have OLED LG CX which I use to watch HDR content also, NV HDR doesn't only OS HDR works with 165...

it stops working because of the bloody time limit bomb..... I always forget. why do such an annoying thing, if it works fine why do you bomb us with a time limit..... NV HDR doesn't work with any version above 113..... can't understand this.



Why I can't get NV HDR back working now, I'm tired of this, every time I copy the newest beta version it stops working and I don't remember how to go back...................... wasting so much time because of this crap really.


No one ever says it - MUST RESTART COMPUTER AFTER CHANGING MADVR VERSION (ELSE AMD/NV HDR DOESN'T WORK)!!!

TIME BOMB EVERY X TIME need to update MADVR VERSION or some things stop working, that's what always happens like 0-255 and 16-235 can't switch between them.

[huhn]

just move on from it instead of a version that actually works on win 11 we got a time bomb that is a beta somewhere in a thread...

not in this opening post not somewhere sticky elsewhere no just a random post.

[senzaparole]

Hi guys.
I have a problem. After allowing several updates I noticed that my TV no longer automatically switches to HDR mode.
I have a PC connected to LG TV. Does anyone know how i can fix it?

[mclingo]

probs need to give us a bit more to go on, is this is windows 11 there might be some issues there or if you switched to NVIDIA it keeps getting removed from the drivers.

Double check you have it set in two main areas of MADVR:

in display properties the native display bit depth should be set to 10 bit or higher I think.

In rendering, I think you still need to have "use DIRECT3D for presentation ticked"

to make sure its not a windows issue, turn on HDR in windows and see if your TV goes into HDR mode.

[senzaparole]

I solved. It was an AMD driver update. I unistalled them and now everything works fine. Thank you very much

[ashlar42]

if you switched to NVIDIA it keeps getting removed from the drivers.
Hi! Could you please clarify what you meant above? What's being removed for Nvidia users? I don't get it.

[huhn]

there are multiply reports of nvidia been unreliable with HDR passthrough.
some get it fixed with a simple restart other have to reinstall driver and the issue is gone.

worst case no one knows what's really wrong but seem rare.

[Alamei]

Is there a current workaround available for the screen re-synchronizing delay when switching between windowed and full-screen windowed modes? I recently purchased a Gigabyte M34WQ, and now any time I toggle a video to full-screen (not FSE, just normal windowed full-screen), the screen goes blank for a couple of seconds before displaying the full-screen video. Interestingly, the same does not occur when toggling back from full-screen windowed to normal windowed, so it's something specifically about the action of switching to full-screen that's causing the monitor to blank out.

Some troubleshooting notes:

Switching MPC-BE to use EVR-CP for playback removes the issue, so it's definitely MadVR related.
This issue didn't occur on my previous ASUS PG279Q (traditional G-Sync, instead of G-Sync compatible) monitor on this same computer. However, I don't know if that has anything to do with it, because disabling G-Sync entirely on the new monitor has no impact.
I don't experience the black screen delay going in and out of any other full-screen applications (games, etc...)
Using the Nvidia Profile Inspector to add MPC-BE (and MadVR) to the Windows Media Player profile (recommended as a solution back in 2018 in this thread) doesn't work.
I've tried changing all sorts of settings in the Nvidia Control Panel for MPC-BE, including Fixed Refresh vs G-Sync, Application-Controlled Refresh Rates vs Highest Available, etc., with no impact from any of them.


Has anyone run into this issue on another monitor, and, if so, found any sort of solution?

[ryrynz]

Try the latest madvr beta build, If that doesn't fix it submit a bug report and maybe madshi might improve it. Wouldn't hurt to try whatever you can do to see if something helps.. Like disabling mpo and full screen optimizations.. Try a different direct3d mode.

[huhn]

check HDMI content type select one but this only works if you would run this device using HDMI and not using DISPLAY port with should be exclusively used with this device.

[Sunspark]

Alamei: I have the same issue, but it's caused by changing both the resolution and the refresh rate. It's never going to be instant. There's a delay with the graphics drivers and then there's a second delay where the monitor locks in to the new resolution&refresh. If you want it to be instant, you need to stay at the same resolution and refresh as your desktop.
Uncheck "switch to matching display mode" in madvr. You may also need to check the player too, because the player can also change. For mpc-hc playback>fullscreen. For mpc-be video>fullscreen. Uncheck autochange.
As for why you'd change resolution/refresh, it's so you can have your screen at 23.976 for example.

[Alamei]

Try the latest madvr beta build, If that doesn't fix it submit a bug report and maybe madshi might improve it. Wouldn't hurt to try whatever you can do to see if something helps.. Like disabling mpo and full screen optimizations.. Try a different direct3d mode.
I tried the latest beta build without seeing any differences. Ditto for full-screen optimization changes. What is MPO in this context? I don't think I've adjusted that as a test.

check HDMI content type select one but this only works if you would run this device using HDMI and not using DISPLAY port with should be exclusively used with this device.
The monitor is hooked up via DisplayPort, so this shouldn't be impacting the configuration.

Alamei: I have the same issue, but it's caused by changing both the resolution and the refresh rate. It's never going to be instant. There's a delay with the graphics drivers and then there's a second delay where the monitor locks in to the new resolution&refresh. If you want it to be instant, you need to stay at the same resolution and refresh as your desktop.
Uncheck "switch to matching display mode" in madvr. You may also need to check the player too, because the player can also change. For mpc-hc playback>fullscreen. For mpc-be video>fullscreen. Uncheck autochange.
As for why you'd change resolution/refresh, it's so you can have your screen at 23.976 for example.
Switch display modes is already unchecked, and I can tell that a display mode switch isn't causing the issue, because if it were, then there should be a blank screen both entering and exiting full-screen, whereas this issue is occurring solely when entering full-screen. That's part of what's confusing me about the problem, because I've never run into an issue that didn't occur on both engaging and disengaging full-screen mode before.

[clsid]

MPO = Multi Plane Overlay
You can disable that with a registry tweak. Google it.

Press Ctrl+J to display madVR OSD and make a screenshot in windowed mode and fullscreen. That is easiest way to see if anything is different.

[70MM]

I cant get any profiles to activate and work under Devices, yet all my other profiles on other pages work.

Im trying to use the A stretch 4/3 on and off under Devices/Config, I can make the two profiles using keystroke 1 & 2, but it wont activate or show in the top left corner of the screen.

All my other profiles in all the other tabs besides Devices work and display in the top left corner of the screen.

Has anyone ever seen this happen and if so what might be wrong here?

Thanks in advance.

[Budtz]

I get no tonemapping and wahsed out colurs. in windows 11 with neweset drivers.

Is there a setting that needs to be set to get it tor work again. Might just give up at use VLC. that works fine

[SunnyM]

Hi, first thanks for your job on madVR !

I've got an issue with madVR zoom control stretching image instead of zooming on my 21/9 monitor.
I googled for this issue but did not find anything relevant, so here I am.

Here's the original video (16/9 with 21/9 scenes): https://imgur.com/a/CsqL6NH
With zoom control enabled: https://imgur.com/a/sYt0Q7u
What it should be: https://imgur.com/a/eRruf88
MadVR settings: https://imgur.com/a/AUA6ntw
LAV settings: https://imgur.com/a/7euellJ

I use PotPlayer but extending/croping/resizing are disabled and almost all non filters related settings are by default.

I really don't understand what's wrong, thanks for your help !

[Siso]

What is the resolution of the movie? I'm on 21:9 monitor, and I don't use this madvr feature. You can assign buttons to change the zoom. I'm using "Keep Aspect Ratio" and "Stretch By Keeping Aspect Ratio".

[SunnyM]

I don't want to press a button each time video goes from 4K IMAX to 21:9 and vice-versa if madVR can do it dynamically.
AFAIK it can but there's a bug or I missed a setting and madVR stretches instead of zooming.

[el Filou]

I've got an issue with madVR zoom control stretching image instead of zooming on my 21/9 monitor.
[...] I use PotPlayer but extending/croping/resizing are disabled and almost all non filters related settings are by default.Must be caused by some setting in your media player that instructs madVR to stretch it. Please post the second screenshot again with the OSD (Ctrl+J) shown.
With either MPC-HC or MediaPortal using "touch window from inside" and those same settings it work as intended on my system (my screen is not 21:9 but with e.g. old letterboxed 4:3 DVDs).
Can you try with MPC-HC just for a test?

[SunnyM]

Hey el Filou, thanks for your reply.
Here's the capture with madVR OSD: https://imgur.com/6fc4rc2
Tried with MPC-HC and MPC-BE but I can't make zoom control working, tried with internal/external LAV filters and double checked that madVR was in active filters, normal or touch from inside is the same.

[el Filou]

I really can't reproduce this even with your exact madVR settings. We can see that madVR is cropping correctly (3840x1606), and then that it's scaling while forcing a 16/9 aspect ratio (the "-26%" bit). It won't decide to do that out of the blue, it's either the media player or the video decoder telling it that this is the display aspect ratio it needs to force.
For zoom control to work with MPC-HC/LAV Filters, you need to choose None or DXVA2 copyback in "Hardware Decoder to use" in LAV Video.
Check this and try again with MPC-HC to see if it's doing the same thing.

[SunnyM]

OK I found the correct setting in potplayer is "Default Original DAR" instead of recommended "Default Display AR" https://imgur.com/NfB7GPI
No more stretch and madVR wasn't involved, seems to work flawlessly now.
Sorry for disturbance !

[70MM]

Is there anyone here who read my post and has ever experienced this problem Ive been having as its driving me crazy? https://forum.doom9.org/showpost.php?p=1980122&postcount=63720

[huhn]

yes but one place is enough.

[flossy_cake]

I cant get any profiles to activate and work under Devices, yet all my other profiles on other pages work.

Im trying to use the A stretch 4/3 on and off under Devices/Config, I can make the two profiles using keystroke 1 & 2, but it wont activate or show in the top left corner of the screen.

All my other profiles in all the other tabs besides Devices work and display in the top left corner of the screen.

Has anyone ever seen this happen and if so what might be wrong here?

Thanks in advance.

I am using some aspect ratio profiles and they are working fine. I don't use hotkeys to activate them; I tag the parent folder or filename with eg [profile='aspect 1.33 to 1.36'] and then during playback I open MadVR settings and that profile is highlighted in bold font which lets me know it's active (it's not in the screenshot cause I couldn't be bothered).

https://i.ibb.co/KFJwyXk/Untitled-2.png

But nowdays I do most aspect ratio adjustments in Avisynth script (text file with .avs extension containing Avisynth commands and stuff, then open the .avs file with media player).

On an unrelated note, I was wondering about the "matrix" and "primaries" info on debug ctrl+J screen... is my understanding correct that:

1. "matrix" refers to the formula that madvr is using to convert the source YCbCr to RGB

2. "primaries" refers to the wavelengths of light that RGB correspond to, so that madVR knows how to convert the source RGB to whatever your display mode RGB happens to be (eg. if source is 709 and display mode is 709 then no conversion is done)

The reason I'm asking is cause Avisynth source filter doesn't output any metadata for the pixel format (matrix & primaries) so MadVR always has to use "(best guess)" and I want to make sure I'm understanding this right so I'm getting correct colours.

:thanks:

[flossy_cake]

Ugh, am I correct in understanding that if we DON'T manually tell madVR that for example "this display is calibrated to rec 709 gamut" in the calibration section of settings, then madVR WON'T perform any gamut conversion at all?

i.e without doing the above, if we play content which has different gamut to the monitor, such as playing DVD content on a 709 monitor (typical pc monitor) then we will actually get the WRONG gamut?

I'm asking as this seems to be what's happening when displaying PAL DVD color bars and watching what happens to them when toggling that option - the colours change in such a way that indicates this.

If this is true it means I've been watching wrong colours this whole time for non-709 content on my 709 monitors and TV!

I mean it's not a HUGE deal since 601 (SMPTE-170M / SMPTE-C / PAL / NTSC) is pretty close in gamut to 709 anyway...but still, kind of embarrassing that I've been watching wrong colours for over a year and didn't realise it :o

Because I was looking at ctrl+J saying "primaries 601" which I thought meant MadVR understood the gamut of the source material is 601 and is therefore converting it to the display mode's gamut, but no it's not actually doing that it seems, unless we manually tell MadVR what the monitor gamut is.

I thought MadVR would INFER the monitor gamut based on display resolution or possible other metrics like whatever the GPU driver says about the display mode (or at least just assume 709 if no information is available, since that is what most monitors will be).

edit: it seems there are actually 2 PAL gamuts in use:

1. SMPTE-170M / SMPTE-C / PAL / NTSC
2. EBU / PAL

https://www.kernel.org/doc/html/v4.8/media/uapi/v4l/pixfmt-007.html

And the difference is not trivial - using 1 for 2-content results in quite more brighter reddish skin tones.

_______________________

On another note... regarding the Family Guy DVD chroma alignment issue (https://forum.doom9.org/showthread.php?p=1966569#post1966569), the fix was easy: just move the chroma up by 1 line (seems to work for s01 - s07 but I still need to go through each episode to make sure there aren't outliers). This can be done with Avisynth script and then opening the script in media player without having to re-encode the video:


DirectShowSource("C:\Family Guy episode.mkv")

MergeChroma(last, LanczosResize(width, height, 0.0, 1.0, width, height)) # shift chroma up 1.0px (http://avisynth.nl/index.php/Resize)

LanczosResize(720, 540) # stretch 720x480 -> 720x540 (4:3) cause Avisynth source filter doesn't output aspect ratio metadata & MadVR would end up treating NTSC pixels as square pixels

[Sunspark]

One way you could evaluate this, would be to run a youtube video in a different colour space in the player through madvr. You will need to have yt-dlp.exe in the player's folder. https://github.com/yt-dlp/yt-dlp

Here is a DCI-P3 video I came across, https://www.youtube.com/watch?v=_Ld-du6giUo

You could do a run with disable calibration controls for this display, and a run with this display is already calibrated and set to bt.709/pure power 2.2.

[nevcairiel]

Ugh, am I correct in understanding that if we DON'T manually tell madVR that for example "this display is calibrated to rec 709 gamut" in the calibration section of settings, then madVR WON'T perform any gamut conversion at all?

This is correct, which IMHO is a silly default, as most people get the wrong result from that, instead of just assuming any screen in this day is just 709 by default, which would be far more often right then it would be wrong.


edit: it seems there are actually 2 PAL gamuts in use:

1. SMPTE-170M / SMPTE-C / PAL / NTSC
2. EBU / PAL


While techncially true, the source content can identify the difference between them if it cares to do so. But the EBU/PAL option has long been deprecated and is likely not used in digital media all that often.

[huhn]

is assumes BT 709 by default.
no calibration controls and defaults from "this display is cali..." are very very similar there where some difference but i can't remember.

i tested tone mapped bt2020 source i have no bt 2020 source at hand that is SDR.

on the other hand there is a good possibility that it ignores ebu smpte C and such.
i only tested a barely any color encode i had a round with smepte C bt601 meta data and it was working properly.

with passthrough it is assuming bt 2020 if not forcing it.

[flossy_cake]

But the EBU/PAL option has long been deprecated and is likely not used in digital media all that often.

Are you sure because all my PAL DVD's (both ISO's and mkv remuxes which I made myself from the physical discs) are showing up as "EBU/PAL (says upstream)" in ctrl+J.


is assumes BT 709 by default.

Here is 75% bars EBU/PAL https://drive.google.com/file/d/195ywphKmOz3sn2XAe_xmKKSF8MVSI-N1/view?usp=share_link

Take a screenshot and inspect RGB values in photoshop they are different when I toggle between "disable calibration controls for this display" and "this display is already calibrated bt.709".

PAL and 709 are close but enough to see a slight increase/decrease on the red and magenta bars in a light controlled room. Green bar changes from RGB 0,191,0 to 0,191,25 but not perceptible to me. On actual content cannot tell in a double blind test but can see some skin tones slightly changing with A-B comparison.

Anyway I guess I finally know the meaning of "gamut conversion disabled" on ctrl+alt+shift+P :)

[olli66]

Hello all. I am using madvr since years and all of a sudden in my mpc-hc (64bit) it does not show up as option for video renderer in the output settings anymore. It shows in the external filters and is configured but it is not available to select as video renderer. What could be the issue? Thanks for any hints/tips.

[huhn]

if this wasn't changed it should show an "madVR "not available/installed"" if not your mpc hc version does not support it.

alternatively you just have an version installed that timed out because that's a thing now:
https://www.videohelp.com/software/madVR/old-versions
165 will work for a couple more weeks then it will start to complain and after a couple more months stop working.

166 will show up sometimes "soon" or is atleast supposed to do that.

[olli66]

I reinstalled everything and switched to the 32bit version, it works now
I just haven't figured out yet how to display 3D content and watch it with VR. I did everything according to this guide but I don't get a top/bottom image.
https://www.tomchapin83.com/how-to-watch-3d-blu-ray-movies-on-the-htc-vive-or-oculus-rift-without-having-to-re-encode-the-movie/

[flossy_cake]

I mean it's not a HUGE deal since 601 (SMPTE-170M / SMPTE-C / PAL / NTSC) is pretty close in gamut to 709 anyway...

I take that back - the difference on reds is significant:

https://i2.lensdump.com/i/Ru5jRT.png
https://i3.lensdump.com/i/Ru5IF7.png

[flossy_cake]

I take that back - the difference on reds is significant:

https://i2.lensdump.com/i/Ru5jRT.png
https://i3.lensdump.com/i/Ru5IF7.png

Huh that's weird, on my TV the difference between those 2 images is quite large, but on my PC monitor it's only a very subtle difference, almost imperceptible. I guess my TV must have some nonlinearities in the reds or something.

[Sunspark]

Your browser probably doesn't have colour management turned on. On mine in Firefox looking at the image, the difference is huge.

The disabled controls image has a cold blue cast in the red. The set to bt.709/2.40 one has a different gamma and an orange cast in the red and also a less saturated/pastel blue.

I actually prefer the 2.40 image because the other one is too cold, and the gamma too dark in the mid-tones.

[flossy_cake]

Your browser probably doesn't have colour management turned on. On mine in Firefox looking at the image, the difference is huge.

Whether I view them in Firefox, Brave, IrfanView or Photoshop, the difference is the same on this particular monitor (Acer XB271HU).

Interesting that you are seeing a big difference though as that is consistent with what I'm seeing on my TV (Samsung plasma 51D450).


I actually prefer the 2.40 image because the other one is too cold, and the gamma too dark in the mid-tones.

If I change the gamma in madvr's calibration settings and hit Apply, the colour doesn't change at all, so I think that gamma setting only comes into play when Madvr is converting HDR to SDR maybe?

edit: nope I was wrong, the colour does change.

edit2: alright, so MadVR's gamma setting doesn't do what I thought it would do. Toggling it between extremes of 1.8 and 2.6 reveals virtually no perceptible change in shadow details of dark colours like grays, but does show quite a big difference on the bright reds on the family guy title. I figure MadVR must be using gamma ONLY as part of the gamut conversion formula, when converting SDR to SDR. It doesn't appear to be doing a gamma conversion, eg. assuming that 601 content was mastered at 2.x gamma and then tone mapping that to say 2.4 if that's what you chose. Whereas it DOES do that when converting HDR to SDR.

[Sunspark]

Do you have an icc colour profile set on your Acer? My monitor does. Also be mindful of which preset you're in. On mine, 3 of them can do 4:4:4 chroma, but the others are 4:2:x so you need to test with the 4:4:4 chroma test image to find out which is which as this may make a difference.

I have no idea if this is accurate or not, but f.lux in the "Options and Smart Lighting" menu item, "Driver Info" button says my display has sRGB gamut: 100% and AdobeRGB gamut: 93%. Not bad for a 12+ year old 6-bit FRC panel if so.

[huhn]

the gamma option doesn't change the gamma you only tell madVR what gamma your end device has why would it now change that?

it's not meant to change anything for SDR.
for HDR it's different because that's an absolute luminance format meaning there is no different gammas there is only 1 correct value so it has to compensate for the end device gamma.

[flossy_cake]

the gamma option doesn't change the gamma you only tell madVR what gamma your end device has why would it now change that?

I agree it shouldn't change gamma because we don't really know what gamma all SDR content was mastered at due to gamma being poorly standardised until 2011 when it was finally defined in BT.1886.

But hypothetically if we did know that all SDR content was mastered at say 2.4, then if the user's monitor is calibrated to 2.2, madVR could hypothetically do a conversion from 2.2 to 2.4 similar to how it it converts HDR PQ to gamma 2.4. But yeah I'm glad it doesn't do this as I use vcgt for 2 different gammas day and night, so if MadVR was doing a conversion it would clash with that. So I am grateful that madVR does not do gamma conversion.

The reason I got fooled into thinking madVR was doing gamma conversion for SDR was because I was using this family guy title screen (https://drive.google.com/file/d/1BtqAR7C4WMMzZy5-k617E3FznLQ-q_nb/view?usp=share_link) as my test pattern, and that shows a noticeable change in tone mapping when changing gamma in madVR settings which gave the impression it was doing a gamma conversion but in reality I think that is just madVR using gamma as part of the gamut conversion only. For example if I set madVR's calibration gamut to SMPTE-C which is the same gamut as the above clip, then toggling madvr's gamma between 1.8 and 2.6 does nothing at all. But if I select a different gamut eg. 709 then 1.8 vs 2.6 shows quite a big difference.

[flossy_cake]

Do you have an icc colour profile set on your Acer?

I do not have any ICC profiles associated with the display in Windows Color Management if that's what you mean. I am using the vcgt to calibrate gamma on both screens. For that I am using my own app - Calibration Tools (https://bitbucket.org/CalibrationTools/calibration-tools/src/master/).

Also be mindful of which preset you're in. On mine, 3 of them can do 4:4:4 chroma, but the others are 4:2:x so you need to test with the 4:4:4 chroma test image to find out which is which as this may make a difference.


So my PC monitor is of course RGB 4:4:4 like pretty much all monitors, but my TV downscales internally to 4:2:2 even when fed a 4:4:4 signal. I can't imagine this would affect the colour of solid fields of red very much, but the TV is weird for other reasons for example I have to choose xvYCC gamut in order to get "acceptable" looking skin tones so it's probably not a very good display to check things on. I think my PC monitor should be the more accurate display. Nearly pulled the trigger on LG CS OLED as the prices were crazy low but want to hold out for the next panel as that has a lot more brightness and viewing angle too.

[huhn]

But hypothetically if we did know that all SDR content was mastered at say 2.4, then if the user's monitor is calibrated to 2.2, madVR could hypothetically do a conversion from 2.2 to 2.4 similar to how it it converts HDR PQ to gamma 2.4. But yeah I'm glad it doesn't do this as I use vcgt for 2 different gammas day and night, so if MadVR was doing a conversion it would clash with that. So I am grateful that madVR does not do gamma conversion.

you can use gamma and color.
there you tell madVR what gamma you want to see which only works if the gamma you currently have is selected under calibration.

and with a 3D LUT it will blind assume 2.2.

what so ever madVR should always assume bt 709 not only with bt 2020 input.

[flossy_cake]

you can use gamma and color.
there you tell madVR what gamma you want to see which only works if the gamma you currently have is selected under calibration.

For completeness, it seems that if "calibration > disable calibration controls" is chosen, then "color & gamma > enable gamma processing" still works, but appears to assume monitor is 2.2 (based on no visible change in colour when toggling "enable gamma processing" on/off when set to 2.2).

[Sunspark]

flossy_cake, the way plasma draws to the screen is different. It doesn't have individually lit RGB pixels on at the same time like an LCD, it draws a single monochrome frame of a specific colour on the entire screen, then another frame of a different colour, then another, etc. It does this very rapidly.

You should view the images on more devices, such as your smartphone. I was curious and looked using my OLED phone and while both images looked closer, I could still see a difference especially in the gallery app at max brightness. The two files do not have the same shade of red in them. It's your monitor. #D90E08 RGBA(217, 14, 8, 1) vs #D42900 RGBA(212, 41, 0, 1). It's probably the green and blue values at play.

[flossy_cake]

#D90E08 RGBA(217, 14, 8, 1) vs #D42900 RGBA(212, 41, 0, 1). It's probably the green and blue values at play.

Yep, mostly the green I would imagine as it makes up 58% of the luma in SMPTE-170M.

[flossy_cake]

Just a random comment... when playing DVD discs or remuxed DVDs, don't trust the frame rate reported by MadVR's debug screen. It's not a real time value and is often wrong when dealing with NTSC DVDs that use soft telecine, repeat field flags, or variable frame rates. I had no idea NTSC DVDs were so devilish with the way they encode frames. The only way I can have a hope in hell of determining the frame rate of such content is to use MPC Video Renderer's debug screen, which shows the frame rate in real time and whether the current frame is interlaced or progressive.

[huhn]

why would you care what the OSD says?
if it is 3:2 hard telecine you see 3:2 judder and you can run detelecine on it.

if it is soft telecine lav filter software decode will output 23p.
only hardware decoder may turn soft telecine into hard telecine.

[flossy_cake]

why would you care what the OSD says?

Open this (https://rationalqm.us/misc/lainvob.vob) with MPC Video Renderer's Ctrl+J and watch the frame rate. Couple more examples: 1 (https://drive.google.com/file/d/1xz_WEX36iv8tpC18zR8e8-etGwtqfuVb/view?usp=share_link), 2 (https://drive.google.com/file/d/1nQ9LnKWWq0OJp_FoOZpIIuf8YEnDH3nF/view?usp=sharing).

The fact that LAV + MadVR works without audio going out of sync is something of a miracle - I'm guessing it's using something similar to DVD2AVI's "force film" (https://forum.doom9.org/showthread.php?t=174522) trick to keep it in sync.


only hardware decoder may turn soft telecine into hard telecine.

Turning soft telecine into hard telecine is just a result of obeying the repeat field flags in the MPEG2 stream. I do this with Avisynth because converting it back to hard telecine 29.97i allows me to handle scene splices with orphaned fields in a better way.

[huhn]

mircale...
i mean it's just a frame time for NTSC there is only 33 and 42.

it most likely just ignores the flag and changes the frame time from 33 to 42 and also signals if the frame is interlaced or not.