Press down chord and use multiple times action 'Script: ReaperTonStepInsertOrModifyHeldNotesByGridRight. Third bug without consistent reconstruction:ġ. Any suggestions highly appreciated Cheers Matt Every time you use autotune, God kills a kitten. until you hit the next key/chord: then the old key/chord is released and the new one sounds until you hit the third, and so on and so on. > expected result: get the same behaviour for all midi notes, either 'continue' the previous note or create a new midi note. Basically, when you hit a key (or a chord), it is held (like with a sustain) after you release the keys. > sometimes some note continues (connects to the previous same midi note) without starting a new midi note while other notes create a new midi note Select a note as your starting point Select the Re-Pitch option from the Note input drop-down menu or use the keyboard shortcut, Ctrl + Shift + I (Mac: Cmd + Shift + I ). repeat cycle multiple times to reproduce bug several times (on my setup it's like every third time) A collection of 25+ MIDI data filters in LV2 plugin format. Press down same chord again and use action 'Script: a' and release chordģ. Second bug with quite consistent reconstruction:Ģ. > expected result: new midi note gets written in midi editor, not the erased one > on my side is result that only the last deleted midi note from previous chord gets written down after 3rd step Press down another note that did not belong to the previous chord and use action 'Script: a' and release note Press down only one midi note from previous chord and use action 'Script: a ' and release noteģ. Step 3: There are seven main note names for the white notes, starting with A and continuing through B, C, D, E, F and G. Press down chord and use action 'Script: a' and release chordĢ. There are a few bugs I documented in the gif, so here is one, that can be replicated consistently on my setup:ġ. LE: Undo was fixed, pretty happy with the resultĬan you describe your gif, what were you doing, what you expected, what happened Unfortunately that is advance stuff witch I don't know at the moment. This most likely can be fixed using an extension by listening to the midi events. In the future I would like to create an full fledged extension.Īs an known issue, that I can't work around, is that notes with the same velocity will not be considered re-triggered and thus they will result in the lengthening of the previous note instead of adding a new one. (the original script had multiple functionalities)Īt the moment I'm still learning my way around Reaper and Lua so sorry if the code is a mess. This information will be sent along a cable via the MIDI out port or the USB depending on what you are using. I want to reproduce exactly what is happening in Ableton and nothing more. When you play a series of notes on one of these instruments it will send MIDI data for the note played (a number between 0 and 127) and a series of other numbers for velocity, pitch bend etc. That adds, lengthens, shortens and removes notes base on forward backward cursor movement. Updates will come in the next weeks as I clean up, optimize and fix the messĮnd goal is to have two action and a combined one for midi cc relative or mouse wheel.
0 Comments
Leave a Reply. |