[Bug] Weird connection names in Jack patchbay

[sylsau]

$ jackd --version
jackdmp version 1.9.16 tmpdir /dev/shm protocol 8
$ seq64 --version
seq64 0.96.8-7-g895de580 * master 2020-07-05
Built Jan 19 2021 21:19:24
  C++ version 201402
  App name: seq64; type gtk; engine rtmidi
  Build OS: 'Linux 5.10.7-arch1-1 x86_64'
  Native JACK/ALSA (rtmidi)
  Event editor
  Follow progress bar
  Highlight edit pattern
  Highlight empty patterns
  JACK session
  JACK support
  Seq32 chord generator, LFO window, menu buttons, transpose
  BPM Tap button, solid piano-roll grid
  Song performance recording
  Optional pattern coloring
  Multiple main windows
  Pause support
  Save time-sig/tempo
  64-bit

Hello,

First and foremost thank you for your amazing software. The linux audio ecosystem is in need of this kind of KISS programs that can do one thing perfectly -- also I'd gladly exhort you to play a blind ear to any fancy cosmetic need some people might have -- if it's a fast and stable MIDI sequencer, who cares how it looks? ;-}

Anyway, i am simply here to report a bug that should be simple to fix, namely that seq64's ports on Jack patchbay seem to take the names of the program they happen to be auto-linked to at startup. This might cause problem on resuming a Jack session with QJackCtl and others.

Attached here are screenshots of the patchbay in Carla and QJackCtl. I guess the ports should just be "midi_in" and "midi_out_1", "midi_out_2".

Thank you for your work!

[sylsau]

After having read the manual, I must say I feel silly for not uncovering the command-line options sooner...

This problem can be temporarily fixed by disabling autoconnect of Jack ports : seq64 -mR (if I recall correctly -- can't test it right now).