OpenGL Texture Limit
I have this OpenGL warning with X11-OpenGL driver: void AWindowGUI::update_asset_list(): Warning: /home/paz/Video/hdr/hdr_02.mp4 dimensions 3840x2160 exceed OpenGL texture limit 0 In this case I used a 4k source, but the same happens with any resolution, since the “texture limit” is 0. I found this answer: "If you want to know dynamically the texture size limit of your device (because it's change depending on the device), you have to call this method: int[] maxTextureSize = new int[1]; gl.glGetIntegerv(GL10.GL_MAX_TEXTURE_SIZE, maxTextureSize, 0); And don't forget that for some device (the Nexus One for example), the texture size must be a power of 2 !" And also: "One note: It's a static method, so you can simply call GLES10.glGetIntegerv(...)" See: https://registry.khronos.org/OpenGL-Refpages/es2.0/xhtml/glGet.xml But I have absolutely no idea where and how to use that call code. Suggestions? Note: the limits of my device (on the specification sheet) should be: 16384x16384
чт, 5 июн. 2025 г., 10:30 Andrea paz via Cin <[email protected]>:
I have this OpenGL warning with X11-OpenGL driver:
void AWindowGUI::update_asset_list(): Warning: /home/paz/Video/hdr/hdr_02.mp4 dimensions 3840x2160 exceed OpenGL texture limit 0
To be honest I think this is just something wrong with X server/mesa /glvnd layer. I do not see this on my compilation of cingg when running with mesa git/xserver git. Because I think we both on amdgpu/radeonsi now common parts should be ok.... May be get apitrace installed and .... file another bug at Mesa3d bugtracker?
In this case I used a 4k source, but the same happens with any resolution, since the “texture limit” is 0. I found this answer:
"If you want to know dynamically the texture size limit of your device (because it's change depending on the device), you have to call this method:
int[] maxTextureSize = new int[1]; gl.glGetIntegerv(GL10.GL_MAX_TEXTURE_SIZE, maxTextureSize, 0);
And don't forget that for some device (the Nexus One for example), the texture size must be a power of 2 !"
And also:
"One note: It's a static method, so you can simply call GLES10.glGetIntegerv(...)"
See: https://registry.khronos.org/OpenGL-Refpages/es2.0/xhtml/glGet.xml
But I have absolutely no idea where and how to use that call code. Suggestions?
Note: the limits of my device (on the specification sheet) should be: 16384x16384 -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
On Thu, 5 Jun 2025, Andrea paz via Cin wrote:
I have this OpenGL warning with X11-OpenGL driver:
void AWindowGUI::update_asset_list(): Warning: /home/paz/Video/hdr/hdr_02.mp4 dimensions 3840x2160 exceed OpenGL texture limit 0
I saw similar warning (different dimensions, mine were 640x480) when testing if cingg runs under Xwayland, with a short test video. It ran despite the warning, and I have not observed any quirks. AWindowGUI is the GUI of Resources Window. Are OpenGL textures used in this window at all? I don't know. Perhaps this warning does not appear under Xorg server and appears only under Xwayland server. I do not use Xwayland, always ran cingg only under Xorg and do not remember ever to see such a message. _______________________________________________________________________________ Georgy Salnikov NMR Group Novosibirsk Institute of Organic Chemistry Lavrentjeva, 9, 630090 Novosibirsk, Russia Phone +7-383-3307864 Email [email protected] _______________________________________________________________________________
Perhaps this warning does not appear under Xorg server and appears only under Xwayland server. I do not use Xwayland, always ran cingg only under Xorg and do not remember ever to see such a message.
No, I always use X11 in order to take advantage of monitor profiling. Maybe Kwin (from KDE) doesn't work well, I read that it will be split into Kwin and Kwin-X11 but Arch linux hasn't done the split yet. I have some problems with X11-OpenGL anyway: frequent freezes and crashes that don't happen with X11
чт, 5 июн. 2025 г., 11:32 Andrea paz via Cin <[email protected]>:
Perhaps this warning does not appear under Xorg server and appears only under Xwayland server. I do not use Xwayland, always ran cingg only under Xorg and do not remember ever to see such a message.
No, I always use X11 in order to take advantage of monitor profiling. Maybe Kwin (from KDE) doesn't work well, I read that it will be split into Kwin and Kwin-X11 but Arch linux hasn't done the split yet.
I have some problems with X11-OpenGL anyway: frequent freezes and crashes that don't happen with X11
Yes, I remember. Did you tried those env variables? https://docs.mesa3d.org/envvars.html RadeonSI driver environment variables radeonsi_no_infinite_interp Kill PS with infinite interp coeff (might fix hangs) radeonsi_clamp_div_by_zero Clamp div by zero (x / 0 becomes FLT_MAX instead of NaN) (might fix rendering corruptions) radeonsi_zerovram Clear all allocated memory to 0 before usage (might fix rendering corruptions) AMD_DEBUG a comma-separated list of named flags, which do various things: nodcc Disable DCC. nodccclear Disable DCC fast clear nodisplaydcc disable Delta Color Compression (DCC) on displayable images nodccmsaa Disable DCC for MSAA nodpbb Disable DPBB. Overrules the dpbb enable option. noefc Disable hardware based encoder color format conversion lowlatencyenc Enable low latency encoding notiling Disable tiling nofmask Disable MSAA compression nohyperz Disable Hyper-Z no2d Disable 2D tiling ===== there is *a lot* of testing, but eventually you can test all of them, I guess? --
Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
So far I have tried different env variables, but not the ones you proposed. I am using this startup script, to which I change variables all the time. #!/bin/bash export CIN_EDITOR=kate export CIN_CONFIG=$HOME/.bcast6 MESA_LOADER_DRIVER_OVERRIDE=radeonsi_dri.so # MESA_VK_DEVICE_SELECT_FORCE_DEFAULT_DEVICE=1 MESA_VK_DEVICE_SELECT="vid:did" RADV_PERFTEST=video_decode,video_encode /home/paz/cinelerra5/cinelerra-5.1/bin/./cin The last test was with: MESA_LOADER_DRIVER_OVERRIDE=radeonsi_dri.so But it doesn't change anything. It's probably the one that's active by default. With: radeonsi_no_infinite_interp radeonsi_clamp_div_by_zero radeonsi_zerovram AMD_DEBUG=nodcc (nodisplaycdd) (noefc) (nohyperz) Nothing changes. After Georgy said the warning comes up with wayland, maybe it started with KDE6, which integrates wayland by default. But I'm not sure.
On Thu, 5 Jun 2025, Andrea paz wrote:
Perhaps this warning does not appear under Xorg server and appears only under Xwayland server. I do not use Xwayland, always ran cingg only under Xorg and do not remember ever to see such a message.
No, I always use X11 in order to take advantage of monitor profiling. Maybe Kwin (from KDE) doesn't work well, I read that it will be split into Kwin and Kwin-X11 but Arch linux hasn't done the split yet.
Just now I checked explicitly once again: Under fvwm2: no message Plasma (X11): no message Plasma (Wayland): in konsole: BC_DisplayInfo::gl_fb_config failed in Message log and konsole: void AWindowGUI::update_asset_list(): Warning: /disk2/sge/test/transitions/test1.m4v dimensions 640x480 exceed OpenGL texture limit 0 nevertheless everything played OK just as always Plasma (Full Wayland): same messages as Plasma (Wayland), and everything played OK. I don't know what is the difference except some programs work under Wayland and refuse to start under Full Wayland. My OS is slackware-15.0, KDE Plasma-5. _______________________________________________________________________________ Georgy Salnikov NMR Group Novosibirsk Institute of Organic Chemistry Lavrentjeva, 9, 630090 Novosibirsk, Russia Phone +7-383-3307864 Email [email protected] _______________________________________________________________________________
participants (3)
-
Andrea paz -
Andrew Randrianasulu -
Georgy Salnikov