Start-up Options
There are a number of start-up options that you can use with the command under special circumstances. More than one start-up option can be specified on the command line. These start-up options are case-sensitive.
You can see an on-screen list of these start-up options by typing:
Framestore-Related Start-up Options
| Type: | To: |
|---|---|
| Initialise the framestore volume (all projects). | |
| Specify the remote host name. | |
| Specify the framestore name. | |
| Remove all clips from the project. | |
| Initialise only the Desktop for the selected project. | |
| Activate repair mode. This option enables vic to search the media library and replace missing frame ids with a LOST frame label. In the library, the names of impacted clips appear red. When these clips are loaded into the record timeline, the names of the affected segments also appear red. Lost frames are displayed with the LOST label over them. The flag set on clips is not permanent, so resaving the clip will remove the red from the names. |
Audio sources are stored on the framestore, so initialising the framestore also removes all audio clips from the project.
Project Management-Related Start-up Options
| Type: | To: |
|---|---|
| <filename.cfg> | Use a configuration file other than the default, where <filename.cfg> is the name of the file. The specified file supersedes the default configuration file. If you do not use the option, Flame looks first for init.cfg, and if that is not found, it looks for flame.cfg. |
| <project> | Define the project that appears in the Project Management menu when you start Flame, where <project> is the name of the project you want to use. If you start Flame with both the and options, Flame bypasses the Project Management menu. |
| <user> | Define the user that appears in the Project Management menu when you start Flame, where <user> is the name of the user you want to use. If you start Flame with both the and options, Flame bypasses the Project Management menu. |
Miscellaneous Start-up Options
| Type: | To: |
|---|---|
| Force Flame to install new fonts that you added to the directory /usr/lib/DPS/outline/base (and /usr/lib/DPS/AFM if you have also installed the corresponding font metric file). See Installing Fonts. | |
| Prevent the broadcast monitor from blanking when an image viewer
or Player is not displayed. The broadcast monitor then displays
the screen content that is displayed in the corresponding region. This option is hardware dependent and may not work on all hardware configurations. |
|
| Disable writing to the .log file. Flame keeps a log file of your actions in a text file (.log) in your Flame home directory. Usually this file is cleared and recreated every time Flame is started. (Note that the log file is useful when reporting problems to Customer Support.) | |
| Append the current session to the existing log file. (See description of the log file above.) | |
| Define the amount of memory assigned to frame buffering. This option overrides the default settings, or if it has been uncommented, the value set by the MemoryApplication keyword in the file init.cfg. | |
| <n> | On multi-processor machines, start Flame using less than the full array of processors, where <n> is the number of processors to be used. Normally, Flame uses all available processors. |
| <filename> | Use a custom menu file, where <filename> is the name of the menu file. For information on custom menus, see Creating Custom Menus. |
| <project> <user> <batch_setup> | Launch Flame and specify a Batch setup to render. Flame launches,
renders the setup, and exits. Use the option
only if you want to use Burn for rendering. To avoid corrupting the render, which uses the graphics hardware, you should not use the graphics console of the system (such as command shells) while the render is taking place. |
| Starts Flame and skips the integrity check. |