If the audio and video clips have metadata that LightWorks can use to match them up, it can automatically sync a whole bin at once using the metadata combined with the marks.Īlternatively, select each audio-video pair and manually sync using the marks. Start by setting a mark at the clapper point in each clip whether it’s audio or video. Syncing happens in bins also, and although LightWorks doesn’t provide a waveform based sync option, it handles timecode based syncing very smoothly. Logging and OrganizingĪs in most NLEs, LightWorks provides a bin-based interface for organizing clips and editing clip metadata. There is functionality available in the flexible layout that isn’t available in the fixed layout, like editing from one timeline into another. The flexible layout is pretty much whatever you want it to be. These interfaces resemble comparable interfaces in other editing applications, in order to facilitate the transition to working with LightWorks. It’s based around a series of task-specific workspaces for logging, editing, effects, and audio mixing. User InterfaceĮditShare added a new fixed UI layout to LightWorks in v14. It does use the GPU for effects, via pixel shaders, much like a game engine does.
I didn’t expect this to work well, but I was in for quite a surprise.įirst off, LightWorks has remarkably efficient engine, and it’s largely CPU based rather than GPU based. I’ve been doing some editing in LightWorks using my Spectre x360, with 8K footage. In light of that, one might reasonably expect that the only way to edit 8K footage on an ultrabook like an HP Spectre x360 (Kaby Lake-R) would be via DIs. Rakesh Malik tells all.Įditing 8K footage sounds a bit daunting, especially given how much computer power some people are throwing at the task. Editing 8K on the move isn't as hard as you might thinkĨK takes huge amounts of resources to edit you say? Not if you edit using Lightworks it doesn't.
0 kommentar(er)
