View Single Post
Old 17th May 2009, 07:59   #1049  |  Link
madshi
Registered Developer
 
Join Date: Sep 2006
Posts: 9,140
Quote:
Originally Posted by wayland View Post
how do you open the detailed osd in 0.10? ctrl+j twice doesnt seem to do it any more.
There is only one OSD in 0.10.

Quote:
Originally Posted by wayland View Post
also going a bit off topic but how should the dynamic range be set on nvidia hardware full(0-255) or limited (16-235)? either seems to result in a differant image with madvr and HR compared to evr custom
Quote:
Originally Posted by wayland View Post
about the nvidia question i asked changing from rgb to YCbCr444 fixes it
If you do that, the graphics card will apply processing on madVR's output, which is what we usually don't want. Furthermore, if the image looks different that way, your GPU is probably doing something wrong. Cause madVR's output is how it's supposed to look. I'd guess that your EVR Custom image quality is all wrong. However, there's a chance, albeit very low, that your display doesn't handle RGB input correctly and needs YCbCr input. But I really doubt that's the case...

Quote:
Originally Posted by honai View Post
Tested it again on the Iron Man BD w/ the 4770, refresh rate was correctly detected at 60.00071 Hz (and stayed there for the whole 250s I tested), decoder queue 16/16 fixed, upload queue 4/8 fixed, render queue 8/8 fixed, 10 dropped frames, 2 delayed, all during first few seconds. Playback "feels" almost perfectly smooth, the very tiny stuttering could also be the effect of 23.976@60Hz playback. Feels definitely as smooth as the best iteration of Beliyaal's EVR CP.
Good to hear. For me EVR CP is not perfectly smooth, either. I guess my PC is just not up to the task in windowed mode. But the good thing is that on my PC madVR seems to be as smooth as EVR CP now, too, just like on your PC.

Quote:
Originally Posted by honai View Post
One tiny request: Could you make the OSD position toggle between the top and bottom? Might come in handy for us plasma users.
Maybe later. There are so many very important things that still need to be done. So I don't really want to spend time on doing things like moveable OSD right now when more important things are still on the to do list...

Quote:
Originally Posted by Mark_A_W View Post
Madshi, this new version, well...


YEA HAR!!


display 95.90368Hz (397s) perfect, time just keeps growing
movie fps 23.976fps (says source filter)
decoder queue 16/16
upload queue 4/8
render queue 8/8
movie res 1920,1080
target rectangle 0,0,1920,1080
v sync interval 10.43ms
movie frame interval 41.71ms
dropped frames 3 Just from startup, stable after that
delayed frames 3 Just from startup, stable after that

Playback is smooth, so far.


Quote:
Originally Posted by Mark_A_W View Post
Was it the interlaced res that causes the scanline reporting issue?
I don't think so. madVR asks the GPU about which scanline is currently being drawn. The allowed numbers (according to Microsoft documentation) are between 0 and the height of the graphics mode you're using. So if your GPU is set to 1080p, your GPU may return scanline numbers between 0 and 1080. However, I got scanlines reported like 1116. That confused my display refresh rate calculation formulas. This looks like a simple bug in the graphics driver to me.

Quote:
Originally Posted by Mark_A_W View Post
A small feature request: A tearing/smoothness test. Using Zoomplayer, with Reclock "bypassed", I have no tearing bar test, which is very handy for checking issues.
Yeah, would make sense. But just as the moveable OSD position I have to say that there are simply more important things that need to be done first.

Quote:
Originally Posted by Mark_A_W View Post
And that raises the Reclock issue...are you using Reclock? If so, what settings? Active or bypassed? If not, will Reclock bypassed, just a WASAPI renderer, cause any issues? It doesn't seem to.
Currently I'm not using ReClock, but I might use it soon due to WASAPI rendering.

Quote:
Originally Posted by Mark_A_W View Post
I'm slightly concerned about the need for Fullscreen Exclusive for "perfect" playback. I understand why (I think), but it's a bit clunky - and there goes the UI on Zoomplayer.
Well, if you have perfectly smooth playback in windowed mode then just use that. Maybe faster PCs can do that.

Quote:
Originally Posted by Thunderbolt8 View Post
just to nitpick, does it have to be 0.10 or 1.0? 10 comes after 9, yes, but just from the looks after 0.9 I'd expect to get 1.0. I'd rather say that 0.10 follows after 0.09 :P
I thought about going 1.0. After all smooth playback is a BIG thing. But 1.0 is supposed to be a stable build where all important features are implemented - and madVR is not there yet. So I decided to go 0.10. Yeah, so I should have started with 0.01. Well, there are more important things than version numbers...

