Cakewalk // Documentation // SONAR X2 // AUD.INI
Table of Contents Previous Next Index

To edit Aud.ini, do the following:
Go to Edit > Preferences > Audio - Configuration File.
Under Configuration Settings, click Edit Config File.
The Aud.ini file opens in the default Windows text editor.
Edit Aud.ini as desired.
Save Aud.ini and close the Windows text editor.
Click Reload Config Settings to reload the current audio configuration settings from Aud.ini.
Table 231.  
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 variable allows you to change the size of this interval. It goes in the [Wave] section. For example:
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.
Note: although SONAR doesn’t enforce a fixed value range, the recommended range should be between 10 and 200 milliseconds.
This variable specifies the maximum size of the picture cache. The picture cache is located in the directory specified by the PictureDir=<path> variable (defaults to <Cakewalk Folder>\Picture Cache).
<Cakewalk directory>\Picture Cache
This option allows waveform pictures to be computed in the background while audio playback is in progress. Most modern computers should be able to handle this load with no problems. Note that work is only done while new pictures are actually being computed—once the pictures are finished rendering there is no overhead.
This option creates extra background worker threads for the generation of wave pictures when you load a project. One worker thread is automatically created per CPU/core. Setting EnablePicCacheThreads=0 reverts back to only using a single thread for picture computation.
If you are running a system with multiple CPU's or cores setting this to 1 can greatly speed up the computation of pictures.
The default setting causes SONAR to perform disk reads (for audio playback) before attempting any disk writes (for audio recording). Overriding this value by setting it to 1 causes SONAR to attempt disk writes first. This yields the best results when you are attempting to record a large number of tracks at high latency.
This variable determines how SONAR performs writes to disk in cases where multiple inputs are being recorded simultaneously. The default setting causes SONAR to write all the data for all inputs all at once, and then wait for the entire set of writes to complete. Overriding this value by setting it to 0 causes SONAR to perform each input’s write separately, and wait for each individual write to complete before proceeding to the next one.
<0 to no upper limit>
It instructs SONAR to set aside extra audio data buffers, to accommodate plug-ins which do large amount of internal buffering and therefore "keep" data buffers to themselves. Recommended maximum setting of 64 or 128.
This line goes in the section of the Aud.ini file under [name of your sound card (‘n’ in , ‘n’ out) ]. If you get an error message when you try to change the audio driver bit depth to 24, try setting this line to 1. Most USB audio devices that use WDM drivers need this line set to 1.
The audio engine will now render a smooth fade in whenever audio playback is interrupted and there is a abrupt transition in gain. The purpose of doing this is to dezipper (smooth out) the gain transition due to the discontinuity. For example, if you click on the time ruler to jump to a new time location during playback, the engine will smoothly render the transition to the new gain level as a fade in. This smoothing also takes place whenever playback gapping occurs. You can control the fade in time via the GapDezipperUsec variable, which is expressed in microseconds per dB and controls the speed of the fade in to the new gain value. (default = 500 microseconds. i.e. the fade will take 500 microseconds per change in dB at the transition point). You may increase or shorten the time of the fade by increasing or decreasing this value. The normal legal value range for this variable is 0 to 1000 microseconds.
This variable should be set in the [Wave] section. A value of zero turns off dezippering on gapping completely.
This variable is similar to GapDezipperUsec except that it controls how the mixer itself renders abrupt gain transitions due to envelopes in the project. This variable is expressed in microseconds per dB and controls the speed of the fade in to the new gain value (default = 50 microseconds). The normal legal value range for this variable is 0 to 1000 microseconds.
This variable should be set in the [Wave] section. Important: Changing the value of this variable will affect how envelopes are rendered by the mixer and may cause your mixes to sound slightly different. Setting MixDezipperUsec too low can cause clicks while rendering abrupt gain changes due to envelopes.
A value of 1 (default) allows multiprocessing during fast bounce when multiprocessing is enabled in SONAR. Set to 0 to temporarily disable multi-threaded mixing mixing during a fast bounce operation.
If this is set TRUE, pre fader sends on both tracks and buses are automatically muted when the track/bus is muted. Also if another track is soloed the pre fader sends on other tracks will be muted.
The integrated channel EQ is pre effects bin by default, 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).
This is a line in the Wave section of the Aud.ini file that sets the buffer size for bouncing tracks. At a value of 0, the bounce buffer is the same size as the Mixing Latency value that you set in Edit > Preferences > Audio - Driver Settings. If you find that bouncing tracks, especially with certain soft synths, takes a very long time, you can set this value to 100, or some value between 0 and 350 so that the bounce buffer will use a more efficient size for bouncing, which has different requirements from normal playback latency.
Note: on larger projects, setting this variable to a large value can cause out-of-memory errors.
Under high system load conditions, the SONAR audio pump mechanism may become starved. When this condition is detected, SONAR drops out. The DropoutMsec variable allows you to configure the tolerance time in milliseconds. This variable applies to all driver modes.
Setting DropoutMsec to a positive value > 0 specifies the actual time in milliseconds to tolerate before dropping out due to starvation.
Setting DropoutMsec to a negative value < 0 means we use a multiple of the audio buffer size as the tolerance. i.e. -2 means we use twice the audio buffer size.
Note that setting this value too low (e.g. 0) can result in more frequent dropouts in the program. If you notice too many dropouts, try raising it in buffer multiples or by explicitly specifying a millisecond value.
This is a line in the [Wave] section of the Aud.ini file that controls whether VST plug-ins are suspended and resumed prior to starting a bounce operation.
When set to 1 (default), VST plug-ins are suspended and resumed both before and after the bounce process. This flushes any residual buffers that might be present from plugins that have internal latency.
This is a line in the Wave section of the Aud.ini file that specifies whether SONAR uses multichannel audio devices as multiple stereo pairs or just a single stereo pair.
This is a line in the Wave section of the Aud.ini file that specifies whether SONAR uses multichannel audio devices as multiple stereo pairs or just a single stereo pair.
This is a line in the Wave section of the Aud.ini file that controls whether or not audio devices are reset in response to transport changes (play/stop).
<task name>
By default, SONAR uses the MMCSS task profile named Pro Audio. If desired, you can instruct SONAR to use a custom MMCSS task profile.
This determines whether SONAR manages the ASIO thread priority when necessary. This defaults to 1.
This variable enables disk write thru caching. 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.
This variable specifies whether preroll buffers are pumped as fast as possible or in real-time.
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.
When using the External Insert plug-in alongside the original dry signal in WDM mode, 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: Setting the value to 2 might have an adverse effect with certain audio hardware, causing recording to drop out. If this occurs, reset the value to 8 and try using ASIO drivers if your hardware has ASIO support.
This variable goes in the [Wave] section and controls the interaction of the main audio thread and worker threads on multiprocessor systems when the Use Multiprocessing Engine option is enabled. Depending on the system, a particular model may result in less glitching and better overall performance. The values are as follows:
1 = (default) Better thread balance. Model is more efficient and can provide cycles for other tasks.
2 = Additional worker thread is created. This may result in improvement with Quad processor systems or higher. Not recommended for Dual processor systems.
This variable applies to ASIO mode only and controls whether SONAR internally compute the sample position based on buffer switch calls or uses the ASIOGetSamplePosition reported value to retrieve the driver reported value.
Some drivers change the reported sample position based on how long a buffer switch took to complete and this can cause problems since SONAR expects the reported position to be in sync with the number of buffers actually streamed.
When using a non-default pan law with floating point or 24-bit audio, SONAR would previously apply the pan law twice; once at the clip level and once more at the track level.
In SONAR 8.5.2 and later, pan laws are only applied once at the track level and only for mono tracks. Any clip pan envelopes will continue to work, but behave strictly as a balance control.
If you have existing projects that use a non-default pan law (i.e. other than 0dB center sin/cos taper), the mix might sound louder in SONAR X2.
When the value is 0 (default), non-default pan laws are not applied at the clip level. Clip pan envelopes always use the (0dB center sin/cos taper) law.
When the value is 1, pan laws are applied at the clip level. It is not recommended that you use this value unless you need to retain backwards compatibility with pre-SONAR X2 projects that use a non-default pan law.

Copyright © 2020 Cakewalk, Inc. All rights reserved
Sitemap | Privacy Policy | Legal