Multiple dvr-ms files

[Squid]

Hello,

I seem to be getting multiple .dvr-ms files when I record something. One of them is the right one ( it is very large ) and it has a -1 after the filename. I also get another file that is 4kb in size. When I try to play the files through the recordings interface nothing happens. I can play the file through the Video interface ( only after it is done recording ). This is with a HVR-1600 ATSC broadcast, overlay mode.

From looking at the logs it looks like it fails to do something, retries and succeeds but then doesn't update the database to point to the new file. But that is pretty wild guessing about what is going on.

Logs Attached.

Thanks,

Squidi

[whurlston]

Some of us had this issue with the HDHomeRun. Changing "BDASubmitTuningRequestTwiceOnRecord" to "true" in the config.xml solved it for most. There was one person it didn't work for though, I never could figure out why.

[Squid]

I changed that setting, it didn't have any effect. It does it every time I record something ( I thought it was intermittent initially ), so any testing or logs or whatever, just let me know.

Squidi

[Squid]

I hit edit instead of reply, which makes it so my edit will probably never get read:

I changed that setting, it didn't have any effect. It does it every time I record something ( I thought it was intermittent initially ), so any testing or logs or whatever, just let me know.


Thanks for any input,

Squidi

[bgowland]

Squidi - from what I can tell from your description, at least part of what you're seeing is normal behaviour.

The dvr-ms recording process will start by creating a ~95MB file which it uses to write the AV to. It will also create another 1 or 2 files of about 4-6KB - I believe they're called 'backing' files. This is part of the Stream Buffer Engine being able to do more complex things than just making permanent recordings.

What you should see during recording is that the main file will grow in ~95MB chunks. When the recording finishes, the backing file(s) will be flushed/deleted and the main file will be truncated to the actual size of the data it contains (plus the ASF header).

Sorry I can't help with why your DB doesn't seem to be getting updated but hopefully the above explains what you're seeing during the recording process.

Cheers,
Brian

[wannabepvr]

As I understand it this is a result of the 'Second Chance' code Sub added a few releases back. If the recording file size is not growing then GBPVR tries again to tune the tuner.

I find this second chance works very well, although more often that I like to see.

The only issue except that the database and postprocessing (comskip) aren't updated to the new file.