I have a case where I record two consecutive hours from the same Stream (URL). For example, first recording starts at 18:00 with duration 60 minutes, second recording starts at 19:00 duration 60 minutes.
In the past (MC 32), the first recording overlapped about 15 seconds into the second recording. I liked that, because I was guaranteed not to miss any program material when I listened back the next day.
Sometime during MC33, this overlap dropped to about 3 seconds. I felt that was cutting it close, but still OK since a clear overlap was still there.
In the most recent drop of MC33 (came onto my system about February 16), this overlap was changed to zero. Somebody apparently thought it would be cool to cut down the first recording to the very last sample with no overlap to a new recording starting on the next sample.
I think this is cut too close. On two consecutive recordings that occurred last night, I'm not convinced that samples aren't missing. Please restore the code to at least the state where there were 3 good seconds of overlap. Please don't continue to fool with the code to try to achieve no duplicated/missing samples in this use case. The time is better spent on regression testing or implementing new worthwhile features.
Author
Topic: Scheduler -> Record Stream: record time overlap vanished (Read 53 times)