JackOpenError when (re)creating clients with identical name

[spatialaudio]

JackOpenError when (re)creating clients with identical name

[HaHeho]

Can somebody else confirm the behavior? My testing was done on macOS 10.15.7, jackd 1.9.16 (via the new installer) and jack-client 0.5.3.

I very much assume that this error has nothing to do with the Jack Python API, since I also encountered this when instantiating ecasound via shell scripts. However, this was the most straight forward way to test the behavior to me. Maybe we can help to resolve the issue upstream by narrowing it down first.

I did not encounter this problem (at least so systematically) before jackd 1.9.16. Maybe the provided binaries are not perfect yet and are causing the issue here. I think testing the latest version, but built locally in the traditional way, would be the first case to check whether it behaves differently. Doing this on my dev system is inconvenient though.

@mgeier do you have a convenient way of testing this on different Jack versions and OS?!

[C0nsultant]

This is reproducible upstream without the Python binding. It's a problem I've faced on Windows since at least 1.9.11.
I reported this at jackaudio/jack2#658 together with a reproducer (not really a convenient way of testing).

[HaHeho]

Resolved with jackaudio/jack2#788.