Rudimentary support for reading MS-200D+ effect files #95
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
I'm not sure these are regular independent effect files. The effect name for a lot of these odd ZD2 files are "CMN 0". So the effect name is not unique, and CMN is perhaps an abbreviation for "CoMmoN", indicating that this file contains code shared by multiple other effects. That's just a guess. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some (but not all) of the ZD2 files for the MS-200D+ have INF2 and CCOE chunks, and are missing the DATA chunk. decode_effect.py would fail when reading these files.
With this small fix, decode_effect.py is able to decode these ZD2 effect files from MS-200D+.
Example: python .\decode_effect.py --dump MS200DPLUS\COEHC2G8.ZD2
I have not made any attempt at figuring out the contents of these two new chunks.