[WiP] madVR support in MP1 (25 Viewers)

[joecrow]

Sorry to have to report that with v166 I am still seeing intermittent (ca. 50/50 for catchup, better with Live) failures as before, i.e. on starting a video I get a couple of seconds of audio without video then it hangs with a black screen and I have to kill MP with the Task Manager. In the attached log after the initial failure I restarted MP and was able to play the same vid. OK, but another vid then failed. I have also included a Madvr freeze report for the second failure. Does not seem to be a problem with EVR. Since yesterday I have replaced my graphics card, it is now an AMD RX 460, no change on the OV problem but the Elysium clip now plays smoothly and I am using much less CPU for HEVC encoded TV.

 

[azzuro]

@joecrow im interested by your feedback on rx460. Drivers / MP GUI reaction...

 

[Sebastiii]

Sorry to have to report that with v166 I am still seeing intermittent (ca. 50/50 for catchup, better with Live) failures as before, i.e. on starting a video I get a couple of seconds of audio without video then it hangs with a black screen and I have to kill MP with the Task Manager. In the attached log after the initial failure I restarted MP and was able to play the same vid. OK, but another vid then failed. I have also included a Madvr freeze report for the second failure. Does not seem to be a problem with EVR. Since yesterday I have replaced my graphics card, it is now an AMD RX 460, no change on the OV problem but the Elysium clip now plays smoothly and I am using much less CPU for HEVC encoded TV.

It freeze here :

VMR9: mediaCtrl.Stop() 1 for both

I already get that but rarely and was not able to fix it, are you able to try with old GPU to compare ?
In fact somehow the call to stop the directshow graph get stuck and it's timing related for sure (maybe new GPU is faster and then this issue can occurs more quickly)

 

[joecrow]

It freeze here :

VMR9: mediaCtrl.Stop() 1 for both

I already get that but rarely and was not able to fix it, are you able to try with old GPU to compare ?

Not easily, my HTPC is somewhat builtin and getting to it and opening it up is not at all a simple task, sorry. Please note that my previous report of this problem here https://forum.team-mediaportal.com/threads/madvr-support-in-mp1.133972/page-206 was using my old GPU (AMD HD6770), is it the same problem?

In fact somehow the call to stop the directshow graph get stuck and it's timing related for sure (maybe new GPU is faster and then this issue can occurs more quickly)

Yes my new GPU is much faster but that my be secondary, I get the feeling that it is more to do with the workload (and maybe timming) of Madvr, the more I ask it to do the worse the problem becomes. This was the same with my old GPU but now with the new one I can select much heavier settings.

@joecrow im interested by your feedback on rx460. Drivers / MP GUI reaction...

With respect to the drivers for the RX 460, no problem, I already use the Crimson package on my desktop so no surprises there. AMD have greatly simplified/optimised the settings compared to the old Catalyst version, for example there are no settings for selecting std. screen size and refresh rates you have to go to Windows to check/change that, makes sense, I guess, avoids conflicts etc. which seems to be the thrust of Crimson.
I use the Default Wide HD skin in carousel mode and I have noticed that since the upgrade navigating from one icon to another is no longer a smooth transition, it is not jerky, more instant if you know what I mean. Are you seeing the same or is it something else?

 

[rohnfe]

With respect to the drivers for the RX 460, no problem, I already use the Crimson package on my desktop so no surprises there. AMD have greatly simplified/optimised the settings compared to the old Catalyst version, for example there are no settings for selecting std. screen size and refresh rates you have to go to Windows to check/change that, makes sense, I guess, avoids conflicts etc. which seems to be the thrust of Crimson.
I use the Default Wide HD skin in carousel mode and I have noticed that since the upgrade navigating from one icon to another is no longer a smooth transition, it is not jerky, more instant if you know what I mean. Are you seeing the same or is it something else?

Couldn`t this be related to 24 or 23 refresh rate as well?

@Sebastiii i will try do to some dpi testing today or tomorrow. Don`t know if i get to it today.

 

[joecrow]

Couldn`t this be related to 24 or 23 refresh rate as well?

@rohnfe Not sure what you mean there please can you elaborate.

 

[rohnfe]

Couldn`t this be related to 24 or 23 refresh rate as well?

@rohnfe Not sure what you mean there please can you elaborate.

I am not sure if this is right but i`ve read somewhere that setting the refresh rate to 23/24 in the system settings could cause stuttering of the MP GUI... probably it was somewhere in this thread. More likely due to the low refresh rate than to MP GUI.

 

[joecrow]

I am not sure if this is right but i`ve read somewhere that setting the refresh rate to 23/24 in the system settings could cause stuttering of the MP GUI... probably it was somewhere in this thread. More likely due to the low refresh rate than to MP GUI.

Thanks for that you were dead right, the refresh rate was set to 23hz which was a bit strange cause I know I set it to 50hz. Even stranger when I tried to set it to 50hz Win 10 crashed/rebooted, no sure if it was a BSOD or what the screen just went black as per a normal refresh rate change but longer then it was restarting. All subsequent attempts to change to 50hz at the windows display settings level gave the same result as did an attempt to play TV in MP. Just when I was beginning to think my new GPU was screwed I tried to play an HD (23hz) video in MP, this worked what is more then TV did too and I was also able to set 50hz in the windows settings level without crashing.. Tried several other things, turning off Radeon Settings, closing MP but the crashing still ocurred whenever any attempt was made to change the refresh rate from 23hz to 50hz, other rates may also be effected, I did not try, but changing from 50hz to 23hz was OK. The problem was also unchanged after playing a video with MPC-HC and Madvr.

@Sebastii I have not tried going back to v164 but is there anything in v165 that might have caused this, I know the problem is there regardless of whether MP is running or not but the fact that it can be fixed by running the MP video player but not MPC-HC is pointing at something I think. I found that once the refresh rate could be set to 50Hz setting the "Use my settings for this device" option under Windows Colour Settings Management at least meant that when a crash happened it would default to 50hz after reboot.

 

[kenwonders]

Have you thought about reinstalling drivers after a DDU uninstall? The issue looks outside MP to me, though if there are madVR issues you could also try killing the madHcCtrl.exe process before changing the res.

166 running really well (zapping better than ever) for me, no issues, but I haven't touched 3d (can't be bothered mostly for 3 films)

 

[joecrow]

Have you thought about reinstalling drivers after a DDU uninstall? The issue looks outside MP to me, though if there are madVR issues you could also try killing the madHcCtrl.exe process before changing the res.

166 running really well (zapping better than ever) for me, no issues, but I haven't touched 3d (can't be bothered mostly for 3 films)

Yes, I did a complete uninstall/reinstall as part of the troubleshooting and I can now confirm the same problem with v164. MadHcCtrl.exe is not run by default on my setup it only comes up when something is playing that uses Madvr or I want to change settings so is not running when I have attempted to change the refresh rate. 166????? Any chance you could try this with your Nvidia setup, just as a sanity check, go to Advanced Display settings/Display Adaptor Properties then on the Monitor tab set to 23hz apply and keep changes then try setting back to 50hz