It tried to create a Macro for this by doing Split Range then Mute, but it doesn’t select the new part to mute it, so I thought a PLE might be the way.
Having a hard time coming up with a way to do this in PLE, though (admittedly I still have a lot to learn with PLE).
Here’s what I want: Split an audio or MIDI event in the range I have selected with the Range tool, then mute the new event that’s created by the split.
As I wrote, that doesn’t work for me. It doesn’t select the actual range that it just split so it can mute it…so it can’t mute anything. Try it out and see.
This turned out to be a bit more convoluted than I first would’ve thought.
Perhaps there is a more elegant solution to this, but the below seem to work.
You will need to create two PLEs—“Select Parts beyond cursor” and “Deselect Parts beyond cursor”.
Thank you SO much – this works almost perfectly. Sometimes it will hide all tracks after doing it a few times, and also for some reason always scrolls to the top-most track in the Project Window after it’s done muting.
Perhaps this would work too. I see similarities to @mlib 's approach as expected, the main difference being that I’m using the “select events under cursor” command instead of PLEs, right after I turn the object selection tool on, in order to get rid of the range tool.
Thanks! I tried this and it didn’t work unfortunately – it leaves the split event un-muted and instead mutes the event in the track underneath for some reason. I’ll see if I can figure out why.
@m.c The “Select Events under Cursor” is a good idea!
I tried the following macro and it works on my end.
Note that the last two commands in the macro are optional.
The track visibility commands are necessary steps with this approach as without them, you will mute parts on other tracks as well. It’s unfortunate since, as @Electriks pointed out above, it causes the project window to scroll to the top and you loose your place when editing.
Ideally there would be another, more suitable mechanism for converting a range selection to a part selection. Something like “Select Parts inside Range Selection”. Alternatively, a way in the PLE to have actions only affect selected track(s).
I see, I didn’t know, you tried exactly this Macro.
If this is the case, my expectation is, that the issue is the well-known “idle” in Macros. Cubase doesn’t wait until the command A is executed. Cubase just fires the series of commands.
My workaround is to insert the Save command in between. Cubase always has to wait for the Save command.
That means, in this case the Macro would look like this:
You should try your own macros before posting them.
There are several things wrong with your suggestion. One of them being that you can’t perform “Edit > Mute” when using the Range Selection Tool. Secondly, the Part has to be selected before muting it and the Range Selection doesn’t select the Part.
Do you have an actual example of this? I have never had an issue creating macros due to such behavior. However, I have noticed timing issues when using PLE Pre/Post commands.
I understand. Most probably I missed the point of selected tracks only. However, when I’m using the range tool, I think of it as selecting an area, and apply my edits on this area, not just a previously selected track (or tracks).
BUT, I always have the option “Track Selection Follows Event Selection” enabled, and so, whenever I draw a range, the corresponding tracks are automatically selected. If I disable this, then my macro won’t work properly if at all. I’m mentioning this, just in case it would be of help.
This is really odd. The first time I tried your macro I could’ve sworn it didn’t work for me. Now it does though.
However, it only mutes the part on the top most track. It seems when switching to the Object Selection tool the selected tracks change. I have “Track Selection Follows Event Selection” enabled as well.
Before:
After:
I’m on 12.0.70 so there could be a difference between versions I suppose.
Either way, I find your solution much more neat and had it worked for me the first time I tried it, I wouldn’t have bothered messing around with convoluted PLEs! (I’m still scratching my head on that one. Even restarted Cubase to make sure that wasn’t it.)
Thanks for pushing your solution again or I wouldn’t have tried it a second time!