Live 2.1.2 "Options.txt" parameters

UHE is now closed. For Technical Support from Ableton, please go here: http://www.ableton.com/support
Locked
Alex
Posts: 4006
Joined: Wed Apr 03, 2002 1:07 pm
Location: Ableton Headquarter

Live 2.1.2 "Options.txt" parameters

Post by Alex » Sun Jul 06, 2003 10:04 am

Hi folks,

If you have questions about the following "Options.txt" part, feel free to contact support@ableton.com or me ( alex@ableton.com ).


Options.txt for Live 2.1.2
===============================================

With the options.txt file we offer a way to change some options for special circumstances.
Because I can already hear the questions "why not having this stuff in the 'real' preferences?"
The answer simply is that these options are mainly used for developing and internal testing.
But for some of you they could be useful too.


How to use Options.txt
===============================================

First you have to create a text file called "Options.txt" in the same folder where Live's
preferences.cfg file is located.

OS 9: ".../Preferences/Ableton/Live 2.1.2/Options.txt"

OS X: ".../Preferences/Ableton/Live 2.1.2/Options.txt"

Win: ".../Program Files/Ableton/Live 2.1.2/Preferences/Options.txt"



You can of course activate several options in the Options.txt file but only one per line.
The syntax is really simple. Each options begin with a "-" sign (See example below).


If you use a wrong syntax you will get an error message when Live is started.
If you want to be sure that your option was detected you can open Live's log file "Log.txt".
It's located directly beside the Options.txt file. It's a simple text file you can open
with a text viewer/editor.



"ClipFireWillContinueSong"
===============================================
When fireing clip(s) while the song is still stopped the song will continue to play. Without this option the song position will jump back to the play start marker and play from there.
Example: "-ClipFireWillContinueSong"


"ReWireChannels"
===============================================
Number of ReWire channels appearing in the ReWire master when Live runs as ReWire slave.
Default = 16, Min = 0, Max = 64, must be even
Example: "-ReWireChannels=32"



"ReWireMasterOff"
===============================================
Disables ReWire Master functionality.
Example: "-ReWireMasterOff"



"ReWireMasterBufferSize"
===============================================
This could be interesting for Project5 users.
It can be use to change the buffer that is passed to a ReWire slave application.
Currently Live use a fixed size of 256 samples. Some reWire slaves have performance
problems with such small buffers. So you can use this one to increase the buffer.
But be careful: A higer buffersize will also increment the latency on the ReWire slave
side.
Default: 256, Min: 64, Max: 4096.
Example: "-ReWireMasterBufferSize=1024"



"AllowSamplesFromCD"
===============================================
Enables to load Samples directly from CD. Please have in mind that no .asd file
can be written then. If you click on the 'Save' button in the clip settings
you'll get an error message that the .asd file could not be written.
Note: Playing several audio files from a CD can be a performance issue cause
transferring data from a CD is slower than from a harddisk. Additionally it depends
also of the state of the CD.
Example: "-AllowSamplesFromCD"



"FileOpenLimit" (OS X only)
===============================================
Limits the number of simutaniously open files. Default = 1024, Min = 256. Be
careful with max! system limits may apply
Example: "-FileOpenLimit=768"



"SoundManagerBufferSize" (OS 9 only)
===============================================
Size of the audio buffer in frames. Default = 512, Min = 16, Max = 8192
Example "-SoundManagerBufferSize=256"



"AsioNoSetSampleRate" (OS 9 & Win)
===============================================
When accesing your audio hardware using an ASIO driver and you have problems with
setting the sample rate you can try this option so that Live instead of setting
the sample rate always tries the one that#s coming from the audio interface.
Example "-AsioNoSetSampleRate"



"AsioNoSampleRateCheck" (OS 9 & Win)
===============================================
With this option Live will not check if the sample rate of the card is (externally) changed.



"AsioSupportProcessNow" (Win XP & Win2000 only)
===============================================
This options is just currently just useful
if you use an Emagic EMI 2|6 or EMI 6|2 interface on under Windows 2000/XP
Use the ProcessNow flag from Asio callback. The number stands for the timer
rate in ms. As smaller this number is as smaller latencies are possible but
menas aslo more work for the system.
Example: "-AsioSupportProcessNow=1"


"DontUseCoreAudio" (OS X only, Live 2.1.2 only)
===============================================
With this options no CoreAudio device will be accessed by Live.
This canbe helpful to avoid conflicts with other audio hardware
Example: "-DontUseCoreAudio"


regards,
Alex
Last edited by Alex on Mon Oct 06, 2003 4:55 pm, edited 7 times in total.

Agnishvatta
Posts: 101
Joined: Sat Mar 08, 2003 3:50 pm
Location: Mie, Japan

Post by Agnishvatta » Sun Jul 06, 2003 11:05 am

Hello Alex,

I'm just wondering if this stuff will be necessary in Live 3.0, will it be? Are you still planning on adding dynamic ReWire buffersizes?

Now to try out this beta.

Thanks

Alex
Posts: 4006
Joined: Wed Apr 03, 2002 1:07 pm
Location: Ableton Headquarter

Post by Alex » Sun Jul 06, 2003 11:56 am

Hi Agnishvatta,

all or most of these stuff will be necessary in the next bigger release, depending on the particular option. Sooner or later I think that some of them will be obsolete while others will move into Live's "right" preferences.

Dynamic ReWire buffersizes will definitively come but probably not yet in the next release. But this is not decided.

If I remember rigth you wrote in another thread that having both options (dynamicand fixed buffersize) would be the best, where I would totally agree. Dynamic buffersize can be done without user interface change but fixed buffersize and the switch to select between probably not.

regards,
Alex

Agnishvatta
Posts: 101
Joined: Sat Mar 08, 2003 3:50 pm
Location: Mie, Japan

Post by Agnishvatta » Sun Jul 06, 2003 1:14 pm

If I remember rigth you wrote in another thread that having both options (dynamicand fixed buffersize) would be the best, where I would totally agree.
Yes, definately.

Thanks for the other information too.

Locked