madVR - high quality video renderer (GPU assisted)

[madshi]

I don’t know. Well, the thing is, any software that offers Row Interleaved output, offers Column Interleaved as well. Below is a quote from AMD HD3D_Whitepaper (https://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=12&ved=0ahUKEwj2ivuX8K7KAhVMA44KHf8wAiM4ChAWCCAwAQ&url=https%3A%2F%2Fwww.amd.com%2FDocuments%2FHD3D_Whitepaper.pdf&usg=AFQjCNGcXp5WJyo377npml7vNBKKXWHAWQ&bvm=bv.112064104,d.c2E&cad=rja)that you may find interesting:

“The column interleaving mode is convenient as some auto-stereoscopic panels (such as those developed by Sharp and others) use a parallax barrier to ensure that alternating columns are viewed by the left and right eyes. Content that is column-interleaved can thus be presented without any decoding.”
Well, I think currently most displays that do passive 3D are using LG panels and those are row interleaved. I'm not sure if Sharp still builds passive 3D screens. Anyway, I guess I can do row interleaved, too, but then we run into the problem mentioned by huhn (I think) that many TVs these days convert down to 4:2:2 for processing, and that would destroy the left/right chroma seperation. So I'm not sure how useful such a mode would really be.

I dont know, but at least the conclusion here might suggest this: http://www.interdigital.com/download/54313edae262284525000224
That's a completely different algorithm, and doesn't have much to do with Shiandow's Bilateral chroma upscaling algorithm, as far as I can see.

[jmone]

Originally Posted by jmone View Post
It is in 23.976 and one static SBS Image. Log at:
https://dl.dropboxusercontent.com/u/...3D%20Crash.zip



Thanks. But you didn't my question about refresh rates.


When the crash happens, the OSD is showing the refresh rate is in "23hz" (eg near 23.976 not 47.xxx). To be sure here is a pic of what it shows:
https://dl.dropboxusercontent.com/u/59011278/madVR3DOSD.jpg

[XTrojan]

Seems that no matter what MPC-HC can't engage 3D Frame-packing mode directly, I have to go from fullscreen to windowed to fullscreen to windowed again for frame-packed 3D to activate.

Also MadVR won't switch back to 2D after I close MPC-HC if my resolution was 1080p before I activated Frame-packed 3D.

[BetA13]

cant use the new builds at all.. :(
Everything from madVR v0.90.0 and upwards isnt working for me.

It plays too fast sometimes and when i want to go into fullscreen it freezes or black screen or it doesnt go into fullscreen at all and stops all together..

My TV and Hardware is:

Win 7 64bit, gtx670, intel q9550

TV:
Toshiba LCD COLOR HDTV 32WL66P (30hz in windows @ 1080i) in madVR it uses 60hz and 60fps and works very nicely usually, if i use VERSION "madVR 0.89.19".

im using d3d9 new path, Exclusive fullscreen and Enable window overlay.

On the other hand, on my CRT Monitor the new madvr version works with no problem, but this i dont use to watch movies...

If u need any other information or anything else let me know how i do it and i will get back with it :)

greetz

[dansrfe]

I'm getting consistent crashes with the last 2-3 versions for some reason. Same exact config, files, and playback environment I've had before.

Crash report: https://drive.google.com/file/d/0B9iVOLolmqxdR0ZlSUdrY1RnODg/view

[4h4h270]

Are you talking about the Ctrl+J OSD saying "1 frame drop every ..."? Or are you actually getting those frame drops (OSD increasing "dropped frames" statistic regularly every 30+ seconds)? The former is just a rough estimate by the OSD. The key statistic is the "dropped frames" line. As long as that doesn't increase that often, you're fine. If that one does increase regularly, you may have to use custom resolutions to optimize the display mode's refresh rate.

OSD told me drop frames every 30+s, and it's true. I can see frame drop every minute, and get massive frame drop after 1 hour play. My monitor already@1080p24. If I disable reclock, no frame drop anymore.

[MistahBonzai]

Thanks, I will give it a try.

You will find that it's easy to over due it - like jack the CPU and GPU queues to like 24 and 20. Then you are still dropping frames (because the CPU queue is too high) and perhaps assume you need more rather than less...

You have to tweek to find the right amount for your specific configuration. I quit trying to get it perfect quite a while back. However, I had a go at it again with finding the top end of the CPU queue (it seems like 20 works well for me) and then massaging the GPU queue (where 16 seems like the sweet spot). You'll most likely discover that some video content (like unmoving credits on a black screen) still stimulate dropped frames - but you'll never see it happen :)

