View Issue Details

IDProjectCategoryView StatusLast Update
0000227madVRbugpublic2015-03-23 13:56
Reporterromulous Assigned Tomadshi  
Status closedResolutionfixed 
Summary0000227: Pause Message on Zoom Player OSD
DescriptionThis is another bug that was reported to the Zoom tracker (0000624) which bLight thinks is actually a madVR bug. Basically, under some circumstances, the Zoom Player OSD does not display the Pause message when you pause a file.
Steps To Reproduce1. Ensure Zoom is using madVR, and FSE mode in madVR is enabled. Also, the 'Display OSD through MadVR's OSD API (preserves fullscreen exclusive mode)' option must be enabled.
2. Start a file playing in Zoom and enter fullscreen mode, and wait for madVR to enter FSE mode.
3. Then, hit P to pause the file. The Pause message will not appear on the OSD. However, if you then hit P to unpause and then P to pause again, the message will display - so it is only the first time after you start playback that the pause message is blocked.
TagsNo tags attached.
madVR Version0.87.10
Media Player (with version info)Zoom Player v9.1
Splitter (with version info)LAV v0.62
Decoder (with version info)LAV v0.62
Deinterlacingauto mode
DXVA2 Scaling Activeno
Aero / Desktop CompositionOn
Problem occurs with modefullscreen exclusive mode
GPU ManufacturerNVidia
GPU ModelGTX 660Ti
GPU Driver Version337.88



2015-03-22 12:47

administrator   ~0000805

I can't seem to be able to reproduce this with ZP v10. Can you still reproduce it? If so, are you pressing [P] before or after the "Exclusive" madVR OSD message goes away?


2015-03-23 09:17

reporter   ~0000838

Yes, can still reproduce it using the listed steps. P is pressed after the 'exclusive' message has disappeared.


2015-03-23 09:31

administrator   ~0000841

I can't reproduce the issue, for some reason. Is there any way you can send me your ZP v10 settings? I'm not sure where they are stored. You could also send me your madVR settings (settings.bin in your madVR folder, if madVR has write access there, otherwise export the madVR registry folder).


2015-03-23 11:10

reporter   ~0000842


2015-03-23 13:56

administrator   ~0000845

Ok, the settings helped. This issue should be fixed in the next build.

Issue History

Date Modified Username Field Change
2014-07-13 15:18 romulous New Issue
2015-03-22 12:47 madshi Note Added: 0000805
2015-03-22 12:47 madshi Assigned To => madshi
2015-03-22 12:47 madshi Status new => feedback
2015-03-23 09:17 romulous Note Added: 0000838
2015-03-23 09:17 romulous Status feedback => assigned
2015-03-23 09:31 madshi Note Added: 0000841
2015-03-23 09:31 madshi Status assigned => feedback
2015-03-23 11:10 romulous Note Added: 0000842
2015-03-23 11:10 romulous Status feedback => assigned
2015-03-23 13:56 madshi Note Added: 0000845
2015-03-23 13:56 madshi Status assigned => closed
2015-03-23 13:56 madshi Resolution open => fixed