Have you noticed "Look Mom, No MIDI!" in Studio One Reference Manual? It was a major design decision: once MIDI events arrive to Studio One, it converts them into it's own internal format, and converts back to MIDI when sending out. I don't understand this decision at all. Better support for virtual instruments? As far as I know, Kontakt and anything else not PreSonus is still controlled by MIDI.
Anyway, there is no MIDI inside your songs in Studio One! That's why patch names are unsupported. Yes, unsupported -- I saw their suggestion how to add Program Change automation in your Instrument Tracks. It comes with a formula for MSB, LSB and Patch number: (100 / 128) x MSB. What they failed to see is that 128 is greater than 100, so you won't be able to select some banks and patches because of rounding errors.
Also, there are no Event Lists, for the same reason: there is simply no MIDI in your songs. Also, there is no SysEx support, and it won't be added, ever. So in Sonar I could auto-select the right song in my Kronos sequencer or load/save it's setup, and in Studio One it's not possible, and I have to turn to the instrument, enter Disk mode and load/save the Sequencer there.
PreSonus is not going to revert this design decision (which was hubris, IMHO) and rewrite Studio One. For one, it would require to add a converter for existing songs to switch to the new (old) MIDI format. So don't say "it should be easy to add this or that" - it's not.
Cubase Patchname Scripts are profitably used with Cubase sequencers to revoice MIDI-files. Then it is possible to select the patchnames (voicenames) of the specific models of keyboards or synthesizers instead of its bank- and voicenumbers (MSB, LSB, voice#).
Both filetypes include in different structures the same information. So it was easy to write a program, which converts Cakewalk instrument definitions into equivalent Cubase Patchname Scripts. The PatchnameConverter is specialized to work for XG synths and keyboards. A manual is not needed: Load an instrument definition, select the model, perform converting and save the script-file. An important information: In contrast to Cakewalk instrument definitions the scripts are divided in blocks of equal types of voices. The PatchnameConverter deduces the groups from intervals of voicenumbers. This is mostly correct for XG models. If the program is unable to associate a group the voice line is inserted into the special group "Other Voices". I recommend to examine for each generated script this group if there are voice lines that should be inserted into another group or if a new group is the better way. This is the reason that converted scripts for example for Yamaha Motif synthesizers must be extensively edited.
I have applied the PatchnameConverter with a lot of freeware Cakewalk instrument definitions that I found in the internet. The scripts should work with Cubase, but I can not guarantee the quality of the content.
Due to the fact that I do not use Cubase by myself, I cannot answer questions about the usage of scripts and about Cubase general. Werner Ogrodnik has published installation guidelines for several Cubase versions on his homepage STUDIO4ALL:
Patchname Script Installation Guideline
This 'unofficial' Forum is dedicated to the Clavia Nord Keyboards, including the Nord Stage, Nord Electro and Nord Piano. Discuss any issues around Nord's keyboards, share your favorite patches, samples, and music. We are not affiliated with Clavia!
1 Installing Cubase Patch Scripts A patch script, or patch list, is the bridge that integrates your external MIDI keyboards and sound modules with your sequencing software. Without this list, there is no way for the software to know which sounds reside in your gear. A patch script is basically a listing of all the sounds with their MIDI addresses programmed in the format that the software requires. As of yet, there are no universal formats for such listings. Each program requires a different type of format and as such, there is no real way to guarantee that an individual patch script will work in your specific setting. Patch scripts have been tested on several different versions and platforms of Cubase SX, but they are provided As Is and there is no guarantee that they will work with new or old releases of Cubase. Roland Corporation U.S. does not provide any additional support for setting up, installing or troubleshooting Cubase patch scripts beyond this document. Please refer to your software s documentation for more detailed use of patch scripts. Installing the patch script is a simple matter of copying it to the correct directory on your computer and then enabling it from Cubase s MIDI Device Manager. At this point you should already have the patch script file on your Desktop and ready to install. Let s Begin. (Macintosh users can skip this section) Windows Users: In order to gain access to the directory you need, you will need to enable the View Hidden Files option. 1. From the Start menu select Control Panel. 2. Select Appearance and Themes. 3. Select Folder Options.
2 4. In the View tab enable the Show hidden files and folders radio button. 5. Click OK 6. Close the Control Panel. Now that you can view hidden files, you are ready to copy the Cubase patch script to your user Cubase script folder. Follow these steps to navigate to the correct folder. 1. From the Start menu, open My Computer.
4 5. Open the Application Data folder. If you do not see the Application Data folder, then confirm that you have enabled Show hidden files and folders (see page 1 for these steps). 6. Open the Steinberg folder. 7. Open the Cubase folder for the current version of Cubase that you will be running. 8. Open the Scripts folder. 9. Open the Patchnames folder. 10. Open the inactive folder. 11. Copy the Cubase patch script file from your Desktop to the Roland folder here. Now that the file has been copied to the correct folder, your device will be available in Cubase s MIDI Device Manager. Skip to Setting Up Cubase for more information.
5 Macintosh Users: You will copy the Cubase patch script file to one of two locations depending on the version of Cubase you will be running. 1. Open (double-click) your hard drive and navigate to your User/Library. 2. For Cubase SX 2 and Cubase SX 3, navigate to Preferences/Cubase SX 23/Scripts/ Patchnames/inactive/roland.
6 For other versions of Cubase, navigate to Application Support/Steinberg/Cubase version/ Scripts/Patchnames/inactive/roland. 3. Copy your Cubase patch script file to the roland folder. Now that the file has been copied to the correct folder, your device will be available in Cubase s MIDI Device Manager. Skip to Setting Up Cubase for more information. Setting Up Cubase: 1. Start Cubase. 2. Select MIDI Device Manager from the Devices drop-down menu.
9 3. With your device selected as the Out: port, you can now select your patches by name from the Programs drop down menu. You are now ready to use the Cubase patch script in your music production. For more information about patch scripts or Cubase, please refer to the Cubase documentation Roland Corporation U.S.
The bank's patch names and all associated Properties are written to a .csv file for import into a database or spreadsheet. This includes: comment, all eight tags, author, copyright, song, musician, band, and long name. When this option is selected, a file selector is displayed. Enter the name for the file and press save.
However, I can only select the General MIDI Patches (or, patches 1-128 if you will). I know I can used the Bank Sel MSB/LSB numbers to get to all the other banks, but it would be so much easier to click "Strobot" when the Fantom is the selected output, and have it go right to that patch.
In Cubase, some "Patch Scripts" came with, and others I downloaded from the internet. I even had to make one for an old TX 802 (that took a lot of time, which I don't have now, especially since these 2 synths have 1000s of patches instead of just 256!).
I need a step-by-step on how to import one of these files into the environment so when I look at the inspector, and click the patch name, I see all the patches for each synth (one at a time of course).
I can double click them and see the different patch sets (for example, there's one for regular patches, and then one for the rhythm sets, etc.) where I can see all the correct names. But clicking them there doesn't select the patch, and they don't show up in the inspector.
I did try this: I've imported the file and copied and pasted both the patch names and the custom bank messages into my existing MIDI Instrument (labelled Fantom XR because that's what it is in Apple's Audio/MIDI setup).
Under "Channel Settings", check Channel parameters.
Leave the other unchecked.
(Even though you're planning to build a panel later, but we're gonna be copying the patchnames first, any extra parameters added would confuse the copying stage, so it's better not to check any of these here, but add them later after all the patchnames/banks are copied).
(Well, basically, follow the image!!) Clicking on OK will bring you to the Device page. Again we need to go to the Patch Banks page. In the Patch Banks editor, it should default to an Empty Bank, no sub folders, no presets. Click the Enable Edit Button. Rename the 'Empty Bank' to the same name as the other device.
(In this case, "Micro Q"). Since in this particular example, the previous device has 3 sub-folder banks, for convenient sake, I usually add a similar structure (but just one sub folder instead of 3). Either using the Commands drop down or right-click on the root bank and select New Folder.Rename this to the same as in the previous device. Next, close the editor, and then EXPORT the device by pressing the Export Device button in the Midi Device Manager. Now you should have 2 XML files. One with all the Patch Names but no identical channel settings, one with proper settings but no patchnames defined.
d0d94e66b7