Quote:
Originally Posted by Hypernova View Post
Refresh rate is correct. Upload queue is ~4-5/8. Render queue is ~7-8/8. But I can't get any smooth playback if my setting is anything beyond Bilinear/Bilinear when go fullscreen (2560x1600). Drop and delayed frame also keep on incresing. Maybe I did something wrong?
I don't think you did anything wrong. I'm not totally sure why some PCs seemingly can do smooth playback without any hiccups in windowed mode while other PCs can't. On my PC my logs are telling me that sometimes the PC is busy doing "something" (I don't know what) and so madVR is not getting any processing time for sometimes 30ms at a time. In such a situation there's no way to avoid a delayed or even dropped frame. Probably it's the same cause for you. You could try minimizing the amount of processes and services running on your PC that might interfere. Maybe that helps. You could also try reducing that output resolution a bit. 2560x1600 is quite taxing on the hardware, of course. Although your upload and render queues do look fine, so your GPU seems to be up to the task... I can only hope that fullscreen exclusive mode will fix the remaining non-smooth problems on your PC - and mine. Although I'll get a new HTPC early next week. So maybe my problems will be gone by then...

Quote:
Originally Posted by cyberbeing View Post
It seems much smoother now, which is good, but it's unstable. I've had at least 10 random lockups of the renderer in the last hour, when doing things like pausing, seeking, and going from fullscreen <-> windowed. If you don't mess with it, it seems fine though.
Yeah, exactly what I wrote in the release notes...

Of course I could have waited with releasing madVR 0.10 until it's completely stable. But that would have meant that you guys would have had to wait another 1-2 weeks.

Quote:
Originally Posted by cyberbeing View Post
Pausing the video and going to fullscreen seems to lockup the renderer every time. It goes to fullscreen with the screen black, displays what I assume was in the frame cache, the screen goes black again, and the renderer locks-up.

There is a randomly occurring issue when it get the end of the file. Sometimes it will exit fullscreen, display a black frame, and then playback the last half-second (emptying the frame cache?).

Moving the video window around with MPC-HC results in massive flickering and tearing.
Ok, thanks, will look into that (next week).

Quote:
Originally Posted by cyberbeing View Post
For some reason I occasionally get delayed frames (the render queue fluxuates between 7/8 and 8/8) when I downscale a 1920x1080 video to 1600x900 (1600x1200 display res). When upscaling, I don't have this problem.
The render queue fluctuating between 7/8 and 8/8 is perfectly fine. It may go down to 4/8 without having to worry. Lower values than 4/8 might be dangerous for smooth motion, though. And of course the "delayed frames" number in the OSD increasing throughout the whole movie is bad.

Quote:
Originally Posted by cyberbeing View Post
It's also not remembering luma scaling settings
Ouch, true.

Quote:
Originally Posted by Egh View Post
Epically superior build!!!!


Quote:
Originally Posted by Egh View Post
Believe it or nuts, but you [almost] solved the secondary monitor problem! Now it doesn't max one of the cores, keeps it at half (i.e. tends to be around 50%) on one of the cores! That said, however, there's still substantial increase when moving MPCHC window to a different monitor. Increase happens on one core only so there's still something lurking in the code. But generally for 720p here I can even move the window and still have good CPU rates.
Moving the window to another monitor while the playback is already running is not supported yet. Currently in order to get the best results you have to move MPC HC to the right monitor first and only then load the movie file and start playback.

Quote:
Originally Posted by Egh View Post
That is still pales in comparison to the CPU usage. What did you do?!!! It now runs on primary monitor with just half of the previous CPU load!!!
Using lanczos4&softcubic50 I can achieve just less than 20% cpu typical usage. That is on 720p avc content slightly downscaled (so shader math still works).
It is indeed too early to compare HR and mVR directly, as mVR doesnt' do subs yet, but I expect it to be on par regarding CPU usage.
Yeah. Seems like redoing the presentation logic did the trick with CPU usage. I always said that madVR was not supposed to consume (much) more CPU than the other renderers. For me madVR 0.10 consumes slightly more than EVR-CP, but really only slightly more. CPU consumption got down quite a bit compared to 0.9. Maybe I should have added that to the changelog...

Quote:
Originally Posted by Egh View Post
a. Chroma upscaling setting is not remembered.
b. Ugly when moving window around, video is flickering ( blank black area clearly seen and then video).
c. Even more annoying -- in fullscreen mode it flickers (again showing blank black frame and then back to video) when moving cursor to the control bar below.
It flickers twice -- first when opening the bar and when closing it.
Yeah, that are all things I need to work on.

Quote:
Originally Posted by Egh View Post
d. Each change of upscale method leads to quite serious amount of dropped frames.
Not nice. But I don't really know if I will spend much time to improve that. After all you usually won't change these settings in the middle of watching a movie. One of the reasons for the dropped/delayed frames when changing settings is that madVR clears the rendering queue to make sure that the changed settings show effect immediately.

Quote:
Originally Posted by Mark_A_W View Post
I'm using Zoomplayer and when running MadVR my monitors turn off (screensaver settings). When running any other renderer all is well.
So basically I need to stop screensavers from appearing, right?
madshi is offline   Reply With Quote