Database deletes recording entry when .ts deleted but transcode exists.

[mvallevand]

My understanding of how mp4 transcoded files worked in v4 is the database didn't need to get updated, it could show as .ts but NextPVR would play (on the host only) the mp4 file if no ts file is found.

The API based system did not work this way, it does not even expose files when the ts file is not found.

Regarding Nlite, it is a hybrid the file would shows because it doesn't use the /live?recording= interface it uses the /stream= interface however both apis's will stream the mp4 file.

NextPVR v4 remote client cannot play these files via the NextPVR protocol

I suspect v5 works the same way. nlite and Kodi UI client should be able to play the file. I'd be interested in seeing the Kodi knewc logs for UI client for one of these files.


Martin

[vintdiesel]

Just of interest and may or may-not be relevant:

Martin, that is correct that in V4 clients won't play .mp4's as per my post a while back https://forums.nextpvr.com/showthread.ph...post526273

so in the config there was an entry to just play the recording as a file instead of streaming it by changing the config line entry:
<RecordingDirectoryTranslation>d:\temp~\\someserve r\someshare</RecordingDirectoryTranslation>

I was hoping similar is possible when a future windows V5 client is released that connects to a server on a different machine.

[sub]

What normally happens, in v4 or v5...

1)Whenever the application asks for the recording list, it loads the list from the database, checking each file exists before adding it to the list returned.
2)If a file didn't exist, and you've got <CheckForRenamedRecordings> set to true, it'll check if there is an alternative file with same name + different extension, like .mp4 etc, and if found will update the database
3)If a file didn't exist, and you've got <CheckForRenamedRecordings> set to false, it'll delete the entry from the database

The one complication, is when the web app, or web api in v5 asks for the recording list requests the 'superfast version', which basically bypass the file check, and just returns the filenames from the database. I would think your mp4 files should be listed there, but there may be somewhere else I forget, which is filtering out non .ts files.

[sub]

Nlite still says the recording is there

So Nlite doesn't use that superfast version of the api, so should do the checks listed above. If it's listings your recording in Nlite's Recording screen, then it's definitely still in the database.

[sub]

I usually leave everything as .mp4, but I'll try to reproduce it.

[vintdiesel]

Just an update. Last night I set <AutoRemoveMissingRecordings>false</AutoRemoveMissingRecordings> and not only the new recordings but the previously missing recordings have shown up on the recordings history.
The url you sent me also shows the .mp4s listed.