On Donnerstag, 23. Mai 2019 14:06:51 CEST David Bolton wrote: > Here's the messages I get when I launch linuxsampler.exe from the command > line: > > C:\Program Files\LinuxSampler\64>linuxsampler.exe > LinuxSampler 2.1.0.svn8 > Copyright (C) 2003,2004 by Benno Senoner and Christian Schoenebeck > Copyright (C) 2005-2019 Christian Schoenebeck > Binary built: Mar 11 2019 > Detected features: MMX SSE SSE2 > Automatic Stacktrace: Off > Creating Sampler...OK
So like I expcted, the stand-alone app runs there. Then the problem you have with the LS VST not launching in Ardour is indeed very likely caused by a conflicting libstdc++ version. Background: we are currently still using GCC as compiler on our build server for compiling the daily snapshot installers for Windows. And I am pretty sure your Ardour binary was compiled with clang. The two compilers use their own implementation of libstdc++, and both cannot be loaded into one process at the same time. Like already suggested in the Ardour forum, one workaround would be if we statically link libstdc++ into our binaries (instead of letting our binaries load libstdc++ dynamically as DLL on startup like it is now). But that is tricky and may introduce new problems, since all libs used must then use our statically linked libstdc++ instead. Another option would be if we just switch to clang for compiling the Windows installer. But then it would cause other DAWs getting the same VST issue if they were compiled with GCC instead. IMO the best solution on long term would be Ardour running VST plugins in their own process, instead of loading VST plugins directly into the Ardour process. That way libs loaded by VST plugins would no longer conflict with libs of other plugins or host app (i.e. Ardour). Because even if we do some of the workarounds mentioned above, the next issue would already be ahead: e.g. if you want to edit a gig file currently being played back as VST instrument in Ardour, then our gigedit instrument editor would try to load Gtk3 libs, and Ardour already loaded Gtk2 libs, hence gigedit would never show up on your screen. I know the opinion of Ardour developers is that running plugins in their own process would be inefficient due to expensive context switches, but other DAW apps like Logic already switched to that new model and performance seems to be Ok nowadays. In the end this could also become an optional setting per plugin on Ardour side. Opinions? > Starting LSCP network server (0.0.0.0:8888)...LSCPServer: Could not bind > server socket, retrying for 180 seconds...gave up! That error is probably because the LSCP server crashed with your VST plugin. Rebooting should fix that issue. > If try to open the qsampler.exe stand-alone app, I get the following error: > > --------------------------- > qsampler.exe - System Error > --------------------------- > The code execution cannot proceed because Qt5Network.dll was not found. > Reinstalling the program may fix this problem. I just fixed that in our Windows installer scripts. So when you download the latest installer, that error should be gone now. > If I open JSampler, it complains about not being able to find javaw.exe > (even though I added the javaw.exe folder to the Windows path variable and > restarted the computer). However, I can manually browse to javaw.exe at > each start up and JSampler opens. When it opens I get the following error > message: "Connecting to LinuxSampler: Can't establish connection" No idea about that one. I have to add, I am actually no longer using Windows for several years, same applies to Java. CU Christian _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
