Cable icon indicating copy to clipboard operation
Cable copied to clipboard

[Feature request/suggestion] Add option to open the app directly to the graph

Open fabioraitz opened this issue 2 months ago • 6 comments

A command line option to open the application directly to the graph would be very useful . something like cable --graph argument so we could run from terminal or a new shortcut to make quick new audio routes. Other tabs on the cables window could have those argument shortcuts also.

fabioraitz avatar Oct 19 '25 18:10 fabioraitz

It should be doable, as long as you are not requesting graph tab to work as a separate window. When and if I would attempt it, I don't know.

Right now, your options are: -you can setup "Cables" as default app in tray menu. It will take a single click on tray icon to open graph if that was your last active tab. (behaviour may vary in different desktop environments though). -you can run Cables window directly with 'python connection-manager.py' (very verbose in terminal!)

magillos avatar Oct 20 '25 16:10 magillos

I don't think it need to work separate, just a shortcut. I didn't realize using the default setting on systray work that way because I don't use the app on systray. I was suggesting because I was wondering if the app could replace qpwgraph all togeter for me. I open it wit hot keys so a specific command line for the graph function would work just as I need. I use the .deb version. is there a way to open graph directly from terminal in this version?

fabioraitz avatar Oct 20 '25 18:10 fabioraitz

python3 /usr/share/cable/connection-manager.py

You will need to accept its verbose output. I have it there for diagnostics and it's normally not visible.

magillos avatar Oct 20 '25 19:10 magillos

Doesn't work.

$ python3 /usr/share/cable/connection-manager.py
Warning: alsaaudio.MIXER_CAP_PVOLUME not found. Using default int value 2.
Warning: alsaaudio.MIXER_SWCAP_PLAYBACK not found. Using default int value 1.
Warning: alsaaudio.MIXER_CAP_CVOLUME not found. Using default int value 1.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
exec of JACK server (command = "/usr/bin/jackd") failed: No such file or directory
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
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
Traceback (most recent call last):
  File "/usr/share/cable/connection-manager.py", line 61, in <module>
    sys.exit(main())
             ^^^^^^
  File "/usr/share/cable/connection-manager.py", line 51, in main
    window = JackConnectionManager()
             ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/cables/connection_manager.py", line 89, in __init__
    self.client = jack.Client('ConnectionManager')
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/jack.py", line 213, in __init__
    raise JackOpenError(name, self._status)
jack.JackOpenError: Error initializing "ConnectionManager": <jack.Status 0x11: failure, server_failed>

Anyway, I'll keep using qpwgraph, or the cables tray shortcut.

fabioraitz avatar Oct 20 '25 20:10 fabioraitz

If you are on Ubuntu based system, you may need to run it with pw-jack.

magillos avatar Oct 20 '25 20:10 magillos

Worked! Thanks!

fabioraitz avatar Oct 20 '25 20:10 fabioraitz