-
Why does AME do nothing to save exported data when it runs into an error?
So I’ve just wasted 12:12:16 (12hs) exporting a video and at the very end: “File importer detected an inconsistency in the file structure of VIDEO.mp4. Reading and writing this file’s metadata (XMP) has been disabled. / Adobe Media Encoder / Could not write XMP data in output file.” Which of course with an MP4 means: “Here, this is a 24-byte MP4 file that has absolutely nothing and is useless. You’re welcome!”
Now, I understand this error is because there wasn’t enough space in the drive. And having been using video-exporting software for over 20 years, this isn’t the first time it’s happened. Knowing this, however, I made sure to have what I assumed was more than enough space free on my SSD for the export (not only the calculated final video file size, but also more than enough for the “raw” material before the final compression and encoding).
Anyway, my main question is: Why at this point doesn’t AME (a) warn you beforehand that it probably needs more space than is currently available and/or (b) pause the export at the very end and warn you BEFORE it just tosses everything in the bin and (as what can only be called a taunt) gives you a useless tiny file with nothing inside? I’ve waited for years for AME to incorporate an auto-shutdown feature at the end of all exports, and that’s only just been made available; so am I right in thinking that this is another feature that could indeed be implement but Adobe, as per usual, is just dragging its feet?
Now, my rant about Adobe over (knowing full well they ain’t gonna read it), do I dare hope that somewhere in my computer I may have access to the “raw” file and might be able to rescue my export? (I already know the answer is still no; but here’s me crossing all the fingers I own.)
-
0 Replies
Sorry, there were no replies found.
Reply to this Discussion! Login or Sign Up