What happens if I change a file location from a Local Content Source to a DVR DB Storage Path?

I began using the Local Content Sources Settings section to add network paths for TV and Movies. These sources contained primarily shows and movies that had been recorded with other DVRs, primarily TiVo, Windows Media Center, and HDHomerun DVR. After getting reliable access to this content using the Channels Library, I also added a high capacity drive to the Channels Server's PC. In doing so, I added it as a Source under the Local Content section.

Screenshot 2022-09-26 132434_sm

The drive I use for Storage for the DVR Database is not as large as the newer drive, and I find that I'm moving recordings off of it to other locations where there is more space on a regular basis. This has caused some inconsistency in the metadata from time to time, and it seems I may have been better off adding the new drive as a second Storage Path for the DVR Database.

However, now that I have so many non-Channels recordings on this drive under the Channels folder, can I still change it from a Local Content Source to a DVR Database Storage Path?

No, it won't recognize any external recordings in additional storage.

That's the important distinction I was looking for. Thanks!

If I need the additional storage for Channels DVR Recordings, I guess I'll relocate all the "external recordings" to locations like "G:\Channelz\Movies" and "G:\Channelz\TV" and reserve "G:\Channnels" for Channels DVR Recordings only.

BTW, I'm guessing that once a recording has been moved from the DVR Database to a non-Database folder, it has been permanently orphaned and cannot be brought back into the Channels DVR Database. Is that correct?

It doesn't care if you move files. But if you then go and prune the database and the database entry is removed, then yes it's gone forever.

It makes total sense that Local Content has to be handled completely different from Channels DVR recordings.

You said the database doesn't care if the recordings have been moved. Are there constraints on that? Or does that just mean that the database record remains until purged and is available should the recording be found in any of the source paths?

Correct

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.