Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
AVA-DS and AVA-SC don't draw GUI elements (Linux/KDE Plasma)
#1
Hello, this is my first post here...

I'm Edgar, long time Ardour community member, I also maintained Ardour's german translation during the last decade or so.

Coming to my problem, I've installed the latest AVA plugin pack and yesterday purchased the last missing license (for AVA-DS, as I found out the reduced price offer from a month or so ago still was valid).

Then in Mixbus32C (also latest 5.3.22) I realized that the Deesser and the spectral compressor don't show their GUI properly on this laptop I'm writing this on (see attached screenshot).

I've attached gdb to running mixbus32c process and here is the relevant excerpt from "thread apply all bt" (the thread trying to display AVA-DS, if I understand it correctly):

Code:
Thread 27 (Thread 0x7fb9ca398700 (LWP 23369)):
#0  0x00007fba32cbebdf in poll () from /lib64/libc.so.6
#1  0x00007fba31c3f742 in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007fba31c400ba in xcb_wait_for_special_event () from /usr/lib64/libxcb.so.1
#3  0x00007fb9d86e139e in ?? () from /usr/lib64/libGLX_mesa.so.0
#4  0x00007fb9d86e14c8 in ?? () from /usr/lib64/libGLX_mesa.so.0
#5  0x00007fb9d86e185e in ?? () from /usr/lib64/libGLX_mesa.so.0
#6  0x00007fb9d86e1c1c in ?? () from /usr/lib64/libGLX_mesa.so.0
#7  0x00007fb9cac24464 in ?? () from /usr/lib64/dri/i965_dri.so
#8  0x00007fb9cac249c5 in ?? () from /usr/lib64/dri/i965_dri.so
#9  0x00007fb9cac29a08 in ?? () from /usr/lib64/dri/i965_dri.so
#10 0x00007fb9db95b08f in ?? () from /home/ed/.vst/AVA-DS.so
#11 0x00007fb9db94763c in ?? () from /home/ed/.vst/AVA-DS.so
#12 0x00007fb9db96a01a in ?? () from /home/ed/.vst/AVA-DS.so
#13 0x00007fb9db7f4db9 in ?? () from /home/ed/.vst/AVA-DS.so
#14 0x00007fb9db7f4fbf in ?? () from /home/ed/.vst/AVA-DS.so
#15 0x00007fb9db7f488d in ?? () from /home/ed/.vst/AVA-DS.so
#16 0x00007fb9db7f4999 in ?? () from /home/ed/.vst/AVA-DS.so
#17 0x00007fba356a1f2a in start_thread () from /lib64/libpthread.so.0
#18 0x00007fba32cc94af in clone () from /lib64/libc.so.6

I've also installed the latest versions of everything on my desktop PC, and surprisingly the problem doesn't show there.

The desktop PC also has an ASUS mainboard and nVidia graphics, and runs the same operating system, openSUSE Tumbleweed, both boxes fully up to date at the latest snapshot, but using slightly different additional 3rd party repos for additional software).

Any clues? I'll continue to try things like changing desktop environments or even boot to Windows and install it there, but otherwise I'm out of ideas...

Greetings, Edgar


Attached Files Thumbnail(s)
   
Reply
#2
(12-22-2019, 05:39 AM)edogawa Wrote: Hello, this is my first post here...

I'm Edgar, long time Ardour community member, I also maintained Ardour's german translation during the last decade or so.

Coming to my problem, I've installed the latest AVA plugin pack and yesterday purchased the last missing license (for AVA-DS, as I found out the reduced price offer from a month or so ago still was valid).

Then in Mixbus32C (also latest 5.3.22) I realized that the Deesser and the spectral compressor don't show their GUI properly on this laptop I'm writing this on (see attached screenshot).

I've attached gdb to running mixbus32c process and here is the relevant excerpt from "thread apply all bt" (the thread trying to display AVA-DS, if I understand it correctly):

