Disagree B) , while the phrase editor fulfills most, if not all basic arpeggio needs, being able to have this tools functionality in the 3.0 pitch envelopes means you can tweak and experiment, create slides, transpose melodies differently through hooking up macro knobs to the parameters. Eg; being able to gradually fade-in/fade-out the arpegiated pitch melody through linking the from and/or to + duration fader modulation devicesettings to a macro. Gradually modulate a melody that is imported in the pitch envelopes through a lfo et cetera. Try to this in the phrase editor .
Maybe if because of all the changes in the lua api this proofs to much work for the reseq tool, the initial tool which it is inspired from might be easier to update?
I just need a way to get the pattern editor notes (and phrase editor?) in an instruments pitch envelope!
Yeah, now the dust has settled somewhat on R3 I agree with what you say… I think given all the changes that were made to instruments I’ll go back to basics with this one and just look at getting the piano roll to pitch envelopes working first and take it from there… Another thing I miss in the new instruments is the envelope follower on the filter envelopes… I managed to get some cool sounds with this tool and the env followers which I have not been able to replicate with the new instruments… yet
With all the new instrument editor envelope goodness in 3.1, I’d really like a way to convert note-events from the pattern editor into pitch (point) values in the modulation tab.
For example add an lfo device after such pitch conversion in an envelope and gradually increase the amplitude from the lfo to bend the melody in flexible ways, easier to realize then fiddle with the pitch pattern commands. Would open up many rooms for experimentation.
Although this tool deals with a lot more, I mainly am looking for note to pitch value conversion.
yeah, I was thinking about bumping that thread first , think it didn’t work in 3.1 last time I tried. Importing the tool right now gives an error notice that it has been disabled, will try the manual manifest updating to see if it works and report back.
ok, so after changing the manifest api nr from 3 to 5, I can enable the tool in the tool browser, however when opening it from the tools menu (on an empty instrument) gives;
'C:\Users\pluge\AppData\Roaming\Renoise\V3.1.0\Scripts\Tools\com.afta8.NotesToEnvelope.xrnx' failed to execute in one of its menu entry functions.
Please contact the author (afta8 | fathand@gmail.com ) for assistance…
main.lua:43: unknown property or function ‘sample_envelopes’ for an object of type ‘Instrument’
stack traceback:
[C]: in function ‘_error’
[string “do…”]:48: in function <[string “do…”]:35>
@afta8 do you still have the original old code for the reseq tool somewhere? Would like to trial and error it in chatgpt to get it working again since it stopped after one of the api updates.
ok the main issue is that there’s no sample_envelopes anymore, aka you can’t just go sample_envelopes.cutoff - they’re all wrapped inside sample_modulation_sets now.
this is gonna be interesting.
EDIT: then when you get it to load the devices, it’s still referring to p_env.envelope which doesn’t exist, so those need to also be referring to the envelope device. what a mindwreck.
i’ve done what i can and got it to here, but there’s still lots of errors going on. i’ll want to be looking at this a bit later furhter down the line, it hasn’t been very fun
had to remove the follower stuff too since apparently no longer there. com.afta8.ReSeq_V0.6.xrnx (6.2 KB)
once the day is over i can have another look. yes, the filtertypes shoot errors, too. but at least it boots up with Renoise 3 now.
Cool, just tried it and it accepted the full code in one go which is better then chatgpt, though returning the full code as an answer immediately reached the end limit of the session . 20$ a month really isn’t an option for a non coder with too many subscriptions already. For now I stick to editing small things.
.
B)
.
