(2021-12-18, 05:35 PM)sub Wrote: Actually, here is a newer one, with an additional improvement.
Thanks a lot for having spent time to fix this issue.
Out of your screen shot, it seems ok. I will be able to test as soon as I will be back to home, ie next monday.
Can you please explain why this new npvrtsmon.ax is fixing the issue (in simple word for neophyte ;-)) ?
(2021-12-25, 10:41 AM)MaxFromFrance Wrote: Can you please explain why this new npvrtsmon.ax is fixing the issue (in simple word for neophyte ;-)) ?
It was seeing the channels, but the unusual order of data in the stream was causing the scan results for the frequency to be reset before the application had a chance to show the list of channels.
(2021-12-25, 10:41 AM)MaxFromFrance Wrote: Can you please explain why this new npvrtsmon.ax is fixing the issue (in simple word for neophyte ;-)) ?
It was seeing the channels, but the unusual order of data in the stream was causing the scan results for the frequency to be reset before the application had a chance to show the list of channels.
Very clear, thx.
Will you intend to merge this code into your main branch, to include the fix for your further versions?
btw, before the crash of my htpc, these channels was present.
The thing is I do not remeber with which version of NextPVR I did the scan, as I am a very old user of your soft :-)
So a "regression" was certainly introduced. Happy if I had the opportunity to help to correct it.