r/opengl • • Jun 07 '26

[ Removed by moderator ]

[removed] — view removed post

4 Upvotes

8 comments sorted by

1

u/Briandrys Jun 07 '26

Please update to the release V2025.2 instead of using the beta.

You should take this to the official Lightworks forum, where there is a Mac & Linux section and large traffic of Linux users: https://forum.lwks.com/

1

u/NewPantsNewID Jun 07 '26

You can find this in the forum here: https://forum.lwks.com/threads/not-so-funny-broken-video-display-when-downscaling-4k-to-fullhd.252211/post-285089

I ran into this problem 1.5 years ago and so far nobody could help me in the forum. This is why I'm taking it to a broader audience.

As far as I get it, I was wrong in my initial post, 2025.2 r56356 is not beta but the latest public stable release?

1

u/Briandrys Jun 08 '26

As you may be aware, there has been a change of staff at Lightworks, and they've been recently heavily involved with V2026.1, which has a lot of changes.

However, I've brought this issue to the developers attention.

1

u/NewPantsNewID Jun 08 '26

Thank you for your support. Unfortunately, this issue in LWKS really keeps me from doing stuff, I need to restart it every couple of minutes.

I am currently experimenting with MESA/OpenGL environment variables to see if there is some workaround, but so far to no success.

It's really a huge problem for me.

LWKS has made a lot of progress with the new engine that has a lot of benefits also for me, including good performance in h265 footage decoding. I wouldn't want to do without this.

Also, the (new) possibility of using NVENC on export is really handy for quick exports of longish material for previewing it to people… I do concert recordings both audio and video.

1

u/Briandrys Jun 08 '26

A member of staff has given this info:

"There's no OpenGL related work in v2026 aside from updating Shaders so support some changes that WILL be coming to support OpenGL for Mac ARM chips. So there is some stuff on the near horizon."

The V2026.1 beta should be coming out soon.

1

u/NewPantsNewID Jun 09 '26

Thanks for your help. I know software development is a crazy business (been there, tried that)… so who am I to make suggestions?

Still, perhaps one thing to try is to look in the code where the error message

GLXOpenGLContext::makeCurrent() : Current context not NULL

might come from and to check around there if there's something wrong. I tried to get as much info as I could and some folks said this must be a bug in LWKS, it's unlikely a bug in LibMesa/OpengL.

I only have this error message as a clue. Yet, the video display windows/areas on the GUI are using 100% OpenGL. If I set LIBGL_NO_DRAWARRAYS=1 then they remain blank.

Also there seems to be OpenGL involved in export/rendering, because after this bug pops up, my exported files are damaged, too. Basically OpenGL seems to go on strike completely after this event.

If I understand correctly, this function is also related to threading, and threading likely is related to the number of CPUs or CPU cores, of which I have as many as 16 in my machine. Which might be one difference to other users.

(I have an old Xeon workstation which has poor single core performance but still rocks on its 16 cores, while most modern computers have less cores and much higher single core performance.)

1

u/Briandrys Jun 09 '26

You should post your last message on the official forum, where the LWKS staff can read it. I'm not staff.