-
Notifications
You must be signed in to change notification settings - Fork 36
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
Error opening aaf file #133
Comments
From that magic signature it looks like a KLV formatted AAF file. It is basically an MXF file. These type of files have been starting to coming up recently, another user has reported them to me as well. pyaaf doesn't really support them yet. The mxf parser in pyaaf can read them and with some modification the pyaaf could convert them to standard aaf. The AAF SDK has a tool that can convert them to the standard format too I think. What is the transcoding software? Are you able to provide a sample? |
Hi Mark, thanks for taking a look. These files are produced by a piece of transcoding software called Amberfin, made by Dalet. I will email you a sample file if that works. I was able to read and dump the file using the mxf module. Is it possible to edit parameters and save the file? |
this also relates to #53 |
Hi, I had the same result when trying to read AAFs exported from Avid Interplay Access. The file is just an metadata for a sequence with the links to the MXF files. Attaching the AAF (please rename the file to AAF) CompoundFileBinaryError: invalid file magic signature: [b'\x06\x0e+4\x02\x05\x01\x01'] |
Hello Mark. Thank you so much for your work on this project. I am still new to the module, so please forgive me if this is simple. I can open certain aaf files, however I am trying to open an aaf file that was generated by a piece of transcoding software that our facility uses. When I do, I get the following error:
CompoundFileBinaryError("invalid file magic signature: {}".format([self.magic]))
CompoundFileBinaryError: invalid file magic signature: [b'\x06\x0e+4\x02\x05\x01\x01']
How might I troubleshoot this?
The text was updated successfully, but these errors were encountered: