-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
SysEx MIDI input #272
Comments
Sysex needs often more complex handling. You can use them with scripts, and create "middle" variables that will hold the interpreted informations |
Thanks for answer! I still do not understand how to use scripting. Maybe you can share a link with some kind of manual about scripting? I just need to use constant incoming sysex message to trigger a consequence. Task is simple, but ... |
well, create a midi module and create a script in it (in the "Scripts" section. It will be automatically filled with everything you need and documented code |
Created empty script. In what place of script do I need to add my sysex command? |
The better place for this discussion is on the discord, in the forum. There are far more people who read that and can help you out there. |
Is it possible to add sysex support for input in future to be possible to use sysex message as condition? Currently I can't use sysex input. Chataigne can see my sysex messages in log window, but it can't learn sysex message.
It can be very useful for some consoles (like Yamaha M7CL etc.)
The text was updated successfully, but these errors were encountered: