madVR - high quality video renderer (GPU assisted)

[Sunset1982]

Ah, I see, thanks. The cause of the problem is that the LAV Video Decoder doesn't inform madVR yet about whether the movie is 3D or not, at the time when LAV and madVR are connected. This is already planned, though. The next LAV build will probably already do that. So by then this problem should automatically be fixed. You will then be able to remove the 1080p23 from the settings dialog, but madVR will still automatically switch to 1080p23 for 3D movies - but to your 4K resolutions for 2D movies.

ok, great! Thx for your hard work mashi! Now I just have to wait for 3D support in profile rules.

[Wilbert]

@Neroldy, files are too large. Please upload them somewhere else if still necessary.

[Manni]

Originally Posted by madshi

Ah, I see, thanks. The cause of the problem is that the LAV Video Decoder doesn't inform madVR yet about whether the movie is 3D or not, at the time when LAV and madVR are connected. This is already planned, though. The next LAV build will probably already do that. So by then this problem should automatically be fixed. You will then be able to remove the 1080p23 from the settings dialog, but madVR will still automatically switch to 1080p23 for 3D movies - but to your 4K resolutions for 2D movies.

Will this work even if we don't use MadVR autorefresh mode for 2D movies? In other words, does MadVR always switch to 1080p23 when it's sent 3D, and then switch back to 4K/UHD if that was the mode it was in before?

[madshi]

Originally Posted by Sunset1982

ok, great! Thx for your hard work mashi! Now I just have to wait for 3D support in profile rules.

It's already implemented, will be in the next build.

Originally Posted by Manni

Will this work even if we don't use MadVR autorefresh mode for 2D movies? In other words, does MadVR always switch to 1080p23 when it's sent 3D, and then switch back to 4K/UHD if that was the mode it was in before?

Yes.

Any news about the AMD 3D delay bug with Crimson?

[madshi]

@Sunset1982, try the latest LAV nightly, it might already allow you to remove 1080p23 from the display mode switcher, and still have it working:

https://files.1f0.de/lavf/nightly/

[4h4h270]

Originally Posted by madshi

Then you need to create a custom resolution to get your refresh rate tuned.


Not sure why that occurs. Do you have any 3rd party application running which might access the GPU?

My monitor have 1080p23hz&24hz display mode, it will play 3D @1080p23.973, but reclock thought my refresh rate is 24hz, it changed media speed to 24fps, then I get frame drop. Cause my refresh rate is slightly lower than 23.976, w/o reclock I will get 1 frame drop every few minutes.
Reclock will treat 23hz as 24hz only play 3D, hope they can fix it

I'll try to close all other application during play next time.

[Sunset1982]

Originally Posted by madshi

@Sunset1982, try the latest LAV nightly, it might already allow you to remove 1080p23 from the display mode switcher, and still have it working:

https://files.1f0.de/lavf/nightly/

Allready used this build when I created logs for you. Reinstalled it, not working...


next problem: restarted my pc and now have crashes again when trying to start 2D movies. 3D movies are playing but in 2D when 1080p23 is deleted in display modes.


have 2 new crashlogs:

crash when starting 2D mkv: https://www.dropbox.com/s/1powwghbwa...%202D.txt?dl=0

3D movies not getting 1080p23 with latest lav:https://www.dropbox.com/s/d3kujsjrz7...%203D.txt?dl=0

It's already implemented, will be in the next build.

thank you!

[har3inger]

Originally Posted by madshi

Is it a new bug with v0.90.x? That would surprise me. Which subtitle renderer are we talking about?

xysubfilter 746, LAV splitter 67.0, madvr 90.2, in mpchc, running 64bits, d3d11. I could be wrong about when the issue started popping up.

I can send you a sample if you wish.

[Manni]

Originally Posted by madshi

It's already implemented, will be in the next build.


Yes.

Any news about the AMD 3D delay bug with Crimson?

Sorry, was only able to test tonight.

Happy to report the AMD bug is fixed with Crimson

No depth issue anymore. I tried with the latest 16.1 hotfix, but I assume it was fixed in Crimson 15.x.

Great to hear the 3D profile is implemented in the next build, I need to seriously reduce processing with 3D to get smooth playback with my HD7870.

Now we only need BDMV/SSIF support to be able to ditch PDVD for 3D without having to re-rip all our 3D blurays.

One suggestion, similar to the suggestion I made for P3/Rec2020 calibrations which need a filter, it would be great not only to have a separate 3D LUT slot for 3D, it would also be useful if we could pair it with a specific user mode on displays which are controlled by MadVR like the JVCs, so that for example we can switch to high lamp, iris fully open and a different color temp calibration automatically.

If we could assign a specific user mode next to each calibration slot that would be ideal.

[edigee]

For those who experienced random blanks(black screens) for less than 1 sec. on HDMI displays with NVIDIA cards and the 361.60 driver. It's nothing related with madVR,LAV or MPC-HC(MPC-BE) but only a driver issue.

[Manni]

Unfortunately Crimson 16.1 is still clipping whites between 230-235 in 3D when the GPU is set to RGB Full, and there is still no way to specify a dynamic range separately from the pixel format, so going back to Catalyst 14.12.

