Replay from FilMic Support team:
"Thank you for writing in. Apologies for what you saw there. Truthfully we have only seen this reported two other times and we have no real answer for what happened because it's impossible to tell without having it hooked up to a debugger while the issue occurs.
What we DO know is that something catastrophic happened to the device while it was recording. Extreme memory issue, audio or video (camera) framework failure. Regardless something happened to the hardware during the recording which corrupted the app's ability to record the entire clip. Our hypothesis is that one of the failures mentioned above happened at the point that your video stops. The FiLMiC encoder kept on going trying to record what it could but the data it received was nonsensical and hence unusable.
This is about the worst possible thing to see with a recording app to be sure. We are aware that it has happened two other (reported times) but there is precious little to go on and we are still looking at a needle in a haystack at this point.
We are nearly certain it is not the app but rather the device. It's just unfortunate that it occurred while using the app as it obviously will paint us in a negative light. Let us know if you have any questions and you have our apologies that this happened to you. "
"f it were a 'buggy app' then we'd be seeing probably hundreds of reports. There are nearly 350,000 customers on the newest version. This sort of issue has been reported into support only three times and it goes back to more than 18 months ago. Highly unlikely that it's an issue with our codebase as the code was completely rewritten for v6 and the first report was on a relatively early build of v5.
We have reviewed the two clips in the previous reports and in neither case was any of the footage recoverable unfortunately so it's likely not worthwhile for you to send in the file at this point.
… occasionally, as B-cam (C-cam??) , or 100fps slowmo machine…
Schnurr wrote: …Replay from FilMic Support team:
… we have only seen this reported two other times…
Nice reaction, and I assume a 100% legit, keeping in mind, it is THE recommended 'pro' tool...-
but doesn't fix your problem…
No hands-on here, but mentioned in some threads about 'damaged' files:
This company in Spain seem to have an excellent track-record… linked to the price-section intentionally first
the statement from Filmic seems to be a bit weak as the piece of software shows at least the missing frames that Filmic didn't store properly.
lets see how they will react because remotely can't be the clip be processed according to the software and repair costs would be 138Euro so a bit to much for editing just my son's soccer team. A pity because they won 7:2 in their last match and finished the F2 season being 1st
Schnurr wrote: …the piece of software shows at least the missing frames that Filmic didn't store properly.…
I'm by far no expert, how .mov files are stored, what and where a video-stream contains of 'data'… but very obvious: the 'video' itself is there - what's missing is a 'structure' to make it usable…
Soo, from the outer rims of my Bag of Dirty Tricks:
Have you tried VLC for playback?
VLC can playback anything … and because it was meant, in it beginnings, for streaming media, I could imagine, it has some 'fail fixers' which 'ignore' the bumps in your file.
When, or If it works, fingers crossed, It has some weird 'export/share/convert…' - never understood the interface… but worth a try.
thanks for the hint. I tried it but the App crashed a couple of times after opening the file. Tried it as well with other repair software but without success. so lets see with what aeroquartet will come back. Super fast email responses by the way