I'm using build 134 in my PC that I use as a DVR (because I update it less frequently because stability is the most important quality for that PC). IF this is a bug that was fixed in a more recent version, let me know, but that seems unlikely. I am using two Hauppauge PCI TV tuners. MC19 is setup to record in .TS format (which outputs both during the recording and then only leaves .TS at the end).
Steps that cause the problem:
1) Hard drive has insufficient disk space to fully complete the current recording (so it runs out of disk space while MC19 is recording TV).
2) The scheduled end of the recording occurs, and there is still insufficient disk space. (The recording's JTV folder and TS file are each less than the size of a full recording.)
3) After the scheduled end of the recording, the human notices the problem, and deletes a bunch of old files, creating a lot of disk space.
4) MC19 then continues to write to both the JTV folder and the TS file forever. (from looking at the file later, it looks like the same channel as the original recording.)
( I then rebooted the PC to stop the recording, and MC19 did not resume "recording" upon reboot. )
My guess is that when the scheduled time occurs to stop the recording, the insufficient disk space condition interferes with MC19 executing the portion of the code that finishes the recording. The bug is that - even though insufficient disk space has caused the completion to fail - there should be code to set the recording as flagged "completed" so that it does not record infinitely.
