Welcome, Guest
Username Password: Remember me
  • Page:
  • 1

TOPIC: Config.dat parameters, V14.0 and later

Config.dat parameters, V14.0 and later 3 years, 4 months ago #142710

  • hugly
  • OFFLINE
  • Platinum Boarder
  • Posts: 25449
  • 3 years, 4 months ago
There was a valuable discussion in V14 beta forum about documented and undocumented parameters in config.dat. Unfortunately the discussion isn't accessible anymore due to restricted access to older beta forums.

Default parameters:
{ config

# Configure the number of undos that are available for each edit
backup_depth 10

# Edit milestone configuration
milestones_per_edit 10
mods_per_milestone 10

# Define the 'preview' preroll duration in seconds
preview_preroll_secs 3

# By default EDL reel IDs are limited to 8 characters in length.  Set to 0 to lift this limitation.
edl_limit_reel_length 1

# By default, when trimming a cut with two moving sides, Lightworks will monitor the audio from the side
# closest to the current-time - this can lead to silence when that side of the cut is black. To automatically
# monitor the non-black side, set this value to 1
trim_avoid_silence 0

# By default, popped out tiles are revealed in the Content Manager.  Change to 0 to reveal them on the desktop instead.
reveal_tiles_in_bins 1

# Configure the contrast for timeline waveforms. Lower numbers will be darker.
waveform_colour_scale 0.8

# Define the central proportion of a timeline segment that can be grabbed for drag/drop.
# Set to 0 to effectively disable segment drag/drop
stripv_segment_drag_size 0.5

# By default, tiles can be dragged/dropped into timelines. Set to 0 to inhibit this behaviour
stripv_accept_tiles 1

# By default, tiles can be dragged/dropped into a viewer. Set to 0 to inhibit this behaviour
viewer_accept_tiles 1

# By default, bin groups are sorted when viewed in Content Manager.  To respect manually ordered racks, set this to 0
sorted_racks 1

# Pressing replace/insert will by default create a new edit if there isn't one present.  To inhibit this behaviour, set this to 0
create_edit_on_demand 1

# Lobby thumbnail layout
num_projects_across 4
num_projects_down 3

# Additional entries can be added here





} config

In addition to the default parameter there are some more. Based on different posts I collected those shown below:

####################################################################
# Additional entries can be added here
####################################################################

# for turning off the automatic edit creation when Inserting/Replacing
create_edit_on_demand 0

#Improved edit backup procedure to resolve performance issues with large edits, primarily during audio mixing
decoupleEditBackups 1

#Show progressive SD formats
allow_progressive_sd_export 1

#V14 Lobby layout
num_projects_across 4
num_projects_down 3

} config

Not many, and I don't know whether everything shown above is still valid with V14 release nor whether other parameters (new, or used in older version) will work properly.

Any suggestions?
It's better to travel well than to arrive...
Last Edit: 7 months, 4 weeks ago by hugly.

Re: V14 Config.dat Additional Entries 3 years, 4 months ago #142766

  • jwrl
  • Moderator
    Pro User
  • OFFLINE
  • Moderator
  • Posts: 12786
  • 3 years, 4 months ago
Just a word of caution: in that same thread in the beta forums Great White advised that these were undocumented commands and were very much in the category of "use at your own peril". They can have unexpected results.

Re: V14 Config.dat Additional Entries 3 years, 3 months ago #143517

  • hugly
  • OFFLINE
  • Platinum Boarder
  • Posts: 25449
  • 3 years, 3 months ago
It's better to travel well than to arrive...

Re: V14 Config.dat Additional Entries 7 months, 4 weeks ago #209818

  • hugly
  • OFFLINE
  • Platinum Boarder
  • Posts: 25449
  • 7 months, 4 weeks ago
I've been using the mute/solo button on the timeline for quite a while. I just found where I first saw it.

www.lwks.com/index.php?option=com_kunena&func=view&catid=24&id=142629&Itemid=81#142656
# Add mute/solo button on the timeline. Left click to mute/unmute, chord click to solo.
timeline_mute_solo 1

Any news on the parameters in config.dat, in general? Can we hope for a cross-platform documentations soon?
It's better to travel well than to arrive...
Last Edit: 7 months, 4 weeks ago by hugly.

Re: V14 Config.dat Additional Entries 7 months, 4 weeks ago #209826

  • hugly
  • OFFLINE
  • Platinum Boarder
  • Posts: 25449
  • 7 months, 4 weeks ago
New parameters added with V14.5, from here, referring to release notes, typos corrected:

