Bug when interrupting one recording by another

[tschoo]

shall there be a defined behaviour in case one scheduled recording interrupts another?
I wanted to record two shows which are immediately succeeding.
Show one was scheduled from 0:50 to 2:45,
show two was scheduled from 2:45 to 4:40.
I have set 1 minute pre-pad and 20 minutes post-pad.
I expected that the file for show one starts at 0:49 and is interrupted at 2:44 by the second show, thus containing about 1:55 hours of video. Actually, it contains only 1:31 hours of video and I lost the rest.
Of course, I can adapt the pre-pad and post-pad each time when I record succeeding shows, but it would be more comfortable if there is a defined behaviour for this situation.

-tschoo

[sub]

Padding is only applied if the there isn't another show scheduled to record.

In the situation above show one should contain approximately 0:49 - 2:44:59, show two should contain 2:45 - 4:59:59.

[tschoo]

Thanks for the prompt answer, sub.

In the meantime I detected that truncating the files is caused by another effect, which seems to be very strange:

I detected that recording my last show stops at about 2.3GB - I detected it only because the file did no longer grow, the recording service still shows 'Recording'. At the same time, I detected that the network did not work any longer. After I have restarted the network driver, the file continued to grow!

I should mention that I have a PVR-350 and the effect seems to be very similar to the one noticed by cannabinoidboy in recording stops prematurely.

I have noticed a very similar behaviour also before starting to use gb-pvr, when using wintvcap (but I didn't previously notice the interdependency with the network card). Therefore maybe this is a driver issue?

Maybe there is some interdependency with automatic standby, which I enabled some time ago. I will disable it and see if the effects continue.

Sub, I believe there are two ways to assure that the system does not enter standby mode during the execution of a program:
- answering a WM_POWERBROADCAST with BROADCAST_QUERY_DENY or
- calling SetThreadExecutionState with argument ES_SYSTEM_REQUIRED
Which one do you use? Maybe using the second one inhibits making standby requests thus not triggering a possible bug in the Hauppauge driver?

-tschoo

[sub]

Based on the size of your file, are your running a FAT filesystem? Could this have been the maximum file size on a FAT volume. I run all NTFS here.

[tschoo]

It's NTFS. And I have about 99GB free space.

-tschoo