bccrew Posted February 22, 2017 Share Posted February 22, 2017 I had a crash of my DVBViewer RS server and I was able to restore my recordings from a backup. I noticed that placing the *.ts files in a folder and select that folder as the default recording folder in the RS settings is not enough to rebuild the history. Also, when I click the option to rebuild the history in the webinterface, the history is not rebuild. Can I do this another way? Link to comment
Langhuse Posted February 23, 2017 Share Posted February 23, 2017 You will probably have to also copy the .txt file into the same directory as the .ts file. I have had no succes importing .ts file, although that would be a nice feature Link to comment
Tjod Posted February 23, 2017 Share Posted February 23, 2017 Importing as recording is only possible if EPG info data exist attached as NTFS data stream to the file or as separate EPG info file (txt with the same name as the recoding). Link to comment
bccrew Posted February 23, 2017 Author Share Posted February 23, 2017 I have the files in a structure like this. How do I proceed? When I click rebuild recording history, nothing happens :s Link to comment
Tjod Posted February 23, 2017 Share Posted February 23, 2017 OK then it should work. But you have to run in the RS web-interface > Tasks > Refresh Recording DB There are two databases. One is the Recording DB, for recordings which are present and can be watched. And then there is the Recording History DB, which is only used by the automatic timer generation (EPG search) if you enable there "Deactivate auto-timers with the same Recording ..." it can also include already delete recordings. So that if you are recording series and delete old episodes. Reruns of those episodes will not be recorded. Link to comment
bccrew Posted February 24, 2017 Author Share Posted February 24, 2017 I'm sorry but it just won't work. I have deleted the SvcDatabase.db3 database and restarted the service so a new one is generated. After that I click on Refresh Recording DB but in the task manager I don't see any high CPU activity that indicates that the recording folder is being scanned for recordings. Link to comment
bccrew Posted February 26, 2017 Author Share Posted February 26, 2017 It turned out to be an access rights problem to the drive. Link to comment
Recommended Posts