Something that probably is not so hard to implement and that would be very useful (IMHO): possibility to set envelope/LFO tempo (BPM) individually for the instrument – independently from the song tempo (global BPM).
It’s a bit inconvenient/unnatural that for now any global tempo changes affect e.g. piano or drums envelopes…
After exploring all the new features of the new instruments available in Renoise 2.7 I believe the following should be features considered for implementation in upcoming versions:
KeyTracking amount assignable to vol/pan/cut/res envelopes.
All of the above should be able to be implemented and still keep backwards compatability with existing instruments (assign all samples to a single keygroup, scale existing envelopes, keytracking=0).
If the heirarchical browser is also implemented (please!) then keygroups could just be another level, i.e.:
Instrument
- Keygroup 1
- Kick
- Snare
- Keygroup 2
- Closed hihat
- Open hihat
Further development would be to create an ‘envelope device’ and ‘MIDI CC device’ for the track DSP chains. The ‘MIDI CC device’ would receive midi controller parameters and pitch bend etc. and output them to DSP effect parameters.
Then strip out the vol/pan/pitch/cut/res envelopes and replace them with a ‘Instrument DSP chain’ (track DSP chain equivalent). This DSP chain would be one per keygroup (as vol/pan/pitch/cut/res were) and could contain any native track DSP.
This would also allow MIDI mapping of instrument parameters by using the aforementioned ‘MIDI CC device’ so we could finally use pitchbend etc. on sample instruments.
Backwards compatability could still be maintained by having a DSP chain which emulates the existing vol/pan/pitch/cut/res envelopes.
As an aside, should this thread be tidied into pre-2.7 and post-2.7 discussion?
isn’t that the user’s problem though? (;
No it isn’t, an application should not have a feature that has a half baked effect and a lot of irritation around it.
There are already enough half baked effects around for features that aren’t completely supported by every plugin in the world (like audio routing and aliassing)
oh, i didn’t mean that renoise should come with a lot of plugs pre-installed or something. just an option for the user to embed plugs that they have used.
anyways, it was more of a question, not actually something i need in renoise. i guess it would only be good for collabs really.
mxb: Christ on a pogostick, yes! That is exactly what we need, and well laid out. Percussion sets especially would be a dream to mix that way, and we could finally convert those large sets to XRNI and have full sample access to them instead of running them in VSTi samplers.
2.7 was a serious step in the right direction. If this feature set is added, Renoise would transcend most instrument formats and finally truly move tracking into the new (well, -ish) millennium.
Cheers for that post.
/ Ahni
I would really like to see an option to make an instrument monophonic, and with glide to boot. Yeah, single note columns basically make it monophonic and you can use the glide and pitch slide commands when sequencing, but I want to be able to play it. As weird as it feels for me to say that, being a big sequencing junkie, I would really love to be able to just hit a couple buttons and adjust a parameter and then jam along with a monophonic instrument that glides between notes to get a feel for how the part’s going to go. It’d definitely get me one step closer to getting rid of my VSTs and relying more on native stuff. It would also make live performance a little less intimidating, as I use a lot of monophonic stuff anyway, but I’m not the best keyboard player, so I’d rather the note overlap just be taken care of for me so I can do all my crazy arpeggios and shiz with far less effort.
Speaking of which, also worth mentioning is that I would also really love to see an actual arpeggiator. Yeah, I know the envelope trick, but that’s pretty roundabout.
Seen the second, and not really attracted to it unfortunately. The first is what I’m saying though. Cool.
I came to renoise from another sampler, E-mu Emulator X3, so here are the things I’d like to see:
LFO in the instrument. This LFO would have have the usual suspects, but also a custom (we’d call it a function generator) where you would draw the curve (it was done in a series of steps - and you could increase the resolution of the steps). Important to include a lag feature (ms) so you can determine at what point the voice is played that the lfo would kick in.
Mod matrix. You can do some clever programming this way and extends the functionality of the sampler.
More to follow!
Well, there are mainly 6 things that the Renoise sampler is still missing:
Envelopes per sample! For some reason, right now, the envelopes are per instrument (can anyone explain the benefit of this?) This is also never mentioned in the manual, but it certainly should be as this behaviour is very unusual and also clearly not intuitive, given the place of the envelopes in the GUI.
Sample groups. With own envelopes of course.
Routing to multiple outputs.
Choke/Mute groups.
Crossfade looping.
Automatable sample start/end.
Did I forget something?
Those all sound awesome.
Also, nice numbering scheme.
Sigh I shouldn’t use copy and paste too late at night…
Anway, I fixed the numbering 
I have faith this will be coming and had as near as any feature has even been had promises from the Devs. Hopefully next version but I can’t tell for certain.
Could be useful but not really needed. Set more than one Envelope by selecting more than one sample at a time. You already have Mute Groups as a separate entry.
Renoise can output any instrument to every track in the track if you want it to do so (not at the same time in VST or other plugins) and tieing them to a track would be more limiting. I can see the benefit for when playing them live and this has already been implemented with MIDI.
Agree and also believe it’s on the cards.
With user definable cross-fade points/size, not a one size fits all solution you sometimes see.
09xx - Note Off/Note Cut.
Cool!
I agree, but would be very useful in combination with the output routing, read on.
Well, if I layer a snare drum with different keyzones on the same note, but with different samples, such that I can trigger them together, I would still like to be able to mix them separately. I want to play the snare, record it, it should get one single note in the pattern editor, but I should get as many channels in the mixer as I have layers.
Cool!
Sounds good.
No, again not suitable when trying to create “playable” instruments!
Also I think the track assignment is currently per instrument, no way to do it per sample. This is something I have supported, especially for recording (or live jamming) a drum kit instrument, where you want to be able to route each note to a separate track (although you may also want to disable it at other times.)
Also a toggle so the fixed track routing can also be taken advantage of with with computer keyboard, not only MIDI.
Yeah, I kinda wrote the “Split into separate tracks” with recording a drumkit in mind.
Yes, that would be important, too. I agree. Although this routing option would still be a workaround, since setting it up is quite cumbersome and you loose it as soon as you want to play a different instrument with the same controller.
I was thinking more a mapping would be saved with an instrument (within a song at least) but you could toggle it on and off. So if you didn’t want the routing, eg wanting to lay down a part in a different track to normal, then you can turn it off without loosing all the routing you have set up and then turn it on again later.
Simple velocity amount setting for envelopes wouldn’t cut it?