I just reinstalled GBPVR and I can see my old recordings but I can't play them, only delete them. I tried reimporting the recordingdump file but that didn't work. What do I do to play them again?
To me it sounds like you've got <AutoRemoveMissingRecordings>false</AutoRemoveMissingRecordings> in config.xml, but you're recordings arent in the place they were when GB-PVR recorded them. ie, you moved the recordings to a different drive or directory.
The 'play' button is not shown because the filename in the database does not match a filename on your hard disks.
I recently had a similar one off problem. Because it happened only once I didn't investigate much and I haven't kept the logs. It seemed be something along the lines of ...
GBPVR is configured to use the DVR-MS mux.
A recording begins but the references in the log are to a .MPG file.
An .MPG file is created in the recording directory but is tiny.
A second file, DVR-MS, is created ( I guess because of a recording restart because the first file was not growing) and this grows to normal size and can be played back using WMP.
The entry in Recordings points to the .MPG file and has Close and Delete buttons but no Play button.
Quote:An .MPG file is created in the recording directory but is tiny.
A second file, DVR-MS, is created ( I guess because of a recording restart because the first file was not growing) and this grows to normal size and can be played back using WMP.
Did you chance the preferred mux mid way through the recording, then restart the recording service? I cant think of any other reason you'd initially have a .mpg file initially, then a .dvr-ms file.
When GB-PVR initially requests the recording to start, it always for a .mpg file, but if its using the DVR-MS mux then it'll create a .dvr-ms file and return this as the "final filename", which will then be saved in the database.
I guess a crash between starting the recording and saving the final filename to the database might cause an incorrect filename in the database, but it would be very unlikely, and doesnt sound like the cause of Jarobata's problem.