Lightworks: The professional editor for everyone - Forum Kunena Site Syndication Tue, 22 Jan 2019 23:56:33 +0000 Kunena 1.6 components/com_kunena/template/default/images/icons/rss.png Lightworks: The professional editor for everyone - Forum en-gb Another timeline zoom out question - by: theeded
I have screencap 01 and 02 for reference.


On image 01, I am able to see "gaps" on the timeline. I like it that way.

Image 02 is another project. For some reason, I amjsut unable to zoom out and see those gaps. I can only zoom out as much as the size of my clips allow. No gaps in there.

I am not being able to get the project back to allowing me to see the gaps in there, and zoom out simply does not go beyon that point.

Can anyone please tell me how I can see those gaps again? I really don't want the length of the clips taking absolutely the whole timeline.]]>
GUI / display / keyboard Tue, 22 Jan 2019 21:20:55 +0000
Applying a transition to FX titles - by: tomw85
Still new to Lightworks but am enjoying getting to grips with it. I suspect this may be a routing issue - which I am finding tricky to get my head around.

I have two clips on V1 with a wipe transition between them. The first clip has title text (as will the next clip - it's the names of the characters I'm introducing).

I would like for the text to be "wiped" off with the first clip, as the second clip wipes on. What actually happens is the text remains there until the end of the FX1 block.

I've attached a screen grab of the routing. At the moment I can't disconnect the clips from the wipe module.

If anyone can help it'd be greatly appreciated.]]>
Effects Tue, 22 Jan 2019 18:56:36 +0000
HDR High Dynaic Range Explained - by: hugly]]>
Miscellaneous Tue, 22 Jan 2019 14:10:59 +0000
The most important features of V14.6 - by: hugly
1. Native HEVC support on import
2. Significantly improved quality (presets/parameters) for Youtube, Vimeo and h.264/MP4 export.
3. Search function on project browser for project content.
4. Support of variable frame rate with non-standard nominal frame rate in .mp4 container
5. Flawless merging of splitted MPEG2 transport stream and similar formats (chunks of mpeg-ts, ts, mts, m2ts, vob) on import

Edit: That's a wish list and, except of the search function, mainly based on recently reported issues. The features listed here don't exists in the official announcement of V14.6 and V15. Thoughts and opinions of others truly appreciated.]]>
Miscellaneous Tue, 22 Jan 2019 11:08:40 +0000
Export Videos - by: Hồ Phát Tài
I cannot export videos with 1080 HD quality.
(I am using the free version.)
Software Activation / Licensing / Updating Tue, 22 Jan 2019 03:05:21 +0000
I accidently deleted a whole sequence while editing (urgent) - by: Civester Editing Tue, 22 Jan 2019 03:04:31 +0000 14.5 Audio desync - by: NeptunianEmp
Complete name : C:\Users\NeptunianEmp\Downloads\game.mp4
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42 (isom/mp42)
File size : 2.30 GiB
Duration : 2 h 15 min
Overall bit rate mode : Variable
Overall bit rate : 2 423 kb/s
Encoded date : UTC 2018-12-02 19:30:35
Tagged date : UTC 2018-12-02 19:30:35
gsst : 0
gstd : 8136852

ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L3.1
Format settings : CABAC / 3 Ref Frames
Format settings, CABAC : Yes
Format settings, RefFrames : 3 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 2 h 15 min
Bit rate : 2 294 kb/s
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 (29970/1000) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.083
Stream size : 2.17 GiB (95%)
Title : ISO Media file produced by Google Inc. Created on: 12/02/2018.
Encoded date : UTC 2018-12-02 19:30:35
Tagged date : UTC 2018-12-02 19:30:35
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Codec configuration box : avcC

ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 2 h 15 min
Bit rate mode : Variable
Bit rate : 128 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 44.1 kHz
Frame rate : 43.066 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 124 MiB (5%)
Title : ISO Media file produced by Google Inc. Created on: 12/02/2018.
Encoded date : UTC 2018-12-02 19:30:35
Tagged date : UTC 2018-12-02 19:30:35

