The extra muxing overhead increases file size very slightly (mine increased in size by 6 KB or 0. After the crash, select the option to launch debugger. If not, then when running from the command line you can do one of two things: Run EXE, and before the crash do an Attach To Process (Tools menu on Visual Studio). If so, then great - youre all set to look at things. The default GOP size in Simple output mode is 250 frames (4.1 seconds at 60 FPS or 8.2 at 30). Then try running from the IDE first to see if you get the crash. When doing fragmented MP4, each GOP becomes its own "fragment" and no moov atom is necessary, so in the event of a crash you will lose, at worst, a single GOP - the last one that was being written at the time of crash. Normally, an MP4/MOV file must always contain a moov atom, but it can't be known until the entire file is done encoding, so if the encoder or the muxer crash during the output, the whole file becomes unusable. Your MP4/MOV recording will still open in video players and video editors.įor those who are curious: this tells the ffmpeg muxer to create a so-called "fragmented MP4". Want to try it? Start recording, record for at least 4 seconds, then kill obs-ffmpeg-mux.exe and obs64.exe in Task Manager. Now you can select MP4 or MOV and not worry about losing recordings if OBS Studio crashes while recording.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |