On Friday, 8 May 2026 03:02:41 CEST TJ Lindgren via Linuxsampler-devel wrote: > Hi, I just wanted to check in on the state of LinuxSampler on macOS and > Apple Silicon. To my knowledge there is no way to run LinuxSampler on a > recent version of macOS or an Apple Silicon machine.
I guess you mean the automatic builds from the LS website. These do not even build an arm64 slice for the macOS binaries yet, only x86 slices. I assume you used Rosetta to launch them on Apple Silicon. > My question is, has anyone successfully managed to do this? And if so, how? > > Here’s a semi-exhaustive list of my findings trying to use LinuxSampler on > an M4 Mac Mini Pro running macOS Sequoia 15.7.4 > > - AU plugin: This plugin will not scan properly in almost all DAWs except > for Reaper. Although Reaper is able to scan the plugin, it cannot open it. > All other DAWs I’ve tried such as Logic and Plogue Bidule the plugin fails > to scan properly. > > - VST2 plugin: No DAW I have tried properly scans the VST2 plugin so I can’t > test whether it works. I’ve tried recent wrappers as well including this > one, which unfortunately did not work even though it can load older plugins > such as the Camel Audio VST2 plugins. > > https://github.com/mannixsquared/vst-wrapper I bet the plugins are not detected by VST/AU hosts on Apple Mx Macs because they would only accept arm64 plugins, not x86 ones. > Graphical Front Ends: > > - QSampler: The latest build will not load due to not being able to load > QtSvg. > > "Library not loaded: QtSvg.framework/Versions/5/QtSvg” > > QtSvg has been installed via homebrew as well as Qt@5. However, QSampler > still can’t find it. I just addressed that. The latest Mac snapshot build does include this and other Qt frameworks now. So far we had an explicit list of Qt frameworks to be bundled with the Mac installer. But as one can see, this can easily be forgotten if the dependency changes on QSampler side. So I added all Qt frameworks now. The size diff is not worth it anyway. > Previous builds of QSampler would not work unless you symlinked the latest > libgig dylib file and renamed it to an older version (e.g. symlink > libgig.11.dylib and rename it to libgig.10.dylib) OK, but that's actually been a while when that happened to you for the last time, right? In the past, yes, that used to happen after new releases, as libs like libgig got their version bumped and that involved manual changes on our build server. But in the meantime I have automated the release process to prevent such things from happening, i.e. the build server configuration is automatically updated on new releases. Nevertheless, it would be better to send a short message to the mailing list than using such short wire library tricks. Because different libgig versions are in fact not compatible with each other. > - Fantasia: The Fantasia version that installs with the latest build will > only run if you right-click the app, go to Show Package Contents and > navigate to Contents/MacOS/Fantasia and open the jar file directly. The > Universal Java Application Stub trick from a few years back where you > renamed the current JavaApplicationStub and replaced it with the Universal > one no longer works. > > The self-contained Java version released here: > > https://github.com/grigoriliev/jsampler-fantasia/releases Well, Fantasia hasn't been worked on for so many years that I fear that Fantasia has to be removed from installers in near future anyway, unless somebody volunteers (which I doubt) to update Fantasia sources for it to work with a more recent Java version. The Java version Fantasia depends on is so old, that it doesn't make sense from security PoV alone, and of course all the struggle on modern systems to make it running. > I realize this is a pretty niche user base, especially on MacOS. However, > there is currently no other way to play gig instruments and it really has > been a fantastic tool in the past. For someone like me with a large amount > of custom giga libraries, it would be really great to see this working > again on latest Macs/Apple Silicon. If there’s any more information I can > provide, please let me know. Yeah I guess that's the main problem here: right now I am basically the only one working on this stuff here, at least in the last bunch of years. And I can't work (or care) for everything. Most people just stop by, ask some question, and that's it. I don't even see people helping other people with their questions. /Christian _______________________________________________ Linuxsampler-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
