View Issue Details

IDProjectCategoryView StatusLast Update
0000073madVRbugpublic2013-06-06 14:48
Reporter6233638 Assigned Tomadshi  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Platformx64OSWindows 8OS Version6.2 (Build 9200)
Summary0000073: Display Mode is not restored when playback is stopped in JRiver Media Center
DescriptionIf JRiver Media Center's switcher is disabled, and madVR is allowed to handle all display mode switching, the original refresh rate is not restored when playback is stopped.

The refresh rate is only restored if you exit fullscreen playback first.
Steps To Reproduce1. Disable Media Center's Display Mode Switcher (Tools > Options > Video > Display Settings)
2. Play any video which requires the refresh rate to be changed.
3. Stop playback without exiting fullscreen mode.
Additional InformationThe stop button may need to be enabled under: Tools > Options > General > Behavior > Show stop button
TagsNo tags attached.
madVR Version0.86.2
Media Player (with version info)JRiver Media Center 18.0.194
Splitter (with version info)LAV Splitter 0.57
Decoder (with version info)LAV Video 0.57
DecodingDXVA2 Copyback
Deinterlacingauto mode
DXVA2 Scaling Activeno
Aero / Desktop CompositionOn
Problem occurs with modewindowed mode
GPU ManufacturerNVidia
GPU ModelGTX 570
GPU Driver Version320.18 WHQL

Activities

6233638

2013-06-04 21:09

reporter   ~0000143

Appears to be an issue with Media Center.

If Media Center is closed, the refresh rate is restored.
If Media Server is running, this must also be closed for the refresh rate to be restored.

http://forum.doom9.org/showpost.php?p=1631666&postcount=18991

madshi

2013-06-04 22:21

administrator   ~0000147

madVR has a special logic to restore the original display mode when the media player process is closed. This is done so that restauration works even if the media player crashes during playback. So if you close MC, this special logic comes into play.

Not sure why the display mode is not restored when stopping playback. I'll have to check that...

madshi

2013-06-06 14:48

administrator   ~0000170

This will be fixed in v0.86.3.

Issue History

Date Modified Username Field Change
2013-06-04 20:59 6233638 New Issue
2013-06-04 21:09 6233638 Note Added: 0000143
2013-06-04 22:21 madshi Note Added: 0000147
2013-06-04 22:21 madshi Assigned To => madshi
2013-06-04 22:21 madshi Status new => assigned
2013-06-06 14:48 madshi Note Added: 0000170
2013-06-06 14:48 madshi Status assigned => closed
2013-06-06 14:48 madshi Resolution open => fixed