128 channel support #253
Closed
128 channel support #253
Conversation
This file contains 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
totally untested
tests updated too
existing getEntryById method renamed to getEntryIndexById since that's more accurate of what it did.
|
Exciting news. Looking forward to this! |
|
Closed - superceded by PR #254 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Implements 128 channel support in EPS.
Extension will use 128 channels during import if REAPER version >=7.0, otherwise it continues to use 64 channels.
Export code supports 128 channels throughout since it will only use as many channels as necessary for the project anyway (and so is self-limiting since nothing can be routed to channels above 64 in REAPER <v7)
Plugins are fixed to 128 channels but will disable channel selection >64 if running in REAPER and the REAPER version <7.0
Closes #244