[Bug]: Problem with BespokeSynth being "killed" when using it with pipewire-jack

[PrinzNika]

Detailed steps on how to reproduce the bug

https://github.com/BespokeSynth/BespokeSynth/issues/500 as described in this issue, BespokeSynth, that uses Juce for its audio processing, crashes directly on startup, when used with pipewire. The people commenting on the Issue seem to be pretty sure that it is an problem related to compatibility between Juce and Pipewire, but I didn't see any open issue about this here. Would be nice if this could get investigated by some developers.

What is the expected behaviour?

well.. that bespoke opens even when running with pipewire-jack

Operating systems

Linux

What versions of the operating systems?

Manjaro

Architectures

x86_64, 64-bit

Stacktrace

No response

Plug-in formats (if applicable)

No response

Plug-in host applications (DAWs) (if applicable)

Bespoke Synth

Testing on the develop branch

The bug is present on the develop branch

Code of Conduct

• [X] I agree to follow the Code of Conduct

[ghost]

An approach might be to provide native pipewire output.

For example https://github.com/clangen/musikcube/tree/master/src/plugins/pipewireout

[sjomae]

An approach might be to provide native pipewire output.

For example https://github.com/clangen/musikcube/tree/master/src/plugins/pipewireout

So then it only works with pipewire and not with Jack? No that will certainly not be the right approach imo. Implement good Jack support, then it also works with Pipewire. Example is here: https://github.com/jpcima/ADLplug/blob/master/sources/jack_main.cc

[Sahaathyva]

I add myself to this, bespoke wont start with JACK backend selected

What has been thinked for this case and globally JACK backend handling ?

[PowerUser64]

Also related, including a solution that involves patching JUCE: https://github.com/BespokeSynth/BespokeSynth/issues/626

[Sahaathyva]

Thanks @PowerUser64 , i tried this patch, it does not work sadly :(