yes, I've not seen a single post-comskip freeze since installing 2.4.3 with that update. They didn't happen all that often before either, but I think I'd have seen one by now. Well done sir!
server: NextPVR 5.0.7/Win10 2004/64-bit/AMD A6-7400k/hvr-2250 & hvr-1250/Winegard Flatwave antenna/Schedules Direct main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV
minor point of interest... a couple of days ago I installed the latest AMD Radeon driver set (Catalyst 12.3) and just to see how it performed I switched to the included ATI MPEG-2 Decoder. While the video looked great and everything seemed to work fine, the frequent freeze-after-comskip problem came back! FF/RW using in FastPlay mode didn't seem to work right all the time either.
Today I switched back to the Microsoft DVD-DTV Decoder and all seems well again.
Sub, I can certainly see where all these interactions between your code, video drivers, decoders, and renderers must drive you insane from time to time.
server: NextPVR 5.0.7/Win10 2004/64-bit/AMD A6-7400k/hvr-2250 & hvr-1250/Winegard Flatwave antenna/Schedules Direct main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV
johnsonx42 Wrote:Sub, I can certainly see where all these interactions between your code, video drivers, decoders, and renderers must drive you insane from time to time.
Yep - I'm at the mercy of the decoders etc behaving well. Painful.
Had the same problem here with the ATI codec .... Switched to the Microsoft codec and problem solved
I was also having a problem changing channels too, it would freeze for several minutes but you could go back to the Main menu and go back in and it would come right up.
Looks like a Bug in the ATI codec and not your worry, just something people need to be aware of.
Running 2.4.3 with just the patch in this thread. I think I'm running into the same issue as everyone else: Skipping in general seems to work really well, except when using the "ATI MPEG Decoder". When using that, a skip (including one generated by comskip) seems to pause the playback. Oddly enough, skipping again seems to make it work again. So, right now when I use the ATI Decoder, after each commercial break, I hit the back-10-seconds button, and playback resumes reasonably.
The reason I want to use the ATI decoder is that it seems to be the only one (and I've tried quite a few) that shows the ATSC/QAM Closed Captions right. Other decoders either show nothing at all or show garbled captions, sometimes like it's just missing a good part of the closed caption data, sometimes like it's just getting noise or something. So, I'd be fine with getting captions working on one of the other decoders, but I'm guessing that it may be easier to get the ATI Decoder to not pause on each skip.
Let me know if there are any logs, recorded files, version numbers, or whatever that might be helpful in diagnosing this when you get a chance, sub. Thank you so much for this awesome product. All this mess of different decoders behaving differently is surely a big pain.
If the ATI decoder doesn't work, then it doesn't work. There probably isn't really anything I can do about it. You might be able to get it to work with a different video renderer. Sorry.
When it comes to decoders you pretty much need to use whatever works well on you specific setup.