[LAU] jconvolver does not find a running Jack2 server

[Moshe Werner]

Hi everyone,



On Tue, Aug 6, 2019 at 9:40 PM ORL - AMMD <orl at ammd.net> wrote:

> Hi!
>
> Le 06/08/2019 à 20:24, Chris Caudle a écrit :
> > On Tue, August 6, 2019 12:10 pm, Moshe Werner wrote:
> >
> >> Normally I would use Cadence to start Jack
> > Checking jconvolver after starting jackd on the command line would give
> > indication whether Cadence is starting jackd in an unexpected way.
> >
>
> Yep, could be. Once I got a similar problem (a long time ago), and the
> fact is, I played with the jack server name options, and finally the
> apps couldn't recognize the jack server running (iirc because of that
> jack server name). It might be that Cadence runs jack with a specific
> server name, and that you have to run every app through Cadence.
>

How can I check with what server name jack is run by Cadence?
This is the output in Cadence's log window:

Wed Aug 7 06:41:37 2019: Starting jack server...

Wed Aug 7 06:41:37 2019: JACK server starting in realtime mode with
priority 89

Wed Aug 7 06:41:37 2019: self-connect-mode is "Don't restrict self connect
requests"

Wed Aug 7 06:41:37 2019: Acquired audio card Audio2

Wed Aug 7 06:41:37 2019: creating alsa driver ...
hw:D1248,0|hw:D1248,0|128|2|48000|0|0|nomon|swmeter|-|32bit

Wed Aug 7 06:41:37 2019: configuring for 48000Hz, period = 128 frames (2.7
ms), buffer = 2 periods

Wed Aug 7 06:41:37 2019: ALSA: final selected sample format for capture:
24bit little-endian in 3bytes format

Wed Aug 7 06:41:37 2019: ALSA: use 2 periods for capture

Wed Aug 7 06:41:37 2019: ALSA: final selected sample format for playback:
24bit little-endian in 3bytes format

Wed Aug 7 06:41:37 2019: ALSA: use 2 periods for playback




> Another thing I'm thinking of, it might be that Cadence doesn't allow
> self-connection from applications (there is an option in Ladish for
> that, so that you don't have connexions messing up between those made by
> Ladish and those made by the apps themselves). If yes, then maybe
> jconvolver just wants to connect to some jack ports at startup and as
> Cadence doesn't allow it, then it stops.
>

I normally start Ardour not through Cadenca and that works as expected.


>
>
> In both cases, starting with jack in terminal, as Chris said, and
> checking whether you can run jconvolver then will already help avoiding
> some hypothesis.
>
>


 That looks as expected, no warnings shown.
> What happens when that jackd instance is running and you start jconvolver?
> Can you post the same for the jconvolver command?  I tried just to check
> and did not see many startup messages, just one about modifying the
> requested partition size from the conf file.


 with jackd from commamd line:

[moshew at moshe-laptop ~]$ jconvolver
/usr/share/doc/jconvolver/DRC-Salon-Sofa/salonsofa.conf
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
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
Can't connect to JACK

Hi Oliver,

--period 128 -> this is very low. Not all system/hardware are able to
> handle it.


All other programs (Ardour & Pianoteq etc.) work with this settings.
Do you see any reason why jconvolver would not?

Thanks

Moshe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.linuxaudio.org/archives/linux-audio-user/attachments/20190807/9a24137d/attachment.html>