taken from
As stated, this would be useful for creating a Key Command matrix for PLE/Macro scripts
taken from
As stated, this would be useful for creating a Key Command matrix for PLE/Macro scripts
Select Tracks of Selected Events
Selects the tracks of which have events
I came across an instance of needing a function like this when writing an AutoHotKey â Cubase Macro script.
I think this could actually be very useful in other more basic PLE / Macro scenarios (ones that donât require AutoHotkey)
Basically the only way to emulate this, is by enabling preference âTrack Selection Follows Event Selectionâ - but, because this is a toggle preference, it is not very dependable in scripts, and secondly, leaving that preference on sometimes clashes with other preferences and scripts.
The other option, is
WHOPS, threads so long I forgot I already requested this lol
Protocol for connecting Tracks to FX and Group Channels.
For example:
MediaTypeIs | Equal | Audio
Container Type | Equal | Track
Property | Is Set | Event is Selected
Track Operation | Connect Unused Send | Param 1 | Param 2
Param options:
Name â Param2: __________ (entry)
Name Contains â Param2: __________ (entry)
Track # â Param2: > Param2: __________ (entry) (or Track # list?)
Plugin-Name â Param2: Plugin List
â Could list all Sends in operation ontop of âUnused Sendâ ie
Unused Send
Send 1
Send 2
Send 3
Send 4
Send 5
Send 6
Send 7
Send 8
â
Same idea could be used for changing track direct outputs âConnect Direct Outputâ | Name Contains, etc
edit
The above could potentially be accomplished a different way, ie
You select an FX track and then the script targets tracks to be connected to it.
MediaTypeIs | Equal | Audio
Container Type | Equal | Track
Name | Contains | Voc
Track Operation | Connect To Selected | Unused Send | -6db
and another way, more similar to first
Whichever way, this could allow for some very quick, streamlined, routing. Especially for people who have detailed templates with FX tracks already created and named. Users in many instances, would never have to open up their sends routing, as this type of PLE preset could be hotkeyed, even macro combined with other track selection based PLEs.
Upon opening PLE Window, hitting tab once, only cues the header description space. It goes no further - doesnât enter into the actual script portion.
If this could be done, a scripting program like AutoHotkey could be used to tab to the, for example, name replacement fields
This would be useful in templates for users who are consistent in their track setups.
For example, if I set up my multi-timbral synths to be in folders with the same setup such as
/Folder/
And I set up all my multi-timbral vstiâs like this, then I could come up with a consistent track selecting system
This would require that
A.) Cubase sees when user has selected a FolderTrack and or a Track inside a FolderTrack and thus binds this protocol to that specific group of tracks.
B.) A new protocol is added to PLE: Folder Track-Position
0 = FolderTrack
1 = first topmost track
2 = second track
and so on.
In addition, there could be some other PLE protocols here, if there was a targeting condition âIn Selected Folderâ,
then specific track types could be targeted
Some general key commands could be included in the context of this idea
-Select First Track in Folder
-Select Last Track in Folder
âAdd Selectionâ
âToggle Selectionâ
Use Case:
With PLE, I have 16 MIDI Channels, Iâve created key commands to select each one, 1 through 16, using track name targeting,
This only only allows me to select one channel at any give time though. If the above was added, I could create toggle selector key commands, and or, addition selection key commands.
Not sure if PLE should handle this, but there needs to be a way to target specific Visibility Presets beyond the 1-8 key commands provided.
TrackVersions are another feature that was added to Cubase which never made itâs way into being integrated into PLE.
This would very useful, as it would allow TrackVersion operation without track selection, based off things like track name, âhas dataâ, etc
for example, as part of my template, i have record tracks 1-16. Essentially a record track for each of my AD/DA, all these are tucked into a folder. Iâve created PLEs already that target this record folder and record tracks - toggle show/hide folder, toggle record arm of each track or all tracks, etc, etc.
These tracks are named in a specific way so they can be targeted - CH#, MicPre name acronym.
If I could target these tracks TrackVersions would make for very fluid workflow without having to select them to carry out:
-New TrackVersion
-Duplicate TrackVersion
-Delete TrackVersion
-Rename TrackVersion
-Prev TrackVersion
-Next TrackVersion
ManâŚyou are really really deep into it. Impressed.
Is there a site or post where you share your created PLE presets or even Macros? I am sure you came up with insane ideas that could help a lot of people with their workflow (incl. me). Ideas i havent even thought about yet probablyâŚ
probably at some point but havenât had a chance to organize it/them in a way that would be tangible for someone else to understand, and also, a lot of the mechanics depend on being used in a macro and vice versa so they wouldnât work if I only shared just the PLE preset file, Iâd have to give macro instructions and the topology order as well. So it will take some time
I will probably wait and see if they update PLE in the next couple versions before I do any tutorials
While they are at it, some attention on the LE would be nice. Getting it to select different length notes, especially triplets is a PITA.
This thread is great - some really great suggestions.
Iâm a massive fan of the PLE and have utilised it massively when building my Open Stage Control Touch screenâŚ
But here is my request -
Speed the preset menus up!! please!
As you start to build a good bank of presets up the PLE gui slows down so it takes longer and longer to select them or edit them. Automation through the generic remotes you donât see the slow down but when manually doing it, time can stand still.
I have over 4000 presets now and it is totally unworkable if I want to manually reset or amend one.
Cubase seems to cycle through the whole list every time or something when loading one so it takes forever!
Extensive PLE (and MLE) user here so a hearty +1 to all of these suggestions. Especially the idea of being able to instantiate, query and/or address specific insert slots and plugins by name
I know you canât reply, very sad. But if you have consistent track/template setups, then canât you just apply one of infinite colours to the track and tell the PLE to look for it?.
Yeah, I like to brain storm what Cubase could (should) be. The LE and PLE were cutting edge DAW additions. I doubt we will see many improvements in this area as those devs have probably moved on to greener pastures.
Yes this is an issue, I know for certain the devs are aware of it, hopefully they can figure out a way to create some sort of index file similar to how MediaBay works
Property Is Set | is Locked / Property Is Set | is unlocked
great for finding events that are locked which sometimes prevents an action. can be annoying with 1000s of tracks and events.
Could also be used to target locked/unlocked tracks.
Another thing, PLE canât target audio events inside an audio part. Not sure how this could be resolvedâŚ
Not sure that window focus based target would be good, so perhaps a new PLE condition: MediaTypeIs | PartEvent
Another feature that would be great -
Search/do action based on content of notepad.
If tracknotepad contains <some text> do a PLE action/function
Great idea!
Could also maybe use PLE to add to notepad.
Brings me to another idea - I wish in the PLE, the user could enable a text prompt box that pops up if the script is ran.
âeasyâ implementation - /p (prompt)
which, this idea could be continued to other places, like all the menu selections could have a Prompt option.
Letâs keep the PLE ideas flowing! Most important part of Cubendo that more people should know about, and more dev resources should be put into.
Anyone who has already picked up c12 know if this has been fixed?!