Two DVR-MS files created per recording

[OscarL]

Hello,
I have noticed that since upgrading to 0.97.9 there are two dvr-ms files created per scheduled recording. The first one is only 4kB, the other one (ending with -1.dvr-ms) seems ok.
I saw that there is a new parameter in config.xml "<BDASubmitTuningRequestTwiceOnRecord>true</BDASubmitTuningRequestTwiceOnRecord>".
Is that parameter related, if so is this behaviuor as expected.
I enclosed a log if this is not correct.

Regards and thanks again for a great sw.
Oscar

[bgowland]

This is a side effect of how the Stream Buffer Engine records dvr-ms files. The little one is one of the 'backing files' used in the process. It's always done this but it used to be that GB-PVR cleaned up afterwards. Also, it used to be that the little one had the '-1.dvr-ms' filename and not the main file.

I spotted this just before the latest release so I didn't get a chance to mention it to sub. It won't hurt but you'll have to delete the files manually.

Cheers,
Brian

[sub]

I saw that there is a new parameter in config.xml "<BDASubmitTuningRequestTwiceOnRecord>true</BDASubmitTuningRequestTwiceOnRecord>".

Its actually not a new setting, but try setting it to false to see if it corrects your problem. Let me know.

[Serg]

When I use Microsoft DVR-MS multiplexer I also have two .dvr-ms files created and both of them are empty if I cancel recording I also get third .mpg file.
-native.log file contains

BDARecorder:::StartRecording(KWorld ATSC-110, 1, I:\TV Recordings\Wild About Animals\Wild About Animals_20060604_11301200-2.mpg, T:44,5,1)

but then

Target DVR-MS filename: I:\TV Recordings\Wild About Animals\Wild About Animals_20060604_11301200-2.dvr-ms

And .exe.log file has

Recording file cant be found. Giving second chance: I:\TV Recordings\Wild About Animals\Wild About Animals_20060604_11301200.mpg
Stopping recording
...
Restarting recording

That is when it creates second .dvr-ms file, I guess.
And my recording service crashes. :mad:

[sub]

Looks like youre device is failing to lock onto the requested channel, so no data is produced. After while it has a go at restarting the recording to see if it can get it started, but it still fails to lock a channel.

[Serg]

Looks like youre device is failing to lock onto the requested channel, so no data is produced. After while it has a go at restarting the recording to see if it can get it started, but it still fails to lock a channel.

What about the difference in file formats?
It looks like it creates .dvr-ms file but then it's trying to write to .mpg file and can't find it.

[sub]

I'm pretty sure that aspect just relates to the logging messages, and can be safely ignored.

Did the initial dvr-ms file exist, and if so, how big was it? If it was less than 30K, it'll do this second chance restart.

[Serg]

I'm pretty sure that aspect just relates to the logging messages, and can be safely ignored.

Did the initial dvr-ms file exist, and if so, how big was it? If it was less than 30K, it'll do this second chance restart.

Since my Recording service crashes I usualy get two .dvr-ms files 5.5KB each