4.2.2 STOP command wont work
|
2018-07-15, 11:12 PM
NextPVR uses Windows media player components to play recoding's. You could try a reboot after any change to the decoder settings that doesn't seen to work. This would force media player components to reload and start over.
Graham Wrote:NextPVR uses Windows media player components to play recoding's. You could try a reboot after any change to the decoder settings that doesn't seen to work. This would force media player components to reload and start over. Thank you for the idea. There are no problems with playing recordings. There are no problems with watching live tv. All decoders I have tried work fine. The problem is the STOP function does not function when watching LIVE TV only with 4.2.2. It was random with previous release (like 50%) but now it is generally not functioning 99% of the time. The saf6 install made it work 100% of the time but as I mentioned perhaps it was just another fluke. I will have to retry it to see if I can reproduce the success. That is why I was wondering at the differences between it and the GitHub lav. As I mentioned it looks like it tried to install directx 9. not sure if windows 10 allowed it. Maybe that made the difference if it did? Just that the system restore stopped working. U said NPVR uses WMP components to play recordings. What components are used to play Live tv? I will try reboot some more and see if that does anything though I have tried it before.
2018-07-16, 08:54 AM
eastavin Wrote:As I mentioned it looks like it tried to install directx 9. not sure if windows 10 allowed it. Maybe that made the difference if it did? In the past, NextPVR required some specific DirectX components that were not part of "standard" DirectX. It was necessary to run a specific DirectX installer to get these components ... http://www.nextpvr.com/nwiki/pmwiki.php?...requisites The DirectX update got bundled into SAF as part of the one stop shop ... Running the DirectX update has never been known to have caused a problem not even when it is run repeatedly. For completeness ... running SAF a second time should uninstall everything that was installed by the first run of SAF.
2018-07-24, 02:10 AM
sub Wrote:Oh, I've heard of SAF - I just don't know the details of all the shit it installs, so I wouldn't have recommended it myself. (it might be fine, just never used it myself, and don't know much about it). So the final test results are in. NPVR behaves the same way in 4.2.2 regardless of the codec being used. The single issue is the stop button and all similarly named features are at best intermittent. They either randomly decide to work for periods or seemingly randomly stop working for much longer periods. No difference whether I use Hauppauge codec, Lav codecs or Cyberlink codecs or how many times I reboot. The difference is having a DirectX 9 run time module installed. Once this is installed the stop feature starts working 100% regardless of how you access it. You must have some windows xp code left in this area of NPVR. Not sure why it needs directx9 when directx12 is present but that is beyond my pay grade  I downloaded the Directx 9 from this location https://www.microsoft.com/en-us/download...35&nowin10 because it showed a 2011 date rather than a 2007 date on the link I see in our forum.The machine this is on is an Acer Aspire xc-704 with Intel J3710 cpu and intel HD graphics and Windows 10 Home. No screaming eagle but just enough guts to do the job for about 8-11 watts per hour. Hope this test info helps you keep the code humming smoothly. Thanks to you and to everyone that responded to my post. Edward
2018-07-24, 03:59 AM
eastavin Wrote:So the final test results are in. NPVR behaves the same way in 4.2.2 regardless of the codec being used. The single issue is the stop button and all similarly named features are at best intermittent. They either randomly decide to work for periods or seemingly randomly stop working for much longer periods. No difference whether I use Hauppauge codec, Lav codecs or Cyberlink codecs or how many times I reboot.I don't have DirectX 9 on machine, which was a freshly install Win10 setup a few days ago, and my click is working reliably. When you move the mouse over the buttons do they change color? (white vs gray)
2018-07-24, 04:21 AM
I've attached an updated nextpvr.exe, which logs click messages. You could check for these messages to see if they're happening. If not, it's possibly something to do with your video renderer, which routes clicks during video playback to the application code.
Messages look like this: 2018-07-24 16:17:37.341 [DEBUG][1] MouseClick({X=1.423027, Y=3.519669}) 2018-07-24 16:17:37.852 [DEBUG][1] MouseClick({X=11.12549, Y=5.175983}) etc It'll be interesting to see if you get the MouseClick messages or not. If you do get them, we may need to check the numbers, so we can see if it's reporting the correct location for the stop button etc.
2018-07-24, 07:36 PM
sub Wrote:I've attached an updated nextpvr.exe, which logs click messages. You could check for these messages to see if they're happening. If not, it's possibly something to do with your video renderer, which routes clicks during video playback to the application code. Thanks. I will give it a go. does the onscreen stop button require 1 or 2 clicks to activate? (just so I know for sure) where will the mouse click messages appear? on screen or in logs? Thanks Sub.
2018-07-24, 07:41 PM
They only require a single click.
These message appear in the npvr.log file.
2018-07-25, 06:10 AM
sub Wrote:I've attached an updated nextpvr.exe, which logs click messages. You could check for these messages to see if they're happening. If not, it's possibly something to do with your video renderer, which routes clicks during video playback to the application code. Here are two log files one with just directx12 and one with 9runtime. I tried various buttons including both the onscreen stop and the menu item stop. Neither worked with just directx12 but both worked with directx9 runtime. Let me know if you saw any messages you were looking for. If the test is not long enough I will let it run a few days and send it again. Many thanks Edward
2018-07-25, 06:38 AM
Yeah, oddly no sign of any clicks during video playback in your directx12 logs. I've got no idea why that might be - nether directx12 or directx9 are used by NextPVR for playback. It's possible the Microsoft EVR video renderer is using these behind the scenes, and something about this is effecting the ability to get mouse click events from the video renderer. I'm not seeing this problem here, and my machine doesn't have the directx9 runtime installed.
What video card are you using? When you move the mouse over the buttons, do you see them change from white to grey? If you temporarily try the "VMR9 Custom" renderer, do clicks work then? |
|
|
