I know this can be one in the Project logical Editor, but that is limited to one preset per name, or having to open the window and change the name. I could also use Soundflow to do that of course using shortcuts and clicking etc.
The only track related Cubase item I could find is 'tracksActByName' and I thought using 'sf.ui.cubase.tracksActByName({containsName: 'Test'})' may be working towards using it, but I fear that command is not what I think?
So basically I want to be able to have a popup text where I can type something contained in multiple tracks, and then have them all selected?
Christian Scheuer @chrscheuer2018-07-28 22:56:08.169Z@JesperA, do you know if this is currently possible?
Jesper Ankarfeldt @JesperA2018-07-29 03:49:13.168ZWe were working on it, but skipped the select function.
The idea is that it's indeed calling a Project Logical Editor script, and if it's not there it create it on the fly. But in order for Cubase to see the script you have to "re-initialize" the Project Logical Editor. And there's an error right now, which makes it not call that function.If you look in packages -> soundflow -> Cubase, you'll see the different functions available.
For instance, "Hide Track by Track Name" would equal the function you wrote, but like this:
sf.ui.cubase.tracksActByName({title: 'Hide Tracks with Name', presets: ['HideTracks'] });
The title is just a text.But try:
- use the build in function, maybe "Hide Track by Track Name". After calling it, you will get an error message (the thing that doesn't work).
-Then open the project logical editor and load a random script, close the editor, then call "Hide Track by Track Name" again with the same name input.
-This time it will work.
And to enable functionality of "select tracks with name containing", would be fairly simple I'd say. Not sure where it would be on the roadmap. But it's a functionality with huge potential.
Already the show/hide/show only etc is great.
- use the build in function, maybe "Hide Track by Track Name". After calling it, you will get an error message (the thing that doesn't work).
In reply tostevef⬆:Jesper Ankarfeldt @JesperA2018-07-29 03:50:59.497ZIf you want a script for "re-initialize" the Project Logical Editor, here's one:
sf.ui.cubase.appActivateMainWindow();
sf.ui.cubase.menuClick({ menuPath: ['Edit', 'Project Logical Editor...'] });
var projectLogicalEditorWIn = sf.ui.cubase.getWindowWithTitleStartingWith('Project Logical')
projectLogicalEditorWIn.mouseClickElement({ relativePosition: { x: 130, y: 30 } });
sf.keyboard.press({keys: 'Page Down,enter,cmd+w'});- In reply tostevef⬆:Christian Scheuer @chrscheuer2018-07-29 04:44:23.283Z
This will be possible in next release by doing:
sf.ui.cubase.tracksActByName({ containsName: 'Guitar', presets: ['SelectTracks'] });The other bug @JesperA mentioned should also be fixed (we're testing it now)
- SSteve @stevef
This now works, but I am left with menu items as per the attached picture. Is it possible to have SoundFlow delete these automatically after the command has finished? Or do I have to manually do that?
Thanks.
Christian Scheuer @chrscheuer2018-07-31 21:59:49.504ZKeeping them there will drastically improve performance, so it's by design that they stay. Just curious - why would you want to delete them?
- SSteve @stevef
It’s just that when I use the naming scripts I have the number of times I will, I am going to end up with hundreds of items aren’t I? I just think it starts to get messy with that many items.
It seems to create on every time i use it, or is that not right?
How does it improve performance to keep them?
- Christian Scheuer @chrscheuer2018-07-31 22:29:04.242Z
The improved performance comes from not having to make the PLE reload its inputs. It does take any significant time to generate the new file, but the PLE is so slow, it can take seconds to reload. While with a preset already present, there's no need to even open the PLE window, we can just activate the preset from the regular menu - which is invisible and fluent to the user.
In cases where you are working primarily with this type of function for the same tracks, it would drastically degrade performance to remove the files.
That being said, I can see why some workflows would benefit from deleting the files, but that should definitely be opt-in.
Do you wanna log an idea for this feature so we keep track?- SSteve @stevef
Ok, I understand. I will log something in the morning. But just to clarify; if I search for a tracks with ‘NAME 1’ in and it creates a preset, does it then use that same preset to search next time for NAME 1? If so, then it is maybe not so bad all the time.
- Christian Scheuer @chrscheuer2018-07-31 23:51:12.423Z
Yes exactly. I think it caches based on exact spelling, but case insensitive, if I remember correctly. (Mathing Cubase's algorithm, hopefully)
- SIn reply tostevef⬆:Steve @stevef
Thanks both. This will certainly be very useful!
- Christian Scheuer @chrscheuer2018-07-30 15:20:15.907Z
@stevef this should be possible now in Beta 3.10, please check it out:
https://forum.soundflow.org/-234/200-beta310- SSteve @stevef
Oooh, lovely, thanks!