We STRONGLY recommend that you read this document in its entirety before installing your Lexicon Studio Core2. The first section below helps you insure that your Core2 is installed properly and is configured for optimal performance. This if followed by general and audio application-specific notes. 1. Installation 2. V2.12 Core2 General Notes 3. V2.12 MP100 General Notes 4. Cakewalk 5. Cool Edit Pro 6. Cubase 7. Logic Audio 8. Samplitude 9. Sound Forge 10. Vegas Pro 11. Wave Lab 1. Installation Before you install this Version V2.12 of the Lexicon Control Software, visit the Lexicon Studio download area at our web site, http://www.lexicon.com/downloads/studio_download.htm to insure that you are installing the most updated version of this product. (All driver updates are Free of Charge). We continue to enhance Core2 with new features and fix problems that arise with updates for most audio software applications and highly recommend you install our latest drivers. Also, be sure to check the Lexicon Studio areas of our Support Knowledge Base in the Support area of the web site - www.lexicon.com. http://www.lexicon.com/kbase/kbase.asp The Support Knowledge Base is reviewed and updated on a regular basis. Please follow the Installation Instructions included inside the Core2 box for proper installation of the Core2 PCI card and software drivers. If you are adding an MP100 on an existing Core2, use the CD that came with your MP100. The correct CD is labelled V2.12. If you are doing a Core2 upgrade (including adding an MP100) and your application software is Cubase or Wavelab, the Core2 installer will delete your plugins. You should follow these additional steps: 1) Copy your entire Plugins folder (probably in ..\Programs\Steinberg\CubaseVST24\VST Plugins) to the desktop, 2) Install Core2 V2.12, following the directions, 3) Copy the Plugins folder from the Desktop to its original location. When working with your Core2 and MP100 card or other cards in your computer, be sure to use the anti-static wrist strap included with your Core2 and follow all anti-static precautions noted in your Owner's Manual or Installation instructions. We highly recommend that you familiarize yourself with your computer. Identify the other cards in your system and make a list of them and the slot numbers that they occupy. If you know that you have Legacy cards (non-Plug & Play devices) installed and you know what IRQs they are using, include this on your list. Also, be sure to install your Audio application software prior to installing the Lexicon Studio Core2 drivers. ***************************************************************************** Lexicon Studio Core2 Installation Tips & Troubleshooting (Go through these steps immediately after you have installed the Core2 drivers and BEFORE you attempt to launch the Lexicon Control Panel or your audio application.) NOTE: This file is available as a text file in your V2.12 CD-ROM root directory as "Lexicon Studio Installation Core2 V2_11.txt". You can print this file to get a hardcopy of it. Athlon-based Computers - Not supported by Core2 At this time there remain unresolved issues with Core2 and Athlon-based computers. You should not install a Core2 in an Athlon-based computer. Windows - Unique IRQ for the Lexicon Core2 card Make sure that your Lexicon Core2 card is not sharing an IRQ with anything other than "IRQ Holder for PCI Steering". To check for IRQ sharing, go to the Start menu and select Settings/Control Panel. Double click the System Icon to open the System control panel. The System Properties dialog box will open. Click on the "Device Manager" tab and double click on "Computer". (Make sure that the "Interrupt Request (IRQ)" radio button is selected). Look for "Lexicon IDS Sound System" in the list of hardware devices. Check the IRQ setting to the left of the device listed (Lexicon IDS Sound System) and take note of the IRQ number. Check to see if there is any other device using that IRQ (it is okay for it to share with "IRQ Holder for PCI Steering"). If Lexicon IDS Sound System is sharing with anything else, Shut Down your PC and try physically moving the card to another PCI slot. Reboot and check the IRQ again. If your computer has no free IRQ's available, try disabling the device Core2 is sharing with. If you are unable to get Lexicon onto its own IRQ, give Lexicon Customer Service Tech Support a call at 781-280-0300 or email: csupport@lexicon.com. Windows - Legacy Device IRQ Conflicts The Device Manager tab of the System Control Panel usually just shows resources in use by Plug & Play devices. Legacy devices (non-Windows Plug & Play) that are installed in your computer will not display the resources that they are using. If it appears that you are experiencing an IRQ conflict and the Device Manager does not indicate a conflict, it may be caused by a Legacy device attempting to use the same IRQ that the Core2 card is using. You should reserve the IRQ needed for your Legacy device in Windows so that the Core2 (or other Plug & Play device) does not attempt to configure itself to use the same IRQ. To do this, go to the Start menu/Settings/Control Panel. Double click the "System" Icon. The System Properties dialog box will open. Click on the "Device Manager" tab and double click on "Computer". The Computer Properties dialog box will open. Click on the "Reserve Resources" tab. Make sure that the "Interrupt Request (IRQ)" radio button is selected. Click on the "Add..." button and enter the IRQ that your Legacy hardware device is using. This will reserve the IRQ for use only by that device and force Windows to assign a different IRQ to the Core2 card. Random System Crashes - Video Acceleration Some video cards use a great deal of your computer's CPU and PCI bandwidth. If you are experiencing random crashes, pops or clicks, try turning the video acceleration on the graphics card down to none. To check the graphics hardware acceleration, go to the Start menu and select Settings/Control Panel. Double click the "System" Icon to open the System control panel. The System Properties dialog box will open. Click on the "Performance" tab. Then click on the "Graphics..." button. If the Graphics Hardware acceleration is set to Full or any setting above None, try a lower setting by sliding the control closer to None. If you make a change to this setting, follow the instructions that will appear upon closing this dialog and restart your computer. You can also try switching your monitor to a lower resolution or mode (switch to VGA mode). We recommend the use of AGP video cards. Be sure to check the Support Knowledge Base on our web site - www.lexicon.com. http://www.lexicon.com/kbase/kbase.asp Select the Lexicon Studio/Lexicon Studio Computer Platforms section for any updated information. Pops and Clicks - Windows Configuration Issues 1. Turn Read Ahead optimization to None. To do this, go to the Start menu and select Settings/Control Panel. Double click the "System" Icon to open the System control panel. The System Properties dialog box will open. Click on the "Performance" tab and click on the "File System..." button. The File System Properties dialog box will open. Click on the "Hard Disk" tab and set "Read- ahead optimization:" to None. Also set the "Typical Role of this computer" to "Network server". 2. Disable write-behind caching. To do this, follow step 1 above, but select the "Troubleshooting" tab. Now check the "Disable write-behind caching for all drives" box (put a check mark beside it). 3. Use a separate hard drive for audio. (Do not partition drives for audio.) Defragment all hard drives regularly. 4. Run scan disk or other utility regularly. 5. Disable screen savers and background applications that aren't needed for audio. Disable virus protection software while using an audio application (re- enable it whenever you are downloading files from the internet, receiving email, or inserting disks into your machine). ***************************************************************************** RELEASE NOTES V2.12 |------------------------------------------------------------------------------------------------------| Manual Notes - Page 2 suggests that MP-100 is compatible with Opcode Vision DSP. This is not true since the current release is only for Windows. - Page 13 references the PC90. The reference should be to the MP-100. |------------------------------------------------------------------------------------------------------| 2. V2.12 Core2 General Notes ************************************ - MP100 tab without MP100 card Note: If V2.12 is a software upgrade for your Core2 and you don't have the MP100 option card, the MP100 tab will appear in your LexPanel. It doesn't do anything. If you route through the MP100, audio will disappear (since it's being routed to and from empty connectors). If you ignore the MP100 tab, your V2.12 will operate normally. - MMIO Applications Issue: After an upgrade installation of V2.12 Core2 software, immediately launching an MMIO application or running an application's MMIO device setup, may cause the system to post the following VxD error: "Page Free in Bad Close Output Channel" Solution: Enable the last four analog outputs in the Core2 LexPanel before running any MMIO application the first time. Remember to re-boot your computer any time you re-route MMIO audio. Issue: In Cool Edit or Acid, if you open the application w/ punch disabled, then press play in the application with the lexpanel open, you will get an error - "cannot find specified playback devices" Solution: Be sure that punch is on before opening the application, and keep it on in the application - if you get the error, you can make it work by turning on punch again, but this is not reliable. It is best to cold boot your computer. - Audio lost when opening LexPanel Issue: If LexPanel is opened while playing, audio may be lost. Solution: Make sure the "Play in background" option is checked in your application preferences. - Help Function in LexPanel Issue: The LexPanel doesn't support Help. - Using ADAT Lightpipe (TOSLINK) Outputs in All Applications: Issue: I hear a click/pop at the TOSLINK outputs whenever I launch the Lexicon Control Panel from the Windows Task Bar. (This is the same issue as above). Solution: 1. Turn the faders down on your console/device. 2. Double-click/launch the Lexicon Control Panel (LexPanel) from the Windows Task Bar. 3. Bring up your faders and switch to your audio application using the mouse or ALT+Tab, keeping the LexPanel open in the background. Note: We suggest enabling 'Play Audio In Background' in your audio app. so that you will continue to hear playback audio when switching to the Lex. Control Panel. - Low Latency Option Note: The Low Latency checkbox option is designed for ASIO drivers only (Cubase VST & Logic Audio ASIO). Please leave this unchecked when using MMIO applications (Cool Edit Pro, Cakewalk Pro, Vegas Pro, Sound Forge, Samplitude, etc.). - Graphic Painting Issue: When the LexPanel is brought into and out of focus, the repainting is sometimes incomplete. This may also be a problem after closing clock source notifications. Solution: Close and re-launch the LexPanel. - Config Message Box Disappears Issue: When changing the Core2 config, the "Apply Changes" message box disappears very rapidly. This is only an informational message and no user options are lost. - Clock Restoration Time Issue: In some circumstances, Core2 may take some time to re-acquire lost or rapidly switched clock sources. Solution: Close and re-launch the LexPanel or enable Clock Source and Sample Rate notifications. This is a check box in the System Tab. - Display of ADAT BRC Clock Rates Note: If you change the sample rate using the ADAT BRC, the LexPanel will not display the change until the panel has been closed and re-opened. - Sample Rate changes Issue: Distortion may occur after switching from 44.1 kHz to 48 kHz. Solution: Some applications open all available streams. If you get distortion after changing from 44.1 to 48 kHz, you may need to reduce the number of channels in the Core2 config tab. 3. V2.12 MP100 General Notes ************************************* - Aux Sends and Returns w/ MP100 in stand-alone Issue: When trying to use the MP-100 as a stand-alone effects processor, the audio is muted when I enable the Aux Send & Returns in the LexPanel Punch tab. Note: The Aux Send and Aux Return are not physical connections; Therefore, when using the MP-100 like an outboard effects processor (i.e. you are not using an audio host applications), you must use "Cascade with Input" routing as illustrated on Page 13 of the User Guide. - Aux Send routing not available w/ 2-channel applications Issue: Aux Send Sum routing does not work with 2-channel applications, i.e. Sound Forge and WaveLab. This routing is designed for multi-channel applications. - Reverb Configuration can cause Feedback Issue: If Punch I/O is set up for Input Cascade and the same source is selected for both MP100 inputs, feedback may result. Solution: Always use a stereo input or only input to one channel of the MP100 - Setting Reverb While Playing Issue: If you attempt to change the reverb routing while audio is playing, the audio may disappear. It then reappears when you stop and then play the song. Solution: Stop the transport and then press Play. We recommend stopping audio when re-routing the inputs & outputs to the MP-100. - Flange Phase Parameter Issue: The manual states that the Light Flange and Deep Flange have 4 Phase values (0, 90, 180, 270 degrees). The display shows a sweep from 0 to 359. Audibly, only there are only the four described values. You should use 0, 90, 180 or 270 as your setting. - Windows amovie.ocx Playback Issue: When a .wav file is previewed using amovie.ocx, audio will not be properly reproduced. Solution: Please select a different default application for playing .wav files (for example, Cool Edit Pro SE which is located on your Core2 CD). - Launching Application changes Reverb Note: If you first work with the Reverb in the LexPanel and then launch the application, the MP100 will be re-initialized. This loads the default program, which is probably different from the one you were working with. |------------------------------------------------------------------------------------------------------| 4. Cakewalk Pro Audio 9 (Cakewalk) - Cakewalk Crashes Issue: Everything was working fine with Pro Audio 8, but Pro Audio 9 consistently crashes when I press Play or Stop. Solution: 1. In Cakewalk Pro Audio 9, Select the "Options" menu, then "Audio..." 2. Click on the "Advanced" tab. 3. Disable the WavePipe (TM) Acceleration checkbox by de-selecting it. - Punch Monitoring & Cakewalk Note: When doing punch record, we recommend that you monitor punch only on channels 1&2. Once recording is complete you can playback on any channels. |------------------------------------------------------------------------------------------------------| 5. Cool Edit Pro (Syntrillium) - Can't Find Playback/Record Device Issue: When I try Play or Record, Cool Edit Pro gives me the following Error message: "Cannot open specified wave device(s) for Playback". Note: You have selected different Playback Devices which are assigned to the same Core2 outputs. Solution: 1. Look at the Playback Device assignment for each track (the small box to the right of the Panning control) and be sure they all have the same number. 2. If they do have different numbers assigned, be sure that they are not duplicated in the "Preferred Multitrack Devices" (select the "Option" menu, then "Device Preferences"). |------------------------------------------------------------------------------------------------------| 6. Cubase VST & Cubase VST/24 (Steinberg) - Missing Output Buses Issue: I can only see one output bus in Cubase's Master Mixer. Note: This is not a bug but the way VST handles Master Buses when there are less than 3 stereo buses. You simply need to enable more output channels. Solution: 1. In Cubase VST, select the "Audio" menu and then select "System..." 2. Click on the "ASIO Control Panel" button to launch the LexPanel. 3. Select the "Core2" tab and enable Outputs 5-8 (or ADAT Out or SPDIF out). 4. Click Apply; Then Click OK 5. Exit/Quit Cubase VST 6. Re-launch Cubase VST - Loading MP-100 Programs within the Rack Expander Panel Issue: The MP-100 Programs don't load properly from VST's rack expander. Solution: After selecting the MP-100 plugin, press Edit and load all effect programs from the pull-down menus in the Lexicon MP-100 panel. - Saving MP-100 Programs Note: Hitting Cubase "save bank" or "save song", causes Cubase to cycle through all the presets, which may take 3-4 seconds. Suggestion: Use "save bank" or "save effect" to store your edits and name the entire bank of programs. Recall this bank using "load bank" or "load effect" and the name you gave it. Both save & load bank commands cause the MP-100 to cycle through your presets. Loading a bank typically takes more time than saving a bank. - User Presets not in VST Effects Panel Issue: The 240 Factory Programs are displayed in the VST Effects Panel at once Suggestion: We recommend using "load bank" and "save bank" as described above to load and save user programs. - MP100 automation startup Issue: MP100 automation does not start with the first bank, but rather with the first change. Solution: Use a pre-roll to set up your first bank as a change. - Aux Send/Return Routing in Cubase VST (Instructions) Issue: In the channel settings, the MP-100 appears in the pop-up list as a routing selection under Cubase Aux sends, but appears to do nothing to the audio. Solution: Cubase VST sees your MP-100 like all other plugins, which it is not (it is a hardware plugin) and therefore assigns the label "MP100" to the list in the Aux Send assignments. Do not select MP100 from the list. 1) Be sure that Aux Send & Aux Return buttons are active in the Core2 Tab of the Lexicon control panel 2) In VST, go to the Audio menu and select Master. 3) Look across the lower portion of the Master window (you may need to open up this window) and locate "Aux Send L". 4) Verify that this bus is Active (the green LED will be lit). 5) Click on the Bus # (in yellow letters) and rename the Aux Send bus "MP-100". 6) From the Audio menu, select Effects. Assign the MP-100 to a rack expander module. 7) Now, from the mixer, press the FX button on the channel you want to route into the MP-100. 8) In the pop-up list under the Aux send button, you will see MP-100 L & MP-100 R. Use these sends (not the MP100 send at the top of the list). - How to add MP100 effects in real time (with zero latency) in Cubase: Use Send Sum routing method: 1) Be sure that Aux Send & Aux Return buttons are active in the Core2 Tab of the Lexicon control panel 2) In VST, go to the Audio menu and select Master. 3) Look across the lower portion of the Master window (you may need to open up this window) and locate "Aux Send L". 4) Verify that this bus is Active (the green LED will be lit). 5) Click on the Bus # (in yellow letters) and rename the Aux Send bus "MP-100". 6) From the Audio menu, select Effects. Assign the MP-100 to a rack expander module. 7) Now, from the mixer, press the FX button on the channel you want to route into the MP-100. 8) In the pop-up list under the Aux send button, you will see MP-100 L & MP-100 R. Use these sends (not the MP100 send at the top of the list). 9) Launch the Lexicon Control Panel 10) In the MP100 tab, set the Sources to Aux Send L (ASIO) and Aux Send R (ASIO) 11) In the MP100 tab, set the Destinations to the desired Core2 output pair (for example, selecting D/A 1 and D/A 2 will send the output of the MP100 to Analog outputs 1 and 2 of the Core2) Note: You can record the output of the MP100 back into Cubase using the routing described above. To do this: 12) Follow steps 1-11 above 13) In Cubase, go to the Audio menu and select Inputs 14) Activate the Aux Return and note the corresponding VST Label (e.g. - it may be called In 3L and In 3R) 15) In the Audio menu select Monitor 16) On two unused tracks in mixer, set the inputs to the Aux Return (remember that this will be the VST label noted in step 14) 17) Arm these two tracks for recording and put Cubase into record 18) This will record the output of the MP100 onto these two tracks. Assign the channel directly to the Send bus: 1) Follow steps 1-5 above 2) On the channel that you want to send to the MP100, click on the output bus assignment button at the bottom of the channel strip. 3) Set it to the Aux Send bus that you activated in step 4 above. 4) Continue by following the instructions on page 2 of the MP100 User Guide PDF starting from step number 6 (this can be found in C:\Lxstudio\Docs) Use Punch and Global Disable 1) Follow the instructions on page 2 of the MP100 User Guide PDF (this can be found in C:\Lxstudio\Docs) 2) In Cubase, go to the Audio menu and select System 3) Set the monitoring type to "Global Disable" 4) Launch the Lexicon Control Panel and go to the Punch tab 5) Select the Aux Return L and R as the sources to punch 6) Select an output pair as the destinations of punch (e.g.: choosing D/A 1 and D/A 2 as the destinations of Punch will allow you to hear the MP100 from Analog outputs 1 and 2 of the Core2 Note: You will be monitoring the MP100 in mono if you use this method. - Sizing the MP-100 Panel Issue: I can not "stretch" the MP-100 panel in the Cubase Rack Expander Panel Note: Cubase VST does not allow rack expansion modules to be sized. - Unexpected SPDIF outputs Issue: When using Cubase with SPDIF routing inactive (i.e. it is grayed-out), Core2 will unexpectedly pass audio through SPDIF outs. Note: We are unclear as to why VST activates these output channels. Since SPDIF is inactive, we hope you will consider this an added feature until it is addressed in a future release. - Multiple MP-100 Instantiations (visible panels) Issue: In Cubase, I can open up to 8 separate control panels of the MP-100 controller, even though there is only one MP-100 daughterboard. Note: Although VST allows you to do this, we recommend that you to open only one MP-100 panel. Opening multiple panels is both unnecessary and uses extra CPU resources which will decrease the responsiveness of your computer. - MP-100 Tape-Type Monitoring Latency Issue: When using Aux sends/returns in the Tape-Type Monitoring mode (under the Audio/System menu), a considerable latency (delay) shows up in the monitors. The latency is not present in the recorded tracks. Solution: Since the Core2 has real-time monitoring without any latency (this is what Punch mode is all about), we suggest setting Monitoring to Global Disable and monitoring with the Punch mode. 1. In VST, go to the Audio menu and select System 2. In Monitoring, Select "Global Disable" 3. Click to open the Core2 "ASIO Control Panel" and select the Punch Tab 4. Check "Enable Punch" and highlight your desired inputs (A/D) and outputs (D/A) OR 1. Select low-latency option in the LexPanel - ADAT Clock Warnings Issue: With TOSLINK (ADAT) inputs activated, enabling Aux return inputs will cause Core2 to post a clock source warning message that pertains to TOSLINK ins. This happens in ASIO, using an internal clock. Solution 1: The warning message has a check box that can suppress future displays of the warning. - Editing with Arrow Keys Issue: I am trying to use the up, down, left and right keyboard keys and the keypad to edit the MP-100. Note: Like most VST plugins, keyboard commands are not supported. Please use the Adjust knob, inc and dec keys with your mouse. |------------------------------------------------------------------------------------------------------| 7. Logic Audio (Emagic) - Logic Audio 4.1.1 limitations Issue: At this time Logic 4.1.1 does not work properly in ASIO or VST Plugin modes. Recommendation: We strongly recommend using Logic 4.1.1 in MMIO mode only. In addition, we recommend saving a named device setup in MMIO mode, using the device setup program. This will prevent Logic from being "confused" about whether it has been started in MMIO or ASIO mode. Remember to re-boot your computer after any configuration change in MMIO. - Track limitations on record Issue: Logic 4.1.1 can record only 8 tracks at a time. The track total can be higher, but you can only record 8 tracks. - Sample Rate changes Issue: Distortion may occur after switching from 44.1 kHz to 48 kHz. Solution: Logic Audio opens all available streams. If you get distortion after changing from 44.1 to 48 kHz, you may need to reduce the number of channels in the Core2 config tab, or use Logic Audio Device Setup to select groups of channels to use. - Lost Mouse Issue: Sometimes at application startup, the mouse doesn't work to answer the startup dialog. Solution: Hit "Enter" on the keyboard and Logic will return control to the mouse. - Logic Audio has a number of issues that you should be aware of that are not Core2 related: A. In some earlier versions, Logic Audio did not support audio files at 48KHz sampling rate. B. Ignoring pop-up message windows in Logic can easily cause crashes. C. Scrolling quickly through windows in Logic can interrupt audio and cause performance problems. |------------------------------------------------------------------------------------------------------| 8. Samplitude - Re-launching Same Sound File Issue: When I play a sound file in Samplitude, Exit, re-launch and play that same file, I hear a "machine-gun" sound the first time I try to play. Solution 1: Before leaving Samplitude, close all output devices, by going to the "Special" pull down menu and selecting "Close Audio Devices." Solution 2: Simply Stop and then restart Play. |------------------------------------------------------------------------------------------------------| 9. Sound Forge (Sonic Foundry) - Volume Control in Mixer Issue: The volume control in the Sound Forge Mixer doesn't work. Note: With most "host-based" applications, the mixing functions are done by the Intel or main CPU. Core2 itself does not appear as a "Windows Mixer Device"; Therefore, this volume control is not operable. |------------------------------------------------------------------------------------------------------| 10. Vegas Pro (Sonic Foundry) - Output Bus Offsets Issue: The following actions will cause offset between the output busses: soloing tracks, launching LexPanel, re-sizing workspace. Solution: Check and/or increase the buffer size in Audio Preferences. |------------------------------------------------------------------------------------------------------| 11. Wave Lab (Steinberg) - Volume Control in Mixer Issue: The volume control in the Wave Lab Mixer doesn't work. Note: With most "host-based" applications, the mixing functions are done by the Intel or main CPU. Core2 itself does not appear as a "Windows Mixer Device"; Therefore, this volume control is not operable. - MP-100 presets missing Issue: Wave Lab does not support the full complement of MP-100 presets on the presets page. Suggestion: Use "save bank" or "save effect" to select presets form the MP-100 panel and to store your edits and name the entire bank of programs. Recall this bank using "load bank" or "load effect" and the name you gave it. Both save & load bank commands cause the MP-100 to cycle through your presets. Loading a bank typically takes more time than saving a bank. - MP-100 program name editing Issue: Wave Lab edit program feature does not edit MP-100 program names. Solution: Make and save presets in MP-100 panel, using "save bank" and "load bank". - Bypass issues Issue: Wave Lab bypass button does not affect MP-100 audio Solution: Use the MP-100 bypass button. - Multiple MP-100's Issue: If an attempt is made to open more than one MP-100, Wave Lab will freeze. Solution: There is only hardware support for one MP-100, so don't try to open a second instantiation. - Fast Keys Issue: When in Wave Lab, the up, down, left and right keyboard keys and the keypad are not available to adjust the MP-100. Solution: Use the knob, inc and dec keys with your mouse. - MP100 Panel Launch Issue: Launching the MP100 from the Master Panel only paints half the panel. Solution: Use the "maximize" button in the upper right of the panel to open it all the way. ***************************************************************************** LEXICON 3 Oak park * Bedford MA * 01730-1441 Tel: (781) 280-0300 * Fax: (781) 280-0490 www.lexicon.com * csupport@lexicon.com Lexicon Part No. 070-14379