-
Notifications
You must be signed in to change notification settings - Fork 114
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
Is it necessary to distinguish between different channels for one track? #294
Comments
peterrudenko
added a commit
that referenced
this issue
Feb 3, 2024
All piano events are grouped in tracks by channel, automation events are are grouped by controller number
Thanks for the suggestion! I guess that MIDI import should be smarter in how it splits events into tracks: in MIDI files, channels can be set per message, while in Helio channels are per track for simplicity, because a different channel often means a different instrument. Please check if the development build now fixes it for you. If you have ideas for further improvement, I'd be happy to hear. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is it necessary to distinguish between different channels for one track?
For example, a MIDI file has only one track, and there are multiple channels in that track, and the MIDI channels specify different instruments.
Helio now renders a track, but doesn't distinguish between channels, so only one instrument renders the track's notes...
Euterpe-X-MI-Seed-5.zip
The text was updated successfully, but these errors were encountered: