Hi - I applied pitch bend to a single note in the piano roll/MIDI editor.
I did this over and over to the same note, deleting it between each time (mainly because I was learning how to use it from a YT vid).
I noticed several times that the pitch bend applied to that one note was sometimes applied to other notes: at least once to a note that overlapped, and at least once to notes that were farther down the timeline and didn’t overlap.
I can confirm that after drawing in a pitch bend curve for a single MIDI note in the Note Expression Editor, the last value drawn in affects all subsequent notes played in the loop.
Thanks for any thoughts!
And I’d love to learn “how to fish” - can’t wait to see what you might say.
Thank you for showing me to focus on that area of the GUI, @Johnny_Moneto , I had no idea!
So close! I can actually change the pitch of the note by using the Draw Tool in the notes’s NE Editor, but I suppose the fact the process is unsupported in this patch is what is responsible for it’s not working properly - in this case, affecting the pitch of subsequent MIDI notes. (perhaps?).
All this started because I would like to pitchbend a normal piano-played MIDI note to make it sound more guitar- like, using this specific Halion 7 Sonic patch (Warm Chorused Strat).
Using the CC# is awkward, because the MIDI notes overlap, so a pitch bend meant to affect one note only winds up undesirably affecting the overlapping note.
Is there a way within Cubase to pitchbend just one of two overlapping notes, when using this patch?
This has nothing to do with Cubase and all with the particular preset - it is not possible. Not in Cubase nor in any other DAW or even without a DAW.
I don’t know why they created the guitar presets without NE support.
When you draw pitch bend data into the NE editor it is the same as drawing pitch bend data onto a controller lane, except the later one is more comfortable. It will affect all notes.
Oh, btw, pitch bend is not a CC; it is a class of its own in midi. Just to prevent potential future misunderstandings
Great to know, thanks @Johnny_Moneto , though the info itself is not great
I will almost certainly be buying musiclabs guitars, and SomethingorOther6 Amps (the first I’ve researched extensively; the second one is just a recommendation from a very trusted source), so all this will be history for me, but I sure did waste a lot of time assuming, duh, that a guitar preset would have Note Expression support.
(BTW - I went to make your answer the official green-checked one, but for some reason that option is missing on my screen now. I’ll try to come back and check later).
It took me a bit to understand the concept, too, and I am not sure that I get it 100% right.
For me it was easier to understand by looking at Retrologue. If you use the init settings and switch to modulation page 4 you see that two of the up to eight NE parameters are assigned to certain paramters of Retrologue, Cutoff and Resonance.
Volume, Pan, and Tuning seem to always be there. Then we can have up to eight other parameters for NE. The list gets automatically populated based on the VSTi’s setup.
All the other entries underneath (starting with CC 1) seem to be just another place to enter regular midi data, perhaps to accommodate MPE? I honestly don’t know what they are there for.
Of course the issue with Halion Sonic is that it doesn’t allow you to edit the NE setup of a preset. You have to live with how the preset was programmed. In Halion we can make those settings ourselves.
To add: Some presets of Halion (Sonic) allow us to set up NE ourselves. The Guitars of FM Lab (additional purchase, if I recall correctly) for example:
And while I am already stock piling info into this topic that nobody asked for:
If you want to actually use NE with Retrologue you have to first enable it here: