Deepblue1968
New Member
Using OBS 25.0.1 (64bit, windows) I have observed the following "feature" when using the Output Timer tool to terminate a recording session:
- The FIRST recording after launching OBS works as expected. Recording stops after exactly the specified time and is complete and correct.
- The SECOND recording (with the same or different settings) leads to a dysfunctional recording: the output file is 185 Byte in size and does not increase during recording. During this "fake" recording, the output timer decrements as expected and the recording stops as expected - but with the mentioned defective output file.
- When stopping and pressing Start Recording again (either in the "Controls" panel or "Output Timer" window) it works again as expected.
==> My current workaround is to press Start Recording/Stop Recording/Start Recording and then it works as expected (indicated by the "Pause Sign" = || being displayed right next to "Stop Recording" in the Controls panel). That way I end up with one invalid recording and a correct one each time.
This is acceptable, given the excellent results I get using the OBS software. But I wonder if this is a bug or if I'm overlooking something.
- The FIRST recording after launching OBS works as expected. Recording stops after exactly the specified time and is complete and correct.
- The SECOND recording (with the same or different settings) leads to a dysfunctional recording: the output file is 185 Byte in size and does not increase during recording. During this "fake" recording, the output timer decrements as expected and the recording stops as expected - but with the mentioned defective output file.
- When stopping and pressing Start Recording again (either in the "Controls" panel or "Output Timer" window) it works again as expected.
==> My current workaround is to press Start Recording/Stop Recording/Start Recording and then it works as expected (indicated by the "Pause Sign" = || being displayed right next to "Stop Recording" in the Controls panel). That way I end up with one invalid recording and a correct one each time.
This is acceptable, given the excellent results I get using the OBS software. But I wonder if this is a bug or if I'm overlooking something.