


Of course the interesting question remains, does Lightworks do the caching, or QuickTime, or Windows?Īnd then it would be interesting to know which location is being used for that, it might need some cleanup once in a while as well.Įdit: It cannot be my page file since I switched of VM completely.The main benefits of Lightworks are easy drag-and-drop technique, video routing and keyframing, and direct exportation to YouTube. Thought that might be usefuly to some of you guys: Keep an eye on your (system) disk space (or where Lightworks is installed?), otherwise you might see your rendering process saying good-bye B) So I cleaned some stuff in order to have around 30 GB free and rebooted.Īnd voila, my full HD rendering is running, at least until now (around 07:50:00 hours out of initially 08:15:00 remaining). I noticed that from my 80 GB disk less than 4 were still free. But still, as it seems somehow the local disk C: where my Lightworks is installed is used for caching the video stream during export. I always render to some external media, in order to save render time. With 720p exports everything went fine, but when I tried to export 1080p25 video, after several minutes of rendering Lightworks just quit.Īs it seems, today I could find the cause for that and hopefully solve it:

Recently I did a lot of direct MPEG-4 exporting with the pro version.
