-
Notifications
You must be signed in to change notification settings - Fork 153
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
RIFX, nested structs and endianness #1022
Comments
Incorrect. Embedding was removed, nesting was never an issue. You have to make a more precise question for me to be able to answer it. |
Can Consts have endianness? I.e. the FourCC is either RIFX or XFIR. I would like to create one struct that can handle both. |
I'm currently checking out old Quicktime files and I'm having the same issue.
Each type has specific documented fields.
It looks to me construct works best when the data is known in advance. |
Hello,
I'm working with construct to parse RIFX files for director.
My goal is to create file format documentation and code side by side and browse-able inspection of files, in the same vein as the construct editor.
In short, RIFX is a container format, a header with a count of the assets in the file, followed by a
count
times repeating struct with the asset type, size, offset in the file. Followed by the actual assets. See [1] for an overview of the format.First of, is there a way to specify endianness for the whole structure?
RIFX files for windows and classic mac have the same file structure, they differ in endianness,
i.e. XFIR instead of RIFX.
The documentation mentions that nested structs are not supported, only inlines.
I would like to leverage the parsing in construct as much as possible.
Since nested structs aren't available, what is the recommended way to deal with
nested structs?
Are there examples of parsing container formats like these?
[1] https://nosamu.medium.com/a-tour-of-the-adobe-director-file-format-e375d1e063c0
The text was updated successfully, but these errors were encountered: