Sonar™ 8: (Windows XP, Windows Vista)
Sonar™ 8: (Windows XP, Windows Vista)
This file contains supplemental information on SONAR™, Version 8.0.0. It was prepared on
September 8, 2008.
Contents
2
Top Issues in SONAR 8
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.
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 8 are included on the SONAR 8 DVDs.
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 8 can load projects from any previous versions of SONAR, but projects that are saved in
SONAR 8 cannot be re-opened in SONAR 1.x or SONAR 2.x. In case you need to open a pre-
SONAR 8 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 8.
3
Project files saved in SONAR 8 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 8 will not open in SONAR 5 if they reference 64-bit audio clips.
SONAR 8 project files may contain new features that will be missing if opened in SONAR 5 and
earlier, including:
SONAR 8 project files may contain new features that will be missing if opened in SONAR 4,
including:
Re-saving a SONAR 8 project file in an older version may permanently remove the project data
described above.
Template files saved from SONAR 8 will not load in earlier versions of SONAR. This is because
of changes made to SONAR's view persistence code in SONAR 8.
Windows Vista
The following issues are known problems with Microsoft Windows Vista (as of Vista SP1):
In WDM or WASAPI mode for some audio devices, SONAR reports an "Unable to
Open..." error when attempting to record w/ multiple input drivers. This may occur when
SONAR attempts to open more than one input for recording when "Allow Arm Changes
During Record Or Playback" is selected in Transport | Record options. This problem is
most likely caused by the driver disallowing multiple inputs to be used simultaneously.
4
As of Vista SP1, WaveRT drivers for onboard audio devices do not work in Vista X64
while running the 32 bit version of SONAR. This is due to a problem with WOW64 in
Windows Vista X64 that has been reported to Microsoft.
5
Audio Performance Issues
The following issues concern improving and troubleshooting audio performance in SONAR.
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
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.
6
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.
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
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
8
General
The following topics cover general issues in SONAR.
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 8 Producer Edition\WMV Profiles
directory in order to be available in SONAR.
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.
9
Cakewalk External Encoder Config Utility
SONAR 8 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 8 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.
[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
10
The wave picture shows a flat line in strange places
Extreme timing issues when bouncing the clip
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.
Beginning with SONAR 7, global and view toolbars are 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
11
Track View Control Size and Layout
It is possible to alter the default size and layout of the controls in the Track view. This requires
adding entries to the CAKEWALK.INI file.
[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.
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).
12
MIDI note colors are tinted depending on their velocities. Notes will appear darker for higher
velocities and lighter for lower velocities.
This feature may be enabled (1) or disabled (0) in the [Wincake] section of the Cakewalk.ini file.
For example:
[Wincake]
PRVColorizeVelocity=0
Note: if you are using SONAR 8 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
To learn how to import any of these .INS files, see the online Help topic titled "Importing
Instrument Definitions”.
13
14
Known Issues
The following topics cover known issues in SONAR that may be addressed in the future.
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
X-Ray Windows is not compatible with plug-ins that use DirectDraw to create their windows,
such as many recent plug-ins by Waves. If a plug-in is not compatible with X-Ray, the plug-in's
window will either flicker or not display properly. If you have any plug-ins that are affected by
this, you can exclude the plug-n(s) from X-Ray by following the instructions 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 8
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:
; Cakewalk FxDelay
XRayExclude13={985DAF67-589F-4B8D-8BBC-D7AD651B9022}
If there was also a VST version of the Cakewalk FxDelay, you would add another line:
16
XRayExclude14=[some VST ID number, with no brackets]
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 8. If you are playing back a
legacy project in SONAR 8, 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 8, you must install both the filters AND
QuickTime. Below are some other known QuickTime issues:
17
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.
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.
When there is a ReWire application loaded into a SONAR project, the SONAR Fast Forward
button/command only works if there is a clip at the end of the SONAR project or if "Stop at
Project End" is not checked.
ReWire Tracks Silent When Using Metronome Record Count-in
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).
18
TTS-1 DXi Does Not Support 88.2 kHz Sample Rate
The Cakewalk TTS-1 soft synth supports 44.1 kHz, 48 kHz, and 96 kHz sample rates, but not
88.2 kHz. The audio engine will not engage if SONAR is configured to use a sample rate of 88.2
kHz while TTS-1 is loaded and connected,
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
Digidesign Mbox and Multiprocessing Engine
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.
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).
20
SONAR Hangs on Deleting Control Surface While TranzPort is
Connected
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 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.
21
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.
//END OF DOCUMENT
22