I would like to suggest again that the renoise team rethink their strategy regarding moving note data.
Currently the data will be truncated or last line in pattern won’t be touched, which makes not too much sense from musical point of view.
If note data is moved up or down and should reach next or prior pattern, using any kind of operation (dragging, adv. Edit Etc), I would like to suggest a logic similar to this:
move data to the other pattern, if it has another number and is not repeated anywhere
duplicate the other pattern, if it was repeated somewhere in the whole sequence and is not the same pattern
duplicate the current pattern, if the other pattern is the same
First I thought this idea would bring a mess with unpredictable behavior. But it’s not a bad idea if envisioned and implemented properly IMO. I imagine it would make totally sense given a requester pops up stating “This operation requires pattern x to be made unique - [Make unique] / [Cancel operation]”.
If that was the case I’m all for it. It would then be clear and not disturb or confuse what we’re already used to, but rather be a nice refinement to the current behavior.
PS. Scripting some additional shortcuts for song-wide insert/backspace line is a very nice idea btw.
I wouldn’t want this behavior as default, in any case it should be optional. For example I wouldn’t want every time I (accidentally) hit the insert or backstage key (too many times) when editing note events in a pattern, this to affect all notes in the song of that particular track! Should you forget in which pattern you made the edit, you can ctrl+z, but what if you have done a lot of things since, you’ll have to go back in the song and preview patterns until the first note shifting action is found. I see more caveats then benefits atm.
A modifier key combo could be a solution, shift + insert, shift + backspace, only have such combo’s affect notes globally. Probably such thing can be scripted already B) .