Continuity in API improvements and their expansion. There are still things to polish.
From the API, ability to overlay already set MIDI mapping settings, without losing it entirely.
There are a lot of details here and there that could be improved
On the other hand, with version 3.2.4 on Win10 x64 and using tools related to handling MIDI input, renoise crashes with no error reports. I don’t know what the cause is.
I suppose it is still very important to keep trial and error testing in multiple circumstances to keep the software as stable as possible. It would not be surprising that with the new VST3 support and MIDI control there may be stability problems.
Deeper more advanced modulation possibilities, more vst directories, better and more advanced time stretching (non real-time would be fine) , microtonal capabilities, being able to create and save tuning templates the same way in which dsp chains and modulation presets are saved. More advanced groove settings and a greater ability to control them. Better wave editing in the sample editor, would like to see sound forge/reaper type editing capabilities.The ability to load and save text files and also a calculator.
fx layer device (found in Bitwig in Ableton as well)
ability to create parallel chains within the single mixer track. With the dedicated solo and mute buttons, and volume for each chain. (Bitwig FX Layer device is great to take a look at)
Multi selection of DSP lanes, reflected in the API
I would like to suggest multi selection of DSPs in the dsp lane and mixer view, reflected in the API. This would make a lot of new tools possible. You can already somehow emulate multi selection of DSPs in the api, but it will be ugly.
Route midi / note data to the fx chains
Then we could put VSTis into the FX chain, setup a whole instrument setting including fx, and parallel routing and then put it into a preset. Also then you could trigger multiple instruments at once with a single note. The abstraction layer instrument / fx chain could be used with its full potential.
As a bonus, the whole VSTi/VST layer could be activated for Redux, too!
For heavy VST users like me what would be cool is :
Freeze track feature (I know there was a tool for that), or a way to render VST instruments to sample INCLUDING the effects (instruments effects or track effects).
Tool to see CPU consumption and latency for each VST instrument/effect
That send tracks could be put anywhere
Thanks to the developers for keeping Renoise alive!
I know I have seen it thrown out there before, but multiple song Templates would be pretty useful. I think I saw a Tool for this but would still like to see it as a native option. Such a trivial thing yet very useful, at least for the way I work.
-Velocity to sample playback start position.
-LFO snapshot recall via macros.
-Native support for more instrument formats. E.g. sf2. or to be able to reuse Remorse tools on Redux.
Something I have been thinking about since using Sends a lot more.
“Soloing a Send track would switch all send devices routed to it to Mute source (if not already) and not mute the tracks themselves, so you would just hear the effects on the Send track.”