first I want to say lightworks is awesome.
but navigate with the mousecursor through stripview is a little bit annoying. I unjoin constantly cuts, because I dont hit the frame marker right. Maybe bigger symbols were great, so you can better see what you do. These tiny white C and H are to small.

Or just make something like ctrl+leftclick for entering the unjoin mode. When you have a really small clip you have to zoom it to be able to see what you are doing or if you want to click in the middle to move the clip.

Also it's really easy to move a clip with the mouse, really reactive. But when you enter in unjoin mode, and try to extend a clip, the mouse go crazy, it doesn't really work, you have to make big gestures, and at some point you go really further than what you wanted to do. I hope this is a bug that can be fixed.

I know people are gonna say that it's better to use keyboard, but here we are just talking about mouse navigation.

Yes - I'll be looking at this shortly.


Trimming & navigation is optimised for console use, but we're working to make it great whichever way you want to drive it. Please keep the suggestions coming.

Hammerhead wrote:


You might consider adding different motion parameters (speed, acceleration, sensitivity, whatever you have...) for different input methods, rather than settling on a compromise, which may be good for none of them.

Maybe you could have a standalone text file for each "input method profile". I am a fan of human-readable configuration files. It is easy to customize them.

sterovetta wrote:


That's what the config.dat file is for that's found in the installation directory.

See "here".

It's for Alacrity but some of the parameters work in Lightworks. It would be nice if the devs published a list for Lightworks and/or added it to the User Guide.

I did a search for each parameter from this PDF file in all the files in the Lightworks installation directory and noted the ones that were found and not found within the files.

The big one for me is default_border_width. Setting this to 12 makes the blue and red border around viewers and strip views easier to see.

khaver wrote:


Yes, I know. I tend to avoid suggesting inconsistent features. Since LW already has textual configuration files, then I was suggesting one specific to input methods.

I agree that it would be nice to have it documented in a reference manual. (I am implicitly referring to my previous suggestion to split the current guide into a more detailed ref. manual and a more task-oriented user guide).