Ę











Tips for Studio Vision Pro 4.5

Installation
Even if you are upgrading from a previous version we still recommend using the Easy Install package. The latest version of OMS, OMS 2.3.7, is included in the Studio Vision installer and we encourage all users to upgrade to it. The Easy Install package will install everything that you need in order to run Studio Vision Pro 4.5.

Icons
The application and file icons for Studio Vision have been changed for the 4.5 release. After installation you will most likely need to rebuild your desktop to see these new icons. To do this simply hold down the Option + Command keys as you restart your Mac. Continue holding the keys until you see a message asking if you want to rebuild the desktop of the particular hard drive. See your Macintosh documentation for more info on rebuilding the desktop.


Getting more from your Computer
When using real-time VST type effects it can be very easy to run low on available CPU power (check the Performance Window for current system status). There are several things you can do to free up some of the load:
-Disable unused inputs & outputs in the Audio Instruments Window.
-Bounce tracks that involve CPU intensive plug-ins. Reverb, for instance, can be quite heavy on the CPU. By using either the Mix-to-Disk or Bounce-to-Disk functions of Studio Vision you can print these tracks as audio files that contain the effects. You can then remove the plug-ins (in a console) to get some of your CPU power back.
-Turn off unused EQ bands. Turning on the EQ for an audio channel will enable all 4 bands of the EQ by default. If, after you have made your adjustments, you find that some bands are not being used (the Gain parameter is set to O) you should turn the particular band off. 

Plug-in Automation Parameter Names
As you start to use the new VST plug-in automation you will notice that some plug-ins provide the names of the parameters in the List Window, Strip Charts, etc. while others don't. The reason for this is that 'faceless' VST plug-ins (plug-ins that have a generic user interface such as the opPLUGS) can display their names while 'faced' VST plug-ins (plug-ins that have their own specific user interface such as the Fusion effects) can not.

Parameters for 'faced' VST plug-ins are given the simple name of 'Parameter' followed by the parameter number, ie. Parameter 50. If you're unsure of a particular parameter number simply record a small amount of automation data for that particular parameter. You can then edit this data using any of Vision's editing environments.

Switching Audio Systems or ASIO Drivers
Switching between audio systems or changing your ASIO driver will cause all EQ, plug-in & routing settings to be reset. The best idea is to make any changes before you open the desired song or to close your song file, make the changes then reopen the file. If you find that you need to switch ASIO drivers in the middle of working on a song please make sure to save before changing drivers.

Using Vision DSP with ReWire applications
When using Vision DSP with a ReWire compatible application sych as ReBirth you will need to allocate more RAM to Vision. Allocating 30-35megs of RAM to Vision should be sufficient. Please check the Vision DSP documentation for further information.

The Preferences File
If your computer crashes while Vision is running, we recommend that you throw away your Preferences file (found in System Folder>Preferences folder) before relaunching Studio Vision. This preference file can get corrupted during a crash, which may cause other problems. If you use a unique configuration of Vision DSP and would rather not spend time resetting your preferences after a crash, you should save a good copy of your Preferences file in case problems occur. If you need to replace it, simply drag it to your Preferences folder to replace what is there (or Option-drag to retain a copy).

Recording MIDI in Wait for Note mode into a sequence containing audio
Short MIDI events played at or near the beginning of a sequence may not be recorded correctly when audio is present.  Instead choose Countoff, or play longer MIDI events at the beginning of the sequence and edit them to the desired length after recording has stopped.

Lexicon Studio Users
When you first launch Studio Vision after installing the Lexicon software you may be presented with an warning message concerning the initialization of the PCM 90 plug-ins. The problem is simply that the Lexicon Core32 ASIO driver is not selected and therefore the hardware effects can not be initialized. After you have selected the Core32 driver in Audio>Hardware Setup quit Vision then relaunch. You should not see the initialization warning during this launch. However, the warning may return if you trash your Vision Preferences file.

QuickTime Musical Instruments
When enabled, the QuickTime Musical Instruments extension uses a substantial portion of your Mac's CPU time (even when no MIDI data is routed to it). This may cause performance errors when playing or recording digital audio.
If your Audio System menu item is set to something other than MIDI Only, we recommend that you disable QuickTime Musical Instruments in OMS: To do this:
1. Open your current OMS Studio Setup document.
2. Double click the "QuickTime Music" icon in your Studio Setup document.
3. In the resulting dialog box, click the Off radio button, then click OK.
4. A circle with a slash across it appears over the "QuickTime Music" icon indicating it is disabled.

1400 PowerBooks and Audio
During our testing we have found that there are performance issues playing audio tracks on 1400 PowerBooks when Studio Vision is set to the Acadia audio system. We have also had some reports from users that they are unable to see audio input levels in the Record Monitor Window on 1400cs PowerBooks.

What do I do if OMS canŐt find (auto-detect) my MIDI hardware?
Verify that your MIDI interface is connected to the MacŐs serial port and all of its buttons are configured correctly. MIDI interfaces and MIDI cards will not be recognized if their corresponding OMS drivers are removed from the OMS Folder (which resides in your System Folder). In order for a MIDI instrument to be detected by OMS, both of its MIDI ports must be connected to your MIDI interface (OUT to IN, and IN to OUT). Some older MIDI instruments, and even some very new ones, may not be recognized by the OMS auto-detection routines. 

DonŐt worry, however, if OMS canŐt detect some of your MIDI devices. You can manually enter Manufacturer and Model names for any ŇUndefined DevicesÓ in your Studio Setup. Simply select 'Other' for the manufacturer and/or model then type the information into the devices Name field in the OMS Device window.

How come I canŐt get MIDI to record or play?
One of the very best ways to trouble-shoot MIDI input and output is with ŇTest Studio,Ó which is enabled from the Studio menu in OMS Setup. With Test Studio active you can click on a device in your Studio Setup to test MIDI output, or play some notes on your controller to verify MIDI input. Consult your OMS Manual for more information on testing your Studio Setup.

What is Galaxy the Universal Librarian?
Galaxy, included with your Studio Vision package, allows you to store, retrieve, and organize the patches from your MIDI instruments. If your instrument is supported, Studio Vision can subscribe to a Galaxy bundle and then display those patches by nameĐand even group them by instrument type or bank.

Where can I go for help? 
The first place to look for assistance is in your Opcode documentation. For last minute changes, check the Read Me files in the Information folder on the CD. DonŐt forget about the online help available within most Opcode programs. In Studio Vision, use Command-Shift-Option to click on any field, button, icon or menu item for pop-up help on that item. OMS Setup incorporates Apple's Balloon Help; once enabled, simply point to any icon in your Studio Setup, or any menu item, for balloon help. Once you have exhausted these resources consult the Technical Support Information PDF document, included on the CD, on how best to contact Opcode.



