#32 Liblo 2.7.1 doesn't work properly for x86_64

[DaveJ]

Description of problem:
The fluidsynth-dssi plugin is not functional from Rosegarden as it will not allow sound fonts to be loaded or voices to be selected.

Other dssi plugins cannot open dialog boxes either.

Version-Release number of selected component (if applicable):

How reproducible:
Always

Steps to Reproduce:
1. Start qjackctl
2. Start Rosegarden
3. For any track, in Track Parameters panel on left select Device -> Synth plugin
4. In Instrument parameters press "<no synth="">" button
5. A "Synth Plugin" dialog will appear. As "Plugin:" select FluidSynth DSSI plugin
6. Try to press "Editor" button at bottom of dialog</no>

Actual results:
Nothing happens

Expected results:
A dialog appears that allows you to load and select Soundfonts

Additional info:

1. "yum downgrade liblo" fixes the issue. liblo 2.6 works with x86_64.

2. Tried to test fluidsynth-dssi from command line without Rosegarden:

jack-dssi-host fluidsynth-dssi.so

jack-dssi-host: Warning: DSSI path not set
jack-dssi-host: Defaulting to "/usr/local/lib64/dssi:/usr/lib64/dssi:/usr/local/lib/dssi:/usr/lib/dssi:/home/kecskebak/.dssi"

Cannot lock down 107335194 byte memory area (Cannot allocate memory)

jack-dssi-host: OSC URL is:
osc.udp://localhost.localdomain:15662/dssi/fluidsynth-dssi/FluidSynth-DSSI/chan00

host: Ready
fsd-gui starting (pid 1933)...
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
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.

This bug has been logged by Fedora and Archlinux

https://bugs.archlinux.org/task/35841
https://bugzilla.redhat.com/show_bug.cgi?id=988421

[Stephen Sinclair]

Hi, this is a known problem. Should be fixed in master branch. There is no 2.7.1, only 0.27, but perhaps I should do a bug-fix release soon.

[Stephen Sinclair]

Can you please verify that this is fixed in master?

[Orcan Ogetbil]

The issue still persists on the latest master checkout

[Stephen Sinclair]

I reproduced the problem and found that it was fixed in the x86_64 branch. I have now merge this branch with master, and the problem is resolved according to my observations.

Fixed in 7a38f5b385d67c3ccffc9e828fcc53c8ca739f01.