2019-01-17, 09:29 AM
(This post was last modified: 2019-01-17, 01:29 PM by latenighter.)
I have encountered a similar problem to the one I reported under https://forums.nextpvr.com/showthread.ph...uide-Entry where a 0x19 was encountered in the Program Description sourced from the Freeview OTA EPG data. This time the 0x19 is in the Program Title and its impacts seem sufficiently different to warrant a check if the planned fix for the earlier reported problem will also fully cover this one.
When selecting the entry from the guide, to set up a recurring recording request for the related series, an error dialog is displayed as shown in the attachment. No Pending Recording entries are created and when navigating to the Recurring Recordings view the same error dialog gets displayed. When the "Continue" option is chosen in the error dialog no entry is shown for the attempted request in the Recurring Recordings view. However, browsing NPVR.db3 I could see a row for the attempted request had been created in the RECURRING_RECORDING table and as expected there was no related row in the SCHEDULED_RECORDING table.
To remove the row from RECURRING_RECORDING that was giving the persistent error dialog I edited the XML field value to remove the 0x19 - this stopped the error dialog and made the request visible in the Recurring Recording view allowing me to delete it. Before I deleted the entry I made various attempts (eg. updating the padding) to get the system to generate the pending recording request but to no avail - probably because there was no longer a match between the Program Title stored for the EPG and the XML value for the title in the recurring recording entry. If it addresses all XML parsing/etc. in the application it's probably in this area where the planned fix for the earlier problem needs to be careful such that the EPG Program Title stored in the database matches the Program Title that gets stored in a recurring recording entry.
To work around this situation, after deleting the incomplete recurring recording request, I set up a keyword recurring recording request that successfully created the required Pending Recording entries. Interestingly the Pending Recording entries are shown in the NextPVR GUI (Guide and Pending Recordings) and in the NEWA Manage Recordings view but are not flagged in the NEWA Guide view - I guess this is an artefact of the originally reported problem that I didn't spot before. As I run a combined Emby/NextPVR set-up I can confirm the Emby Theater client does show both the keyword recurring recording request entry and the generated pending recording requests.
Hopefully the information I've provided will allow an assessment of the completeness of the planned fix for the original problem. If you need any extra information for this flavour - NPVR logs, etc. - don't hesitate to ask.
When selecting the entry from the guide, to set up a recurring recording request for the related series, an error dialog is displayed as shown in the attachment. No Pending Recording entries are created and when navigating to the Recurring Recordings view the same error dialog gets displayed. When the "Continue" option is chosen in the error dialog no entry is shown for the attempted request in the Recurring Recordings view. However, browsing NPVR.db3 I could see a row for the attempted request had been created in the RECURRING_RECORDING table and as expected there was no related row in the SCHEDULED_RECORDING table.
To remove the row from RECURRING_RECORDING that was giving the persistent error dialog I edited the XML field value to remove the 0x19 - this stopped the error dialog and made the request visible in the Recurring Recording view allowing me to delete it. Before I deleted the entry I made various attempts (eg. updating the padding) to get the system to generate the pending recording request but to no avail - probably because there was no longer a match between the Program Title stored for the EPG and the XML value for the title in the recurring recording entry. If it addresses all XML parsing/etc. in the application it's probably in this area where the planned fix for the earlier problem needs to be careful such that the EPG Program Title stored in the database matches the Program Title that gets stored in a recurring recording entry.
To work around this situation, after deleting the incomplete recurring recording request, I set up a keyword recurring recording request that successfully created the required Pending Recording entries. Interestingly the Pending Recording entries are shown in the NextPVR GUI (Guide and Pending Recordings) and in the NEWA Manage Recordings view but are not flagged in the NEWA Guide view - I guess this is an artefact of the originally reported problem that I didn't spot before. As I run a combined Emby/NextPVR set-up I can confirm the Emby Theater client does show both the keyword recurring recording request entry and the generated pending recording requests.
Hopefully the information I've provided will allow an assessment of the completeness of the planned fix for the original problem. If you need any extra information for this flavour - NPVR logs, etc. - don't hesitate to ask.
