Anyone else think ‘Locking effect parameters to patterns’ should be on by default?
You create a pattern you like as a basis for you tune with or without effects/automation, you copy the pattern to the next row to evolve it somewhat and the effects/automation are copied too, but you evolve these again, but automatically this pattern doesn’t change the first pattern in a global manner? So I guess what I mean is global changes are off by default. If I added effects or automation to a copied pattern I don’t want that globally added to the other patterns on that track.
perhaps that could be a preference on the project. To me it seems more logical to have it default to being global, as my mental model is to think of the effects as across the entire track rather than a pattern thing. But I can see your argument too
Yeah I think it’s probably my preference. I like to work on a pattern add effects and automation, copy it to a new pattern keeping everything in the last pattern I worked on then change the effects and automation some more, then copy again to another pattern, but none off this globally changes the other patterns I’ve worked on, they are all individual. I can do it manually locking these but gets a bit clunky.
Yeah a Misc option would be great, even if it was to turn off the global change mode on all patterns for a track. However if you copy a pattern it does bring those settings with it (automation, effects).
+1 I’m more inclined to have effects be pattern specific so I would probably use that, I think the flow would work better for me
I find that I put down the first pattern with a couple effects, then start working on a new pattern (maybe by duplicating the first), and I want to put a new effect on the new pattern. Almost 100% of the time I end up setting the new effect to be pattern specific because I don’t want whatever changes I’m making to screw up the first pattern.
I felt inclined to come back to this thread and say I think I was wrong. After accepting effects as global to the track and not thinking about them as part of the pattern I was really impressed with the versatility and I’m not sure if they work as well from a pattern based perspective.
A setting to change the default behaviour would still be nice. If I’m being picky it should be by track so I can have different tracks behave differently.
I would start with having generic FX1, FX2, FX3… on/off automations pre-populated on the automation list, in the off state, with default value 0… for every pattern.
I believe these automations would be manageable even without explicit names of FX. And they could be made optional as well - we could only enable this via instrument definitions, so we don’t make FX too confusing for new users.
Ideally, the integration between automation lane and mute state on the FX slot would be extended. The mute action from FX slot would overwrite the automation lane. We could have “mute FX on pattern” and “mute FX on ALL patterns” actions in the menu.
That would simplify the ability to use FX per pattern, without adding much clutter.
The FX parameters automation lanes would be added manually if needed and they works be effect specific with names and everything
Ideally, we could add them / enter the automation lane straight from the FX screen by holding Effects button and pressing the encoder of the FX parameter, or some other button combo + encoder press.
EDIT: Just read this post and realized I have probably missed some technicalities of the current implementation, will check again in the evening.
