While that is a good argument, it didn't outperform the args pro CLI args.nils wrote: ↑Sun Aug 28, 2022 9:40 am The original reasoning was that accepting cli arguments can introduce a conflict. You start a program with a --cli command like "start in rack mode" but then switch it, once it is running, to patchbay mode. Now the session closes and starts again later with --rack . Now what?
There are enough extra work needed by a developer to implement NSM support, so for example avoid to allow the user to quit. For args like the one you give the example for, there could be made the same advice.
But, on the other hand, for example guitarix could make heavy usage of cli args, (And non of them is a "start in degub mode" one).
Here are the ones I really miss under NSM.
Code: Select all
-n, --name=NAME instance name (default gx_head)
-D, --disable-multi-client run guitarix as single client
-I, --idle-timeout=SECONDS starved idle thread probe (default: disabled)
-C, --no-convolver-overload disable overload on convolver missed deadline
-W, --no-watchdog-warning do not pop-up warning for bypassed overload condition
-X, --xrun-overload JACK xrun (default: false)
-S, --sporadic=SECONDS allow single overload events per interval (default: disabled)
-N, --nogui start without GUI
-p, --rpcport=PORT start a JSON-RPC server listening on port PORT
-H, --rpchost=HOSTNAME set hostname to connect to
-G, --onlygui start only GUI
-L, --liveplaygui start with Live Play GUI
-E, --hideonquit only hide GUI instead quit engine
-M, --mute start with engine muted
-b, --bank=BANK:PRESET (A:0-Z:9) set bank and preset to load at startup
-t, --tuner_tet=tuner temperament (12, 19, 24, 31, 41, 53) set tuner temperament at startup
-F, --reference_pitch=tuner reference pitch (225 - 453) set tuner reference pitch at startup
--tuner-midi-feedback send tuner midi feedback