That does seem to be the case, ldd (which qjackctl) | grep jack > > libjack.so.0 => /usr/lib/pipewire-0.3/jack/libjack.so.0 > (0x00007f3af17ae000) >
ldd (which linuxsampler) | grep jack > > libjack.so.0 => /usr/lib/libjack.so.0 (0x00007f603e3cc000) > This is rather strange. Those other applications aren't different from the ones that I ran directly on top of normal jack2, how is linuxsampler doing library discovery here? I'm reasonably confident there isn't any compile time pipewire-specific stuff, since when switching from jack to pipewire I didn't have to reinstall any of these packages. I'm using the pipewire-jack-dropin package that gives extra config args to ld: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=pipewire-dropin Thanks, Sawyer Bergeron sawyerberge...@gmail.com On Thu, Nov 4, 2021 at 10:59 AM Christian Schoenebeck < schoeneb...@linuxsampler.org> wrote: > On Mittwoch, 3. November 2021 00:48:40 CET Sawyer Bergeron wrote: > > Hi All, > > > > I'm trying to get linuxsampler running on top of pipewire using > > pipewire-jack. When creating a channel in qsampler I get the following > > output from linuxsampler: > > > > ``` > > > > > LinuxSampler 2.2.0 > > > Copyright (C) 2003,2004 by Benno Senoner and Christian Schoenebeck > > > Copyright (C) 2005-2021 Christian Schoenebeck > > > Binary built: Jun 3 2021 > > > Detected features: MMX SSE SSE2 > > > Automatic Stacktrace: Off > > > Creating Sampler...OK > > > Registered sampler engines: 'GIG','SF2','SFZ' > > > Registered MIDI input drivers: ALSA,JACK > > > Registered audio output drivers: ALSA,JACK > > > Loading instrument editor plugins...OK > > > Registered instrument editors: 'gigedit' > > > Registered internal effect systems: LADSPA > > > Registered internal effects: 467 > > > Starting LSCP network server (0.0.0.0:8888)...Thread: WARNING, can't > > > mlockall() memory! > > > OK > > > LinuxSampler initialization completed. :-) > > > > > > LSCPServer: Client connection established on socket:8. > > > LSCPServer: Client connection established on socket:9. > > > Cannot connect to server socket err = No such file or directory > > > Cannot connect to server request channel > > > Automatic start of JACK server is disabled at configure time > > > jack server is not running or cannot be started > > > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping > > > unlock > > > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping > > > unlock > > > Cannot connect to server socket err = No such file or directory > > > Cannot connect to server request channel > > > Automatic start of JACK server is disabled at configure time > > > jack server is not running or cannot be started > > > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping > > > unlock > > > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping > > > unlock > > > Seems Jack server is not running. > > > Thread: WARNING, can't assign realtime scheduling to thread! > > > Thread: WARNING, can't mlockall() memory! > > > No audio output device connected to sampler channel > > > > ``` > > > > Some other jack applications (ardour, qjackctl) all seem to happily run > > here so I'm pretty sure pipewire-jack is at least running properly. Are > > there any workarounds known of for this? > > > > Thanks in advance for any info, let me know if any further output would > be > > helpful. > > > > --Sawyer > > Looks like this is about this topic: > https://bb.linuxsampler.org/viewtopic.php?f=6&t=19964 > > So you are saying it does work with other JACK client apps, but it does > not > work with LS being a JACK client. > > Please check against which precise JACK libs those apps are linked to on > your > system, which you can easily do by using 'ldd'. Because from what I can > see, > it looks like the working ones are compiled against a pipewire jack client > lib, whereas LS was maybe linked against the "real" / official JACK > server's > client lib. > > CU > Christian > > > > > _______________________________________________ > Linuxsampler-devel mailing list > Linuxsampler-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel >
_______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
