Sonar 4 Readme

Transcript

SONAR™ 4 (Windows 2000/XP) README.RTF Copyright © 2004 Twelve Tone Systems, Inc. All rights reserved. Cakewalk is a registered trademark, and SONAR is a trademark of Twelve Tone Systems, Inc. This file contains supplemental information on SONAR™, Version 4. It was prepared on September 15, 2004. Contents What’s New in SONAR 4 If you have upgraded to SONAR 4 from a previous version of SONAR, please see the New Features in SONAR 4 section in the online Help. You can access this Help topic from Help-What’s New. New in SONAR 4 The following enhancements have been introduced in SONAR 4: ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Surround Mixing (SONAR Producer only) SurroundBridge (Surround Effects Linker) (SONAR Producer only) Joystick Support (SONAR Producer only) Lexicon Pantheon Surround Reverb (SONAR Producer only) Sonitus Surround Compressor (SONAR Producer only) Video Thumbnail Track (SONAR Producer only) Track Folders Freeze Synths or Tracks Loop Construction View Enhancements Bus-able Audio Metronome Group Editing (Multi clip Slip-Editing, fades, and splits) Take Management and Comping Enhancements Track layers Powerful crossfade tool for cropping overlapping clips Mute Tool - Clip-based (Clip Mute) or time-based within a clip, and Isolating (Clip Soloing) Video Export to QuickTime, Windows Media Video, and AVI Enhanced Key Bindings Nudging ? ? ? ? ? ? ? ? ? ? ? ? Navigator view Audition (Selection Playback) Cakewalk TTS-1 DXi Synth POW-r Dithering (SONAR Producer only) Prosoniq MPEX Time Scaling (SONAR Producer only) Configurable RMS and Peak Meter Ballistics Six stereo panning laws Powerful presets for frequently used export settings Export buses and tracks into a composite mixdown, or as individual files WMA9, 5.1 WMA9 Pro, and WMA9 Lossless Encoding Open support for external command-line encoders Color Enhancements (Console view and clips) Top Issues in SONAR 4 Windows 2000/XP and SONAR To install and run SONAR in Windows 2000, Windows XP Professional and Home Edition, you must be logged in as a user with administrative privileges. To use the product you must be logged in as the same user that installed the program; otherwise, you will not have access to your DirectX effects presets. Backwards Compatibility SONAR 4 can load SONAR 1.x, SONAR 2.x, and SONAR 3.x projects, but projects that are saved in SONAR 4 cannot be re-opened in SONAR 1.x or SONAR 2.x. In case you need to open a pre-SONAR 4 project in an earlier version of SONAR, it is recommended that you always create a backup copy of the original project before you re-save the project in SONAR 4. Lexicon Pantheon Reverb Please note that the Lexicon Pantheon reverb plug-in will only work in SONAR. Lexicon Pantheon Surround Supports Surround Formats of 6 Channels or Less If a SONAR 4 project is using the Lexicon Pantheon Surround plug-in, an error may occur if you change the project’s surround format from 5.1 to a surround format containing more than 6 channels (7.1, 8.1, etc.) The Lexicon Pantheon Surround plug-in is only compatible with surround formats of 6 channels or less (5.1, Quad, etc). 2 Also, if the current surround format is already set to 7.0 and above, the Lexicon Pantheon Surround plugin will fail to patch in an effect bin. Bus Solo When a bus is soloed, SONAR will not mute MIDI tracks that are assigned to external MIDI ports. This is intentional, as the external MIDI device’s audio output might be fed back to SONAR via an audio track input. ‘Track Interleave’ and Pre-SONAR 4 Projects When loading pre-SONAR 4 projects in SONAR 4, please be advised that the Track Interleave toggle behaves differently in SONAR 4, which may result in your pre-SONAR 4 projects sounding a little differently. In SONAR 3.1.1, the track interleave button implicitly specifies the input interleave of the effects bin. It has no effect on the actual data streamed out of the track bus when no effects are present. In SONAR 4, track interleave button actually specifies how the data is streamed to downstream buses. For example, you can now switch a stereo track’s interleave to mono and it will send mono data from its output (or sends) to all downstream buses. SONAR 3.1.1 doesn't do this - it ignores the track interleave button unless effects are present. This change will potentially make a SONAR 3.1.1 project sound different if it was saved with the interleave button set to mono but no effects were present in the effect bin. If this is an issue, and you need the project to sound the same again, simply set the track interleave button back to the desired state. Pre-Fader Sends and Pre-SONAR 4 Projects In SONAR 3, track/bus mute and solo affected pre-fader sends. This has changed in SONAR, where mute and solo has no effect on pre-fader sends. Please be advised that mixes created in SONAR 3 may sound different in SONAR 4 when soloing and muting tracks/buses if pre-fader sends were used. MPEX Time/Pitch Scaling & High Sample Rates SONAR 4.0.0 uses the MPEX2 time/pitch scaling algorithm, which currently will not work with any sample rates greater than 96kHz. A future update to SONAR 4 will introduce MPEX3, which does not have this limitation. 3 Multichannel Import/Export System Requirements The following minimum system requirements apply for importing and exporting multichannel files in SONAR 4: Requirements for multichannel audio import  Windows XP (optionally with SP1/SP2)  Not supported under Windows 2000. This is a documented Microsoft OS limitation. Audio from such files will import as stereo only. Requirements for multichannel audio export  Windows XP (optionally with SP1/SP2)  Windows 2000 with SP4. If you wish to export to multichannel Windows Media files, you should additionally have Windows Media Player 9 installed. (not 100% sure about the WMP requirement) Requirements for multichannel Windows Media Video Import in SONAR  Windows XP (optionally with SP1/SP2)  Not supported under Windows 2000. This is a documented Microsoft OS limitation. (only the video will import normally, audio will import as stereo) Requirements for multichannel Windows Media Video export in SONAR  Windows XP (optionally with SP1/SP2) and upcoming QASF.DLL hotfix from Microsoft. The hotfix should be available on the Cakewalk web site (www.cakewalk.com) by the time SONAR 4 is released.  Windows 2000 with SP4 and Windows Media Player 9 installed. (not 100% sure about the WMP requirement), and upcoming QASF.DLL hotfix from Microsoft Keyboard Shortcut For ‘Preview Loop’ In Loop Construction View In previous versions of SONAR, the keyboard shortcut for ‘Preview Loop’ in the Loop Construction view was Shift+Spacebar. Please note that this has changed to Ctrl+Shift+Spacebar in SONAR 4 since Shift+Spacebar is now a global command for auditioning the selected data in a project. Keyboard Shortcut For ‘Preview Loop’ In Loop Explorer View In previous versions of SONAR, the keyboard shortcut for ‘Preview Loop’ in the Loop Explorer view was Shift+Spacebar. Please note that this shortcut has been overridden in SONAR 4 by the global ‘Audition’ command that previews selected data in a project. Use the Key Bindings dialog (Options-Key Bindings) to assign a new keyboard shortcut for ‘Preview Loop’ in the Loop Explorer View Binding Context. 4 Keyboard Shortcut For ‘Play Event’ In Event List View In previous versions of SONAR, the keyboard shortcut for ‘Play Event’ in the Loop Explorer view was Shift+Spacebar. Please note that this has changed to Ctrl+Shift+Spacebar in SONAR 4 since Shift+Spacebar is now a global command for previewing the selected data. Audio Performance Issues The following issues concern improving and troubleshooting audio performance in SONAR. DXi’s & Look-ahead Processing at High Latencies Some plug-ins, such as the Sonitus:fx Multiband and other dynamics processors, use a look-ahead buffer mechanism, which results in a short delay being introduced to the output signal when the plug-in is used in real-time. SONAR’s automatic delay compensation (ADC) takes care of any delays, but you may experience some anomalies when using such a plug-in to process the output of a DXi—especially if SONAR is configured to use a high mixing latency. The symptoms include audio that appears to drop out, and/or missed notes (from the MIDI track that is assigned to the DXi). Again, this is more prone to occur with higher latency settings. This may happen if SONAR doesn’t pump ahead enough MIDI data to compensate for ADC. To fix this problem, go to Options-Global-MIDI and increase the Prepare Using [n] Millisecond Buffers value. Sampling DXi's and the "Enable Multiprocessing Engine" Audio Option A few DXi's that employ sample playback may click or pop if the multiprocessing audio engine is enabled. At the time of the 4.0 release we have confirmed that the DS864 DXi and the LiveSynth Pro both have this limitation. HyperThreading / Multiprocessor Optimization The audio configuration dialog (Options-Audio) has a checkbox "Enable MultiProcessing Engine" on the Advanced page. This checkbox is only active on multi-processing (or hyper-threaded) machines. When checked, the audio engine will use a dedicated worker thread for each CPU, and optimally distribute mixing and DSP tasks 5 across multiple CPU's. You will notice significant performance benefits on true multi-processor systems with this option enabled. MIDI Prepare Buffer Size and Automation If your project contains several track/clip automation envelopes, setting your MIDI playback buffer size too low (in Options-Global-MIDI) can cause audio to crackle if your audio latency is also set very low. This problem will be somewhat worse if you enable multiprocessing in the audio engine. To minimize or eliminate these crackles, please be sure to keep your MIDI playback buffers at or above the default setting of 500 msec. Improve Responsiveness of Real-Time MFX Plug-Ins MfxLookAhead= (default=960*4) This new TTSSEQ.INI variable defines how much extra MIDI data is sent to MFX plug-ins, so that they have extra room to quantize events into the future. Lower values mean MFX plug-ins can work more "just in time". This variable should be set in the [OPTIONS] section. For example: [OPTIONS] MfxLookAhead=480 Confidence Recording Waveform Previews WavePreviewSampleFrequency=<1-10> (default=1) By default, waveform previews take a meter sample for each meter frame. The default interval between meter frames is 40 milliseconds. The ‘WavePreviewSampleFrequency’ CAKEWALK.INI variable lets you specify how frequent samples are taken. The value can be an integer between 1 and 10, and represents the number of frames to sample. It goes in the [Wincake] section of CAKEWALK.INI. For example: [WinCake] WavePreviewSampleFrequency=1 With the default value (1), every meter frame gets written to the history file. With higher values (2-10), frames will be skipped, causing fewer history frames to be written to the history file. Higher values may be desirable if the waveform previews are affecting playback performance. 6 Meter Frame Size MeterFrameSizeMS=<10-200> (default=40)* Meters in SONAR show peak (or RMS) values at a given instant in time. The actual peak value displayed by a meter is the highest peak recorded in an interval of time referred to as a "Meter Frame". The default size for a meter frame is 40 milliseconds, which is an accuracy of 25 FPS. The ‘MeterFrameSizeMS’ AUD.INI variable allows you to change the size of this interval. It goes in the [Wave] section of AUD.INI. For example: [Wave] MeterFramSizeMS=40 Setting this value to a lower value will make the meters record peak info for smaller time slices. However this can also increase the metering CPU and memory cost. * = although SONAR doesn’t enforce a fixed value range, the recommended range should be between 10 and 200 milliseconds. Control Surfaces With Jog Wheel There are two new CAKEWALK.INI variables that control the behavior of using a control surface jog wheel to change SONAR’s Now time: JogPosTimer= (default=120) PauseOnJog=<0 or 1> (default=0; off) JogPosTimer is the period of the now time throttle. When a jog message comes in, SONAR sets the transport time immediately but will not set the transport time again for this length of time. During the time, SONAR just remember the latest jog time received. PauseOnJog is the main switch. 1 does a pause and invokes the throttle timer. 0 just sends the now time with no pause and no throttle timer. If 0, the setting of JogPauseTimer is "don't care". This variable should be set in the [Wincake] section. For example: [Wincake] JogPosTimer=120 PauseOnJog=0 7 General The following topics cover general issues in SONAR. Windows Media Video (WMV) Profiles SONAR 4 includes several profiles for exporting WMV files. You can author your own WMV profiles if you wish to use specific settings. To do so, you need to download and install the Windows Media Profile Editor, which is included with the Windows Media Encoder 9 Series. Download from here: http://www.microsoft.com/windows/windowsmedia/download In ‘Select Download:’ choose "Windows Media Encoder" In ‘Select Version:’ choose ‘”9 Series” The setup program will install the Windows Media Profile Editor utility. If you author your own profiles (.PRX files), they must be placed in the \Documents and Settings\All Users\Application Data\Cakewalk\SONAR 4 Producer Edition\WMV Profiles directory in order to be available in SONAR. Note: if you use SONAR Studio Edition, substitute “Producer” with “Studio”. Cakewalk External Encoder Config Utility SONAR 4 supports external command-line encoders, such as LAME, Ogg Vorbis, Monkey’s Audio, etc. If an external command-line encoder is installed on your machine, the ‘Cakewalk External Encoder Config’ utility allows you to add the encoder to SONAR’s list of available file formats when exporting audio (File-Export-Audio). To use the utility, start SONAR and go to Tools-Cakewalk Ext Encoder Config, then specify the proper settings or the encoder you wish to use. Note: the SONAR 4 CD-ROM includes several pre-defined profiles for various encoders. These profiles can be found in the \Utilities\External Encoder Profiles folder on CD1. You can use these profiles as a starting point when creating your own profiles. Simply double-click the appropriate .REG file to add the information to the Windows registry, then use the ‘Cakewalk External Encoder Config’ utility to specify the correct install path of the encoder. Track View Widget Reordering 8 In SONAR 4, it is possible to alter the default order layout of the Controls (Widgets) in the Track view. This requires adding entries to the CAKEWALK.INI file. All non-fixed controls (controls not forced in the track header like Name, Mute, Solo, Record Arm, minimize and maximize) will layout based on these INI keys. You can independently change the order for Audio Tracks, MIDI Tracks, and Buses by putting entries in three different sections: [Audio Widgets], [Midi Widgets], and [Bus Widgets] Each type of strip has a fixed number of widgets. Type of Strip Audio Track MIDI Track Bus Number of Widgets 8 13 8 Each type of strip has different types of widgets on it as well which are identified by name. The following table shows the names of the widgets for each type of strip: Audio Track Volume Pan Trim Input Output Fx Aux Interleave MIDI Track Volume Pan Trim Input Output Fx Bus Volume Pan Output Fx Aux Interleave Inputgain Inputpan Channel Bank Patch Key Time Chorus Reverb Contents of Widget Group Volume Slider Pan Slider Trim Slider Input Selector Output Selector Fx Bin Aux Send, Pan, Enable, Pre-Post switch Phase and Interleave switches Input Gain Slider Input Pan Slider MIDI Channel Picker MIDI Program Bank Picker MIDI Patch Picker MIDI Key Offset MIDI Time Offset MIDI Chorus ( CC99 ) Slider MIDI Reverb ( CC91 ) Slider How the INI is formatted to reorder widgets A Key-Value pair is defined as: Wn=name where n is the sort order, and name is the widget group name. The name is not case sensitive. Start with a section name for the type of strip you want to reorder widgets on. It looks like this for Audio Tracks: 9 [Audio Track] Now, add the 8 entries that specify the widget order for Audio Tracks. Here is one example: W0=Volume W1=Pan W2=Interleave W3=Trim W4=FX W5=Aux W6=Output W7=Input Note: the layout order will revert to the hard-wired list if any of these scenarios are true: 1? 2? 3? 4? Any section is missing Any individual key is missing False value or name for a key Duplicate keys All sections and keys must succeed, or SONAR reverts to the default hard-wired layout order. Example of working widget reordering entries In order to customize the control layout order, you can copy the sections below and paste them into CAKEWALK.INI. The layout below mimics the hard-wired layout. To reverse, for example, the Volume and Pan order, set W0=Pan and W1=Volume. These settings are loaded *ONCE* per strip when the strip is created, so you can for example make a change to the [MIDI Widgets] section and create another MIDI strip with the new layout (you don't have to restart the application), but all MIDI strips will have the same layout the next time you open the project. [Audio Widgets] W0=Volume W1=Pan W2=Interleave W3=Trim W4=FX W5=Aux W6=Output W7=Input [Midi Widgets] W0=Volume W1=Pan W2=Trim W3=FX w4=Reverb w5=Chorus W6=Channel 10 w7=Bank w8=Patch W9=Output W10=Input w11=Key w12=Time [Bus Widgets] W0=InputGain W1=InputPan W2=Volume W3=Pan W4=Output W5=Aux W6=FX W7=Interleave Warning: Input Echo May Cause Feedback Loop Depending on how your studio equipment is connected—and how audio tracks in a SONAR project are routed--keep in mind that Input Echo on audio tracks may introduce feedback loops which can cause damage to your speakers. If your sound card has a "What U Hear" record input, please disable/mute this input before using Input Echo on audio tracks, and if you are using an external mixer, please lower its master volume before proceeding. In case of feedback, choose Transport-Reset. Always Display Widgets in Track Header Bar TVWidgetsStickInHeader=<0 or 1> (default=0) By default, Track view controls (widgets) will only appear in the track header bar if the track is minimized and there is enough room to display at least one control. SONAR 4 has a CAKEWALK.INI variable that allows you to always display controls in the track header bars, regardless of whether a tracks are minimized or not. It goes in the [Wincake] section of CAKEWALK.INI. For example: [Wincake] TVWidgetsStickInHeader=1 When TRUE (value=1) widgets stay in the header bar regardless of the height of a track. 11 Note: the following controls will never appear in the track header bar: Send widgets, Meters, and Vertical FX Bin. Display Drop Shadow On Clips ShowClipShadow=<0 or 1> (default=0) By default, a drop shadow is not displayed on clips in the Track view. This is different from previous versions of SONAR. SONAR 4 has a CAKEWALK.INI variable that allows you to always display a drop shadow on clips. It goes in the [Wincake] section of CAKEWALK.INI. For example: [Wincake] ShowClipShadow=1 When TRUE (value=1) clips display a small drop shadow. Console View Auto-Resizing By default, the Console view will automatically resize itself vertically as modules are shown or hidden. If you prefer, you can keep the Console view from automatically resizing by holding down the Shift key as you click on a module’s Show/Hide toggle (leftmost pane in the Console view). This will preserve the current Console view size without resizing the view to fit all visible modules. Default EQ Position (SONAR Producer Edition Only) DefaultEqPosition=<0 or 1> (default=0) The integrated channel EQ can be either pre FX bin or post FX bin. The default position is pre FX bin, but you can change the position of any channel EQ by right-clicking the EQ plot and choosing the desired position from the context menu. The ‘DefaultEqPosition’ AUD.INI variable lets you specify the default EQ position for all new tracks/buses. This variable lives in the [Aud] section of AUD.INI, and legal values are: 0 (pre FX) or 1 (post FX). For example: [Aud] DefaultEqPosition=1 Note: this variable only applies to SONAR Producer Edition, not SONAR Studio Edition. 12 User Control of Pause During File Save PauseDuringSave=<0 or 1> (default=0) By default, when saving a project file during playback, SONAR saves the file asynchronously while playback continues. While this is not a problem with most projects, complex projects under high CPU load conditions (particularly while running under low latency) may take longer to save than if the transport was not playing. The new CAKEWALK.INI variable ‘PauseDuringSave’ changes the default behavior and pauses playback temporarily for the duration of the file save. This allows the file save to proceed as fast as possible before playback resumes. ‘PauseDuringSave’ should be set in the [WINCAKE] section of CAKEWALK.INI. Legal Values are: 0 (default): file is saved asynchronously while playback continues. The save operation may take longer than if the transport was not playing. 1: playback is paused for the duration of the file save operation. This allows the file save to proceed as fast as possible, resuming playback when completed. For example: [WINCAKE] PauseDuringSave=1 Automatically Sending Controller Resets to DXi’s SendResetsToSoftSynths=<0 or 1> (default=0) This new TTSSEQ.INI variable controls (globally) whether SONAR sends MIDI controller resets to DXi’s. This variable should be set in the [OPTIONS] section. Legal values are: 0 (default): Resets are not sent to DXi’s 1: SONAR will send MIDI controller resets to DXi’s. This is what SONAR already does for hardware synths. For example: [OPTIONS] SendResetsToSoftSynths=1 13 If you are freezing synth tracks that have MIDI controller messages, setting this variable to TRUE (1) will ensure that synths will have their MIDI controllers reset before a freeze operation. ‘Zero Controllers When Play Stops’ Is Not Applied When Freezing Synths Please note that the global ‘Zero Controllers when Play Stops’ setting is not applied when freezing soft synths. This means that the current state of a continuous controller when play is stopped can cause unexpected results when freezing a synth. If you experience this issue, rewind the project before freezing the synth. Upgrading to SONAR from an Earlier Version of a Cakewalk Product SONAR SETUP does not overwrite your existing MASTER.INS file. That file contains the instrument definitions that SONAR loads every time it starts. SETUP installs new .INS files for each supported manufacturer. These files contain the latest complete set of available instrument definitions. To learn how to import any of these .INS files, see the online Help topic titled "Importing Instrument Definitions”. Old Color Settings Are Not Migrated When Upgrading To SONAR 4 SONAR 4 has many new color settings that most often result in poor results when importing color presets that were created in previous versions of SONAR. Because of this, old color presets are not automatically migrated to SONAR 4 if you are upgrading from a previous version of SONAR. If you would still like to use your old color presets in SONAR 4, you can do so by following the steps below (warning: only do this if you are comfortable with editing the Windows registry; you may wish to back up the registry first): [1] Export the following registry branch (pick the SONAR version you are upgrading from): SONAR 3 (color presets): HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR Producer\3.0\Presets\{6B0298E5-C4B7-4AAF-90EF-B214D18F7654} SONAR 3 (current colors): HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR Producer\3.0\Colors SONAR 2 (current colors): HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR\2.0\Colors 14 SONAR 1 (current colors): HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR\1.0\Colors [2] Open the exported registry file in a text editor (to use Notepad, right-click the .REG file and choose ‘Edit’). [3] Change the path to reflect SONAR 4: If you exported all color presets from SONAR 3, enter the following path: [HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR Producer\4.0\Presets\ {6B0298E5-C4B7-4AAF-90EF-B214D18F7654}] If you exported the current/default colors from SONAR 1/2/3, enter the following path: [HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR Producer\4.0\Colors] Note: if you are using SONAR 4 Studio Edition, substitute ‘Producer’ with ‘Studio’. [4] Save and then close the .REG file, then double-click the REG file to add the information to the registry. Your old color settings should then be available in SONAR 4. Known Issues The following topics cover known issues in SONAR that may be addressed in the future. QuickTime Issues In order to import/export QuickTime files in SONAR 4, you must install both the filters AND QuickTime. Both can be optionally installed by the SONAR 4 installer. Below are some other known QuickTime issues:  QuickTime Import/Export requires version 6.5.1 or higher of the QuickTime Player to be installed (an optional install in the SONAR 4 installer).  Exporting to QuickTime is a two-step process: one pass is done by SONAR and the next pass is done in the background by QuickTime, independent of SONAR. If you wish to cancel the second pass of the export, it must be done in the QuickTime ‘Export to Movie’ dialog.  Exports to QuickTime creates a potentially large temp file that has a file size that depends mainly on the frame size of the movie used in the SONAR video project. Since the temp file is stored in the same partition as the exported movie, the best practice is to save the .MOV in a partition that has several gigabytes of free space.  Audio mixdown to QuickTime must be set to 16 bits stereo or mono, or the resulting export will create a unusable file or abort with an error. 15  Audio mixdown to QuickTime must be set to 48 KHz or less or the resulting export will create a file that plays back incorrectly.  When exporting to QuickTime, the frame rate of the QuickTime video compressor will default to "best possible." Since not all movies in a SONAR video project correctly report their frame rate, the best practice is manually enter the desired frame rate. This is done in the video settings of the QuickTime video compressor.  Exports to QuickTime from a SONAR video project created from an AVI using the Indeo video compressor will create a movie with white frames.  Exports to QuickTime may have an extra white frame on the last frame of the movie. This extra frame can be removed with the QuickTime Pro Player or another QuickTime editing application. Many of these limitations will be addressed in a future update to SONAR. Audio Metronome Issues The default audio metronome sounds are 44.1kHz samples. This may result in a pop when playback or record is started and stopped when using audio hardware that use a native sample rate of 48kHz (such as SB Live!). This is an artifact of the internal sample rate conversion that the audio hardware performs. Note: this is not an issue if your SONAR projects use the 48kHz sample rate. Enabling Mono on a Bus/Main Will Affect Upstream Meters If you make a bus or main out mono by toggling its Mono/Stereo switch, any “upstream” meters—that is, meters on any tracks or buses that are assigned to the mono bus/main out--from the bus/main out will also display as mono. Note: this only affects the meter display, not any audio that is bounced or exported. Adding MIDI Device May Break Control Surface Support and MIDI Key Bindings When adding a new MIDI Device in Options-MIDI Devices, control surface support and MIDI key bindings may no longer work properly. Restarting SONAR will solve this problem. MP3 Files With 256K Bit Rate May Not Play in SONAR 4 MP3 files that are created in Cakewalk MediaWorks version 1.0 with a setting of 256K, may play back as silence when imported into SONAR 4. This may also apply to MP3 files that are authored in SONAR 4 at 44.1kHz, 16-bit, 256K joint stereo. Other bit rates should be fine. 16 Using Cakewalk Kinetic Groove Synth in SONAR 4 If you are a Cakewalk Kinetic customer and you are using the Kinetic Groove Synth in SONAR, please be advised that any saved SONAR projects that make use of the Groove Synth can no longer be opened if you uninstall Kinetic. Attempting to open such a project may result in a crash. The Kinetic uninstaller is removing the Groove Synth sample file, but not the actual synth. Both must coexist or you will run into the issue above. To address this, make a backup copy of the P5antom *.DAT file before uninstalling Kinetic, then copy/move P5antom *.DAT file back to its original location after Kinetic has been uninstalled. Importing MPEG 2 Files in SONAR 4 SONAR 4 does not directly support MPEG 2 import, but if you have installed Cakewalk Pyro Plus, SONAR 4 will be able to import MPEG 2 files by virtue of the shared libraries and filters from the Ligos components of Pyro Plus. However, please be advised that if WinDVD or Power DVD have been installed before Pyro Plus (or MediaWorks) is installed, SONAR may crash when attempting to import MPEG 2 files. Copying Frozen Clip May Create New DXi Track Instead of Audio Track If a DXi track has been frozen and you Ctrl+drag (copy) the frozen clip below the last track to create a new track, SONAR may create a new DXi track instead of an audio track. If this occurs, you may no longer be able to unfreeze the original DXi track. To address this, change the Input control of the new track so it is assigned to a hardware input port (or ‘None’) instead of a DXi port. Exporting 24-bit Audio to WMV Files At the time of writing this ReadMe file, SONAR 4 cannot export 24-bit audio to WMV files. This is due to be addressed in an upcoming QASF.DLL hotfix from Microsoft, which should be available on the Cakewalk web site (www.cakewalk.com) by the time SONAR 4 is released. Successive Snapshots Do Not Update Envelope Node Values 17 When taking multiple automation snapshots at the same Now time, new envelope nodes are created instead of updating any existing envelope nodes. To address this issue, undo the previous automation snapshot before performing a new snapshot. Potential ‘Pops’ When Using Surround Automation (SONAR Producer Edition Only) If you record ‘Angle’ surround pan automation, please note that a pop may occur as the angle parameter jumps from 0 degrees to 180 degrees. This may occur if the jump is not instantaneous, and can be easily solved by zooming in the envelope automation and moving the top and bottom nodes so they are aligned in time (tip: enable Snap to make it easier to align the envelope nodes). Mono Plug-Ins on Surround Buses Mono plug-ins may not work properly when inserted in a Surround bus effect bin. A common symptom is a Runtime error message. Staff View Font May Require Reboot After SONAR is Installed SONAR installs a font that is used by the Staff view. This font is only installed temporarily when SONAR is installed, and becomes permanently installed after the machine is rebooted. On some machines—even if the Staff View font is successfully temporarily installed—some functions that reference the font may fail until after a reboot. The problem is easily identified by corrupt Staff View graphics. Error When Using UAD-1 Plug-Ins as DirectX Effects While Looping When using the UAD-1 powered DSP card plug-ins as DirectX effects and SONAR’s transport is looping, a “Powered Plug-Ins Error” dialog may appear, and audio may eventually become silent. If this occurs, disable looping and restart SONAR’s transport in order to regain any audio signal. The UAD-1 plug-ins should work properly if looping is disabled. For the best possible performance in SONAR 4, we recommend that you use the VST versions of the UAD-1 plug-ins wrapped with the latest VST Adapter (version 4.4.2). For more information, please see the UAD ReadMe.txt file that is included with the UAD-1 powered DSP card. 18 Mono UAD-1/TC PowerCore Plug-ins Do Not Sum Audio on Stereo Tracks When using mono UAD-1 or TC PowerCore plug-ins on stereo tracks in SONAR, the audio is not summed; the left channel is processed and delayed (delay compensation is not applied), and the right channel is unprocessed and not delayed. M-Audio Midisport 8x8 Compatibility The M-Audio Midisport 8x8 driver (as of v. 4.1.21) has a limitation that only allows you to use up to 15 MIDI input ports simultaneously. Frontier/Tascam ASIO Drivers The Frontier/Tascam ASIO drivers install two flavors of the ASIO driver in the registry: a 24-bit one and a 16-bit one. SONAR may have problems trying to profile both drivers. The solution is to remove one of the drivers from the registry. E-MU 1820 Compatibility 96kHz Sample Rate If a 44.1/48kHz session is loaded in the Patchmix DSP application, a crash may occur if you change SONAR’s sample rate to 96kHz. To address this, load a 96kHz session in the patchmix DSP application before changing the sample rate in SONAR. ASIO Panel If the E-MU ASIO Panel is open, a crash may occur if you try to launch the SONAR online Help from the Audio Options dialog (Options-Audio). To address this, you must first manually close the E-MU ASIO panel. A host application has no way of knowing if the ASIO panel is open or closed. 19 SONAR Only Supports GigaStudio Sample Rate When Using WDM Drivers When using GigaStudio and SONAR with WDM drivers, SONAR must use the same sample rate as GigaStudio is using. Can't Print if Staff View is Floating It is not possible to print the Staff view if the Staff view is float-enabled. If necessary, temporarily disable floating if you need to print from the Staff view. RIFF/MID Will Not Launch SONAR When Double-clicked Double-clicking RIFF MIDI files and Standard MIDI files will fail to launch SONAR even if these file types are associated with SONAR. FXpansion BFD Version 1.0.9.0 May Crash SONAR in Rewire Mode When using FXpansion BFD version 1.0.9.0 in ReWire mode, SONAR may not start properly. Use BFD as a DXi or VSTi synth instead. Sony Pitch Shift Plug-in The Sony Pitch Shift plug-in produces more output data than the input data SONAR gives it. So this will cause a dropout when used in real-time, because SONAR has no way to buffer up this extra data indefinitely. This plug-in is only suitable as an offline process in SONAR. SONAR Does Not Record When Using Ping DXi Without a MIDI Track Ping DXi must be fed by a MIDI track, or else SONAR will fail to record audio. Muted MIDI Ranges are Not Distinguished Visually When using the Mute Tool to mute a time range in a MIDI clip, there is no visual indication in the Piano Roll View, the Event List or the Staff View to differentiate between muted and unmuted data. 20 Standard AVI Audio Codecs Do Not Support Multichannel Audio None of the standard AVI audio codecs support multichannel audio. When exporting multichannel audio to an AVI video file, do not select an audio codec (no compression), or use a codec that is known to support multichannel audio. //END OF DOCUMENT 21