Edit NSF export format to allow adding more effects #46
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.
Previously, NSF export wrote command numbers as even bytes, and used them directly as indexes into an array of 2-byte command handler addresses. However we ran out of even bytes in the range of bytes interpreted as commands
[$80 .. $E0)
, meaning there's no unused IDs to use for new effects.Now, each command number is an arbitrary byte, and the driver multiplies commands by 2 (dropping the high bit), turning them into valid indices into an array of 2-byte command handler addresses. Now we have twice as many slots available for effects/commands. This enables adding more effects into the NSF driver, both effects implemented in the tracker but missing from NSF export, and future effects.