truncate a note (addVolumeFade) *after* the note has ended
-
@d-healey yeah that works, but sadly it seems to add a distinct click to the start of every subsequent note...
-
@Lindon What's the fade time set to?
-
@d-healey yeah I just worked that out if fade time = 0 then click, else no click...
so well done - good work.
-
@d-healey ok so (sorry to be a pain here..) this is all nice but....
its using Artificial events, and now I want to add "legato" so:
step 1:play note 1 (and hold) = plays
step 2: play note 2 (and hold) = plays note that slides from note 1 to note 2
step 3:release note 2 = plays a slide from note 2 back to note 1...So pretty standard stuff, and my way (and I think yours is similar) is in the note off at step 3 create a new note and slide it from 2 to 1....
BUT: if we are using Artificial notes for our mono system - then I have no way of turning the new note generated at step 3 into an artificial version of itself...so our new note isnt joining our mono processing club...
So my question is: in the mono code what value is Synth.isArtificialEventActive() adding?
Why are we making it artificial at all? wont it work if we leave it alone? Just trying to understand the script... -
@Lindon said in truncate a note (addVolumeFade) *after* the note has ended:
now I want to add "legato"
You're one of those moving the goal post feature creep clients, I see how it is
@Lindon said in truncate a note (addVolumeFade) *after* the note has ended:
Why are we making it artificial at all?
We can't turn off real events so we have to make them artificial.
I think what you're wanting can be done because I'm doing a similar thing in my legato script, but it's probably a little fiddly.
-
@d-healey said in truncate a note (addVolumeFade) *after* the note has ended:
@Lindon said in truncate a note (addVolumeFade) *after* the note has ended:
now I want to add "legato"
You're one of those moving the goal post feature creep clients, I see how it is
damnit! I am!!! Let me take myself outside and shoot myself....
-
Actually thinking a bit more about this.....
if we are doing legato/glide - then this whole "stop the release sounding" thing might be a bit pointless - as we are sliding some new note into teh equation anyway...
-
@Lindon Yes I think you're right
-
@d-healey actually its simpler than even that I think.....
..separate out mono behaviour from glide/legato behaviour.... so two scripts: mono followed by mono glide...
-
@Lindon Let me know if it works, since we're not calling ignoreEvent I think you should be good.