Thank you for the sugestion,
However, I don't think recording to mpeg2 would add the redundancy required in this case.
The problem was not only with ffmpeg. The problem was in vMix too.
vMix was indicating recording was started, ongoing and that all was going fine.
Record button was red and elapsed time was being displayed and counting, when in reality it didn't even begin to record.
I even choose a so called "fault tolerant" recording format (FFMPEG/MP4), according to vMix User Guide at
https://www.vmix.com/hel...tTolerantRecordings.html To tell reliably whether the recording is ongoing or not is a fundamental function/requirement for any recording software.
And vMix v20 fails at that.
And I don't have any hopes that this is different in vMix v21, since there is no indication on the vMix 21 Changelog
(https://forums.vmix.com/default.aspx?g=posts&t=14794).
Here is my 'PragmaticAgileSoftwareDevelopmentProof' method:
For now, I'm going to transmit every event being recorded, to a private youtube live chanel, in parallel to the local recording.
And, eventually, if possible, I'm going to put a secondary encoder recording in parallel too.
I didn't shut down the computer, hoping someone would tell me a way to recover from this situation.
But I don't think it is possible anymore.
Anyway, I did a recording test following the event and another test after restarting vMix.
The first gave me a FFMPEG error and correctly displayed it to me.
The second test, after restarting vMix, worked without problems: audio and video were recorded.
Since I think vMix developers need to make better ways to detect recording failures,
I'm sharing the logs of such tests in the attached file.
File Attachment(s):
vMixStorage.zip
(9kb) downloaded 2 time(s).You cannot view/download attachments. Try to login or register.
