2021-07-08, 10:44 PM
Hello, thought I would make a comment regarding the decoder errors that appear in the Windows NextPVR.exe client.
I have experienced the decoder error error messages that pop up for the longest time.
However, I have observed something that may be of interest.
Do you happen to be using the OSD LiveTV navigation menu shortcut to change channels?
(ie. Your watching a live channel, and then you use the cursor up/down arrows to choose another channel)
I get the dreaded 'you do not have an AAC decoder configured' error message 100% of the time, when changing channels between a channel with AAC audio and a channel with AC3 audio, and vice versa.
What I have observed, is that if you stop a playing channel, and then select another channel from the guide interface, that it correctly changes channels 100% of the time.
ie. It is the OSD Live TV shortcut navigation that seems to be the issue.
Originally, when I first encountered this behavior, I posted numerous logs etc, and I genuinely thought it was to do with me having an STB in the mix.
It was suggested to me, to add a delay into my IRblasting configuration, as my Colossus capture card requires some time to lock onto audio and stabilize.
However, I discovered that my STB was not the problem at all, as I observed that the decoder error messages also appear when changing channels between DVB-T channels as well
I live in New Zealand, and channels that bring up these decoder error requester windows in NextPVR.exe are any channels with AC3 audio, and channels with AAC audio.
ie. Tune to channel DVB-T 'One' (AC3 audio) and then watching that channel, press cursor key to navigate to 'Bravo', it will 100% of the time bring up an error saying I do not have an AAC decoder configured.
Likewise, it will do the same if you tune to 'Bravo', and then OSD channel change to 'One', it will bring up an error stating that you do not have an AC3 decoder configured.
BUT, if you 'stop' playback of channel 'one' and then use the guide to select 'bravo' it works every single time, and vice versa.
That is the primary reason I use Kodi Matrix as my client, using the NextPVR addon.
Kodi too has it's version of OSD LiveTV channel changing, which you access by holding the enter key down on remote for 2 seconds.
Once in OSD LiveTV mode, you can change between any channel, whether it contains AC3 audio or AAC, and change between STB and DVB-T channels without issue.
It works really well.
Another observation is that the Kodi PVR addon configuration settings include a delay option for channel switching whist watching LiveTV channel.
I have an inkling that this is why Kodi can change between live channels, and NextPVR.exe has issues with audio decoders when doing the same thing.
ie. Could NextPVR.exe be changing channels too fast?
From my experiments with delay scripts, I have Kodi delay setting at 4500ms, and I find that Kodi Matrix with latest NextPVR addon has no issues with channel changing. I use that ms setting, as I have STB in the mix, but probably don't require such a value it for DVB-T channel changing.
But, the point is there is a delay, and it seems to help.
Just my 2 cents worth, and am intrigued to see if your decoder errors you reported disappear if you change channels using the guide, instead of the OSD LiveTV shortcut method, as using it makes my NextPVR.exe a most unenjoyable experience, plagued with audio decoder errors.
However, I really like the NextPVR.exe experience in general, it is elegant.
Just my 2 cents worth.
I have experienced the decoder error error messages that pop up for the longest time.
However, I have observed something that may be of interest.
Do you happen to be using the OSD LiveTV navigation menu shortcut to change channels?
(ie. Your watching a live channel, and then you use the cursor up/down arrows to choose another channel)
I get the dreaded 'you do not have an AAC decoder configured' error message 100% of the time, when changing channels between a channel with AAC audio and a channel with AC3 audio, and vice versa.
What I have observed, is that if you stop a playing channel, and then select another channel from the guide interface, that it correctly changes channels 100% of the time.
ie. It is the OSD Live TV shortcut navigation that seems to be the issue.
Originally, when I first encountered this behavior, I posted numerous logs etc, and I genuinely thought it was to do with me having an STB in the mix.
It was suggested to me, to add a delay into my IRblasting configuration, as my Colossus capture card requires some time to lock onto audio and stabilize.
However, I discovered that my STB was not the problem at all, as I observed that the decoder error messages also appear when changing channels between DVB-T channels as well
I live in New Zealand, and channels that bring up these decoder error requester windows in NextPVR.exe are any channels with AC3 audio, and channels with AAC audio.
ie. Tune to channel DVB-T 'One' (AC3 audio) and then watching that channel, press cursor key to navigate to 'Bravo', it will 100% of the time bring up an error saying I do not have an AAC decoder configured.
Likewise, it will do the same if you tune to 'Bravo', and then OSD channel change to 'One', it will bring up an error stating that you do not have an AC3 decoder configured.
BUT, if you 'stop' playback of channel 'one' and then use the guide to select 'bravo' it works every single time, and vice versa.
That is the primary reason I use Kodi Matrix as my client, using the NextPVR addon.
Kodi too has it's version of OSD LiveTV channel changing, which you access by holding the enter key down on remote for 2 seconds.
Once in OSD LiveTV mode, you can change between any channel, whether it contains AC3 audio or AAC, and change between STB and DVB-T channels without issue.
It works really well.
Another observation is that the Kodi PVR addon configuration settings include a delay option for channel switching whist watching LiveTV channel.
I have an inkling that this is why Kodi can change between live channels, and NextPVR.exe has issues with audio decoders when doing the same thing.
ie. Could NextPVR.exe be changing channels too fast?
From my experiments with delay scripts, I have Kodi delay setting at 4500ms, and I find that Kodi Matrix with latest NextPVR addon has no issues with channel changing. I use that ms setting, as I have STB in the mix, but probably don't require such a value it for DVB-T channel changing.
But, the point is there is a delay, and it seems to help.
Just my 2 cents worth, and am intrigued to see if your decoder errors you reported disappear if you change channels using the guide, instead of the OSD LiveTV shortcut method, as using it makes my NextPVR.exe a most unenjoyable experience, plagued with audio decoder errors.
However, I really like the NextPVR.exe experience in general, it is elegant.
Just my 2 cents worth.