You are here

UI error for the Vee suite

Hi Rui,

Disclaimer: I am not sure whether this relates to kxstudio or qtractor.
Upgraded to Qtractor 0.6.2 and 0.5 Vee's all from the kxstudio repos. When opening the Vee plugins within Qtractor I get:

suil error: Unable to open UI library /usr/lib/lv2/drumkv1.lv2/drumkv1_ui.so (/usr/lib/lv2/drumkv1.lv2/drumkv1_ui.so: undefined symbol: _ZN12drumkv1_waveC2Ejt)
suil error: Unable to open UI library /usr/lib/lv2/synthv1.lv2/synthv1_ui.so (/usr/lib/lv2/synthv1.lv2/synthv1_ui.so: undefined symbol: _ZN12synthv1_waveC2Ejtt)
suil error: Unable to open UI library /usr/lib/lv2/samplv1.lv2/samplv1_ui.so (/usr/lib/lv2/samplv1.lv2/samplv1_ui.so: undefined symbol: _ZNK7samplv19loopStartEv)

Occurs on both Wheezy and Mint14. Apart from that everything works fine.
A small issue with TAL NoizeMak3r plugin: when using a preset and closing/opening qtractor the preset is not loaded 'correctly'. It sounds like some parameters are loaded, but not all. NoizeMak3r is the only plugin having this issues to my knowledge.

Feature requests for 0.7.x + ...
I find myself looking for the ability to mute a single clip. I know that there are workflow-workarounds to fix this, but an easy right-click mute option would be great.
Individual clip-colors: Such a feature would be cool when working with multiple clips, e.g. drums/drumvariations from wav cutups.

Thats it... Keep up the good work and thanks for sharing.
Brg,
Rasmus

Forums: 
rncbc's picture

hi thanks

the issue re. vee one UI is probably one of packaging or messing up with older versions, from qt4 or even the suite itself ?

it seems to be an issue in the kxstudio packaging or build, especially related to the linking eg. between synthv1.so (DSP) and synthv1_ui.so (UI) components. try reading the output of `ldd synthv1_ui.so` and check which synthv1.so it is supposed to be linked to.

hth.
cheers

ps. while on the same example, consider uninstalling any of the synthv1 packages; check if there are leftovers around, namely under /usr/lib/lv2/synthv1.lv2, /usr/local/lv2/synthv1.lv2 or even ~/.lv2/synthv1.lv2 . if there are any, remove them (by force:)); install it again. if the UI still fails, rollback and consider building it from source instead.

pps. you can also try (re)install from custom packagings on my OBS repositories: http://download.opensuse.org/repositories/home:/rncbc/ .

AutoStatic's picture

Got the very same issue. It's probably (probably, assumption is the mother of all you know whats) related to the kxstudio-debian plugins PPA so maybe it's best to inform falkTX about it.

rncbc's picture

hi Jeremy

the part i asked about to `ldd /path/to/synthv1_ui.so` might give us some clues on what's going on...

seeya

AutoStatic's picture

...here it is:

ldd /usr/lib/lv2/synthv1.lv2/synthv1_ui.so
linux-vdso.so.1 => (0x00007fff0d1fe000)
libQtXml.so.4 => /usr/lib/x86_64-linux-gnu/libQtXml.so.4 (0x00007fbe71b62000)
libQtGui.so.4 => /usr/lib/x86_64-linux-gnu/libQtGui.so.4 (0x00007fbe70e94000)
libQtCore.so.4 => /usr/lib/x86_64-linux-gnu/libQtCore.so.4 (0x00007fbe709c1000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fbe707a4000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fbe704a4000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fbe701a7000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fbe6ff91000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fbe6fbd1000)
libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007fbe6f99a000)
libaudio.so.2 => /usr/lib/x86_64-linux-gnu/libaudio.so.2 (0x00007fbe6f782000)
libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007fbe6f48d000)
libpng12.so.0 => /lib/x86_64-linux-gnu/libpng12.so.0 (0x00007fbe6f264000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fbe6f04d000)
libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007fbe6edb1000)
libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007fbe6eb61000)
libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6 (0x00007fbe6e959000)
libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6 (0x00007fbe6e73f000)
libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x00007fbe6e52e000)
libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007fbe6e324000)
libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007fbe6e113000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007fbe6dddd000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fbe6dbd9000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fbe6d9d1000)
/lib64/ld-linux-x86-64.so.2 (0x00007fbe72007000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007fbe6d7a6000)
libXt.so.6 => /usr/lib/x86_64-linux-gnu/libXt.so.6 (0x00007fbe6d540000)
libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007fbe6d33c000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007fbe6d0ff000)
libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007fbe6cef7000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007fbe6ccf1000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007fbe6cad3000)
libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007fbe6c8cc000)

rncbc's picture

i can't see, up there, a link to synthv1.so, which is obviously some kind of a build mistake...

let me compare to mine, ....

> ldd ~/.lv2/synthv1.lv2/synthv1_ui.so
        linux-gate.so.1
        synthv1.so => /home/rncbc/.lv2/synthv1.lv2/synthv1.so
        libQtXml.so.4 => /usr/lib/libQtXml.so.4
        libQtGui.so.4 => /usr/lib/libQtGui.so.4

...
enough. see? a line like synthv1.so => .../synthv1.lv2/synthv1.so must have been there.

i don't even know how that build and packaging got dispatched anyhow. something is really fishy on that ppa or whatever :/

yeah, tell that to kxstudio packagers, have no mercy :)

byee

AutoStatic's picture

export LDFLAGS=-Wl,-O1 -Wl,-Bsymbolic-functions -Wl,--strip-all -Wl,-z,relro,-z,now
Is what is being used for packaging and that causes the linkage issue. It works with:
export LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro

So it's an issue with the KX Studio package.

rncbc's picture

why is LDFLAGS being set like that? what happens if you just unset LDFLAGS ?

byee

AutoStatic's picture

@rapstam, I've modified the LDFLAGS options and pushed new packages to the KX Studio repository. An apt-get update && apt-get upgrade should pull them in and solve your issues.

Working on both Debian and Mint 14. Excellent work.

Add new comment