Code:
Thread 27 (Thread 0x7fb9ca398700 (LWP 23369)):
#0  0x00007fba32cbebdf in poll () from /lib64/libc.so.6
#1  0x00007fba31c3f742 in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007fba31c400ba in xcb_wait_for_special_event () from /usr/lib64/libxcb.so.1
#3  0x00007fb9d86e139e in ?? () from /usr/lib64/libGLX_mesa.so.0
#4  0x00007fb9d86e14c8 in ?? () from /usr/lib64/libGLX_mesa.so.0
#5  0x00007fb9d86e185e in ?? () from /usr/lib64/libGLX_mesa.so.0
#6  0x00007fb9d86e1c1c in ?? () from /usr/lib64/libGLX_mesa.so.0
#7  0x00007fb9cac24464 in ?? () from /usr/lib64/dri/i965_dri.so
#8  0x00007fb9cac249c5 in ?? () from /usr/lib64/dri/i965_dri.so
#9  0x00007fb9cac29a08 in ?? () from /usr/lib64/dri/i965_dri.so
#10 0x00007fb9db95b08f in ?? () from /home/ed/.vst/AVA-DS.so
#11 0x00007fb9db94763c in ?? () from /home/ed/.vst/AVA-DS.so
#12 0x00007fb9db96a01a in ?? () from /home/ed/.vst/AVA-DS.so
#13 0x00007fb9db7f4db9 in ?? () from /home/ed/.vst/AVA-DS.so
#14 0x00007fb9db7f4fbf in ?? () from /home/ed/.vst/AVA-DS.so
#15 0x00007fb9db7f488d in ?? () from /home/ed/.vst/AVA-DS.so
#16 0x00007fb9db7f4999 in ?? () from /home/ed/.vst/AVA-DS.so
#17 0x00007fba356a1f2a in start_thread () from /lib64/libpthread.so.0
#18 0x00007fba32cc94af in clone () from /lib64/libc.so.6

I've also installed the latest versions of everything on my desktop PC, and surprisingly the problem doesn't show there.

The desktop PC also has an ASUS mainboard and nVidia graphics, and runs the same operating system, openSUSE Tumbleweed, both boxes fully up to date at the latest snapshot, but using slightly different additional 3rd party repos for additional software).

Any clues? I'll continue to try things like changing desktop environments or even boot to Windows and install it there, but otherwise I'm out of ideas...

Greetings, Edgar

Yes, I was about to post the same message. Just purchased the AVA SC plugin and get the same screen as you.
Before installing, I made a backup of all my original AVA .so files. I re-placed the De-esser back with the original, and it works just fine. It's the 'new' version that came with the latest download that doesn't work. Nothing to see in log either...
Reply
#3
(12-22-2019, 05:39 AM)edogawa Wrote: Then in Mixbus32C (also latest 5.3.22) I realized that the Deesser and the spectral compressor don't show their GUI properly on this laptop I'm writing this on (see attached screenshot).

Greetings, Edgar

I have the same problem and I reported it to Harrison the day they announced the new AVA plugins. Been in contact with nik@harrison about it and I guess he know a bit of the cause of the problem.

It's ok with the proprietary nvidia card and driver, but fail with the onboard Intel card, that I use. I also have GL 3 installed and that version is a bit old, but as I understand from forum post it have something to do with compatibility with the nvidia card.

S:-)

Mixbus Pro 10.0, Kubuntu Linux 64 23.10, Stock Low latency kernel, KXstudio repos, i7-3720QM CPU@2.60GHz, 12 Gb RAM, nvidia GeForce GT 650M/PCIe/SSE2, X.org nouveau driver, Zoom L12 Digital mixer/Audio interface
Reply
#4
(12-22-2019, 06:53 AM)Sthauge Wrote: It's ok with the proprietary nvidia card and driver, but fail with the onboard Intel card, that I use. I also have GL 3 installed and that version is a bit old, but as I understand from forum post it have something to do with compatibility with the nvidia card.

S:-)

Yes, alright - I'm also running on the intel card, not nvidia, on this laptop, and the backtrace shows the i965 driver module. I've played around with bumblebee in the past to see how to switch to nvidia and what the benefit would be, but in the end stayed with the default(=intel). This escaped my attention before I sent my previous post.

