For AtmoLight users that also use Hyperion I've attached a new build as it seems MadVR is sometimes not sending the frames in correct order upon playback stop which messes up priorities (i.e. leaves leds on), doesn't always happen and you only need it if you use Hyperion with it
Will include this fix in next official release as well, basically what it does is set a frame expiry in Hyperion message and after 2,5s it clears the leds if nothing new was received.
Been test driving V222 and aside from the random issue with black screen during GUI <--> fullscreen toggle it works pretty well, in LAV you have to switch to DXVA if you plan to use NNEDI3 which is a bug in Nvidia drivers most likely as Zoom Player has the same results.
Cranked it up to 64 neurons and 128 neurons for double super sampling (Jinc) and just had to slightly reduce the queues to 8 / 4 to get render times below 20ms but that's not a big deal so long as the GPU can handle it , GPU load on the GTX1080 averages about 60% with 90% spikes (lower when turbo does its thing)
Dropped frames are from me toggling GUI / Fullscreen but during playback it stays at 0 , used this guide for most things which has nice stats and good examples:
When using madvr I notice the following issue: the screensaver isn't working properly. I use the black screen.
When I pause a movie, it will show the mediaportal gui. This disappears after the set time for the screensaver. But the movie itself stays visible.
Hi
After much testing I have somewhat isolated the problem of the long stop. I does not occurr if I set Hardware Decoder to use" for Hardware Accelaration to none in LAV filters. As soon as I use DXVA2 Copy Back for hardware accel. the long stop appears in both Madvr and HEVC branches regardless of EVR or Madvr, sorry I did not try in the std. 1.15. The problem only seems to happen with a GPU that supports HEVC, i.e I do not recall it being so bad when I was using a non HEVC AMD GPU(HD6670) either with Catalyst or Crimson drivers, but would need to retest to be 100% sure. Deselecting HEVC from hardware accelaration in the LAV also does not help.
The bottom line is that the problem is not specific to Madvr, or the Madvr branch but seems to be a LAV/DXVA2 copyback/AMD RX 460 issue (assumming no one has seen this with Nvidia or Intel GPUs that support HEVC etc.
Hope that helps toward a resolution.
So I can avoid the long stop by not uising hardware accel. but then I have a heavy CPU load when viewing HD TV.
I will try thje new Dshowhelpers and report back tomorrow, maybe.