Personally I would rather not render frames on fade in/out and leave the queues set lower - it might be me but I find that higher that default queues (~3 frames or so) can lead into other issues that make it harder to track them down.

Good luck and enjoy it - I hate that pesky dropped frames counter when it increments even if it don't mean $h!t ;)

Edit: Tested with x86 configuration as above and then tested with x64 configuration. Discovered that the x64 version (MPC-HC/madVR/LAV/ffdshow(for me cuz I run AviSynth scripts) displayed less 'jitter' in the queue fill stats and that it dropped no frames (or drained queues) when running my movie credits clip which is composed of stationary credits on a black background. I'm jazzed :)

[aufkrawall]

^ aufkrawall is right. That specific options requires you to increase your GPU/CPU queue sizes a bit.

Do I interpret it right when I think you slightly disagree since you seem to lay emphasizing on "a bit"? :)
The last time I tested, it was a bit of unpredictable if performance is sufficient with the option disabled, at least in situations where aren't many GPU resources left.
This is why I personally really wouldn't recommend to turn it off, there seems to be a realistic chance of unexpected frame drops in performance critical situations.
(Well, since there are so many bad sources, I'd simply recommend to always use a deband strength of medium or even high without fade detection.)

[omarank]

Well, I think currently most displays that do passive 3D are using LG panels and those are row interleaved. I'm not sure if Sharp still builds passive 3D screens. Anyway, I guess I can do row interleaved, too, but then we run into the problem mentioned by huhn (I think) that many TVs these days convert down to 4:2:2 for processing, and that would destroy the left/right chroma seperation. So I'm not sure how useful such a mode would really be.

Ok, if the current Passive displays are mostly Row Interleaved, it makes sense to not spend time on implementing Column Interleaved.

Talking about the 4:2:2 processing, I think every TV has PC mode or equivalent which preserves chroma resolution. The user can use that mode when watching 3D. You may even put a note beside the Interleaved option recommending 4:4:4 mode in TV. The very idea behind sending Interleaved frames to the TV is to avoid any TV processing and use madVR for all processing. A Passive TV user will basically have two choices: either send frame packed 3D and let the TV switch to 3D mode (with not so good processing), or send properly processed Interleaved frames and switch the TV to 4:4:4 mode (if he normally uses 4:2:2 mode). I believe the latter will be preferred by most.

[huhn]

Ok, if the current Passive displays are mostly Row Interleaved, it makes sense to not spend time on implementing Column Interleaved.

Talking about the 4:2:2 processing, I think every TV has PC mode or equivalent which preserves chroma resolution. The user can use that mode when watching 3D. You may even put a note beside the Interleaved option recommending 4:4:4 mode in TV. The very idea behind sending Interleaved frames to the TV is to avoid any TV processing and use madVR for all processing. A Passive TV user will basically have two choices: either send frame packed 3D and let the TV switch to 3D mode (with not so good processing), or send properly processed Interleaved frames and switch the TV to 4:4:4 mode (if he normally uses 4:2:2 mode). I believe the latter will be preferred by most.


most TV have issue with PC mode a lot don't have an PC mode and some are even forcing overscan no matter what.

than you need a note about the underscaling in the AMD driver.

the list of never ending possible issues.

[madshi]

When the crash happens, the OSD is showing the refresh rate is in "23hz" (eg near 23.976 not 47.xxx).
Ok, thanks. Does it not help if you let madVR enable/disable OS 3D support for you, depending on whether the content is 2D or 3D?

Seems that no matter what MPC-HC can't engage 3D Frame-packing mode directly, I have to go from fullscreen to windowed to fullscreen to windowed again for frame-packed 3D to activate.
Interesting. Which GPU? Which OS? Which display mode were you using before starting video playback? Do you have D3D11 presentation activated? Do you have madVR display mode switching activated?

Also MadVR won't switch back to 2D after I close MPC-HC if my resolution was 1080p before I activated Frame-packed 3D.
That's probably GPU driver specific.

cant use the new builds at all.. :(
Everything from madVR v0.90.0 and upwards isnt working for me.

It plays too fast sometimes and when i want to go into fullscreen it freezes or black screen or it doesnt go into fullscreen at all and stops all together..

My TV and Hardware is:

Win 7 64bit, gtx670, intel q9550
Including v0.90.2? And v0.89.19 works without any of these issues? When it freezes, does the media player still react to key presses, right mouse click etc? Or is the media player totally frozen, too?

I'm getting consistent crashes with the last 2-3 versions for some reason. Same exact config, files, and playback environment I've had before.

Crash report: https://drive.google.com/file/d/0B9iVOLolmqxdR0ZlSUdrY1RnODg/view
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.

OSD told me drop frames every 30+s, and it's true. I can see frame drop every minute, and get massive frame drop after 1 hour play. My monitor already@1080p24. If I disable reclock, no frame drop anymore.
Then why do you enable reclock?

You could try to reset the reclock timing database, that might help. In any case, this sounds like a reclock problem to me.

Do I interpret it right when I think you slightly disagree since you seem to lay emphasizing on "a bit"? :)
The last time I tested, it was a bit of unpredictable if performance is sufficient with the option disabled, at least in situations where aren't many GPU resources left.
This is why I personally really wouldn't recommend to turn it off, there seems to be a realistic chance of unexpected frame drops in performance critical situations.
(Well, since there are so many bad sources, I'd simply recommend to always use a deband strength of medium or even high without fade detection.)
I guess it all depends on your GPU RAM size. Increasing the CPU & GPU queue sizes shouldn't have any negative effect on anything, as long as you have enough RAM.

Ok, if the current Passive displays are mostly Row Interleaved, it makes sense to not spend time on implementing Column Interleaved.
Yeah. On the other hand, the code will be 99% identical, so it wouldn't be much extra work.

most TV have issue with PC mode a lot don't have an PC mode and some are even forcing overscan no matter what.

than you need a note about the underscaling in the AMD driver.

the list of never ending possible issues.
Yes, there are several potential issues. But I suppose giving the user the option to try letting madVR render directly to the display's specific needs shouldn't harm. The user can try if it works well for him, he doesn't have to use it. And it will be disabled by default.

[XTrojan]

PC Mode is overall bad for movies since it disables 10p and 2p whites and forces full native colors.
Not to mention disabling 24p mode on some TVs and forcing overscan. Some TVs also use anti-blur that get disabled with PC mode on that can ruin movies.

[sat4all]

You will find that it's easy to over due it - like jack the CPU and GPU queues to like 24 and 20. Then you are still dropping frames (because the CPU queue is too high) and perhaps assume you need more rather than less...

You have to tweek to find the right amount for your specific configuration. I quit trying to get it perfect quite a while back. However, I had a go at it again with finding the top end of the CPU queue (it seems like 20 works well for me) and then massaging the GPU queue (where 16 seems like the sweet spot). You'll most likely discover that some video content (like unmoving credits on a black screen) still stimulate dropped frames - but you'll never see it happen :)

Personally I would rather not render frames on fade in/out and leave the queues set lower - it might be me but I find that higher that default queues (~3 frames or so) can lead into other issues that make it harder to track them down.

Good luck and enjoy it - I hate that pesky dropped frames counter when it increments even if it don't mean $h!t ;)

Edit: Tested with x86 configuration as above and then tested with x64 configuration. Discovered that the x64 version (MPC-HC/madVR/LAV/ffdshow(for me cuz I run AviSynth scripts) displayed less 'jitter' in the queue fill stats and that it dropped no frames (or drained queues) when running my movie credits clip which is composed of stationary credits on a black background. I'm jazzed :)

ok i've managed to find that sweet spot.
Radeon 7950: CPU: 32 / GPU: 16
NUC: CPU: 48 / GPU: 24
Any side effects when increasing the queue? Anandtech's nuc review recommand maxing out both! huh?
Edit: madshi have already answered this

I guess it all depends on your GPU RAM size. Increasing the CPU & GPU queue sizes shouldn't have any negative effect on anything, as long as you have enough RAM.

[XTrojan]

Interesting. Which GPU? Which OS? Which display mode were you using before starting video playback? Do you have D3D11 presentation activated? Do you have madVR display mode switching activated?


That's probably GPU driver specific.

Using GTX 970, Windows 10. Yes I got D3D11 ticked, display mode switching for all files having "3D" in their names switches to "1080p23", this could be normal 1080p23 maybe instead of 3D one? Since I got 1080p23 for 2D as well in my Nvidia settings.

When I switch from 1080p60 to 1080p23 3D will activate but it won't stop even after I close the player, interesting that 2160p fixes this issue but makes it so I can't engage 3D directly.

I use reclock but I have to tell MadVR to quit 3D before entering 2D movies otherwise reclock registers movies as 48.000Fps, in 3D there's no issue it simply just doubles the framerate and adjusts the audio fine.

[XTrojan]

ok i've managed to find that sweet spot.
Radeon 7950: CPU: 32 / GPU: 16
NUC: CPU: 48 / GPU: 24
Any side effects when increasing the queue? Anandtech's nuc review recommand maxing out both! huh?

RAM usage, both GPU and normal RAM, also if you speedup or slowdown or similar, frames get removed from queue, possibly causing lag afaik.

[madshi]

I use reclock but I have to tell MadVR to quit 3D before entering 2D movies otherwise reclock registers movies as 48.000Fps, in 3D there's no issue it simply just doubles the framerate and adjusts the audio fine.
Yes, NVidia and AMD GPUs have a rather weird behaviour in 3D which looks like 48fps instead of 24fps. madVR has the same detection problem as Reclock, but madVR internally corrects for that. Intel doesn't have this issue, it always looks like 24fps, in both 2D and 3D.

[jmone]

Ok, thanks. Does it not help if you let madVR enable/disable OS 3D support for you, depending on whether the content is 2D or 3D?


No - if anything it is worse with all video crashing which is why I started from the most basic test config I could do.

If I keep the same simple test setup but enable all the 3D Check Boxs in madVR, I get a black screen with the madVR Error Box (See link) instead of the hard crash.

https://dl.dropboxusercontent.com/u/59011278/madVR3DC2.jpg

[madshi]

No - if anything it is worse with all video crashing which is why I started from the most basic test config I could do.

If I keep the same simple test setup but enable all the 3D Check Boxs in madVR, I get a black screen with the madVR Error Box (See link) instead of the hard crash.

https://dl.dropboxusercontent.com/u/59011278/madVR3DC2.jpg
Thanks, but a screenshot doesn't help, I need the bug report. Please press on "show bug report", then press Ctrl+C to copy the bug report to the clipboard.

[jmone]

Thanks, but a screenshot doesn't help, I need the bug report. Please press on "show bug report", then press Ctrl+C to copy the bug report to the clipboard.

Here is the bug report (note: in this one the player is still going and you get sound. Just a black screen)

https://dl.dropboxusercontent.com/u/59011278/madvrc2.txt

[madshi]

Here is the bug report (note: in this one the player is still going and you get sound. Just a black screen)

https://dl.dropboxusercontent.com/u/59011278/madvrc2.txt
Ouch, thanks! Does this test build fix the problem?

Edit: new build:
http://madshi.net/madVRjmone2.rar

[jmone]

Ouch, thanks! Does this test build fix the problem?

Edit: new build:
http://madshi.net/madVRjmone2.rar

Nope - same result - latest log:
https://dl.dropboxusercontent.com/u/59011278/madvrc3.txt

[madshi]

Yeah, sorry, you were too fast... :o I uploaded the wrong build. Please try again the link in my previous edited post.

[jmone]

Yeah, sorry, you were too fast... :o I uploaded the wrong build. Please try again the link in my previous edited post.

Excellent - Crash is fixed!

Did some quick testing, as follows:
- Play 3D Video = It is in 3D!
- Stop and Play same file again = SBS D9 mode
- Stop and Play a 2D Video = Fine
- Stop and Play the 3D File = It is in 3D but playback is not advancing. I need to press Pause then Play and it then plays fine

Do you want some Debug logs of this?

[jmone]

I should say it is apparent that playback starts while my TV/GPU is switching mode several times (and I see a "no hdmi connection msg" in the middle of all this display switching)

[madshi]

Did some quick testing, as follows:
- Play 3D Video = It is in 3D!
- Stop and Play same file again = SBS D9 mode
- Stop and Play a 2D Video = Fine
- Stop and Play the 3D File = It is in 3D but playback is not advancing. I need to press Pause then Play and it then plays fine

Do you want some Debug logs of this?
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!

I should say it is apparent that playback starts while my TV/GPU is switching mode several times (and I see a "no hdmi connection msg" in the middle of all this display switching)
Yeah, unfortunately madVR cannot know how long the display needs to resync. But I suppose I could add an option to delay playback start when switching into 3D mode. Would that be helpful? But usually at the start of a movie, there's some stupid movie studio intro, anyway, so I'm not sure whether it's really necessary...

Edit: You'll need a new debug build for this, with the crash bug fixed. Will upload that in 2 hours or so...

[jmone]

Yes it is possible to grab the debug logs in this method. It's 9pm here so once I have the new build I'll generate them tomorrow and upload a pack just showing the issues. Thanks for the quick to and fro on this and fixing the crash (makes it easier to find the rest)!

edit - also I don't care about losing the first few seconds when switching modes, more that I thought the loss of HDMI signal during the switching may cause some of the issues.

[4h4h270]

Then why do you enable reclock?

You could try to reset the reclock timing database, that might help. In any case, this sounds like a reclock problem to me.

I tried to disable reclock, still get some frame drop like OSD told me every 4min+.

Another problem is if I play more than 1 hour, I will get massive frame drop in FSE. I have to pause play and switch to windowed mode wait few seconds then the frame drop gone.

disable frame packing playback like SBS is the most reliable way in my system.

[Sunset1982]

Edit: new build:
http://madshi.net/madVRjmone2.rar

good news mashi! With this new build, my crahes when starting 3D or 2D files after 3D is activated in OS control panel are fixed too!


Bad news are: osd says "D3D11 windowed 3D" but video is shown in 2D. And rendertimes are higher as normal 80ms instead of 38ms.

Any idea? I'm using a LG 4K passive tv. Could that be a problem?

Edit:
OSD says, movie resolution is 1080p and scaling to 2160p... shouldn't it be shown in 1080p 3D mode without scaling?


Edit 2: My native desktop resolution is 38040x2160. It can manually change to 3D mode in nvidia control panel to 1080p(3D) mode. The my desktop is shown in 3D with 1080p resolution. If I start a 3D MVC Mkv now, madvr crashes and my tv is telling me that there is no 3D signal and changing back to 2D mode. When desktop is switching back to 3D mode, tv gets a message that there is 3D mode active again.

[madshi]

I tried to disable reclock, still get some frame drop like OSD told me every 4min+.
Then you need to create a custom resolution to get your refresh rate tuned.

Another problem is if I play more than 1 hour, I will get massive frame drop in FSE. I have to pause play and switch to windowed mode wait few seconds then the frame drop gone.
Not sure why that occurs. Do you have any 3rd party application running which might access the GPU?

Bad news are: osd says "D3D11 windowed 3D" but video is shown in 2D. And rendertimes are higher as normal 80ms instead of 38ms.
Double render times are expected if madVR tries to render 3D.

OSD says, movie resolution is 1080p and scaling to 2160p... shouldn't it be shown in 1080p 3D mode without scaling?
That is with the test build? That sounds strange. The test build should manually switch your GPU to 1080p23 mode if you try to play 3D content. Why is your GPU mode still 2160p? Do you have display mode switching active somewhere outside of madVR? E.g. do you have MPC-HC/BE's display mode switcher active? Or some other media player's display mode switcher?

Edit 2: My native desktop resolution is 38040x2160. It can manually change to 3D mode in nvidia control panel to 1080p(3D) mode. The my desktop is shown in 3D with 1080p resolution. If I start a 3D MVC Mkv now, madvr crashes
Bug report?

[Sunset1982]

That is with the test build? That sounds strange. The test build should manually switch your GPU to 1080p23 mode if you try to play 3D content. Why is your GPU mode still 2160p? Do you have display mode switching active somewhere outside of madVR? E.g. do you have MPC-HC/BE's display mode switcher active? Or some other media player's display mode switcher?

nope, I use madvr to switch display modes... do I have to write a 1080p23 (3D) mode under the display modes tab?


Bug report?

I'll try to get one, last time I was told that mpc-hc has crashed. Ill try and be back in some mins...

[Sunset1982]

@madshi:

found the bug... the bug was me!!! :rolleyes:

forgot to write down 1080p23 mode under the display modes tab!!
now 3D is working!!


And the crash by selecting 1080p3D mode was, because I was manually switching to 1080p24 and not 1080p23 mode. If I select 1080p23, it works!

[madshi]

@madshi:

found the bug... the bug was me!!! :rolleyes:

forgot to write down 1080p23 mode under the display modes tab!!
now 3D is working!!


And the crash by selecting 1080p3D mode was, because I was manually switching to 1080p24 and not 1080p23 mode. If I select 1080p23, it works!
That's still a bit surprising, though, because the test build was supposed to automatically switch to 1080p23 for 3D content, regardless of which mode you entered in the display modes tab.

[XTrojan]

That's still a bit surprising, though, because the test build was supposed to automatically switch to 1080p23 for 3D content, regardless of which mode you entered in the display modes tab.

For me it won't switch, I have to type in 1080p23 and even then it seems like it switches to 2D first before activating frame-packed mode after I tab out and in again, it's rather weird.

I watched Full-SBS yesterday with no issues, the only problem is the amount of GPU power consumed, my 970 could only handle Jinc3 Upscaling + Chroma sampling and ordered dithering on 2160p Full-SBS mode.

Frame-packed mode seems to drain like 4x less power, and since upscaling 3D content to 4k seems near impossible frame-packed is the way, the only issue is that it's very buggy at the moment, my custom profile still has bugs when switching from 2D to frame-packed.

I'll try drop a debug If i got time.

[madshi]

For me it won't switch, I have to type in 1080p23 and even then it seems like it switches to 2D first before activating frame-packed mode after I tab out and in again, it's rather weird.
Is the with official v0.90.2 or with today's test build?

[XTrojan]

Is the with official v0.90.2 or with today's test build?

90.2, didn't see there was a test version out :s

[Sunset1982]

Is the with official v0.90.2 or with today's test build?

same with me (used latest testbuild). 3D is working but only if I put 1080p23 in the display mode tab. But I think it'll choose it even for 2D and will not upscale other movies, right?

[madshi]

same with me (used latest testbuild). 3D is working but only if I put 1080p23 in the display mode tab.
Can I have two debug logs, please? One with 1080p23 in the display mode tab, and one without. So that I can compare why there's a difference. Thanks.

Please create the logs with this new test build (contains both release and debug build, but only 32bit):

http://madshi.net/madVR3dlog.rar

[Sunset1982]

Can I have two debug logs, please?

ok, but how to do this?

[Sunset1982]

ok, created the two logfiles. hopefully if done it right.

https://www.dropbox.com/s/uql4cdtsqpnm5o4/madVR%20-%20log%28with%201080p23%29.txt?dl=0

https://www.dropbox.com/s/gttyauk62fsdz9v/madVR%20-%20log%28without%201080p23%29.txt?dl=0

[madshi]

ok, created the two logfiles. hopefully if done it right.

https://www.dropbox.com/s/uql4cdtsqpnm5o4/madVR%20-%20log%28with%201080p23%29.txt?dl=0

https://www.dropbox.com/s/gttyauk62fsdz9v/madVR%20-%20log%28without%201080p23%29.txt?dl=0
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.

[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]

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]

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.

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]

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]

@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/1powwghbwa65zbx/madVR%20-%20crashlog%202D.txt?dl=0

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




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

thank you!

[har3inger]

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]

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.