Hello, I have a series of 10 logical editor presets that creates a strum effect on a block midi chord.
Basically each Logical Preset moves a note in the chord back a few tics with ever increasing value. So the first preset moves the second note in the chord to the right a little bit, the second preset moves the third note in the chord back a little further and so on and so forth.
I then created a macro that executes all 10 of the logical presets.
The problem is, that unless you run one of the individual logical presets first, the Macro doesn’t work. The notes jump to the wrong position and the Macro is useless.
Once you “manually” run one of the logical presets, the Marco then works until you close Cubase. The next time you open Cubase you have to do the same fix again.
Can someone from Steinberg take a look at this? I’ve attached a screenshot of the Logical preset.
Assuming your first pic shows the first of your 10 LE Presets, try changing their range to be 0-9 rather than 1-10. The lowest note in a chord is position 0 not 1.
If that’s not the issue can you post a screenshot of your Macro.
Hi raino, thanks for checking in. Sometimes people from Steinberg look at this, but you have a point, I should send in a bug report directly to Steinberg.
As for your suggestion, I don’t want the first note in the chord (position 0) to move.
Here are screenshots of the incorrect behavior, when I first try the Macro, before my work around. And then after my workaround.
I’m running it inside the key editor. Either by selecting the specific notes I want, or by having it affect all the notes in the part.
More specifically I’m triggering the macro via the midi remote.
This used to work great, but broke with a Cubase update. I think 12? Haven’t needed it for a while, but the project I’m working on right now has a ton of acoustic guitar parts and so I’m using it all the time at the moment.
I see what you’re saying. The workaround is simple here though. It sufficed to open the LE after opening the program (without hitting Apply), then it works.
Hi @steve thanks for checking. Yes, that’s what I find as well. Opening up the logical editor window fixes the issue. I originally thought I had to run one of the LE presets, but I just tried it and simply opening the logical editor window works.
I suppose I could build the Macro so that the first two steps are to open and close the logical editor window. But it would be nice if this found it’s way to Steinberg as a bug and was addressed
Thanks for taking a look and confirming this with me!
Try wrapping them all up into the project logistical editor which gives you 8, 4 prior to selection and 4 post selection. Perhaps you might have series of similar elements you can group into one in order to meet this 8 max limit. Other than that, try putting pauses or gaps (command with nothing in it) in between. I do what you’re doing here regularly and don’t have this same issue.
Fool proof way would be to copy and paste all these into one big macro of course
Hi Jake, I tried wrapping 8 midi logical editors into the project logical editor like you suggested and to my surprise it worked!
So far there are only two very small disadvantages I can find. The first is that it has a limit of 8 notes as opposed to unlimited with a Macro. And the second is that when you hit undo it undoes each note moving one at a time.
With the macro when you hit undo all the notes go back to their original position. With the PLE workaround you have to hit undo for as many notes that were moved. Like I said, this is a very small hindrance and not really a big deal. Just an observation =)
Thanks for the idea!
Below is a screenshot for anyone that is curious about what we are describing.
No worries, I rarely need more than 8 (I think only one time so far) and although a pain at first, but now I like cause after doing it this way or sometime, I’ve built up a selection of little/shorter macros that when put together do different things as oppose to writing one big one for a very specific task and after that, it really can’t be used for anything else. Sometimes it’s very handy to be able to select or transpose stuff in the middle section too, I try and use this area for things that vary where possible.
One more thing to share, make 8 blank macros and instead of naming them descriptively name them MAC1, MAC2 etc. load these into the PLE in the their sequential order and call it something like testing or Defaul Nested Macro etc. I then take a copy of all those files Their blank state and place inside a subfolder. Now, when you want to do something quickly, or test something, just edit/overwrite the MAC1,2,3 files and run your master one (suggesting making a key command to these, I’ve got them as RMB+1,2,3 etc with 0 as the master macro. Once you get the hang of it its super quick to test ideas and run the ones you memorised over time (Hal time, 1.5time, shift vel on 2nd and 4th beats etc)
Another thing you can do when the LE would otherwise be greyed out is to select the or any midi track and toggle on edit in place. With this on, you can run the LE in the arranger view whenever you need. One exception is though, the midi part you want to edit must have something in it, 1 note, 1 controller automation event etc.
Oh and don’t forget, you could put this master macro PLE, inside another PLE! I wonder how undo states work in that situation? I’m not totally across what you’re trying to do here but the input translator might also be useful
