Professional Documents
Culture Documents
Sonar™ 7: (Windows XP, Windows Vista)
Sonar™ 7: (Windows XP, Windows Vista)
Contents
2
User Account Control and SONAR installer
To install SONAR in Windows XP Professional and Home Edition or Windows Vista, you must
be logged in as a user with administrative privileges.
Once you have installed the product you may then log in as a standard user and use the
application without administrative privileges (you may also choose to log in as the same user that
installed the application if you prefer). Please refer to the notes on User Account Control
elsewhere for more information on running SONAR from multiple user accounts on the same
computer.
At the time of this writing, the only SONAR component that requires administrative privileges, is
the Pentagon I synth. When using Windows Vista, you must choose "Run as Administrator" when
launching SONAR in order to use Pentagon I.
3
Disable Anti-Virus/Spyware Software
Please disable any anti-virus or spyware software before installing SONAR. Utilities such as
“Spyware Doctor” have been known to interfere with the SONAR installation. Such utilities
need not be uninstalled or removed from your system, only temporarily disabled.
SONAR x64
SONAR 5 was the first DAW application to provide a 64-bit audio engine in a 64-bit binary
application. Both a 32-bit and a 64-bit version of SONAR 7 are included on the SONAR 7 DVD.
The following features are not supported in SONAR x64 at this time:
ReWire support for 32-bit clients like Project 5 V2, Reason 2, and Fruity Loops
32-bit DirectX plug-ins
Receiving MIDI output from VSTi plug-ins
DreamStation DXi2
MPEX time/pitch stretching. A 64-bit library is not available for the MPEX time/pitch
stretching algorithm, so this feature is not supported in SONAR x64. Use iZotope Radius
or SONAR’s internal time/pitch stretching instead.
Apple has yet to release QuickTime for Windows x64, so QuickTime import/export is not
yet supported. Note: MPG 1 movie files can be imported.
Backwards Compatibility
SONAR 7 can load projects from any previous versions of SONAR, but projects that are saved in
SONAR 7 cannot be re-opened in SONAR 1.x or SONAR 2.x. In case you need to open a pre-
SONAR 7 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 7.
Project files saved in SONAR 7 will not open in SONAR 4 if they reference or include any of the
following types of data or information:
32-bit and 64-bit audio clips, including clips and tracks that have been frozen or rendered as
32-bit or 64-bit data.
Audio clips that are not all of the same bit depth
Project files saved in SONAR 7 will not open in SONAR 5 if they reference 64-bit audio clips.
SONAR 7 project files may contain new features that will be missing if opened in SONAR 5 and
earlier, including:
4
Synth Rack Assignable Controls
Synth Rack Automation
SONAR 7 project files may contain new features that will be missing if opened in SONAR 4,
including:
Re-saving a SONAR 7 project file in an older version may permanently remove the project data
described above.
This AUD.INI variable enables disk write thru caching, on by default. When write thru caching
is on, data recorded to wave files is written to the hard disk immediately, circumventing the
hardware disk cache. Having write thru caching off can be more efficient for disk I/O but can
result in data loss if your system crashes.
In SONAR 4.0.2 and earlier, opening the property page of a VST plug-in during playback could
result in a slight disruption in playback.
The cause for this problem has its roots in the little "Cancel" button that sits in the top right
corner of the plug-in's property page. The purpose of this button is to allow the user to cancel out
of any changes they might have made to the plug-in, restoring back to whatever state the plug-in
was in before they opened the GUI window. To make this work, SONAR would need to take an
initial snapshot of the plug-in's state, and some plug-ins with large amounts of preset data could
cause an audio hiccup if the data was captured for the Cancel button.
To address this issue, SONAR 4.0.3 (and later) does not take a snapshot of the plug-in's state by
default, and the Cancel button is not available. There is a new CAKEWALK.INI variable to bring
5
back the Cancel button if desired, but be aware that this may also result in hiccups when opening
VST plug-ins during playback.
[WinCake]
EnablePluginCancelButton=1
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.
Set this variable to 0 to temporarily disable multi-threaded mixing during a fast bounce operation.
A value of 1 (default) allows multiprocessing during fast bounce when multiprocessing is enabled
in SONAR.
This variable can be used to improve compatibility with the UAD-1 v4.7.1 driver running in
SONAR compatibility mode. This variable is required because this UAD driver is not compatible
with multiprocessing in SONAR’s fast bounce mode.
If you hear clicks in the rendered audio while running with multiprocessing, you should set this
variable to 0, under the [Wave] section of AUD.INI. This variable is only applicable on
multiprocessor capable PC's when multiprocessing is enabled in Options | Audio | Advanced. For
example:
[Wave]
AllowOfflineRenderMixThreads=0
Realtime Preroll
6
SONAR 6.2 introduced a new 'RealtimePreroll' AUD.INI variable. The default value is 0,
meaning preroll buffers are pumped as fast as possible. Setting the value to 1 pumps preroll audio
buffers in realtime instead of as fast as possible.
Prerolling in realtime may improve buffering and CPU load when using hardware DSP solutions
such as the Universal Audio UAD-1 or Focusrite Liquid Mix.
This variable should be set in the [Aud] section in AUD.INI. For example:
[Aud]
RealtimePreroll=1
In WDM mode when you use an external insert plugin alongside the original dry signal, you
might notice a flanging or flamming effect. To minimize this effect, we recommend that you set
the WaveInBuffers AUD.INI variable to 2.
Note that setting this value to 2 might have an adverse effect with certain audio hardware, causing
recording to drop out. If this occurs please reset the value to 8 and try using ASIO drivers if your
hardware has ASIO support. Also note that this variable only applies when using WDM drivers;
ASIO performance is unaffected by this setting.
To set this variable to 2, please add/modify the following line to the [Aud] section of AUD.INI:
[Aud]
WaveInBuffers=2
7
Control Surface Refresh Rate
Control surfaces are refreshed by posting a windows message every 75 milliseconds.
You may wish to increase the value of this CAKEWALK.INI variable if you are experiencing
sluggish UI responsiveness when using a control surface and playing back high CPU projects.
Also, if you are using a control surface that is not bi-directional, the surface does not need to be
refreshed at all and you can safely increase the value.
[Wincake]
CtrlSurfaceRefreshMS=75
General
The following topics cover general issues in SONAR.
To load this bank of presets, open the LP-64 (either by inserting it into an FX bin or double-
clicking the effect name in a bin), click the “VST” button in the plug-in window toolbar at the top
of the screen, select “Load Bank”, and select the file “LP-64 EQ Default.fxb”.
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 7 Producer Edition\WMV Profiles
directory in order to be available in SONAR.
8
Note: if you use SONAR Studio Edition, substitute “Producer” with “Studio”.
Note: when using DV AVI movies, the transcoding unit must be set to the same format (NTSC or
PAL) as the video file, or Preview to Firewire and Print to Tape will fail to work properly. Also,
CPU consumption will be lower when the source material is in DV format, since the format is
native to the Firewire device and doesn’t incur a CPU hit for transcoding video.
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 7 DVD includes several pre-defined profiles for various encoders. These
profiles can be found in the \Utilities\External Encoder Profiles folder. 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.
By default, the AudioSnap palette appears automatically whenever you enable AudioSnap on a
clip. If you prefer to never auto-show the AudioSnap palette, you can change this behavior by
adding a variable to the CAKEWALK.INI file.
9
[WinCake]
AutoLoadAudioSnapPalette=0
When an audio clip is slip-stretched, a yellow alpha-blended bar is displayed on the clip. This
may affect performance on some systems if there are many slip-stretched clips. There is a new
CAKEWALK.INI variable to disable the alpha-blended bars, and instead only show the percent
value in the lower right corner of the clip.
[Wincake]
AlphaStretchIndicator=0
Or, you might just want a quick way to revert your experiments with AudioSnap back to the
original data.
These symptoms are the result of various AudioSnap issues that have since been fixed in SONAR
6.2.
Note: this gesture is not undoable, so make sure you really want to reset the transient markers.
An alternate solution is to turn off AudioSnap on the clips and then use Edit > Bounce to Clip(s).
However, this will also render any clips fades.
10
Time/Pitch Stretch Plug-in Does Not Work With Groove Clips
The Cakewalk Time/Pitch Stretch 2 plug-in cannot be used with Groove clips. As a result, the
plug-in will fail to load if you try to apply the plug-in as an offline process on a Groove clip.
The SONAR 7 global and view toolbars are now drawn with a background gradient. If you prefer
a flat background, you may disable the gradient drawing by adding the following entry to the
CAKEWALK.INI file in the WinCake section:
[WinCake]
DrawToolbarGradient=0
[WinCake]
TVBoldStripNames=0
Specifies the height of controls. The default height is 17 pixels. This value shouldn’t be changed
more than 1 or 2 from the default value, or you may experience unexpected results.
11
Specifies the width of controls. The default width is 41 pixels.
Specifies the horizontal space, in pixels, between controls. The default spacing is 3 pixels.
Specifies the vertical space, in pixels, between controls. The default spacing is 3 pixels.
Specifies the horizontal space between each button in a “cluster”. The default value is 2 pixels.
The following controls are grouped into clusters:
Specifies whether track/bus names use bold (value=1) or regular (value=0) font style.
Specifies the size of track/bus names. The default size is large (value=1).
SONAR can write Clip Names with an alpha channel such that the waveform behind the clip
name can be seen.
To enable this effect, add the following variable to your Cakewalk.ini file:
[Wincake]
TransparentClipNames=1
MIDI note colors are tinted depending on their velocities. Notes will appear darker for higher
velocities and lighter for lower velocities.
12
This feature may be enabled (1) or disabled (0) in the [Wincake] section of the Cakewalk.ini file.
For example:
[Wincake]
PRVColorizeVelocity=0
If you experience this issue, rewind the project before freezing the synth.
Note: if you are using SONAR 7 Studio Edition, substitute ‘Producer’ with ‘Studio’.
AccessibilityMode
0 - no accessibility (default)
1 - put the access string in the TrackView Cview's caption
2 - put the access string in the CWACCESS window
3 - put the access string in the CWACCESS window and make this window visible
13
To learn how to import any of these .INS files, see the online Help topic titled "Importing
Instrument Definitions”.
If you would still like to use your old color presets in SONAR 7, 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):
[2] Open the exported registry file in a text editor (to use Notepad, right-click the .REG file and
choose ‘Edit’).
If you exported all color presets from SONAR 4, enter the following path:
If you exported the current/default colors from SONAR 1/2/3, enter the following path:
14
Note: if you are using SONAR 7 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 7.
Known Issues
The following topics cover known issues in SONAR that may be addressed in the future.
Dragging a MIDI file from the Desktop into Session Drummer 2 will cause a new MIDI project
to be created in SONAR.
To add a MIDI pattern to Session Drummer 2, you may use its built-in MIDI Pattern Browser, or
you may drag and drop a MIDI clip from SONAR.
If the global "Set Now Time with Full Reset" option (Options > Global > General) is disabled,
Session Drummer 2 may lose sync with SONAR if Session Drummer 2 is auto-playing a pattern
while you seek in the SONAR time ruler.
If you are affected by this issue, the solution is to enable "Set Now Time with Full Reset".
If a MIDI track that is routed to Session Drummer 2 is transmitting RPN events, Session
Drummer 2 will no longer output audio.
To fix this, open the Session Drummer 2 property page, click the ‘VST Preset Options’ button
next to the preset controls, then select ’Plug-in Properties’. Finally, enable “Do not intercept
NRPNs” and click OK.
15
If you have any plug-in’s that flicker or don’t display properly, please see the "X-Ray Windows
Not Compatible With Some Plug-ins" topic below.
1. Open the Cakewalk Plug-in Manager (Tools > Cakewalk Plug-in Manager).
2. In the Plug-in Categories window, select the category that the plug-in you want to
exclude is in.
3. In the Registered Plug-ins window, select the plug-in that you want to exclude.
4. If the plug-in is a DirectX effect or an MFX, write down (or select and copy) the CLSID
value that's in the CLSID field at the bottom of the dialog.
5. If the plug-in is a VST or VSTi, write down the VST ID value that's in the VST ID field
at the bottom of the dialog.
6. Close the Plug-in Manager dialog.
7. Use Notepad to open the XRayExclude.ini file that's in your SONAR program folder
(C:\Documents and Settings\<username>\Application Data\Cakewalk\SONAR 7
Producer Edition).
Note: if you use SONAR Studio Edition, substitute “Producer Edition” with “Studio
Edition”.
9. Exclude your plug-in by creating a blank line below the last entry in the [EffectProps
View] section, and then typing:
For example, if the last entry in the [EffectProps View] section was:
If you wanted to exclude the Cakewalk FxDelay from the X-Ray Windows feature, after
creating a blank line you would type:
16
; Cakewalk FxDelay
XRayExclude13={985DAF67-589F-4B8D-8BBC-D7AD651B9022}
If there was also a VST version of the Cakewalk FxDelay, you would add another line:
10. Save and close the XRayExclude.ini file, and restart SONAR to implement your changes.
A mono VST plug-in will work correctly if "Enable Mono Processing" is checked in the VST
Plug-in Properties dialog and the track interleave is set to mono.
Note: "Enable Mono Processing" is enabled by default in SONAR 7. If you are playing back a
legacy project in SONAR 7, and notice the project does not sound the same, try to disable
"Enable Mono Processing" for any mono plug-ins used in the project.
QuickTime Issues
In order to import/export QuickTime files in SONAR 7, you must install both the filters AND
QuickTime. Below are some other known QuickTime issues:
17
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.
Movies created in QuickTime 7 may not import properly into SONAR 7.
When loading a project with a QuickTime 7 movie into SONAR in WDM driver mode,
SONAR may not play. The workaround is to use ASIO driver mode if your hardware
supports ASIO drivers.
Note: this is not an issue if your SONAR projects use the 48kHz sample rate.
Note: this only affects the meter display, not any audio that is bounced or exported.
There are some situations where the level of a mono clip will be increased by 3db if the track's
output interleave (mono/stereo toggle) is set to mono:
In summary, whenever the track output interleave is mono and the data interleave is stereo, mono
data will be increased in level by 3dB.
18
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.
When using a metronome count-in and recording, any ReWire tracks will be silent at the start of
recording. The silence period will equal the count-in duration. To fix this issue, disable
metronome count-in (go to Options > Project > Metronome and set ‘Record Count-in’ to zero).
Reason 3.04 requires a ReWire update in order to run as a ReWire device in SONAR 7 on a
Windows Vista system. The installer for this update can be downloaded from
http://www.propellerheads.se/download/index.cfm?fuseaction=get_article&article=vista_installer
MP3 Files With 256K Bit Rate May Not Play in SONAR 7
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 7. This may also apply to MP3 files that are authored
in SONAR 7 at 44.1kHz, 16-bit, 256K joint stereo. Other bit rates should be fine.
The Kinetic uninstaller is removing the Groove Synth sample file, but not the actual synth. Both
must co-exist 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.
19
SONAR 7 does not directly support MPEG 2 import, but if you have installed Cakewalk Pyro
Plus, SONAR 7 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.
If you are affected by this, temporarily disable the multiprocessing engine before exporting audio.
20
A crash may occur while recording with the Mbox if SONAR’s multiprocessing engine is
enabled (‘Use Multiprocessing Engine’ in Options > Audio > Advanced) on a HyperThreading
or multi-processor system.
If you are affected by this, temporarily disable the multiprocessing engine before saving the track
template.
This appears to happen with the UAD-1 if you change the buffer size more than once in
succession. The buffer size is automatically reset twice in a row when the double precision engine
is engaged/disengaged. There is no data loss or crash, and the solution is to save and reload the
project.
21
When using the M-Audio Delta 1010 set at 128 sample buffer size (configured in M-Audio Delta
control panel), setting the mixing latency in SONAR to 5.8 milliseconds may results in distortion
if either or both of the following is true:
1. An effect is patched into a track and the track is armed for recording.
2. An effect is patched into a track and Input Echo is enabled on that track.
The track arm button on the TranzPort uses MIDI Key C0, which in SONAR, is the default shift
key when MIDI Key Bindings are enabled. The workaround is to disable MIDI Key Bindings in
SONAR or reassign the Shift Key to a different Key (like Db0).
Occasionally, more than one instance of the Tranzport will appear in the Control Surface dialog.
Unfortunately, SONAR hangs if you try to delete one while the device is connected.
To remove the duplicates, close SONAR, unplug the Tranzport, re-open SONAR, go to Options
> Controllers/Surfaces, and delete all but one instance of Tranzport.
At this point you must close SONAR, re-connect the Tranzport and launch SONAR again in
order for the Frontier MIDI drivers to become available so the surface will work.
If the TranzPort "Skip archived tracks" option is enabled, clicking on an archived track in
SONAR may also cause another nearby non-archived track to get selected.
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
22
the E-MU ASIO panel. A host application has no way of knowing if the ASIO panel is open or
closed.
If you experience problems with tracking, try to increase the Buffer Seconds setting. For instance,
in a 6 minute project, you would want this setting to be at least 360.
If you prefer a slight hiccup instead of hearing the full note duration, you can change the default
behavior with the “Set Now Time with Full Restart” option in Options > Global > General.
Note: moving a MIDI note event during playback is affected by this same issue.
23
Arpeggiator MFX With Low Rate May Affect Playback
When using the Arpeggiator MFX MIDI plug-in and setting the 'Rate' parameter to 1 MIDI tick,
playback may become very sluggish. This is primarily an issue if your MIDI hardware cannot
handle the numerous events that are generated by the Arpeggiator effect.
Dual Video Monitors Set to Different Color Bit Depths May Affect
Performance
If you are using a dual monitor system and experience sluggish performance when selecting and
dragging clips in the Clips pane, confirm that both monitors are set to the same ‘Color Quality’
bit depth.
When using the Creative ASIO driver and starting playback on a project that contains video, the
video may pause for a moment or not animate at all. This may be more pronounced when using a
high latency setting.
This issue is due to the Creative ASIO driver, which returns incorrect sample positions, which in
turn causes the clock to report a bad position causing video to stop playing. This is currently only
known to be an issue with the Creative ASIO driver and not other ASIO drivers.
//END OF DOCUMENT
24