So I would like to know from you, danoise, if you now will add selection in matrix to the advanced options, how you would do manage those boundary cases? So I can understand what you think is the correct way for it?
Yes, I saw that other post. You mentioned notes being pushed out the pattern e.g. when using the "nudge down" feature?
As it is, this would obviously be an improvement natively, in Renoise. Because, currently those notes will simply disappear (say, when using "whole song" as the scope, which also will process multiple patterns). So I could definitely see it as an improvement to Renoise itself.
But "automagic" creeps in once the creation of unique patterns and such also applies in the *API*. That one is purely about raw access to the song data. If you for instance already had programmed a tool that nudges notes and preserves their position, you might have memorized pattern indices to achieve this.
Now, if the API magically was to create a new pattern by itself, that tool would break. See the problem?
Sure, Renoise can have "options" to decide on a given behaviour, but it only spells trouble when a programming language has such a thing.