Skip to content
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

Allow toggling bypass using MIDI messages #791

Open
yorkshiretwist opened this issue Jun 27, 2024 · 7 comments
Open

Allow toggling bypass using MIDI messages #791

yorkshiretwist opened this issue Jun 27, 2024 · 7 comments

Comments

@yorkshiretwist
Copy link

I am trialling Element to act as the host for a virtual guitar pedalboard. I have built a foot-operated MIDI controller using a Teensy (an Arduino clone). This controller will turn on and off effects plugins hosted in Element.

There is a demo here of me using the prototype controller to send MIDI notes triggering pad sounds: https://www.youtube.com/watch?v=rLNCCb5LYW0

I have added some controller mappings, however while it is possible to map controllers to node parameters, it is not possible to map a controller to the node bypass toggle:

node-bypass

Being able to map a controller to this parameter would be a very easy way to turn on and off effects plugins, especially where the plugin has no "bypass" or "power" parameter of its own.

I also found the process of doing the mapping a little tricky. It may be easier and quicker to allow selection of the node, controller, and node parameter from lists in the table at the bottom of the controllers screen:

quick-add-code-control

While I am a developer my C++ skills are very limited, so I'm afraid I can't really help out with development. However I have extensive experience writing technical documentation, and I'm happy to augment and enhance your documentation if you would like me to.

I've tried a couple of other VST hosts and Element is outstanding. I hope you are able to find the time, and some other willing volunteers, to continue working on it.

@yorkshiretwist
Copy link
Author

Alternatively, if it's possible to do more advanced manipulation of node parameters from MIDI using scripts, I'd be interested in learning how to do that. While the scripting amp examples are good, having a scripting example specifically for modifying node properties would be really useful.

@ngburke
Copy link

ngburke commented Jun 28, 2024

I am mapping a MIDI drum pad to the node bypass toggle for use as a guitar pedalboard. In my case the MIDI drum pad is sending a note rather than a CC so maybe try that?

@yorkshiretwist
Copy link
Author

Ah, that's really interesting. Can you tell me how you actually added the mapping? Did you use the "Learn" button? I feel like I don't understand the ways to add mappings. Thanks.

@ngburke
Copy link

ngburke commented Jun 28, 2024

Ah, that's really interesting. Can you tell me how you actually added the mapping? Did you use the "Learn" button? I feel like I don't understand the ways to add mappings. Thanks.

Once you have the control created, go back to the scene view where everything is wired up.

  • Click the Map button in the top right of the window.
  • Click the node bypass button.
  • Touch your midi controller button / pad.

Should be mapped at that point. This tutorial video also shows the process: https://www.youtube.com/watch?v=n_N8tUWBJ3A . The lead developer has other tutorials on his channel you can look at. Hope this helps.

@yorkshiretwist
Copy link
Author

Thank you, I thought I'd tried that and it didn't work. I'll look at the video and try again.

@yorkshiretwist
Copy link
Author

Thank you @ngburke , that did work. I'm not sure what I did before but clearly I did it wrong!

Do you know if it's possible to map a controller to the tap tempo function? I just tried it but it doesn't seem to work. Thank you.

@ngburke
Copy link

ngburke commented Jun 28, 2024

I also want mapping on the tempo and play/pause/stop but as far as I know it doesn't work. I filed an issue for play/stop #789. There was something else on tap tempo maybe scan the issues for some info (include closed ones too).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants