<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>  Configuration &lt; Cinelerra &lt; TWiki</title>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />

<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="http://www.ftconsult.com/twiki/bin/view/Cinelerra/WebRss?skin=rss&contenttype=text/xml" />
<!-- <base href="Configuration" /> -->
<style type="text/css" media="all">
	/* Default TWiki layout */
	@import url('../../../pub/TWiki/PatternSkin/layout.css');
	/* Default TWiki style */
	@import url('../../../pub/TWiki/PatternSkin/style.css');
	/* Custom overriding layout per web or per topic */
	@import url('http://www.ftconsult.com/twiki/bin/view/Cinelerra/%USERLAYOUTURL%');
	/* Custom overriding style per web or per topic */
	@import url('http://www.ftconsult.com/twiki/bin/view/Cinelerra/%USERSTYLEURL%');
	.twikiToc li {
		list-style-image:url('../../../pub/TWiki/PatternSkin/i_arrow_down.gif');
	}	        
	.twikiWebIndicator {
		background-color:#D0D0D0;
	}
</style>
<style type="text/css" media="all"></style>
<script type="text/javascript">
<!-- HIDE
	function initPage() { }
-->
</script>
</head>
<body class="twikiViewPage" onload="initPage()"><a name="PageTop"></a>
<div class="twikiHidden"><a href="#Content">Skip to topic</a> | <a href="#PageBottom">Skip to bottom</a><hr /></div><div class="twikiTopBar"><div class="twikiTopBarContents"><form name="top" action="Configuration"> <div class="twikiLeft">
<a href="http://twiki.org/"><img src="../../../pub/TWiki/TWikiLogos/twikiRobot46x50.gif" border="0" alt="Home"/></a>
</div>
<div class="twikiRight twikiSearchBox">
<table border="0" cellpadding="0" cellspacing="0">
<tr>
<td><label for="go">Jump: </label><input type="text" id="go" name="topic" size="16" /></td>
</tr>
</table>
</div>
</form></div></div><div class="twikiMiddleContainer"><div class="twikiLeftBar"><div class="twikiWebIndicator"><b>Cinelerra</b></div>
<div class="twikiLeftBarContents"><form name="main" action="Configuration"> 
<ul>
<li> <b>Cinelerra Web</b>
</li>
<li> <a class="twikiLink" href="WebHome">Cinelerra Web Home</a>
</li>
<li> <a class="twikiLink" href="WebChanges">Changes</a> 
</li>
<li> <a class="twikiLink" href="WebIndex">Index</a>
</li>
<li> <a class="twikiLink" href="WebSearch">Search</a>
</li>
</ul>
<hr />
<ul>
<li> <strong>Webs</strong>
<ul>
<li> <a class="twikiLink" href="WebHome">Cinelerra</a>
</li>
<li> <a class="twikiLink" href="../Espanol/WebHome">Espanol</a>
</li>
<li> <a class="twikiLink" href="../Francais/WebHome">Francais</a>
</li>
<li> <a class="twikiLink" href="../Italiano/WebHome">Italiano</a>
</li>
<li> <a class="twikiLink" href="../Main/WebHome">Main</a>
</li>
<li> <a class="twikiLink" href="../Sandbox/WebHome">Sandbox</a>
</li>
<li> <a class="twikiLink" href="../Slovenian/WebHome">Slovenian</a>
</li>
<li> <a class="twikiLink" href="../TWiki/WebHome">TWiki</a>
</li>
</ul>
</li>
</ul>
<div class="twikiLeftBarPersonal">
<p />
<ul>
<li> <strong>My links</strong>
</li>
<li> <a class="twikiLink" href="../Main/AeliotBoswell">My home page</a>
</li>
<li> <a href="http://www.ftconsult.com/twiki/bin/search/Codev/?search=InterestedParties.*AeliotBoswell&regex=on" target="_top"><img src="../../../pub/TWiki/TWikiDocGraphics/stargold.gif" style="width:16px; height:16px; border:0px;" alt="Show me topics of interest" /></a>
</li>
</ul>
<div class="twikiSmall"><a href="http://www.ftconsult.com/twiki/bin/edit/Main/TWikiGuestLeftBar?t=20051021145529">edit</a></div>
<p />
</div>
</form></div></div><div class="twikiMain"><div class="twikiToolBar"><div>
<ul>
<li> <a href="http://www.ftconsult.com/twiki/bin/edit/Cinelerra/Configuration?t=1129906529"><b>Edit</b></a>
</li>
<li> <a href="http://www.ftconsult.com/twiki/bin/attach/Cinelerra/Configuration">Attach</a>
</li>
<li> <a href="http://www.ftconsult.com/twiki/bin/view/Cinelerra/Configuration?skin=print.pattern">Printable</a>
</li>
</ul>
</div><div class="twikiRevInfo"><span class="twikiGrayText"><span class="twikiToolbarElem">Cinelerra.Configuration</span><span class="twikiToolbarElem">r1.7 - 26 Jun 2005 - 11:26 - <a class="twikiLink" href="../Main/JeanLucCoulon">JeanLucCoulon</a></span><span class="twikiToolbarElem"><a href="#TopicEnd">topic&nbsp;end</a></span></span></div></div>
<div class="twikiHidden"><hr /></div><a name="Content"> </a><div class="twikiHidden">Start of topic | <a href="#Actions">Skip to actions</a><hr /></div>
<div class="twikiTopic">
<h2><a name="Preferences_Configuration"> </a><a name="Preferences_Configuration_"> </a> Preferences <a class="twikiLink" href="Configuration">Configuration</a>  </h2>
<strong>Cinelerra</strong> is a very flexible system cable of working with a large variety of media types, because of this <strong>Cinelerra</strong> cannot be run optimally without some intimate configuration for your specific needs.
<p />
To configure your working environment in <strong>Cinelerra</strong> go to <a class="twikiLink" href="SettingsMenu">SettingsMenu</a> -&gt;preferences and run through the options.
<div class="twikiToc">
<ul>
<li> <a href="#Preferences_Configuration">Preferences Configuration </a>
<ul>
<li> <a href="#ENVIRONMENT_VARIABLES">ENVIRONMENT VARIABLES</a>
</li>
<li> <a href="#LANGUAGE_SUPPORT">LANGUAGE SUPPORT</a>
</li>
<li> <a href="#Preferences_Playback">Preferences Playback</a>
</li>
<li> <a href="#VIDEO_OUT">VIDEO OUT</a>
</li>
<li> <a href="#Preferences_Recording">Preferences Recording</a>
</li>
<li> <a href="#VIDEO_IN">VIDEO IN</a>
</li>
<li> <a href="#Preferences_Performance">Preferences Performance</a>
</li>
<li> <a href="#BACKGROUND_RENDERING">BACKGROUND RENDERING</a>
</li>
<li> <a href="#RENDER_FARM">RENDER FARM</a>
</li>
<li> <a href="#Preferences_Interface">Preferences Interface</a>
</li>
<li> <a href="#Preferences_About">Preferences About</a>
</li>
</ul>
</li>
</ul>
</div>
<p />
<h3><a name="ENVIRONMENT_VARIABLES"> </a> ENVIRONMENT VARIABLES </h3>
<p />
In UNIX derivatives, environment variables are global variables in the shell which all applications can read. They are set with a command like set VARIABLE=value. All the environment variables can be viewed with a command like env. Cinelerra recognizes the following environment variables:
<p />
<h4><a name="LADSPA_PATH"> </a> LADSPA_PATH </h4>
  A colon separated list of directories to search for LADSPA plugins. These are not native Cinelerra plugins. See LADSPA EFFECTS.
<h4><a name="GLOBAL_PLUGIN_DIR"> </a> GLOBAL_PLUGIN_DIR </h4>
  The directory Cinelerra should look for native plugins in. The default is /usr/lib/cinelerra but you may need an alternate directory if you're sharing the same executable directory among many machines via NFS. Plugins of different binary formats need to be in different directories.
<p />
<h3><a name="LANGUAGE_SUPPORT"> </a> LANGUAGE SUPPORT </h3>
Cinelerra has been translated to many languages. Cinelerra language seetings are normally read from your Linux language settings, to run Cinelerra on a language different than the one selected on your system just change the LANG enviroment variable.
<p />
<img src="../../../pub/TWiki/TWikiDocGraphics/tip.gif" border="0" alt="TIP" width="16" height="16" /> Example : open a shell and type:  <strong>export LANG=es_ES</strong> , then run cinelerra from the same shell, and cinelerra will open set on the Spanish language.
<p />
Available languages 
<ul>
<li> es_ES  - Espanol
</li>
<li> sl_SI  - Slovenian
</li>
<li> fr_FR  - Franais
</li>
<li> <img src="../../../pub/TWiki/TWikiDocGraphics/pencil.gif" border="0" alt="REFACTOR" width="16" height="16" /> insert more languages here
</li>
</ul>
<p />
<h3><a name="Preferences_Playback"> </a><a name="_Preferences_Playback_"> </a> <a class="twikiLink" href="PreferencesPlayback">Preferences Playback</a> </h3>
<img src="../../../pub/Cinelerra/CinelerraImages/preferences_playback.png"/>
<p />
<h4><a name="AUDIO_OUT"> </a> AUDIO OUT </h4>
<p />
These determine what happens when you play sound from the timeline.
<p />
<h5><a name="SAMPLES_TO_READ_FROM_DISK"> </a><a name="SAMPLES_TO_READ_FROM_DISK_"> </a> SAMPLES TO READ FROM DISK (( Cinlerra 1.2 does not need this anymore!, also new screenshot is needed) </h5>
<p />
      Cinelerra uses a pipeline for rendering audio. The first stage is reading large chunks of audio from disk, the samples to read from disk. This is followed by processing small fragments in a virtual console.
<h5><a name="SAMPLES_TO_SEND_TO_CONSOLE"> </a><a name="SAMPLES_TO_SEND_TO_CONSOLE_"> </a> SAMPLES TO SEND TO CONSOLE: </h5>
<p />
      The second stage is rendering small fragments through the virtual console to the sound driver. A larger value here causes more latency when you change mixing parameters but gives more reliable playback.
<p />
      Some sound drivers don't allow changing of the console fragment so latency is unchanged no matter what this value is.
<h5><a name="VIEW_FOLLOWS_PLAYBACK"> </a> VIEW FOLLOWS PLAYBACK </h5>
<p />
      Causes the timeline window to scroll when the playback cursor moves out of view. This can bog down the X Server.
<h5><a name="USE_SOFTWARE_FOR_POSITIONING_INF"> </a> USE SOFTWARE FOR POSITIONING INFORMATION </h5>
<p />
      Most soundcards and sound drivers don't give reliable information on the number of samples the card has played. When playing video you need this information for synchronization. This option causes the sound driver to be ignored and a software timer to be used for synchronization.
<h5><a name="AUDIO_PLAYBACK_IN_REALTIME"> </a><a name="AUDIO_PLAYBACK_IN_REALTIME_"> </a> AUDIO PLAYBACK IN REALTIME: </h5>
<p />
      Back in the days when 150Mhz was the maximum, this allowed uninterrupted playback on heavy loads. Now you'll probably only need it for playing video and audio when the load is to high for uninterrupted audio.
<h5><a name="AUDIO_DRIVER"> </a> AUDIO DRIVER </h5>
<p />
      There are many sound drivers for Linux. This allows selecting one and setting parameters specific to it. Some of the common parameters for a sound driver are
<h6><a name="DEVICE_PATH"> </a> DEVICE PATH </h6>
<p />
            Usually a file in the /dev/ directory which controls the device.
<h6><a name="BITS"> </a> BITS </h6>
<p />
            The number of bits of precision Cinelerra should set the device for. This sometimes has a figuritive meaning. Some sound drivers need to be set to 32 bits to perform 24 bit playback and won't play anything when set to 24 bits. Some sound drivers need to be set to 24 bits for 24 bit playback.
<h6><a name="CHANNELS"> </a> CHANNELS </h6>
<p />
      The number of channels Cinelerra should set the device for. Regardless of the number of channels in the project, the number of channels set here will be written to the device. When this is set to 2 and the project has 1 channel you'll hear sound through the left speaker and not centered as expected for a monaural project. When this is set to 1 and the project has 2 channels you'll hear the left channel centered and not 2 channels mixed together.
<p />
<p />
<h3><a name="VIDEO_OUT"> </a> VIDEO OUT </h3>
<p />
These determine what happens when you play video from the timeline.
<p />
<h4><a name="FRAMERATE_ACHIEVED"> </a> FRAMERATE ACHIEVED </h4>
<p />
      The number of frames per second being displayed during playback.
<h4><a name="SCALING_EQUATION"> </a> SCALING EQUATION </h4>
<p />
      The algorithm used in all video resizing in the virtual console. This doesn't affect scaling to the size of the compositor window.
<h5><a name="NEAREST_NEIGHBOR_ENLARGE_AND_RED"> </a> NEAREST NEIGHBOR ENLARGE AND REDUCE </h5>
<p />
            lowest but fastest quality. Produces jagged edges and uneven motion.
<h5><a name="BICUBIC_ENLARGE_AND_BILINEAR_RED"> </a> BICUBIC ENLARGE AND BILINEAR REDUCE </h5>
<p />
            highest but slowest quality. For enlarging a bicubic interpolation is used, which blurs slightly but doesn't reveal stair steps. For reduction a bilinear interpolation is used, which produces very sharp images and reduces noise. The bilinear reduced images can be sharpened with a sharpen effect with less noise than a normal sized image.
<h5><a name="BILINEAR_ENLARGE_AND_BILINEAR_RE"> </a> BILINEAR ENLARGE AND BILINEAR REDUCE </h5>
<p />
      when slight enlargement is needed a bilinear enlargement looks better than a bicubic enlargement.
<p />
<h4><a name="PRELOAD_BUFFER_FOR_QUICKTIME"> </a> PRELOAD BUFFER FOR QUICKTIME </h4>
<p />
      The Quicktime/AVI decoder can handle CDROM sources better when this is around 1000000. This reduces the amount of seeking. For normal use this should be 0.
<h4><a name="MPEG_4_DEBLOCKING_FIXME_NOT_PRES"> </a> MPEG-4 DEBLOCKING (FIXME - NOT PRESENT ANYMORE IN 1.2 - i think it is on by default but still available in the config files -- andraz) </h4>
<p />
      For assets which are compressed in <span class="twikiNewLink" style="background : #FFFFCE;"><font color="#0000FF">OpenDivx</font><a href="http://www.ftconsult.com/twiki/bin/edit/Cinelerra/OpenDivx?topicparent=Cinelerra.Configuration"><sup>?</sup></a></span> and Quicktime, this enables deblocking. This greatly improves the picture quality during decoding while slowing it down.
<h4><a name="VIDEO_DRIVER"> </a> VIDEO DRIVER </h4>
<p />
      Normally video on the timeline goes to the compositor window during continuous playback and when the insertion point is repositioned. Instead of sending video to the Compositor window the video driver can be set to send video to another output device during continuous playback. This doesn't affect where video goes when the insertion point is repositioned, however.
<p />
      Various parameters are given for Video Driver depending on the driver.
<h4><a name="DISPLAY"> </a> DISPLAY </h4>
<p />
            The is intended for dual monitor displays. Depending on the value of Display, the Compositor window will appear on a different monitor from the rest of the windows.
<h4><a name="DEVICE_PATH"> </a> DEVICE PATH </h4>
<p />
            Usually a file in the /dev/ directory which controls the device.
<h4><a name="SWAP_FIELDS"> </a> SWAP FIELDS </h4>
<p />
            Make the even lines odd and the odd lines even when sending to the device. On an NTSC or 1080i monitor the fields may need to be swapped to prevent jittery motion.
<h4><a name="OUTPUT_CHANNEL"> </a> OUTPUT CHANNEL </h4>
<p />
            Devices with multiple outputs may need a specific connector to send video on.
<h4><a name="PORT"> </a> PORT </h4>
<p />
            The IEEE1394 standard specifies something known as the port. This is probably the firewire card number in the system to use.
<h4><a name="CHANNEL"> </a> CHANNEL </h4>
<p />
      The IEEE1394 standard specifies something known as the channel. For DV cameras it's always 63.
<p />
<p />
-- <a class="twikiLink" href="../Main/AlexFerrer">AlexFerrer</a> - 17 Dec 2003 Copied from <a class="twikiLink" href="SecretsOfCinelerra">SecretsOfCinelerra</a>
<p />
<hr />
<p />
<p />
<h3><a name="Preferences_Recording"> </a><a name="_Preferences_Recording_"> </a> <a class="twikiLink" href="PreferencesRecording">Preferences Recording</a> </h3>
<img src="../../../pub/Cinelerra/CinelerraImages/preferences_recording.png" alt="preferences_recording.png" />
<p />
<h4><a name="AUDIO_IN"> </a> AUDIO IN </h4>
<p />
These determine what happens when you record audio.
<p />
<h4><a name="RECORD_DRIVER"> </a> RECORD DRIVER </h4>
<p />
      This is used for recording audio in the Record window. It may be shared with the Record Driver for video if the audio and video are wrapped in the same stream. It takes variable parameters depending on the driver. The parameters have the same meaning as they do for playback.
<h5><a name="DEVICE_PATH"> </a> DEVICE PATH </h5>
<p />
            Usually a file in the /dev/ directory which controls the device.
<h5><a name="BITS"> </a> BITS </h5>
<p />
            The number of bits of precision Cinelerra should set the device for. This sometimes has a figuritive meaning. Some sound drivers need to be set to 32 bits to perform 24 bit recording and won't record anything when set to 24 bits. Some sound drivers need to be set to 24 bits for 24 bit recording.
<h5><a name="CHANNELS"> </a> CHANNELS </h5>
<p />
      The number of channels Cinelerra should set the device for. Regardless of the number of channels in the record operation, the number of channels set here will be read from the device. When this is set to 2 and the record operation has 1 channel you'll record the left speaker and not a mix of the left and right speakers as expected for a monaural project. When this is set to 1 and the project has 2 channels you'll record the left and right channels mixed into the left speaker and not 1 channel spead across two speakers.
<p />
<h4><a name="SAMPLES_TO_WRITE_AT_A_TIME"> </a> SAMPLES TO WRITE AT A TIME </h4>
<p />
      Audio is first read in small fragments from the device. Many small fragments are combined into a large fragment before writing to disk. The disk writing process is done in a different thread. The value here determines how large the combination of fragments is for each disk write.
<h4><a name="SAMPLE_RATE_FOR_RECORDING"> </a> SAMPLE RATE FOR RECORDING </h4>
<p />
Regardless of what the project settings are. This is the sample rate used for recording. This should be the highest the audio device supports.
<p />
<h3><a name="VIDEO_IN"> </a> VIDEO IN </h3>
<p />
These determine what happens when you record video.
<p />
<h4><a name="RECORD_DRIVER"> </a> RECORD DRIVER </h4>
<p />
      This is used for recording video in the Record window. It may be shared with the Record Driver for audio if the audio and video are wrapped in the same stream. It takes variable parameters depending on the driver. The parameters have the same meaning as they do for playback.
<h4><a name="FRAMES_TO_RECORD_TO_DISK_AT_A_TI"> </a> FRAMES TO RECORD TO DISK AT A TIME </h4>
<p />
      Frames are recorded in a pipeline. First frames are buffered in the device. Then they're read into a larger buffer for writing to disk. The disk writing is done in a different thread as the device reading. For certain codecs the disk writing uses multiple processors. This value determines how many frames are written to disk at a time.
<h4><a name="FRAMES_TO_BUFFER_IN_DEVICE"> </a> FRAMES TO BUFFER IN DEVICE </h4>
<p />
      The number of frames to store in the device before reading. This determines how much latency there can be in the system before frames are dropped.
<h4><a name="USE_SOFTWARE_FOR_POSITIONING_INF"> </a> USE SOFTWARE FOR POSITIONING INFORMATION </h4>
<p />
      Video uses audio for
<p />
      synchronization but most soundcards don't give accurate position information. This calculates an estimation of audio position in software instead of the hardware for synchronization.
<h4><a name="SYNC_DRIVES_AUTOMATICALLY"> </a> SYNC DRIVES AUTOMATICALLY </h4>
<p />
      For high bitrate recording the drives may be fast enough to store the data but Linux may wait several minutes and stall as it writes several minutes of data at a time. This forces Linux to flush its buffers every second instead of every few minutes and produce slightly better realtime behavior.
<h4><a name="SIZE_OF_CAPTURED_FRAME"> </a> SIZE OF CAPTURED FRAME </h4>
<p />
      This is the size of the frames recorded. It is independant of the project frame size because most video devices only record a fixed frame size. If the frame size given here isn't supported by the device it might crash Cinelerra.
<h4><a name="FRAME_RATE_FOR_RECORDING"> </a> FRAME RATE FOR RECORDING </h4>
<p />
The frame rate recorded is different from the project settings. This sets the recorded frame rate.
<p />
-- <a class="twikiLink" href="../Main/AlexFerrer">AlexFerrer</a> - 17 Dec 2003
<hr />
<p />
<p />
<h3><a name="Preferences_Performance"> </a><a name="_Preferences_Performance_"> </a> <a class="twikiLink" href="PreferencesPerformance">Preferences Performance</a> </h3>
<img src="../../../pub/Cinelerra/CinelerraImages/preferences_performance.png" alt="preferences_performance.png" />
<p />
You'll spend most of your time configuring this section. The main focus of performance is rendering parameters not available in the rendering dialog.
<p />
<h4><a name="CACHE_ITEMS"> </a> CACHE ITEMS </h4>
<p />
      To speed up rendering, several assets are kept open simultaneously. This determines how many are kept open. A number too large may exhaust your memory pretty fast and result in a crash. A number too small may result in slow playback as assets need to be reopened more frequently.
<h4><a name="SECONDS_TO_PREROLL_RENDERS"> </a> SECONDS TO PREROLL RENDERS </h4>
<p />
      Some effects need a certain amount of time to settle in. This sets a number of seconds to render without writing to disk before the selected region is rendered. When using the renderfarm you'll sometimes need to preroll to get seemless transitions between the jobs. Every job in a renderfarm is prerolled by this value. This does not affect background rendering, however. Background rendering uses a different preroll value.
<h4><a name="FORCE_SINGLE_PROCESSOR_USE"> </a> FORCE SINGLE PROCESSOR USE </h4>
<p />
Cinelerra tries to use all processors on the system by default but sometimes you'll only want to use one processor, like in a renderfarm client. This forces only one processer to be used. The operating system, however, usually uses the second processor anyway for disk access so this option is really a 1.25 processor mode. The value of this parameter is used in renderfarm clients. 
<p />
<h3><a name="BACKGROUND_RENDERING"> </a> BACKGROUND RENDERING </h3>
<p />
Background rendering was originally concieved to allow HDTV effects to be displayed in realtime. Background rendering causes temporary output to constantly be rendered while the timeline is being modified. The temporary output is played during playack whenever possible. It's very useful for transitions and previewing effects which are too slow to display in a reasonable amount of time. If renderfarm is enabled, the renderfarm is used for background rendering, giving you the potential for realtime effects if enough network bandwidth and CPU nodes exist.
<p />
<h4><a name="FRAMES_PER_BACKGROUND_RENDERING"> </a><a name="FRAMES_PER_BACKGROUND_RENDERING_"> </a> FRAMES PER BACKGROUND RENDERING JOB </h4>
<p />
      This only works if renderfarm is being used, otherwise background rendering creates a single job for the entire timeline. The number of frames specified here is scaled to the relative CPU speed of rendering nodes and used in a single renderfarm job. The optimum number is 10 - 30 since network bandwidth is used to initialize each job.
<h4><a name="FRAMES_TO_PREROLL_BACKGROUND"> </a> FRAMES TO PREROLL BACKGROUND </h4>
<p />
      This is the number of frames to render ahead of each background rendering job. Background rendering is degraded when preroll is used since the jobs are small. When using background rendering, this number is ideally 0. Some effects may require 3 frames of preroll.
<h4><a name="OUTPUT_FOR_BACKGROUND_RENDERING"> </a> OUTPUT FOR BACKGROUND RENDERING </h4>
<p />
      Background rendering generates a sequence of image files in a certain directory. This parameter determines the filename prefix of the image files. It should be on a fast disk, accessible to every node in the renderfarm by the same path. Since hundreds of thousands of image files are usually created, ls commands won't work in the background rendering directory. The magnify.png browse button for this option normally won't work either, but the wrench.png configuration button for this option works.
<h4><a name="FILE_FORMAT"> </a> FILE FORMAT </h4>
<p />
The file format for background rendering has to be a sequence of images. The format of the image sequence determines the quality and speed of playback. JPEG is good most of the time.
<p />
<h3><a name="RENDER_FARM"> </a> RENDER FARM </h3>
To use the renderfarm set these options. Ignore them for a standalone system
<p />
<h4><a name="USE_RENDER_FARM_FOR_RENDERING"> </a> USE RENDER FARM FOR RENDERING </h4>
<p />
      When selected, all the file-&gt;render operations use the renderfarm.
<h4><a name="NODES"> </a> NODES </h4>
<p />
      Displays all the nodes on the renderfarm and which ones are active.
<p />
      Nodes are added by entering the host name of the node, verifying the value of port and hitting add node.
<p />
      Computer freaks may be better off editing the ~/.bcast/.Cinelerra_rc file than this if they have hundreds of nodes. Remember that .Cinelerra_rc is overwritten whenever a copy of Cinelerra exits.
<p />
      Select the ON column to activate and deactivate nodes once they are created.
<p />
      Nodes may be edited by highlighting a row and hitting apply changes.
<h4><a name="HOSTNAME"> </a> HOSTNAME </h4>
<p />
      Edit the hostname of an existing node or enter the hostname of a new node here.
<h4><a name="PORT"> </a> PORT </h4>
<p />
      Edit the port of an existing node or enter the port of a new node here.
<h4><a name="REPLACE_NODE"> </a> REPLACE NODE </h4>
<p />
      When editing an existing node, hit this to commit the changes to HOSTNAME and PORT. The changes won't be committed if you don't hit this button.
<h4><a name="ADD_NODE"> </a> ADD NODE </h4>
<p />
      Create a new node with the HOSTNAME and PORT settings.
<h4><a name="DELETE_NODE"> </a> DELETE NODE </h4>
<p />
      Deletes whatever node is highlighted in the NODES list.
<h4><a name="SORT_NODES"> </a> SORT NODES </h4>
<p />
      Sorts the NODES list based on the hostname.
<h4><a name="RESET_RATES"> </a> RESET RATES </h4>
<p />
      This sets the framerate for all the nodes to 0. Frame rates are used to scale job sizes based on CPU speed of the node. Frame rates are only calculated when renderfarm is enabled.
<h4><a name="USE_VIRTUAL_FILESYSTEM"> </a> USE VIRTUAL FILESYSTEM </h4>
<p />
      Normally the directory on the master node containing the source and destination assets is mounted on the clients. The assets on the clients should be visible in the same locations as they are on the master node. This can be hard to set up and requires root access.
<p />
      A user level version of NFS was built into Cinelerra and called the Virtual File System. This transparently redirects all file I/O over the network without requiring a replication of the master node's directory structure or root access on the client. The client sees the exact directory structure on the master node but in reality is sending network packets to access it.
<p />
      There is a penalty for doing this though, since Virtual Filesystem isn't as refined as NFS. Operations that access one byte at a time are really slow.
<p />
      Certain file format parsers are extemely slow over the Virtual Filesystem because they access very small amounts of data at a time. The PCM audio formats do this. These are best rendered using NFS.
<p />
      Unless you need to run rendering clients without root access or have a lot of assets in different directories, use NFS instead.
<h4><a name="TOTAL_JOBS_TO_CREATE"> </a> TOTAL JOBS TO CREATE </h4>
<p />
      Determines the number of jobs to dispatch to the renderfarm. The more jobs you create, the more finely balanced the renderfarm becomes.
<p />
Determine the total jobs to create by multiplying the number of nodes including the master node by some number. Multiply them by 1 to have one job dispatched for every node. Multiply them by 3 to have 3 jobs dispatched for every node. If you have 10 slave nodes and one master node, specify 33 to have a well balanced renderfarm.
<p />
<p />
<p />
-- <a class="twikiLink" href="../Main/AlexFerrer">AlexFerrer</a> - 18 Dec 2003 Copied from <a class="twikiLink" href="SecretsOfCinelerra">SecretsOfCinelerra</a>
<hr />
<p />
<p />
<h3><a name="Preferences_Interface"> </a><a name="_Preferences_Interface_"> </a> <a class="twikiLink" href="PreferencesInterface">Preferences Interface</a> </h3>
<img src="../../../pub/Cinelerra/CinelerraImages/preferences_interface.png"/>
<p />
These parameters affect purely how the user interface works.
<p />
<h4><a name="INDEX_FILES_GO_HERE"> </a> INDEX FILES GO HERE </h4>
<p />
      Back in the days when 4 MB/sec was unearthly speed for a hard drive, index files were introduced to speed up drawing the audio tracks. This option determines where index files are placed on the hard drive.
<h4><a name="SIZE_OF_INDEX_FILE"> </a> SIZE OF INDEX FILE </h4>
<p />
      Determines the size of an index file. Larger index sizes allow smaller files to be drawn faster while slowing down the drawing of large files. Smaller index sizes allow large files to be drawn faster while slowing down small files.
<h4><a name="NUMBER_OF_INDEX_FILES_TO_KEEP"> </a> NUMBER OF INDEX FILES TO KEEP </h4>
<p />
      To keep the index directory from becoming unruly, old index files are deleted. This determines the maximum number of index files to keep in the directory.
<h4><a name="DELETE_ALL_INDEXES"> </a> DELETE ALL INDEXES </h4>
<p />
      When you change the index size or you want to clean out excessive index files, this deletes all the index files.
<h4><a name="USE_HOURS_MINUTES_SECONDS_XXX"> </a> USE HOURS:MINUTES:SECONDS.XXX </h4>
<p />
      Various representations of time are given. Select the most convenient one. The time representation can also be changed by CTRL clicking on the time ruler.
<h4><a name="USE_THUMBNAILS"> </a> USE THUMBNAILS </h4>
<p />
      The Resource Window displays thumbnails of assets by default. This can take a long time to set up. This option disables the thumbnails.
<h4><a name="CLICKING_IN_OUT_POINTS_DOES_WHAT"> </a> CLICKING IN/OUT POINTS DOES WHAT </h4>
<p />
      Cinelerra not only allows you to perform editing by dragging in/out points but also defines three seperate operations which occur when you drag an in/out point. For each mouse button you select the behavior in this window. The usage of each editing mode is described in editing.
<h4><a name="MIN_DB_FOR_METER"> </a> MIN DB FOR METER </h4>
<p />
      Some sound sources have a lower noise threshold than others. Everything below the noise threshold is meaningless. This option sets the meters to clip below a certain level. Consumer soundcards usually bottom out at -65. Professional soundcards bottom out at -90.
<h4><a name="FORMAT_FOR_METER_FIXME_not_avail"> </a> FORMAT FOR METER (FIXME: not available anymore in 1.2 -- by minmax) </h4>
<p />
      This option allows you to select the format for all the VU meters. If you're a CS major select percentage and if you're a EE major select DB. With that, be aware all levels in Cinelerra are input as DB.
<h4><a name="THEME"> </a> THEME </h4>
<p />
Cinelerra supports variable themes. Select one here and restart Cinelerra to see it.
<p />
<p />
<p />
-- <a class="twikiLink" href="../Main/AlexFerrer">AlexFerrer</a> - 18 Dec 2003 copied from <a class="twikiLink" href="SecretsOfCinelerra">SecretsOfCinelerra</a>
<hr />
<p />
<p />
<h3><a name="Preferences_About"> </a><a name="_Preferences_About_"> </a> <a class="twikiLink" href="PreferencesAbout">Preferences About</a> </h3>
<img src="../../../pub/Cinelerra/CinelerraImages/preferences_about.png"/>
<p />
ABOUT
<p />
This section gives you information about the copyright, the time of the current build, the lack of a warranty, and the versions of some of the libraries. Be sure to agree to the terms of the lack of the warranty. 
<p />
<p />
-- <a class="twikiLink" href="../Main/AlexFerrer">AlexFerrer</a> - 18 Dec 2003 copied from <a class="twikiLink" href="SecretsOfCinelerra">SecretsOfCinelerra</a>
<hr />
<p />
<p />
<p />
-- <a class="twikiLink" href="../Main/AlexFerrer">AlexFerrer</a> - 17 Dec 2003 From <a class="twikiLink" href="SecretsOfCinelerra">SecretsOfCinelerra</a>
<hr />
<br class="twikiClear" />
<a name="TopicEnd"></a>
<span class="twikiRight twikiPageNav twikiGrayText"><a href="#PageTop">to&nbsp;top</a></span><br class="twikiClear" />
</div><div class="twikiHidden"><hr />End of topic<br /><a href="#Actions">Skip to action links</a> | <a href="#PageTop">Back&nbsp;to&nbsp;top</a><hr /></div>
<!---->
<!---->
<a name="Actions"> </a><span class="twikiHidden"><br /></span><div class="twikiTopicAction"><a href="http://www.ftconsult.com/twiki/bin/edit/Cinelerra/Configuration?t=1129906529"><b>Edit</b></a> <span class="twikiSeparator">|</span> <a href="http://www.ftconsult.com/twiki/bin/attach/Cinelerra/Configuration">Attach image or document</a> <span class="twikiSeparator">|</span> <a href="http://www.ftconsult.com/twiki/bin/view/Cinelerra/Configuration?skin=print.pattern">Printable version</a> <span class="twikiSeparator">|</span> <a href="http://www.ftconsult.com/twiki/bin/view/Cinelerra/Configuration?raw=on">Raw text</a> <span class="twikiSeparator">|</span> <a href="http://www.ftconsult.com/twiki/bin/oops/Cinelerra/Configuration?template=oopsmore&param1=1.7&param2=1.7">More topic actions</a><br />Revisions:  | r1.7 | <a href="http://www.ftconsult.com/twiki/bin/rdiff/Cinelerra/Configuration?rev1=1.7&rev2=1.6">&gt;</a> | <a href="http://www.ftconsult.com/twiki/bin/view/Cinelerra/Configuration?rev=1.6">r1.6</a> | <a href="http://www.ftconsult.com/twiki/bin/rdiff/Cinelerra/Configuration?rev1=1.6&rev2=1.5">&gt;</a> | <a href="http://www.ftconsult.com/twiki/bin/view/Cinelerra/Configuration?rev=1.5">r1.5</a> <span class="twikiSeparator">|</span> <a href="../../rdiff/Cinelerra/Configuration">Total page history</a> <span class="twikiSeparator">|</span> <a href="http://www.ftconsult.com/twiki/bin/search/Cinelerra/SearchResult?scope=text&regex=on&excludetopic=Configuration&search=Configuration%5B%5EA-Za-z0-9%5D">Backlinks</a></div>
<div class="twikiTopicInfo twikiRevInfo twikiGrayText twikiMoved"></div>
<div class="twikiTopicFooter"><span class="twikiLeft"><span class="twikiHomePath">You are here: <a class="twikiLink" href="WebHome">Cinelerra</a>  <span class='twikiSeparator'>&gt;</span> <a class="twikiLink" href="CinelerraManualTOC">CinelerraManualTOC</a> &gt; <a class="twikiLink" href="UsingCinelerra">UsingCinelerra</a> <span class='twikiSeparator'>&gt;</span> Configuration </span></span><span class="twikiHidden"><br /><br /></span><span class="twikiRight twikiPageNav twikiGrayText"><a href="#PageTop">to&nbsp;top</a></span><br class="twikiClear" /><span class="twikiHidden"><br /></span></div>
<a name="PageBottom"></a> </div></div><div class="twikiBottomBar"><div class="twikiBottomBarContents"><span class="twikiGrayText">Copyright &copy; 1999-2005 by the contributing authors. 
All material on this collaboration platform is the property of the contributing authors. <br /> 
Ideas, requests, problems regarding TWiki? <a href="mailto:alex@ftconsult.com?subject=TWiki&#32;Feedback&#32;on&#32;TWiki.WebBottomBar">Send feedback</a>
</span></div></div>
</body></html>