Flood of messages with --autoconnect a

[grammoboy2]

Whe one has set --autoconnect a, jackd doesn't autoconnect. But with this setting you get a flood of messages in the terminal. I would think, silence is golden on Unix, so only fail loud when there is a error and be silent when there is no error. Given the fact that I've set --autoconnect a, I would argue that this isn't a error and I shouldn't get this message constantly.

gnoring port self connect request to external port (MPlayer [389410]:out_0 -> system:playback_1) ignoring port self connect request to external port (MPlayer [389410]:out_1 -> system:playback_2) ignoring port self connect request to external port (MPlayer [389410]:out_0 -> system:playback_1) ignoring port self connect request to external port (MPlayer [389410]:out_1 -> system:playback_2) ignoring port self connect request to external port (MPlayer [389410]:out_0 -> system:playback_1) ignoring port self connect request to external port (MPlayer [389410]:out_1 -> system:playback_2) ignoring port self connect request to external port (MPlayer [389410]:out_0 -> system:playback_1) ignoring port self connect request to external port (MPlayer [389410]:out_1 -> system:playback_2)

[nedko]

It is not error, it is warning. Log verbosity can be made more configurable, but I'd rather do it for pipewire at some point than for jack2. Patches are welcome of course. Just removing the message is worse than having it displayed on events it was designed to give light to.