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
"SWS/FNG: Show only used CC lanes" does not restore "Program/Bank Select" lane #1344
Comments
With this change, all these actions ("SWS/FNG: Show only used CC lanes", "SWS/FNG: Hide unused CC lanes", "SWS/BR: Show only used CC lanes (detect 14-bit)") behave better in the sense that they do add a 131 lane, or do not remove it when a PC MIDI event is there. I still don't like the fact that that the "Show" actions add the pretty useless 00, 32 and PC lanes. In my local repo I also have a quite opinionated tuning of |
@icalvo |
Certainly! I wanted first to discuss whether you want simply to add/remove the 131 lane. or do more within the actions. But I find it logical to leave the simple logic of "I add every possible lane that will show info for the selected item, no matter if it is useful or not". My problem is that then I lack a set of actions: "Hide CC lane NNN" for all NNN (same as "Set CC to NNN"). That way I could set up my desired behavior with a custom action like:
So I will submit a PR for the simple thing and then I will create a feature request for the "Hide CC lane NNN" and see if I can implement it. |
It instead sets three separate CC Lanes for "00 Bank Select MSB", "32 Bank Select LSB" and "Program" instead of the very useful "Program/Bank Select" lane that reunites all of them and shows the events as "pencils" with labels with the selected program name.
"SWS/BR: Show only used CC lanes (detect 14-bit)" shows a similar behavior, except it creates a weird "00/32 Bank Select" 14bit lane and the "Program" lane.
My suggestion would be instead to create the "Program/Bank Select" lane when you detect any Bank/Program MIDI events. I don't think the standard CC lane representation is of any use for these kind of events.
Before action:

After action:

The text was updated successfully, but these errors were encountered: