You are here

liblo error on attempting to open DSSI GUIs

I've just done a clean install of OpenSUSE 13.1 64 bit and installed Qtractor 0.5.12.8 from svn. I'm unable to open DSSI GUIs (fluidsynth, xsynth, whysynth) via either the Mixer window or the Track window. I either get the following kinds of errors, or no error at all (seems to depend on the liblo version):

liblo error: lo_send, lo_message_add, or lo_message_add_varargs called with mismatching types and data at
FluidSynth-DSSI_gtk.c:350, exiting.
liblo error: lo_send, lo_message_add, or lo_message_add_varargs called with mismatching types and data at
gui_main.c:267, exiting.

Looking around, it seems other people have had the same problem on a 64 bit OS. They say version 0.26 of liblo should work; however, it doesn't seem to work for me. I've tried the below versions (not sure of the differences between liblo0 and liblo7, so will list both):

liblo-devel
0.27-2.2 (from rncbc repo)
0.26-31.1

liblo7
0.27-2.2 (from rncbc repo)
0.26-31.1

liblo0
0.25-22.1.2

dssi/dssi-devel
1.1.1-29.1
1.1.1-7.1.2

I searched this forum and found this old post, but I'm not sure if it's relevant, or what you mean by "correctly configured". My /etc/hosts file does have the line:

127.0.0.1 localhost

I'd be very grateful if you could let me know how to go about fixing this.

Forums: 
rncbc's picture

might well be some liblo.so mismatch (dis)alignment, whatever :/

try to regress to liblo(-devel) as it's supplied by opensuse/packman repos, as probably it's the one for which the plugins you're after were linked for in the first place.

in any case, please try also with The reference implementation dssi host of them all: jack-dssi-host ...

hth.
cheers

The standard openSUSE/Packman versions of liblo and liblo-devel (0.25-22.1.2) were actually among the ones I tried yesterday. Just in case, I tried again today, but no luck.

However, I looked deeper into the /etc/hosts issue and managed to solve the problem by adding my actual hostname (not "localhost") to /etc/hosts. Not sure if that's the "correct" way to fix this, but I have working GUIs now so it's fine with me :-) I've never needed to do this before, though.

Unfortunately, though, I've just discovered something strange, which may be related to this, or may be a quirk of the new install (something goes wrong in my audio set-up on every new install, without fail :-)). I have a default template loaded and, though the DSSI GUI now works, sending a test note via "Send test note" for any of the plug-ins I've tried (xsynth, whysynth, fluidsynth) produces no response - no sound and no reaction from the mixer meters. In the following cases, however, sending a test note works fine:

- adding a new track to the template (test note works in this new track only; not in the others)
- re-loading a previous project
- adding a track in a new session with no template

If you have any ideas what may be causing this, I'd be interested to know. I've tried two templates, both of which were working in my previous openSUSE/Qtractor install, but neither of which works now. I've also tried creating a new template in this version of Qtractor and the same problem occurs upon loading it.

rncbc's picture

re. the new session default template,

a. is there anything special regarding the DSSI plugins instances you're trying to "send test note" ?

b. what about the MIDI tracks audio output bus? is it dedicated or is it set as default (Master out) ?

c. please try to load the template as usual but then save it as another name; use the new one as new session template; does it behave the same ?

hth.
cheers

Thanks very much for the info - the culprit was "b". I was using dedicated outputs, which had become a bit mixed up (my own fault), so the audio wasn't being routed correctly. Doh :-( Everything looks fine now - sorry for the hassle.

Add new comment