View Single Post
Old 13th July 2015, 13:23   #31739  |  Link
Anime Viewer
Troubleshooter
 
Anime Viewer's Avatar
 
Join Date: Feb 2014
Posts: 339
0s in OSD

Quote:
Originally Posted by madshi View Post
madVR v0.88.17 released

http://madshi.net/madVR.zip

Code:
* madVR now renders in paused and stopped mode, too
* added automatic OSD low latency logic
* added SuperRes anti-ringing filter
* fixed little SuperRes quality detoriation introduced in v0.88.16
* fixed: high GPU consumption in paused mode (PotPlayer, Kodi DSPlayer)
* all (useful) IVideoWindow APIs now work even when no pins are connected
For users, this build is probably not much different to Saturday's test build. Well, at least I hope so. However, for some media player developers there's a big (positive) change. I've been asked to do rendering in paused and stopped modes for a long time, and now finally it's implemented. This required some deeper changes, though, so there's a certain danger of new bugs showing up.

Notes for media player developers:

1) Please set the owner/parent *before* you connect the pins.
2) All the various OSD interfaces in madVR now also work in paused and stopped mode. Maybe you can make use of it in some way?
3) If you're using IOsdRenderCallback, *PLEASE* make sure that your ClearBackground() and RenderOsd() callbacks return "ERROR_EMPTY" if there is no active OSD on screen. This is very important because if you don't return ERROR_EMPTY, madVR will switch into low latency mode to speed up your OSD reaction times. This is good for OSD latency, but not good for video playback reliability.
4) If you're using IMadVROsdServices::OsdSetBitmap, there's a new flag (see header files) that tells madVR whether your OSD bitmap needs low latency or not. Low latency makes sense for OSD elements the user can use to control something, but probably not for purely informational OSD elements.
5) You can see whether madVR is in low latency mode by checking the size of the "present queue". In low latency mode this queue is limited to 2 frames.
I'm not sure which change its from, but my OSD no longer seems to be reporting accurate information:

Even though it says 0s for target rectangle, and all of the queues I'm not seeing any problems with the video playing. (Therefore the dropped frames, delayed frames, and presentation glitches 0s may be correct. I can change my settings to something my system can't handle like 256 neurons, and see if it still reports no problems with drops and glitches to see they are being misreported too). This screen capture of the OSD was taken with the video playing, so it wasn't during a pause or stop.
Edit: When I changed to 256 neurons my render times shot up to 96ms, and I did get dropped frames and presentation glitches so the 0's reported in those areas were accurate.
__________________
System specs: Sager NP9150 SE with i7-3630QM 2.40GHz, 16 GB RAM, 64-bit Windows 10 Pro, NVidia GTX 680M/Intel 4000 HD optimus dual GPU system. Video viewed on LG notebook screen and LG 3D passive TV.

Last edited by Anime Viewer; 13th July 2015 at 13:26. Reason: added results of 256 neuron test
Anime Viewer is offline   Reply With Quote