8000 MIDI channel management · Issue #38 · nudibranchrecords/hedron · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

MIDI channel management #38

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.

Sign up for GitHub

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

Jump to bottom
Closed
funwithtriangles opened this issue Mar 15, 2018 · 1 comment
Closed

MIDI channel management #38

funwithtriangles opened this issue Mar 15, 2018 · 1 comment
Labels
enhancement New feature or request
Milestone
0.7.0

Comments

@funwithtriangles
Copy link
Member

Currently, MIDI channels are ignored and all midi info is parsed. This sometimes causes undesirable behaviour, such as taking in random note information from external devices when doing a 'midi learn'.

In order to fix this, it would make sense to give devices the option to have a 'MIDI channel whitelist'. The user could specify which channels are respected when coming from that device.

Notes:

  • Devices are currently omitted from saved projects, would need a clean way of handling missing devices, etc. Possibly only save the channel stuff and device ID and make use of it if device isn't missing, otherwise ignore.
  • May want to move over to a library for midi message parsing (https://www.npmjs.com/package/midimessage) in order to get the channel
  • Might affect More MIDI options #17
  • Simplest option would be to do this globally and don't think about devices at all
@funwithtriangles funwithtriangles added the enhancement New feature or request label Mar 15, 2018
@funwithtriangles funwithtriangles mentioned this issue Mar 15, 2018
Closed
@funwithtriangles
Copy link
Member Author

Simple global whitelist may be preferable as in reality most messages coming in will be via one connected device anyway. All other devices connected on the chain may only be coming in via one USB port.

@funwithtriangles funwithtriangles added this to the 0.6.0 milestone Jan 31, 2019
@funwithtriangles funwithtriangles mentioned this issue Mar 16, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
0.7.0
Development

No branches or pull requests
1 participant
@funwithtriangles
0