[Linuxsampler-devel] Linuxsampler on pipewire

[Sawyer B. <saw...@gm...>]

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