I hope we can sort this out soon, as I'd like to avoid messing with graphic drivers once again...
Reply
#5
Maybe you missed my post, but I doubt it's purely a graphics driver problem ?
I have the same GUI problem with those plug-ins and I'm using an AMD card, not nVidia.

I already owned the De-esser plugin - which also comes with my newly purchased SC.
The new DS version doesn't display correctly, but when I reverted to my original one all was OK.
So still a slight chance something else changed, in the plugins ?
Reply
#6
Do they show up as white box even if alone on the screen?
Win7/64, Mixbus32C, Mixbus2.5 the QueenSmile UR22, Dynaudio BM5A MKII, Pc all SSD,
Reply
#7
No I didn't miss your post, but while my graphics subsystem is Optimus (intel AND nvidia) it was running on the intel chip.

From the backtrace I still think it's an issue with the video driver and/or Mesa/GLX/libxcb or the way the new version calls into those. The backtrace indicates that the thread doesn't return from poll(). See this similar bug report for a completely different program: https://github.com/kovidgoyal/kitty/issues/1483

Anyway, as a german saying goes, new day, new luck: I've read up on Optimus, bumblebee/bbswitch and the suse-prime package with its prime-select tool, which already was installed on this box (due to my bad habit of trying things, losing interest and leaving installed stuff in place, but forgetting most of what I did there), and managed to switch to nvidia driver (pretty straightforward), and indeed the AVA-DS and -SC GUIs display perfectly fine.

So, for me it's solved for now, but I think it would be nice to more generally resolve this.

So for now there's only one more thing left to do:

I wish merry Xmas and a happy new year to everyone!

Edgar
Reply
#8
(12-24-2019, 05:30 AM)Tassy Wrote: Do they show up as white box even if alone on the screen?
Yes.

(12-24-2019, 06:36 AM)edogawa Wrote: No I didn't miss your post, but while my graphics subsystem is Optimus (intel AND nvidia) it was running on the intel chip.

From the backtrace I still think it's an issue with the video driver and/or Mesa/GLX/libxcb or the way the new version calls into those. The backtrace indicates that the thread doesn't return from poll(). See this similar bug report for a completely different program: https://github.com/kovidgoyal/kitty/issues/1483

Anyway, as a german saying goes, new day, new luck: I've read up on Optimus, bumblebee/bbswitch and the suse-prime package with its prime-select tool, which already was installed on this box (due to my bad habit of trying things, losing interest and leaving installed stuff in place, but forgetting most of what I did there), and managed to switch to nvidia driver (pretty straightforward), and indeed the AVA-DS and -SC GUIs display perfectly fine.

So, for me it's solved for now, but I think it would be nice to more generally resolve this.

So for now there's only one more thing left to do:

I wish merry Xmas and a happy new year to everyone!

Edgar
Glad you got it figured out Cool
Yeah, I've had my share with Bumblebee too, but switched to AVLinux on my laptop. I haven't tried installing the plugins on that OS so I guess I'll give it a try...

Happy new year Wink
Reply
#9
I don't know if it's related, but generally speaking it's better to not install the intel driver. Just run with the kernel modesettings. I bet you guys had some sr0 related errors in the kernel log.

Some links:
http://www.phoronix.com/scan.php?page=ne...-Intel-DDX
http://www.phoronix.com/scan.php?page=ne...DDX-Switch
https://community.kde.org/Plasma/5.9_Errata#Intel_GPUs
Reply
#10
Hello,

I just got AVA Spectral Compressor (I've been using the other AVA plugins for some time) and in order to use it I installed the current (as of yesterday) demo installer for the AVA plugins.

Unfortunately on openSUSE Leap 15.1 (built in Intel graphic of i5-3570K) I've encountered the "empty plugin window with white rectangle" for both DS and SC in Ardour as well as in Carla. I've uninstalled the previously used Intel Xorg driver but even with the modesetting driver, the problem persists.

Questions: Is there a solution? If yes, which? Why are the other AVA plugins (LegacyQ, MC, ME) working fine?

Thanks in advance!
Arnd
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)