Ah, it’s the Session Recording idea! I like the idea, but theres many things to consider before it can be realized.
For example, what would you expect to happen when you enter a block loop? Should the result be an “endless” pattern, repeating over and over? Should the same apply when you hit pageup/down?
“Simply” streaming the performance into another pattern, or even Renoise instance, couldn’t even support this because we have an upper limit to the size of a pattern (512 lines). Should the tool’s “stream target” then automatically divide the input into equally sized patterns?
A perhaps more efficient way to achieve something similar within Renoise would rely on Duplex. If we imagine for a moment that the track muting, pattern navigation etc. is happening “through” Duplex, then Duplex is also able to memorize the performance - and therefore, recall it. But instead of creating a new song from one’s performance, you could end up with an editable list of events:
00:01:52 - Mute matrix slot (Pattern 1, Track 1)
00:02:12 - Volume adjust “-5.1db” (Master track)
etc.
Personally, I like this approach because you can then fine-tune and adjust your performance afterwards. The catch is that the performance relies on Duplex. And not everybody has controllers.