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

When inserting a new MIDI item under the edit cursor, set MIDI item colour to match the articulation colour in Reaticulate #204

Open
DoubleGrit opened this issue Jan 8, 2023 · 1 comment

Comments

@DoubleGrit
Copy link

DoubleGrit commented Jan 8, 2023

When inserting an articulation on a selected track, Reaticulate creates a new item at the edit cursor if one doesn't already exist. I propose an optional behaviour that when it does this, it also sets the colour of this new item to that of the chosen articulation.

This allows user to recognise what articulations are enabled without having to read the PC names, when not using the MIDI editor.

Caveat: this only really makes sense when using Reaticulate to insert a new MIDI item. Existing MIDI items may contain multiple PCs already, so colour changing an existing item will be at best confusing, and at worst, detrimental to the user's project organisation.

My personal context here is that I'm now also using Reaticulate to control MIDI-to-DMX-controlled lights for live shows. I'm using different articulations to choose different RGB blends, so I'm matching articulation colour in Reaticulate to the colour the light actually changes to, for easy selection and viewing.

Thanks!
Jack

@jtackaberry
Copy link
Owner

Hm, this feels like a feature only useful for a very specific niche use case. But I could be wrong, there may be other general uses for it. If you can find two other users who want this feature, I'll implement it. :)

Perhaps ask on Reaticulate's thread in the REAPER forum?

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