Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
|
|
Thread Tools | Search this Thread | Display Modes |
31st August 2020, 04:35 | #1 | Link |
Cary Knoop
Join Date: Feb 2017
Location: Newark CA, USA
Posts: 397
|
Is there a way to recover an interrupted ProRes 4444 encoding?
I was running a Vapoursynth script for about 7 hours with a few more hours to go when I got the BSOD.
Is there a way to recover the frames that were already encoded? FFMpeg message I get is: Code:
moov atom not found video.mov: Invalid data found when processing input Last edited by Cary Knoop; 31st August 2020 at 04:51. |
31st August 2020, 18:58 | #5 | Link |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,750
|
Remuxing it through mp4box might do the trick. Or with ffmpeg.
Some tools add audio while writing video, others may do all the audio at the end. The .mov file format is extremely flexible. If there is an audio track in the file, remuxing might salvage that as well. |
31st August 2020, 19:37 | #7 | Link |
Registered User
Join Date: Dec 2005
Location: Germany
Posts: 1,795
|
I tried different tools for the exact same problem but it was a mp4 instead of a mov. Never could rescue anything. That is why I use mkv now, lesson learned!
__________________
AVSRepoGUI // VSRepoGUI - Package Manager for AviSynth // VapourSynth VapourSynth Portable FATPACK || VapourSynth Database |
31st August 2020, 22:01 | #8 | Link | |
Cary Knoop
Join Date: Feb 2017
Location: Newark CA, USA
Posts: 397
|
Quote:
Interrupting the encoding still allows viewing the already encoded frames! Code:
ffmpeg -i test.mov -c:v prores_ks -profile:v 4444 -pix_fmt yuva444p10le test.mkv |
|
2nd September 2020, 00:41 | #10 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
The really only way (except maybe by using some heuristics) to locate individual frames within a MP4/MOV file is by using the "sample size", "sample to chunk" and "chunk offset" tables. Unfortunately, these tables usually will be written at the very end of the file, after all the frames have been written. So, if the encoding process is interrupted, these tables have not been written yet - and you are pretty much screwed. MKV, on the other hand, is based on EBML, a "binary" variant of XML. It means that, in a MKV file, each frame is wrapped in its own separate EBML element. This can be recovered quite easily, even from an "incomplete" file.
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 2nd September 2020 at 01:01. |
|
2nd September 2020, 01:02 | #11 | Link | |
Cary Knoop
Join Date: Feb 2017
Location: Newark CA, USA
Posts: 397
|
Quote:
From now on it is going to be mkv all the way! |
|
2nd September 2020, 02:54 | #12 | Link | |
Derek Prestegard IRL
Join Date: Nov 2003
Location: Los Angeles
Posts: 5,988
|
Quote:
|
|
2nd September 2020, 15:49 | #15 | Link |
Registered User
Join Date: Dec 2005
Location: Germany
Posts: 1,795
|
In some cases, like x264 with mkv output, the mkv file has "no index". That it why seeking can take very long with big files. I noticed it with my 40gb lossless encodes. Remuxing the mkv fixes it.
__________________
AVSRepoGUI // VSRepoGUI - Package Manager for AviSynth // VapourSynth VapourSynth Portable FATPACK || VapourSynth Database |
2nd September 2020, 17:36 | #16 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,750
|
Quote:
That said, a good remuxing tool can build the index post-hoc by analyzing an existing non-fMP4 file. |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|