View Issue Details

IDProjectCategoryView StatusLast Update
0000040madVRbugpublic2013-06-04 14:37
Reporterturbojet Assigned Tomadshi  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionnot fixable 
PlatformWindows OS7OS VersionSP1
Summary0000040: Switching to display with different refresh rate = dropped frames
DescriptionFor example switching from a 48hz display to a 60hz display without opening a new player instance results in poor playback, lots of frames dropped.
Steps To Reproduce1. Start a video on 1 display
2. Switch to a single display with a different refresh rate
3. Play the video
Additional InformationDoesn't happen with EVR
TagsNo tags attached.
madVR Version85.1
Media Player (with version info)mpc-be 2418
Splitter (with version info)mpc
Decoder (with version info)ffdshow 4499
DecodingSoftware
Deinterlacingnone (progressive)
DXVA2 Scaling Activeno
Aero / Desktop CompositionOn
Problem occurs with modewindowed mode
GPU ManufacturerNVidia
GPU Modelgts250
GPU Driver Versionlatest whql

Activities

turbojet

2013-04-14 00:42

reporter  

madshi

2013-06-01 12:57

administrator   ~0000099

I can't reproduce the issue. I moved a video here between 2 monitors (back and forth). One was 60Hz, the other 50Hz. The video was 24fps. No issues whatsoever. No frame drops. Neither with SmoothMotion FRC on nor off.

Also I've looked at your log. It mentions a few frame drops at the start of playback (during the first 3 seconds of playback), but afterwards there are no frame drops, anymore!

Maybe this depends on which decoder you're using (DXVA? CUDA? software?), or which framerate the movie has? If I can't reproduce the issue, I can't fix it.

turbojet

2013-06-03 23:04

reporter   ~0000136

Last edited: 2013-06-03 23:05

I tried switching to lav from ffdshow and different framerates with no effect. I think it has something to do with window mode relying on composition and not catching to correct composition rate on display change. Overlay and FSE don't have the problem. Attached is stats while video is dropping a lot of frames.

MadVR doesn't report any dropped frames but also doesn't report when gpu usage is 50-70% in window mode with an nvidia 9500GT, 250GTX or intel hd3000. In this case the video is not smooth and looks like dropped frames. Going above about 70% gpu, madvr starts reporting dropped frames, go below about 50% and video plays smoothly. Overlay and FSE play fine at these gpu loads. Is madvr reporting only dropped frames while rendering or does it also try to track dropped frames displayed?

turbojet

2013-06-03 23:05

reporter  

dispchange.PNG (296,631 bytes)

madshi

2013-06-04 09:03

administrator   ~0000138

Dropped frames are frames which were not displayed/presented at all, regardless of whether they were rendered or not.

Please tell me for both monitors:

(1) Which refresh rate does madVR report?
(2) Which composition rate does madVR report?

And which framerate (after deinterlacing) does the video have? And there are no frame drops or presentation glitches reported on the madVR OSD, correct?

madshi

2013-06-04 14:37

administrator   ~0000139

P.S: I've double checked on my setup. The problem seems to be that Windows always seems to use the composition rate of the primary monitor. So if you do playback on the secondary monitor, and if the secondary monitor has a different refresh rate than the primary, refresh rate and composition rate don't match. In this situation it's technically not possible to achieve smooth playback. Maybe EVR plays somewhat better in this specific situation, but technically, madVR can't achieve perfect smoothness, if the composition rate doesn't match the refresh rate.

The only solution to this is to avoid the situation where composition rate and refresh rate mismatch. So: Use overlay, FSE, or make your secondary monitor primary, if you want to play a movie on it... ;-/

Issue History

Date Modified Username Field Change
2013-04-14 00:42 turbojet New Issue
2013-04-14 00:42 turbojet File Added: madVR - change refreshrate.zip
2013-05-31 21:22 madshi Assigned To => madshi
2013-05-31 21:22 madshi Status new => assigned
2013-06-01 12:57 madshi Note Added: 0000099
2013-06-01 12:57 madshi Status assigned => feedback
2013-06-03 23:04 turbojet Note Added: 0000136
2013-06-03 23:04 turbojet Status feedback => assigned
2013-06-03 23:05 turbojet Note Edited: 0000136
2013-06-03 23:05 turbojet File Added: dispchange.PNG
2013-06-04 09:03 madshi Note Added: 0000138
2013-06-04 09:04 madshi Status assigned => feedback
2013-06-04 14:37 madshi Note Added: 0000139
2013-06-04 14:37 madshi Status feedback => closed
2013-06-04 14:37 madshi Resolution open => not fixable