Revision [1727]
This is an old revision of ParisCfg made by admin on 2010-03-06 16:59:57.
PARIS' Configuration File (paris.cfg)
The paris.cfg file is a "preference" file that stores details of your configuration. It stores preferences pertaining to the global operation of PARIS (such as cache settings, enabling/disabling the MIDI engine or jog shuttle wheel sensitivity).
The paris.cfg file is located in the PARIS application folder. It can be edited from the Project Window in PARIS, but additional parameters and values can be accessed and changed by opening it directly in Notepad (or any other text editor). Be certain there are no typos in your edits, and also be certain to rename it with the .cfg file extension after saving (for example, to edit the paris.cfg on a Macintosh you must change the file extension to .txt in order to open it in eg. Simple Text; after you save the file, you must change the extension back to .cfg).
The "default" configuration settings for PARIS tend to be pretty lean and conservative since they were based on assumptions of the strictly limited capabilities of the host computers of the time. To gain a noticeable performance increase on modern computers, some settings can (and should) be increased to higher values. Since in some cases those values should be much higher than the "select a value" menus in the Project Window will permit, it's a good idea to familiarize yourself with editing Paris.cfg manually.
A numerical "1" by itself is the equivalent of "yes"; a numerical "0" is the equivalent of "no". Thus "MIDIPlayDisabled=1" means "yes, disable MIDI functionality" and "MIDIPlayDisabled=0" would mean "no, leave MIDI running" (MIDI is "enabled" by default).
Inside A Typical paris.cfg
*** PARIS Configuration *** *** ENGINE configuration parameters *** * Cache Size in MB CacheSize=128 * Overview cache size in KB OvwCacheSize=8192 * I/O configuration IOSize=256 * SubMix Cache Size in KB SubMixCacheSize=256 ManualRecDelay=4096 RecXFadeLen=20 Use32BitWinMTC=0 DisableDirectX=0 MasterOutputCard=0 ScrubMaxRate=1 WheelSensitivity=20 WheelInertia=68 CSProVersion=ABCDEFGH VSTDirectory=C:\vsts\ MIDIPlayDisabled=1
[A note about the structure of the Paris.cfg - a line beginning with the asterisk is a "comment", meaning it's ignored by the app - it's merely there to provide you with a reference. The second line gives the actual value (in the following case, 128 MB).]
Paris.cfg line by line:
Cache Size (in mb)
* Cache Size in MB CacheSize=128
Disk I/O (undefined value - perhaps samples?)
* I/O configuration IOSize=256
Edmund's discussion of cache settings follows:
The cache size is determined by two factors:
- The Disk IO Size, and
- Number of REAL tracks of playback.
So for Brian with 80 tracks he will need about 5 times the usual amount. More memory is needed IF you switch to larger disk I/O or have additional submixes (count each virtual submix as a 2 more tracks). There is definitely nothing wrong with using larger disk cache sizes, as long as you have the RAM...
Edmund Pirali
Intelligent Devices, Inc.
Note this interaction:
Here is how it works:
- The only factor that will effect number of tracks played/record is the disk I/O size. The larger the size, the more efficient the disk is (almost always), but slower the response time of PARIS.
- The Disk Cache Size needs to be adjust as you increase the disk I/O until it shows the number of tracks you intent to playback. Thats the only real effect. Also if the disk cache is larger smaller loops MAY play from memory and not require disk access.
- The overview cache size usually does not play into this.
Your SeaGate MAY be fast enough got 24 tracks in 24 bits, but your internal Mac SCSI may not be. You may need a SCSI accelerator card.
Edmund Pirali
Intelligent Devices, Inc.
* Overview cache size in KB OvwCacheSize=8192
Your overview cache is used to store waveform views. It can be safely boosted from this number (hard data coming)
DisableDirectX=0
A value of "0" here turns off PARIS' DirectX plugin subsystem, which can be unstable.
MasterOutputCard=0
As stated, defines your "Card A"
ScrubMaxRate=1
Customize the maximum rate of your "audio scrub" function.
WheelSensitivity=20 WheelInertia=68
Customize the behaviour of your C16's jog/shuttle wheel.
CSProVersion=ABCDEFGH
Each letter assigns a particular C16 to C16 Pro mode.
VSTDirectory=C:\vsts\
Can be used to manually delete a "stubborn" VST Path.
MIDIPlayDisabled=1
See "optional settings" below for more information on disabling MIDI in PARIS.
Optional Settings in your paris.cfg
PARIS has several settings that cannot be accessed via the "Configuration" menu entry in your Project Window. Your PARIS.cfg must be opened in a text editor and edited directly to access them.
1) UseHouseSync
If you are using more than two MECs you must 1) use an external clock source, and 2) enable PARIS to use that clock source by including this line.
UseHouseSync=1
(external word clock enabled)
UseHouseSync=0
(external word clock disabled)
Even if you do not use multiple MECs, you must include that line if you're planning to use external word clock.
2) MIDIPlayDisabled
MIDIPlayDisabled=1
(disables MIDI)
MIDIPlayDisabled=0
(enables MIDI)
This is where you enable or disable the built-in MIDI sequencing functionality in PARIS (note that this does not include MTC, which is unaffected). PARIS MIDI can have a destabilizing effect on your PARIS system, so if you're not going to use PARIS' built-in MIDI sequencing, disabling this is best:
3) VSTDirectory
Your VST Plugins Path looks like this when no path has been specified.
VSTDirectory=
After you specify a path, it looks like this:
VSTDirectory=C:/VSTPlugins [or whatever path you've specified]
Unfortunately, the configuration screen in PARIS is not 100% reliable at removing this information. If you want to completely remove your plugin path, delete all information in the same line so it looks like this again:
VSTDirectory=
4) TestFXEnabled
TestFXEnabled=0
Apparently this setting lets you disable all of your EDS FX, just in case you wanted to know.
5) EDSTransfer
We do not have much hard information on EDSTransfer, but it appears to be a way of customizing the buffers between EDS cards. The first number (before the comma) is reputed to be the Card Transfer Size (the default value is 16k). It seems to affect the speed of the data exchange. The second number (after the comma) appears to be the card buffer count.
It's probably best to consider lowering these values to be effectively overclocking your EDS card. This may or may not be the case technically, but the same trade-offs apply: you can get significant performance increases at a potential cost of system stability and the generation of excess (and potentially damaging) heat that may reduce the life span of your EDS card.
With those cautions in mind, lowering these values to the following can speed transfers to the point where Senderella can transmit between submixes at true zero latency. Users have experimented with the following values. 8,16 has been suggested to produce a more acceptable balance of risk/reward than 8,8.
EDSTransfer=8,16
EDSTransfer=8,8
...(8,8 can work too but streaming with too many tracks
over many cards is problematic) - Dimitrios
