Good news. I wrote the Midi Devices part again to import Cubase Patch Scripts directly. What I’m doing is parsing the text and pulling out the Program Names, MSB & LSB and converting the latter two to a bank number ((MSB x 128) + LSB) and so far it’s working really well.
The only anomaly is that S1’s Program field doesn’t accept a “0”, it starts at 1, so I had to increment the program numbers by one just before sending them out to make them match up. Below, if you look in the list of programs, I’ve selected Program 8 (item 9) but I have to set “9” in S1 to get to program 8 on the hardware because S1’s index starts at 1.
Anyway, I went through a bunch of the Cubase scripts while visually checking the Program and Bank result with what it should be and so far it looks to be working as expected but (of course) it needs testing, but so far so good. The code is first draft so it probably will be improved, reduced.
I'm a new PSR SX900 owner, and a Cubase Pro 10.5 user. While browsing for patch scripts in Cubase, I noticed that the most recent model they added a patch script for is PSR S970. While Yamaha offers an official patch script for the Genos on their website (and it is also already included on Cubase), I don't see any for the PSR SX900. A patch is a simple way to apply a small change and is quicker and easier to release than a full new build. It is recommended to only install a patch if it is needed or you are experiencing an issue a patch is known to solve. Patches are typically added to the next released build so they are often obsolete when a new build is published.
Directory Changes:
1. Delete the current Studio One HelperPatch Banks directory and files, no longer used.
2. It will create a new directory named Devices instead, to hold the Cubase script files.
3. In that directory you’d just drop in all the script folders like below.
So once you copy the Cubase script files to the “Devices” folder they’ll load and work. The only thing I need to add to the file parsing is to directly ID them to know for sure that files people may place there later are actually Cubase script files. There’s an ID in the text I can use for that to not load incompatible files and avoid an error from that.
Cubase came with an Oberheim Matrix 1000 panel. No patch selection script inside the panel tho. I have made a Matrix-1000 patch script (numbered, plus some names) for quite some time, so I decided to merge the two. Recently I saw people attempting to make a similar panel but using SysEx as patch selection. Re: Cubase patch scripts for Origin. « Reply #2 on: June 03, 2013, 05:16:21 pm ». If I want to select a multi I send a bank select with the first 2 digits of the multi preset number followed by a program change with the second two digits of the preset number to the global channel of the Origin. If I want to select a program within a.
Patch Scripts Hardware Device panels for controlling your external Studio hardware within Cubase. Most 3rd party Keyboards, ( Korg - Roland - Yamaha etc) Boutique Sound Modules & Effects Rack Units with a nice software based interface via Midi Control.
Here’s the Beta 9 download: http://theaudiocave.com/helper/S1HBeta9.zip
All the patch script folder are in the zip also.
To Do: Investigate the possibilty of drag and drop from that new window, to drop a program directly into the midi editor to set a bank and program change there.
- 2Scripts
Patches
Occasionally untangle will fix a bug or add an enhancement and release it as a patch. A patch is a simple way to apply a small change and is quicker and easier to release than a full new build. It is recommended to only install a patch if it is needed or you are experiencing an issue a patch is known to solve. Patches are typically added to the next released build so they are often obsolete when a new build is published.
Scripts
Occasionally users may wish to accomplish a task that is not considered normal usage and that is not a feature available in the product. Below are some utilities and scripts that accomplish various tasks or tests that is not available in the administration interface.
16.2.2
15.0.0
