Hi. I am a first time user of this software, so I do apologize if any of my questions or statements are redundant.
Last night, I was recording a videogame playing session with some of my friends. I'd been checking up on OBS periodically during that time as to ensure no encoding errors occurred - it had given me one earlier on during the day. Throughout some four, five hours, everything ran smoothly. However, at the very last stretch (so, the last 15-30 minutes of our hangout), OBS sent an encoding error, and now the entire file is corrupted.
Not using the "skip unknown" command made the program give an "invalid argument" error, not even attempting to create a repaired video.
Toggling the -s command is now currently yielding this:
Info: parsing healthy moov atom ...
Composition time offset atom found. Out of order samples possible.
Info: reading mdat from truncated file ...
Info: using 64-bit offsets for the broken file
[aac @ 00000000027bbfe0] Prediction is not allowed in AAC-LC.
Warning: Codec::was_bad_ = 1
Warning: Codec::was_bad_ = 1
Warning: Codec::was_bad_ = 1
Warning: NOT skipping sqcp atom: 1978661779 (at 0x12bd3d74 / 0x12bd3da4)
Warning: Codec::was_bad_ = 1
Warning: Codec::was_bad_ = 1
Warning: Codec::was_bad_ = 1
Warning: Codec::was_bad_ = 1
Warning: NOT skipping sqcp atom: 1978661779 (at 0x13a53d75 / 0x13a53da5)
Warning: Codec::was_bad_ = 1
Warning: Codec::was_bad_ = 1
Warning: Codec::was_bad_ = 1
Warning: Codec::was_bad_ = 1
Warning: NOT skipping sqcp atom: 1978661779 (at 0x148d3d76 / 0x148d3da6)
Warning: Codec::was_bad_ = 1
Warning: Codec::was_bad_ = 1
Warning: Codec::was_bad_ = 1
Warning: Codec::was_bad_ = 1
Warning: NOT skipping sqcp atom: 1978661779 (at 0x15753d77 / 0x15753da7)
Warning: Codec::was_bad_ = 1
Warning: Codec::was_bad_ = 1
Warning: Codec::was_bad_ = 1
Warning: Codec::was_bad_ = 1
And so on and so forth... The progress bar is still moving, although quite slowly, probably owing to the gargantuan file size. It's just yielding four rows of codec was bad, and then not skipping atom , over and over again.
The file itself is 37.4 GB in size. I have shorter ones from the same day, smaller in size, as well as files greater than that, all recorded under the exact same conditions within OBS. I am willing to provide any files necessary in order to secure assistance with this issue.
I'm hoping for a swift response, as I do not know what will happen to my file once I end up unplugging the external hard drive it was recorded to. When I plugged it into my laptop and tried to open/observe the other video that got corrupted, it was displayed as having the size of 0B. I'm deathly afraid of losing this, so please, if there is any way this issue can be helped, do let me know as soon as possible.
Kindest regards, and thank you for making this software in the first place, even if it doesn't end up being able to salvage my file.
12:35PM local time update: The progress bar seems to have halted entirely. These are the last four generated lines: note the _ =1 that is missing from the last line when compared to the standard line.
Hi. I am a first time user of this software, so I do apologize if any of my questions or statements are redundant.
Last night, I was recording a videogame playing session with some of my friends. I'd been checking up on OBS periodically during that time as to ensure no encoding errors occurred - it had given me one earlier on during the day. Throughout some four, five hours, everything ran smoothly. However, at the very last stretch (so, the last 15-30 minutes of our hangout), OBS sent an encoding error, and now the entire file is corrupted.
Not using the "skip unknown" command made the program give an "invalid argument" error, not even attempting to create a repaired video.
Toggling the -s command is now currently yielding this:
And so on and so forth... The progress bar is still moving, although quite slowly, probably owing to the gargantuan file size. It's just yielding four rows of codec was bad, and then not skipping atom , over and over again.
The file itself is 37.4 GB in size. I have shorter ones from the same day, smaller in size, as well as files greater than that, all recorded under the exact same conditions within OBS. I am willing to provide any files necessary in order to secure assistance with this issue.
I'm hoping for a swift response, as I do not know what will happen to my file once I end up unplugging the external hard drive it was recorded to. When I plugged it into my laptop and tried to open/observe the other video that got corrupted, it was displayed as having the size of 0B. I'm deathly afraid of losing this, so please, if there is any way this issue can be helped, do let me know as soon as possible.
Kindest regards, and thank you for making this software in the first place, even if it doesn't end up being able to salvage my file.
12:35PM local time update: The progress bar seems to have halted entirely. These are the last four generated lines: note the _ =1 that is missing from the last line when compared to the standard line.
As of 12:36PM local time, nothing else has been reported by the program.