-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
advice for dpx sequence with bad file #450
Comments
Currently not, it could be implemented but not cheap (lot of corner cases) and we also advice for curating before storing at long term.
If you have audio and use e.g. My recommendation is curating:
Byte? Anyway, if no data I would copy the previous file (and document that).
If you still have the image data part, it is easy to copy the header from the previous file and edit the counter number so better to curate that now. If you don't know how to do it, please send the buggy file as well as the previous file, quick to do on my side. |
+1 |
Fantastic advice thanks. These reels have no audio. I did not know about the --accept-gaps flag, but now I see it in the manual. So it sounds like that is an option potentially, but for archiving purposes curating with documentation sounds more proper, although more time consuming. I don't have access to a hex editor at present but I'll see if someone can help me from my org's network. Otherwise, I'll send you the files, Jerome. Many thanks for the offer of help. Cheers |
Is there any way to rawcook a DPX sequence that has a bad file? We have two reels scanned by a vendor a year ago - so too late to request a rescan - and one has a single zero-bit file, and the other has a file with no DPX header that is unreadable.
Any suggestions for workarounds that would get us a functioning MKV file we would be fantastic.
I have already tried a few things, including removing the file and using a --no-coherence flag, and leaving the file and using the other --no flags, but no luck yet.
thanks,
Megan
[email protected]
The text was updated successfully, but these errors were encountered: