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


The TTSseq.ini file can only be changed using Windows Notepad.
Table 228.  
This line specifies the sync chase delay in 1/10 seconds. During SMPTE/MTC sync, when the position is determined, playback begins at a later time to allow for setup. This line specifies the delay amount. If this value is too long, you always have to wait after starting playback before SONAR locks. If this value is too short—especially on slower computers—then it will try to play before it’s ready, which will cause a spurt of notes to catch up when it actually starts, the effort of which could also cause sync to give up if the CPU is really overtaxed.
This line specifies the SMPTE flywheel time in 1/10 seconds. This is the maximum dropout time length SONAR will allow before aborting sync.
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." Example: MfxLookAhead=480.
This variable controls (globally) whether SONAR sends MIDI controller resets to DXi’s.
This variable should be set in the [OPTIONS] section. Legal values are:
1: SONAR will send MIDI controller resets to DXi’s. This is what SONAR already does for hardware synths. For example:
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.
This line controls whether or not SONAR creates a General MIDI setup measure when loading Standard MIDI Files.
This line specifies which track is to contain lyrics from Type 0 Standard MIDI files. A zero means track 1, a 1 means track 2, and so on.
This setting specifies the minimum amount of time that must elapse between any two MMC commands. Some MMC gear, including the Fostex MTC-1 and the Tascam SY-88, can get confused unless there is at least a 10-millisecond delay after every MMC command. This can cause intermittent problems on fast machines. SONAR corrects this problem with the MMCDelayMsecs=<n> line. The default value is 100 milliseconds, although some experimentation may be required to find the proper value for your system.
By default, SONAR will transit MMC commands on all MIDI outputs. In some situations it is necessary to limit the number of outputs MMC is transmitting on. This line specifies which output MMC is to be transmitted on. The value is 0 based, so a value of 0 means output 1, and a value of 1 means output 2, etc.
This line specifies the MMC pre-locate amount in 1/10 seconds. By default, SONAR waits for two seconds after it starts receiving time code before beginning to playback or record. You can add this line to change the two-second delay.
If this setting does not exist, the value of the ChaseDelay setting is used. If the ChaseDelay setting does not exist either, then the default for MMCPreRoll is 20.
If all MMC features work except for Auto Punch record mode, your equipment probably doesn't support the MMC Event command (consult with the manufacturer if you aren't sure). You can overcome this limitation by adding this line.
This line determines whether or not SONAR should send a Local Control OFF message during startup.
This line determines whether or not SONAR should send a Local Control ON message at exit.
This line determines whether or not SONAR ignores any MIDI time stamping that a MIDI driver does. If you’re experiencing increasing delays between the time you play a MIDI note on a controller and the time you hear SONAR echo it, setting this line to 1 may help. Also, if you find that SONAR is recording MIDI data at a different time from when the data was played, setting this line to 1 may help. If the MIDI driver is using a different clock from SONAR, the time discrepancy increases the longer that the MIDI driver is open, so you need to tell SONAR to ignore the timestamp that the MIDI driver adds to the data (set the value to 1).
When synching to SMPTE, SONAR normally attempts to track the rate of the incoming sync signal, in order to survive dropouts better when the SMPTE source speed is slightly off. Setting this to 0 defeats this. If you have a slower computer and dense work to play, defeating this can result in a small efficiency improvement and also prevent rate-tracking timing inaccuracies when the computer is so busy that it’s late processing incoming sync messages.
This setting causes SONARSONAR to delay Sysx transmission for a certain amount of time if it encounters an F7 in a Sysx bank. This gives some instruments a required amount of delay time that is necessary to process the Sysx transmission. The default delay is 1/18 of a second, but can be changed by also adding the SysxSendDelayMsecs=<n> line.
This setting causes SONAR to delay a specified number of milliseconds if it encounters an F7 in a Sysx bank.
This line specifies the number of bytes between Sysx transmit delays. Sysx bytes are transmitted in packets, with a 1/18 second delay between each packet. Setting this value smaller will help slower MIDI devices (synthesizers, etc.) avoid overflowing their internal buffers.
This line specifies whether or not SONAR should use nonstandard “Cable” meta-events for storing Sysx bank output number into Standard MIDI files (by default, n=1).
Table 229.  
This variable determines the maximum number of MIDI inputs. The value is 0 based, so a value of 15 means that the limit is 16 outputs.
Table 230.  
This variable determines the maximum number of MIDI outputs. The value is 0 based, so a value of 15 means that the limit is 16 outputs.

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