recording clobbered

[peabody]

i think that, if a recording starts and there already exists a file with the name it is using, it clobbers it.

what happened: 4.5 hours into a 5 hour recording, i managed to crash the machine (reason unrelated to gbpvr). it rebooted automatically, and the recording service started recording, presumably to finish. unfortunately, i lost the recording prior to the reboot.

it would be nice if it checked for file existance, and appended something to create a name that doesn't exist. or, alternatively, if it renamed any pre-existing file to something unique. (maybe the latter is easier, i can see there are issues with finding it for playback.)

[peabody]

crash the machine (reason unrelated to gbpvr).

tipstir,

thanks, but i already know why it crashed. regardless of that, gbpvr should not delete an existing file when it starts recording.

[bgowland]

regardless of that, gbpvr should not delete an existing file when it starts recording.

This has been discussed before - unfortunately it does.

Strangely enough though, we had a 'power dip' last night deep enough to restart my machine that was in the middle of a recording. When it came up again I noticed two files - one was filename.dvr-ms and the other was filename-1.dvr-ms

I don't know if this is a property of the dvr-ms bda muxer, I've never seen it when recording in mpeg2 format when there has been a crash/reboot.

sub? Any ideas?

[peabody]

update:

my current work-around for this is to use a postprocessing.bat to append the name of every completed recording to a log file. on reboot, i do not have the recording service start automatically- first i run a script that traverses the recording file tree. any mpg file whose name is not in the log file presumably was interrupted so it gets renamed e.g. foo.mpg -> foo_#_saved.mpg where # is a number that will not clobber anything existing. then i start the recording service. there is also a script to be run once in a while to clean out the log.