just some QOL improvements I am hoping for, especially for editing instruments with a lot of samples:
A possibility to filter/search the samples of an instrument (like you can already do in the file browser) and/or more sorting options like sample length - overall this window is really hard to navigate once you have more than a couple of samples
better sample selection for keyzone editor (selecting all samples in one keyzone becomes impossible if there are samples in the neigbouring keyzones. e.g. allow box-selection to start slightly above/below the keyzone would already help)
better way to copy samples between instruments and/or merge existing instruments into one
a way to do batch-editing to all selected samples for some operations (normalize, cross-fade …) like you can already to with sample properties
add sample groups or layers to instruments for better organisation and more playback options e.g. have the possibility to have one layer of overlapping samples play cycle/random and overlap another group while both play at once or have different groups of articulations per keyzone etc.
ability to easily mute samples / sample groups
allow “Render Instrument to Samples” to capture round-robins by doing multiple capture passes per keyzone and velocity step, automatically remove duplicates
Ideally it would be great if the rendered sliced data could replace the original pattern editor selection, muting residing Track_dsp/vst fx for the time of the rendered selection, so the result is seamless on the same track. But having the renders placed back into the song is already a big win imo. Seems like the tool is gone though
Elastique timestretch algorithms, along with the ability to stretch samples in a “manual” way (unbound by numbers of lines).
Edit: Actually, how about multiple types of timestretching. Including, but not limited to, gritty, nasty, granular timestretching (with multiple grains… I’m not just talking about phrases and 0SXX commands here).
@Daed Man, you speakin’ my language! BTW, have you checked out Radium’s granular capabilities? It sounds so much like Paulstretch mixed with a Pure Data granular patch. Just beautiful. I can’t use Radium very well on my Mac - too much going on, very difficult for me. Still. I’ve been begging for this (as you know) for several years now - since 2018, maybe?
Is timestretching so hard to program that every audio program licenses known solutions? I get it saves time programming and you could up the price for your product to account for the licensing costs, but perhaps native solutions are worth exploring?
Recently got fl studio and am pretty amazed how easy it is to drag audio into weird grooves using time stretching. This in renoises sample editor would be amazing.
Yeah new timestrech types would be cool and not that hard to implement, basically you need another option in the list and integrate the algos… I would like an old school timestretch similar to what is available in reaper or bitwig…
Tomorrow can be far away sometimes… But… Here’s pictures and a bit more info about why…
Currently im trying to manually import some music created in mline tracker (amiga…) into renoise. Step by step, this takes a while, im using PiP on my monitor, two mouses, two keyboard etc… Anyway… Since it’s such a timestretched task i’m doing small things each time spreaded over several weeks and it’s a bit hard to rememeber where i left off. At the moment im using the section-marker as a comment/note:
(it says: continue on pattern 6)
But! It’s a bit spacious, it takes up the same space the other rows when it could have been just a small “bubble” squeezed in near the minus sign or the select-box. Something like this (with a tooltip/box showing when hovering it):
I’ll add two to this long list:
-Auto Scale MIDI CC commands in MIDI Mapping instead of defining Min/Max. For example: I have CH1 CC25 mapped to Current Track DSP [SET] and I only have 2 DSPs. Typical controllers use absolute 7bit: I just have to barely move a knob/slider just to select the next DSP in the current track. Scaling should allow it to be equal of the knob/slider.
Some will say this is a convenience and can be easily edited on a midi controller, but I digress due to the amount of times you have to manually adjust it.
-Add a Midi CC for scrolling through a sequence vertically. The above feature has to be there due to definition of lines varying from 1 to 512. Technically speaking some MIDI controllers has this feature and it’s treated as a scroll up/down but that’s some.
