Sonar Name Server Preferences (Options Menu)
This page defines Midi Quest's SONAR name server.
Midi Quest Pro only
Name Servers allow Midi Quest to keep your sequencer's name lists in sync with your equipment automatically.
How does this work? For Cakewalk and Sonar, Midi Quest automatically updates the MASTER.INS file that these sequencers use to store Banks of Patch names. Each time a bank is sent to an instrument, Midi Quest automatically updates the file so that it contains the same information as is currently in the synthesizer.
Cakewalk/Sonar Limitations: All versions of Cakewalk and most versions of Sonar (except the most recent) only read the MASTER.INS when the program is started. If you send SysEx to an instrument while either of these sequencers is running, you will need to shut down and restart the sequencer to update the names.
The most recent release of Sonar does allow you to reload the Master.INS file
Configuring and Using the Cakewalk/Sonar Name Server
To configure the Name Server,
| 1. | check "Enable Sonar/Cakewalk Name Server" |
| 2. | Press the "Add..." button and a file selector will appear |
| 3. | Use the file selector to find your Sonar folder |
| 4. | Select the MASTER.INS file and press the OK button |
| 5. | If you have multiple Cakewalk or Sonar installations on your computer, repeat steps 2 through 4 for each installation (maximum 10) |
That's all you have to do. Below is a configuration for Sonar 1 and Sonar 2 on a Windows 7 based computer
Once you have the server configured, you should send Sets from Midi Quest to each instrument to initialize the MASTER.INS file.
Run Sonar and choose Options/Instruments... from the menus for display the dialog above. For each instrument Set sent to an instrument you should see the name of the instrument followed by "SQ" (eg Korg 01/W (SQ)". The "(SQ)" indicates that the information was automatically generated by Midi Quest.
Next, link each instrument to the appropriate MIDI port/channel combination listed on the left of the dialog. For example, the 01/W uses MIDI channel 1 on the SB Live MIDI interface. This is your basic setup. As long as you use this with each of your songs you will be able to list and correctly access the sounds in your instrument by name.
In the Sonar Tracks window, to to a MIDI track and select the SB Live (or whichever MIDI port you assigned your instrument to) MIDI interface.
Click on "Ch" (for channel) and the drop down menu will list your instrument, in this case the Korg 01/W. Select it
Finally, if you click on "Pch" to select a patch you will find all of your Korg 01 Patches listed by name.
Remember, the next time you send a bank to your instrument. Midi Quest will automatically update the MASTER.INS file. If you look at the list of patches in the future it may be completely different based on the contents of your instrument.
Configuring and Using the Cubase Name Server
To configure the Cubase Name Server for Cubase versions prior to Cubase SX:
| 1. | check "Enable Cubase Name Server" |
| 2. | Press the "Add..." button and a folder selector will appear |
| 3. | Use the folder selector to find your Cubase installation |
| 4. | Within this installation should be a "Scripts" folder and inside that folder is a "patchnames" folder |
| 5. | Select either the "patchnames" folder itself or any sub folder of this folder |
| 6. | This is where the automatically generated script files will be stored |
| 7. | If you have multiple Cubase installations on your computer, repeat steps 2 through 6 for each installation (maximum 10) |
To configure the Cubase Name Server for Cubase SX versions prior to Cubase SX 1.05:
If you haven't done so already, note that Windows ships with Explorer configured so that the Application Data folder is not displayed. In order to display it, you must:
| 1. | in Explorer choose Tools/Folder Options from the menus |
| 2. | click on the view tab |
| 3. | find "Hidden files and folder" and set it to "Show hidden files and folders" |
| 4. | apply this option to all folders so that the "Save As" dialog will show the folder |
Next follow these steps to save in the early versions of Cubase SX:
| 1. | check "Enable Cubase Name Server" |
| 2. | Press the "Add..." button and a folder selector will appear |
| 3. | Find the following path: |
| 4. | Cubase SX: <Documents and Settings>/<username>/Application Data/Cubase SX/Scripts/Patchnames |
| 5. | Cubase SX 2: <Documents and Settings>/<username>/Application Data/Cubase SX 2/Scripts/Patchnames |
| 6. | Cubase SX 3: <Documents and Settings>/<username>/Application Data/Cubase SX 3/Scripts/Patchnames |
| 7. | Select either the "patchnames" folder itself or any sub folder of this folder and press the Ok button |
| 8. | This is where the automatically generated script files will be stored |
| 9. | If you have multiple Cubase installations on your computer, repeat steps 2 through 8 for each installation (maximum 10) |
To configure the Cubase Name Server for Cubase SX 1.05 and higher:
If you haven't done so already, note that Windows ships with Explorer configured so that the Application Data folder is not displayed. In order to display it, you must:
| 1. | in Explorer choose Tools/Folder Options from the menus |
| 2. | click on the view tab |
| 3. | find "Hidden files and folder" and set it to "Show hidden files and folders" |
| 4. | apply this option to all folders so that the "Save As" dialog will show the folder |
Next follow these steps:
| 1. | check "Enable Cubase Name Server" |
| 2. | Press the "Add..." button and a folder selector will appear |
| 3. | Click the Start button and go to your Cubase installation and select the "Cubase Application Data Folder" to open and display the data folder |
| 4. | Return to the folder selector and use it to find the same folder as displayed by the "Cubase Application Data Folder" |
| 5. | Select either the "patchnames" folder itself or any sub folder of this folder and press the Ok button |
| 6. | This is where Midi Quest's automatically generated script files will be stored |
| 7. | If you have multiple Cubase installations on your computer, repeat steps 2 through 6 for each installation (maximum 10) |
That's all you have to do. Below is a configuration for Cubase.
Once you have the server configured, you should send Sets from Midi Quest to each instrument to initialize the script files.
Available in:
Midi Quest Pro |
|
Midi Quest |
|
Midi Quest Essentials |
|
Midi Quest one |
|
