Hello, I finally managed to create my 20 pages of 220 buttons in Cubase 15 using my touchscreen.
Is it possible to quickly copy certain functions across multiple pages at once, such as start/stop, loop recording, etc., which are recurring functions?
Hello, I finally managed to create my 20 pages of 220 buttons in Cubase 15 using my touchscreen.
Is it possible to quickly copy certain functions across multiple pages at once, such as start/stop, loop recording, etc., which are recurring functions?
Hello, yes, that’s what I did, and I created 20 pages in total.
But I haven’t yet created the global buttons for redundant functions like stop loop recording, etc.
Does this mean I have to delete the 19 pages I duplicated and first create the common buttons on the first page?
Exactly.
Note the difference: There is ONE MIDI Remote Surface, and multiple Mapping Pages.
I can’t put them in afterwards
Because I’ve already assigned all my page change buttons, I’ll have to start over.
Yes.
Honestly, watching the screenshots of your complex PLE setup, I really think you should turn into scripting. First of all, creating the remote surface using scripting is pretty simple, simpler than MIDI learning huge number of messages. Secondly, you can then try to parse your very own commands from your previous setup to a text file (if it’s a Generic Remote xml should be close to trivial), and I or others can even help to build the whole remote using this text file.
Hello and thank you for your feedback, but I wasn’t the one who created the original plugin; it was Karol Obara from 14bitMIDI. The difficulty is that there are, of course, nine XML files, but they only serve as a map for implementation in Sherlock. The entire configuration is saved as a VST preset, hence the difficulty in extracting it.
It captures the 9 XML files and the menu integrated into the plugin to choose the functions, a sort of new MIDI remote in the old Generic remote.
So, the Sherlock plugin by 14bitMIDI, developed by Karol Obara, is absolutely extraordinary and allowed me to discover Cubase in depth, as I only started using it in 2019. Its only drawback is that it’s still based on the old generic remote. He was preparing a version 2, but I think he abandoned it. Furthermore, if I remember correctly, the integrated functions only include those from Cubase 10 and/or 11.
So, all the updates up to Cubase 15 aren’t included.
Also, it sometimes has startup bugs, and I have to close and reopen Cubase.
But the real reason I’m switching to the new MIDI remote is to eliminate limitations on my macros, especially my PLEs, which I use extensively for track visibility.
They’re all named: PLE #001 through PLE #512 and Macro #001 through Macro #512. I initially had 256, and Karol was kind enough to add the remaining 256 for me back then.
I still have plenty of room for improvement with macros, but I’m reaching my limit with PLEs.
Why so many PLUs simply to have access to all my tracks in Cubase which are all deactivated in my Orchestral Template model and which number in the thousands.
I don’t want a remote VEP on another computer, which for me is a complex and potentially problematic system.
With this system I have access to all my instruments, my articulations and/or my instrument families, my keyswitches in a snap.