Qtractor opens empty window when editing VST

[d.healey]

I've loaded a native VSTi onto a track, but when I double click it to edit its settings, Qtractor pops up with a second window that's completely empty. Closing this second window closes the plugin's interface. Also the plugin always opens in the top left of the screen and I'm unable to move it.

index.jpg (20.54 KiB) Viewed 1178 times

[rncbc]

I've loaded a native VSTi onto a track, but when I double click it to edit its settings, Qtractor pops up with a second window that's completely empty. Closing this second window closes the plugin's interface. Also the plugin always opens in the top left of the screen and I'm unable to move it.

this indeed might happen with some (old) VST2... and probably if running the qtractor.AppImage...
which one is that, qtractor and plugin version? where did you got them? did you compile either from source ?
does it happen the same for all VST2 or just that one in particular?
cheers

[d.healey]

I've loaded a native VSTi onto a track, but when I double click it to edit its settings, Qtractor pops up with a second window that's completely empty. Closing this second window closes the plugin's interface. Also the plugin always opens in the top left of the screen and I'm unable to move it.

this indeed might happen with some (old) VST2... and probably if running the qtractor.AppImage...
which one is that, qtractor and plugin version? where did you got them? did you compile either from source ?
does it happen the same for all VST2 or just that one in particular?
cheers

Hi,

I compiled Qtractor from source and the plugin is VST2, also compiled from source. I'm finding this issue with all of my VST/VSTi plugins, both native and bridged using LinVST.

I'm also noticing that some of my plugins aren't showing up in Qtractor after rescanning, is there a blacklist?
I see this message during the scan - QProcess: Destroyed while process ("/usr/local/lib/qtractor/qtractor_plugin_scan") is still running.

[rncbc]

I'm finding this issue with all of my VST/VSTi plugins, both native and bridged using LinVST.

what Qt5 version ? what graphics subsystem? X11, Wayland?

I'm also noticing that some of my plugins aren't showing up in Qtractor after rescanning, is there a blacklist?
I see this message during the scan - QProcess: Destroyed while process ("/usr/local/lib/qtractor/qtractor_plugin_scan") is still running.

there is no blacklist; however, if a plugin crashes during scan it won't show up in the result list...while the scanning process is resumed to the next plugin in search path...

seeya

ps. i've tried one of (your) plugins, the only one that can be downloaded for 0$, and it shows up alright here (qtractor 0.9.16, Qt 5.15, KDE Plasma 5, X11, openSUSE Tumbleweed).

[d.healey]

QMake version 3.1
Using Qt version 5.9.5

X11, Cinnamon 4.4.8, Linux Mint 19.3

[rncbc]

can you try the latest v0.9.16 AppImage? it has Qt5.15 bundled in

thanks

[d.healey]

Oh I didn't even know there was an appimage! Thanks, that solved all of the problems I mentioned

[rncbc]

Oh I didn't even know there was an appimage! Thanks, that solved all of the problems I mentioned

many thanks for taking the chores to try this out, really appreciate that

on the investigative side this ends up as either your build of qtractor is falling short or your mint system on qt5.9 is too dang old for this VST2 tropes whatever (which already are old by 2020 standards;)
consider to move it all to VST3 sooner than later, please. _or_ what holds you up on LV2 delivery, may I ask?
cheers

[d.healey]

consider to move it all to VST3 sooner than later, please. _or_ what holds you up on LV2 delivery, may I ask?

Yes I plan to use VST3 with the next release. JUCE holds up the LV2 although I've seen that some work has been done to try and make it compatible so I shall have to investigate this.