Computer Specs
Processor: AMD Ryzen 5 1600 Six-Core Processor 3.20 GHz
Installed Memory (RAM) 8.00 GB]]>
Audio Tue, 22 Jan 2019 01:22:56 +0000
Upside down video - by: catherine110 ]]> Effects Tue, 22 Jan 2019 00:58:06 +0000 Glitch with importing videos - by: whatsonherface Thanks for your help!]]> Cameras / Capture Cards / Firewire / Importing Mon, 21 Jan 2019 22:45:46 +0000 Boris FX and Proxies - by: Doofer Third Party Plugins Mon, 21 Jan 2019 19:56:31 +0000 Uncompressed 10-bit - by: hugly Compare Versions page it says:

Uncompressed SD 8 bit and 10 bit (AVI and MOV)
Uncompressed HD 8 bit and 10 bit (AVI and MOV)

Does anyone know how to switch to 10-bit?]]>
Codecs / Importing / Exporting / Transcoding Mon, 21 Jan 2019 09:46:41 +0000
Colour correction / grading controller - by: gr00by
There are many hardware panels for colour correction / grading, but there's one fun toy which could be an addition to Shuttle Pro controller. It is a Tangent Ripple. Ideal tool for prosumers.

Lightworks is not on the supported apps, of course. But Tangent is providing a mapper app, which can just map controller's knobs and switches to keystrokes (same as Shuttle Pro app). The problem is that Lightworks FXs can't be controlled by keyboard nor other device. This post is my proposal to introduce such possibility.

I understand it is hard to implement it. I see that UI has no anything what would mimic a "selected/active component" (knob/slider/button). Also Lightworks FX UI is very dynamic - it is related directly to created nodes, where every node can have own GUI, and every FX (GUI) can be repeated many times in the node's graph. Uncontrollable? Well..

I asked myself many times how such potentially complex structure can be controlled without a mouse.
Now I can write my thoughts.


To control effect parameters by any hardware, there must be a possibility to activate (select) a node. This is a must have. And because routing is a graph (DAG, precisely), there should be a some intuitive way of changing nodes. I see three ways.

1. On the "Settings" tab navigation would be simple - there is bottom-up stack visible, so a some key up /key down navigation will be enough. Selected node should have some kind of frame/glow/brighter background.

2. On the "Routing" tab navigation will be harder. There should be 4-ways: up,down,left,right, where next node should be determined by visual position of a current and candidate nodes.

3. Selecting node by some unique identifier and dedicated shortcut. Node identifiers can be set automatically, based on node number (in order of creation) or effect's ID (FX filename or other effect identifier).

a. Node numbers

This is a quite simple mechanism. Nodes should be numbered in order of creation, node numbers should be visible, and user should be able to activate node by hitting some simple shortcut like <mod>+<number>.

This would be enough for cases, where user has own scheme. For example I'm doing CC with few simple nodes in a sequence: (1) CC for lift/gamma/gain, (2) CC for WB fix, (3) 3D Lut, (4) final colour corrections, (5) optional grain. Numbering is not ideal, but enough for most cases.

b. FX identifiers

Every effect can be have it's own identifier (category/name, maybe?). This would give possibility to bind key to particular effect. In such case the order of nodes creation will not be important, and user will be able to immediately select node containing effect he want to modify.

For graphs containing multiple nodes of same effect, hitting the shortcut again should switch to next node (cycle) containing same effect, in order of creation.

c. Locked or editable nodes

To improve usability, nodes can be locked. Alternatively - can be marked as editable/available for tine using external controller. This would give a possibility to eliminate or select nodes that user wants to play with.

Controlling parameters

Each FX exposes it's GUI. It's elements are unique identifiers, default values and limits. They can be just exposed. They should be bindable.

Thinking about 3-way cc - I'm considering about giving the wheels some kind os special (static) identifiers. Same for shadow,mid and highlight sliders. For some kind of consistency and ease of further mappings.

Having the active node, and having controllable UI elements, there will be possibility to control them via virtually any hardware.

MIDI is a protocol which comes into my mind.


This may sound complex, but the UI needs just the active node to be introduced, and effect parameters needs their MIDI equivalents.

As a result users will have possibility to precisely tune colours without external apps, and EditShare will have possibility to create and sell another dedicated controller, which will improve experience and save user's time.]]>
Feature Requests Mon, 21 Jan 2019 01:09:16 +0000