# Inhibits numeric suffixes on Syncs/Subclips - default 1
unique_suffixes 0 

# Inhibits automatic 'Record' status for double-clicked sequence tiles (only Flexible GUI) - default 1
auto_record_status 0 

# For changing Replace to Insert, when dragging tiles from a bin to a sequence - default 0
stripv_insert_dropped_tiles 1 

# Restores the old behaviour of highlighting the Name when opening (only Flexible GUI) - default 0
highlight_filecard_name 1

# Inhibits enabling Fullscreen-preview when double clicking the viewer - default 1
double_click_for_fullscreen 0
It's better to travel well than to arrive...

Re: V14 Config.dat Additional Entries 7 months, 4 weeks ago #209838

  • schrauber
  • OFFLINE
  • Platinum Boarder
  • Posts: 4397
  • 7 months, 4 weeks ago
Thanks for the collection.
I took it as an opportunity to add `preview_position 400` and `timeline_mute_solo 1` to my config.dat.

I've been using for some time, too:
# Define the effect of the timeline zoom buttons (default is `3` to zoom in to one third of what's visible)
zoom 2

Achieves a zoom ratio of 1 / 2 (or vice versa) per click or keystroke.
See: www.lwks.com/index.php?option=com_kunena&func=view&catid=20&id=7242&Itemid=81#7245

This parameter does not support floating point values. Values below 2 therefore make no sense, because the next lower integer "1" would completely disable the functionality (zoom ratio change per click 1/1).
Mainly automatically translated
--------------------------------------------
Software: Lightworks 2020.1; || Windows 10, 64 Bit
Hardware: Intel i5-4440 (3,1 GHz); || shared RAM: 8 GB; || Intel HD Graphics 4600 (can use max. 2 GB of shared RAM)
Last Edit: 7 months, 4 weeks ago by schrauber.

Re: Config.dat parameters, V14.0 and later 4 months, 3 weeks ago #214276

  • Sherwood10
  • Pro User
  • OFFLINE
  • Senior Boarder
  • Posts: 70
  • 4 months, 3 weeks ago
Does anyone know if this command still works?

force_primary 1

I found another thread which said it will make the F12 full screen preview show up in the primary monitor. However, it will not work for me in the 2020 beta version. Thanks,

Re: V14 Config.dat Additional Entries 4 months, 3 weeks ago #214277

  • jwrl
  • Moderator
    Pro User
  • OFFLINE
  • Moderator
  • Posts: 12786
  • 4 months, 3 weeks ago
jwrl wrote:
Just a word of caution: in that same thread in the beta forums Great White advised that these were undocumented commands and were very much in the category of "use at your own peril".

There is an alternative to that command.

This image is hidden for guests. Please log in or register to see it.

Re: Config.dat parameters, V14.0 and later 4 months, 3 weeks ago #214299

  • hugly
  • OFFLINE
  • Platinum Boarder
  • Posts: 25449
  • 4 months, 3 weeks ago
Sherwood10 wrote:
Does anyone know if this command still works?

force_primary 1

Just checked that. On the forum, the command 'force_primary' was last mentioned May 2012 by a developer here and appears to have no effect anymore, not unexpected. The selection of the primary display follows strictly the system settings shown above, no matter what 'force_primary' is set to.
It's better to travel well than to arrive...
Last Edit: 4 months, 3 weeks ago by hugly.

Re: V14 Config.dat Additional Entries 4 months, 3 weeks ago #214300

  • Sherwood10
  • Pro User
  • OFFLINE
  • Senior Boarder
  • Posts: 70
  • 4 months, 3 weeks ago
jwrl wrote:
jwrl wrote:
Just a word of caution: in that same thread in the beta forums Great White advised that these were undocumented commands and were very much in the category of "use at your own peril".

There is an alternative to that command.

This image is hidden for guests. Please log in or register to see it.



Thanks! Sorry to clog up the forum, I did not notice that setting before.

Re: V14 Config.dat Additional Entries 4 months, 3 weeks ago #214301

  • hugly
  • OFFLINE
  • Platinum Boarder
  • Posts: 25449
  • 4 months, 3 weeks ago
Newly published entry for switching the format of voice over recordings from MXF to WAV, from here:

# Switch format of voice over recordings to WAV [default MXF]
audioFormatID WAV
It's better to travel well than to arrive...
Last Edit: 4 months, 3 weeks ago by hugly.
  • Page:
  • 1
Time to create page: 0.43 seconds
Scroll To Top