Arp Sustain with Sustain Pedal
-
Wicked! Will give it a spin.
-
Nice, this seems to be working well. I might just tweak the
Engine.getUptime() - chordStartUptime < 0.02
for my project to add a little more flexibility in the note presses.Appreciate it!
-
@Christoph-Hart -- I know this is very late in the day but can I add yet another feature request in here.
Can we add a couple of range sliders - that set a lower midi note and upper midi note that the arp responds to - otherwise it ignores the input (passes the note thru) un affected - it allows users to play high sounds whilst (say) HOLD is engaged on some low notes.
I've tried coding a separate script to do this - by moving the midi channel of "out of range" notes - but the arp still responds to these notes
-
Oh! I added this to the cpp on my own. It's a pretty easy change, so if Christoph can't get to it, I'll send you a version with that included.
-
@Lunacy-Audio perhaps you could push these to the git hub repository?
-
Whilst we are here...
Tie doesnt seem to work how I think it should...When engaged if I hold down a single key - and have some notes at 100% length - then it works fine, but if I hold down a chord it completely ignores the 100% length and retriggers each step - I think it should work that it decides what note to play and then honours the tie for that step...
-
Ah yes, that might be true I didn't check tied notes.
-
@Christoph-Hart well dont spend any time on it now, instead head off and build those send and receive FX's.. :
-
@Christoph-Hart said in Arp Sustain with Sustain Pedal:
Ah yes, that might be true I didn't check tied notes.
actually this isnt really a problem - you get very "musically interesting" results with it:
engage LATCH (HOLD with reset ), engage TIE, set up a "tied pattern" - press a single note - you get the tied pattern playing, press two noes - you get the "standard" pattern playing, rinse repeat...
-
@Lunacy-Audio perhaps you could push these to the git hub repository?
@Lindon I've made some other changes to the arp which you probably don't want, but I can just send you the key range changes. Not sure if it's the best way to handle it, but it does the trick.
-
@Lunacy-Audio the best way is to push your changes to github
-
@Lindon Oh that's not what I meant by best way. I'm referring to my actual handling of the key ranges.
-
@Lunacy-Audio okay... send away...