This suggestion could either be implemented as a VSTi plugin, or as a native solution that can only be used within the Renoise host itself.
Basically, I’m here suggesting a futureproof and tracker-ish key feature that would make it possible to build further upon in order to handle both the “arranger” problem and the “clips” problem, two issues that have been discussed over the years before.
The idea:
A new object that could be loaded and saved just like .xrni can today. This object would be a sub-instance of Renoise (limited to basic features) - let’s call it Renoise Mini - running in another window and pattern editor that you could switch into. In this Renoise Mini you would be able to load VST instruments and samples and work just like you normally would in the host pattern area, using the same commands etc. Only difference would be that Renoise Minis were self-contained in regard to samples, notes, etc, and therefore could be loaded and used within multiple .xrns projects, independent of each other. (A bit like REX-files in Reason, although with the benefit of being able to manipulate the notes, samples and effects etc within the Renoise Mini instance.)
The Renoise Minis could also be mappable and triggered by notes in the Renoise host pattern editor, running as oneshot or repeated sequences. This would essentially create a dynamic and flexible solution to handle “clips”.
Workflow benefits: You would be able to preview Renoise Minis in the browser and replace them directly in a song project just like you would with single samples. You could test out new ideas on the fly, using and re-using previously saved Renoise Minis, e.g. building complex drumloops and re-install them anywhere in other Renoise songs, instantly. These objects could also be distributed and shared with others.
It has been suggested many times in the past including my +1’s (at least bringing out a VST variant). Would also make Renoise available to a wider audience because it can then be used in other DAWs.
It doesn’t seem to be in the line of where the devs want to take Renoise. Arranger wise that was not the plan at least. (i don’t know what is the plan as i haven’t seen anything this direction lifted from the ground backstage either)
Sounds nice and like overkill at the same time. I’m still hoping for send tracks in groups. If you’d be able to load and save a group’s content (DSP chains, automations, patterns, related instruments) from within a song then, that’d already be a very huge step forward. The pattern content of the groups could be loaded into some reserved or specially marked patterns then, so that you’d only have to use their aliases in the song sequencer.
The self-contained Renoise Minis, as I initially suggested, would also be a step towards (optional) encrypted containers, making it possible to take such sub-Renoise objects to a commercial level.
ReVisIT does quite a reasonable job, specially the assignment of patterns to midi keys is pretty slack. When you want to chain certain instruments, it is a way to accomplish that by simply stuffing the one note of instrument on each track in one pattern. It is only a lot of work to create a pattern per note though.
Eh I don’t think renoise fits with this paradigm. I’d rather not see it.
However, this idea fit well with Sunvox and the new MetaModule does exactly this … use one track’s instruments/routing as an instrument in another track. It’s pretty cool. Some of my half-baked scrap tracks become instruments or preset sounds to be used later.
Pretty sure new renoise vst is focused on the sampler and phraser, probably not including the tracker at all? Seems like the point is to distribute renoise instruments to other DAWS. The sampler would have to be improved a lot vs. version 2 for there to be any uptake with serious sample instrument makers, hence feature set of r3.
And, of course, to allow you to utilize renoise style sampler with the piano roll/arranger of your choice. This makes sense to me because there are going to be some people who are basically never going to bend from wanting renoise to grow eternally more fruity loopy or abletonish or reaper-like. At least with the vst, renoise can maybe keep many of these users in the fold in some way.
They were going to peel off sooner or later, better to give them something to take with them than nothing at all?
Also, many people who would never use renoise in the first place because of tracker interface will hopefully be much more inclined to use the sampler vst.
This might keep renoise on both disillusioned and mildly interested people’s radar while also increasing project support until some more good ideas can be implemented into the ‘daw’ side of renoise.
That assumption is correct for what we have tested so far.
What the eventual face of Redux will turn to in the next stadium, is still unknown, that further improvements are required was a thing the developers already agreed with before they even showcased the Redux concept backstage. Hence Redux Alpha/Beta testing will be postponed until more added and productive features make it a mature and worthy product for testing and discussing.
/> 
/>