The only way to get the correct levels for both PowerDVD/TMT and MadVR in both 2D and 3D with Crimson is to set the driver to RGB Limited, which isn't recommended for MadVR. Plus it still clips white in 3D above 230, so not really an option.

Otherwise, whether you set the display to standard or enhanced, there is no way to get the correct levels and resolve 16-235 in both 2D and 3D with Crimson.

I keep reporting both the white clipping bug in 3D and the need to give us back the ability to set the dynamic range independently from the pixel format at each driver release, it would be helpful if all AMD owners could do this as well.

[Della]

Originally Posted by edigee

For those who experienced random blanks(black screens) for less than 1 sec. on HDMI displays with NVIDIA cards and the 361.60 driver. It's nothing related with madVR,LAV or MPC-HC(MPC-BE) but only a driver issue.

Thanks for the post. I've battled this for the last couple weeks, trying everything. Even talked EVGA into RMAing a GTX960. Tried backing off a driver version or two and still had the random micro-second black flickers.

Do you have a reference to the driver issue?

[adhara]

Hi,

Any issue with "10 bits and more" option in MadVr ?
With 2160p content (upscal from 1080p video source), we can see video is 8 bits (after madvr processing stuff).
Why it is notified "limited range says upstream" ? My outptut is set to RGB 444 (both madvr and nvidia control pannel).

[dansrfe]

Originally Posted by madshi

Can you double check that you definitely don't get this crash with v0.89.19? It looks like a crash in the OpenCL driver when trying to cleanup the OpenCL resources.

I can confirm that this crash does not happen in v0.89.19. It does happen in v0.90.0+.

[AngelGraves13]

Originally Posted by adhara

Hi,

Any issue with "10 bits and more" option in MadVr ?
With 2160p content (upscal from 1080p video source), we can see video is 8 bits (after madvr processing stuff).
Why it is notified "limited range says upstream" ? My outptut is set to RGB 444 (both madvr and nvidia control pannel).

Do you mean YCbCr444? RGB Full and YCbCr444 are not the same thing. YCbCr is always limited.

[leeperry]

Originally Posted by madshi

Have you tried "reconstruction - soft" instead of Jinc?

Yes I did, I've been running a lot of tests today and long story short Jinc AR provides the most natural and subjectively best looking results to my eyes because others either look too soft or too edgy/sharp/artificial. Depending on whether it's SD or HD I play around with the chroma SR strength as it increases sharpness and EE(in combination with luma SR).

I've also run extensive comparisons between both old and new chroma SR and the newest looks a lot cleaner, so much that I run it @1 for 720p@1080p and up to @4 on SD@1080p depending on how noisy it is. The goal of HD is to get the feeling of watching through a window and I'm certainly getting it on 24p movies as chroma looks so amazingly crisp and natural with the Jinc AR + SR combination

BTW I got a funky PAL DVD that I can't get deinterlaced properly whatever by LAV or mVR, I need to figure out how to have its sequencing detected and will cut a sample if you don't mind. PowerDVD was able to make it 25p so I guess it's possible

[dansrfe]

Vobsub is cropped if outside video area yet within screen area and cropping of black bars is enabled. Move subtitles is disabled.

Also, is it possible to keep the vobsubs within the screen area and move them up closer to the center of video area when the screen area cannot the vobsub area.

[jmone]

Originally Posted by madshi

Yes, debug logs would be helpful. If possible it would be great if the logs would only contain the failures, not the success. Meaning, if you could stop MC, then delete the log, then start MC and reproduce SBS D9 mode. Not sure if it's possible to do that, though. Then stop MC again without doing anything else. Same for the 3D pause/playback problem. But there please let playback stay paused for 20 seconds, then press pause + play, then close MC. Thanks!

Attached are the 2 Logs - https://dl.dropboxusercontent.com/u/...-%203Dlogs.zip

Log1: Started 3D Playback initiated correctly but is was "stalled". Waited 30sec then did a Pause/Play and playback commenced correctly.

Log2: Started 3D Playback but it was in SBS mode (and it was "stalled"). Did a Pause/Play and playback commenced.

Tested using the test build in debug mode with the latest nightly from LAV (0.67.0-62).

[huhn]

Originally Posted by Manni

Unfortunately Crimson 16.1 is still clipping whites between 230-235 in 3D when the GPU is set to RGB Full, and there is still no way to specify a dynamic range separately from the pixel format, so going back to Catalyst 14.12.

The only way to get the correct levels for both PowerDVD/TMT and MadVR in both 2D and 3D with Crimson is to set the driver to RGB Limited, which isn't recommended for MadVR. Plus it still clips white in 3D above 230, so not really an option.

Otherwise, whether you set the display to standard or enhanced, there is no way to get the correct levels and resolve 16-235 in both 2D and 3D with Crimson.

I keep reporting both the white clipping bug in 3D and the need to give us back the ability to set the dynamic range independently from the pixel format at each driver release, it would be helpful if all AMD owners could do this as well.

and you are sure the problem isn't your TV ?

[adhara]

Originally Posted by AngelGraves13

Do you mean YCbCr444? RGB Full and YCbCr444 are not the same thing. YCbCr is always limited.

Hi,

My output is set to RGB 444 (full) both on Nvidia and Madvr.