|
|
Which is the first queue (from top to bottom) which gets into trouble? That's the likely bottleneck. What happens if you use software decoding? |
|
|
|
|
|
It all seems to happen at once. It just drops instantly rather than gradually reducing. I've attached a log which shows behavior in DX9 FSW when I hit the ALT key to bring up the menus over the video compared to the video playing full-screen. |
|
|
With first" I didn't mean in a temporal sense, I meant literally the first in the OSD list of queues, from top to bottom. E.g. if the decoder queue goes empty, all other queues will follow. That means the decoder queue is at fault. If the decoder stays nicely filled, but the upload queue gets empty, all other queues below that follow. So the upload queue is the bottleneck then. |
|
|
It would seem to be, though it's very strange that giving another application focus instead of the madVR window would fix the performance in FSW mode. Not breaking FSE, just giving another application focus when DX11 FSW is active. |
|
|
Ehm, which is the first queue going empty? You didn't clearly say that yet... ;-) |
|
|
queues.png (702 bytes) |
|
|
Sorry. The only one which is *empty* is the present queue. --- Not sure how to edit/remove attached files. The "queues.png" file shows the queues in DX11 FSW when madVR is the active window. "DX11-FSW-Background.png" shows the queues when I have another application in front of the video. |
|
|
DX11-FSW-Background.png (731 bytes) |
|
|
Wow, a monstrous decoder queue... ;-) I can see from the debug log that about once every second there's 200ms in which nothing happens in the log. This causes the queues to empty which can eventually lead to frame drops. So the big question is why does this happen? And why about once every second in regular intervals? I've found one thing in madVR that is done every second: Namely updating the debug OSD. Does the same problem happen with the debug OSD deactivated? Of course it's hard to judge without seeing the debug OSD! ;-) You could create another log with the debug OSD deactivated. Then I can check the log. It could be something external, too. Maybe you have some sort of background process running which interferes? Maybe some sort of GPU watcher like GpuZ or something similar? Try closing all 3rd party software, including the browser. Does that help? |
|
|
Dammit, it's f.lux (https://justgetflux.com/) causing this - even though it was currently "disabled". If I put it in "safe mode" or exit the program, suddenly I'm no longer getting these performance drops. There was me thinking I had already disabled anything which could be affecting it. I'm confused as to why DX9 FSW/Overlay seems completely unaffected by this, and the strange behavior where DX11 FSW is only affected when it's in the foreground, but at least I've figured out the cause. |
|
|
I've seen reports of f.lux causing such issues already in the past, same with GpuZ etc. So I guess I can close this issue? |
|
|
Yes, doesn't seem to be anything wrong on madVR's end. Strange that it only seemed to manifest when deinterlacing 50 FPS content. |
- Anonymous
