No Simpledrum in MESS list. I verify the path and presence of the soundfont. It's with OPRE1
No loading of sound fonts with Fluidsynth: Impossible to load the sound font, so no sound on the tracks. OK with OPRE1.
Issue with V4 master
Moderators: MattKingUSA, khz, spamatica
-
- Established Member
- Posts: 118
- Joined: Sat Mar 02, 2019 5:10 am
- Been thanked: 4 times
-
- Established Member
- Posts: 581
- Joined: Mon Feb 08, 2010 10:38 am
- Has thanked: 86 times
- Been thanked: 100 times
Re: Issue with V4 master
This is with the AppImage, right?
Tried it here and I cannot see ŚimpleDrums either.
Edit: Well, what do you know I can't see it with a self built MusE master either. The file is there but MusE does not seem to recognize it.
Tried it here and I cannot see ŚimpleDrums either.
Edit: Well, what do you know I can't see it with a self built MusE master either. The file is there but MusE does not seem to recognize it.
MusE DAW
Re: Issue with V4 master
No idea why that happens, but this seems to be the problem:
I also tested Fluidsynth (with latest AppImage), no problem to be found there.
Code: Select all
pluginScan: Standard error output from scan:
muse_plugin_scan: dlopen(/tmp/.mount_MusE-mL1qNUh/usr/lib/muse-4.0/synthi/simpledrums.so) failed:
/tmp/.mount_MusE-mL1qNUh/usr/lib/libmuse_widgets.so: undefined symbol: _ZTIN7MusEGui15RasterizerModelE
Re: Issue with V4 master
I assume simpledrums.so is dependent on libmuse_widgets.so, which is supposed to be self-contained for this to work.
But RasterizerModel is declared outside of libmuse_widgets.so.
I suppose it's connected to Tim's recent changes to the raster grid.
It seems to be difficult to keep that under control, as there is no compilation error or other hint. Probably the plugins themselves should optimally be self-contained and not rely on core components...
But RasterizerModel is declared outside of libmuse_widgets.so.
I suppose it's connected to Tim's recent changes to the raster grid.
It seems to be difficult to keep that under control, as there is no compilation error or other hint. Probably the plugins themselves should optimally be self-contained and not rely on core components...
-
- Established Member
- Posts: 581
- Joined: Mon Feb 08, 2010 10:38 am
- Has thanked: 86 times
- Been thanked: 100 times
Re: Issue with V4 master
It seems to me it exists in libmuse_core.so, tried to add it to the link list but something more is needed.
It should still be possible to link them correctly. It IS odd that the link stage does not complain.
MusE DAW
Re: Issue with V4 master
Yes, it exists in core (otherwise it wouldn't compile). But I remember the discussion with Tim where he insisted that the /widgets component have to be self-contained and independent of core. There are also similar comments in the code.
Re: Issue with V4 master
This is now fixed (both AppImage and normal build).
Kind of (harmless) workaround, static linkage of the main exe. Seems even to be good for the AppImage, it got some MBs smaller.
Kind of (harmless) workaround, static linkage of the main exe. Seems even to be good for the AppImage, it got some MBs smaller.