2016-02-28, 03:32 AM
I've been having an issue where occasionally, X-NEWA playback of show recordings wasn't loading the .edl data into the Kodi player. It didn't happen too often, and I'd never tracked down the reason. But tonight, I had a little time so I took a closer look.
It appears that when a show's name/title ends with a period ("Chicago P.D."), the recording folder that NextPVR creates does not have the period at the end ("E:\NPVR Recordings2\Chicago P.D\" instead of "E:\NPVR Recordings2\Chicago P.D.\"). But, the row in the SCHEDULED_RECORDINGS table lists the filename with period at the end ("E:\NPVR Recordings2\Chicago P.D.\Chicago P.D..S03E16.The Cases That Need to Be Solved.ts").
When X-NEWA tries to use the path substitution to open the recording file via Samba (and get the .edl file), it fails to find the file because the folder name in the share doesn't match the folder name in the database. So then it falls back to requesting the file via HTTP streaming by OID. NextPVR on the server somehow manages to find the file and stream it, so Kodi does end up playing the file--just without the .edl data. :eek:
It appears that when a show's name/title ends with a period ("Chicago P.D."), the recording folder that NextPVR creates does not have the period at the end ("E:\NPVR Recordings2\Chicago P.D\" instead of "E:\NPVR Recordings2\Chicago P.D.\"). But, the row in the SCHEDULED_RECORDINGS table lists the filename with period at the end ("E:\NPVR Recordings2\Chicago P.D.\Chicago P.D..S03E16.The Cases That Need to Be Solved.ts").
When X-NEWA tries to use the path substitution to open the recording file via Samba (and get the .edl file), it fails to find the file because the folder name in the share doesn't match the folder name in the database. So then it falls back to requesting the file via HTTP streaming by OID. NextPVR on the server somehow manages to find the file and stream it, so Kodi does end up playing the file--just without the .edl data. :eek: