DVR Issues: Recordings don't show up and doesn't Record

[legallink 187]

Since the new server update to 4.3.0.30, the DVR functionality is not working.

 

It doesn't find any of the previous recordings in the DVR Recordings folder, nor is it making new recordings.  I have checked the system config and that seems to be correct.

 

Related (or not), the system no longer displays "Upcoming" TV shows in the TV folder.

 

Note that watching Live TV does function and the TV Guide does display correctly.

 

Server log and screenshots attached.

embyserver.txt

[ebr 16195]

Hey legallink.  The log doesn't contain any recording activity - but I guess that doesn't surprise you.

 

Can you look in the physical location for the recordings and see if the files are maybe there but just not showing in the interface?

[legallink 187]

@@ebr it appears the files are there.  It's strange as the app created new folders with the same name, but backdated their creation date somehow.  So when I searched on "Date modified" the folders didn't filter up to the top.  Somehow, it created all the new folders were all populated with an nfo file dated 9/23/2019.  Not sure as to the significance of that date, but so goes it?  The folders weren't there  So, oddly it does appear to be recording, just not populating the screens appropriately I guess?

[legallink 187]

Any notion on why none of the screens are populating?

[Luke 42085]

Is the recordings library intact in emby library setup?

[legallink 187]

@@Luke and @@ebr it appears that this is only happening with "Mixed Content" libraries.

 

Yes, recordings library is setup and intact. This isn't the only folder that isn't populating.  All Mixed Content libraries aren't populating.

[legallink 187]

Just a note, I went through my logs, and it appears I have the same issue as this user:

https://emby.media/community/index.php?/topic/80081-upgrade-to-430-library-content-not-available-duplicate-path-reported/?hl=%2Bfound+%2Bduplicate+%2Bpath

 

I don't see a response on the issue, but I'll keep searching.

[legallink 187]

And problem solved!!

 

For anyone coming after me:

The Duplicate Path was the trick to identifying the issue.  With the new Camera Upload feature, I simply pointed the "Camera Upload" feature to a drive.  Well, that drive already had libraries created on it.  I didn't really care, because it wasn't going to drop files in those folders, it would just create it's own folders.  Well, for Emby purposes, because it was a level higher than the other folders (Camera Upload was to G:/, the other folders within other libraries were G:/Folder Name), it was a duplicate path and wouldn't identify separately.

[Luke 42085]

Thanks for the info.