Personally, the connections dialog works fine for me, but I was just trying to come up with a solution to the suggestions that both Alex and Domenik were talking about. At least that is the way I understood their requests.
I don't think any hardwiring to any external program would be necessary to pull this off (unless our terminology of hardwiring is in misunderstanding).
* When creating a new track, be it audio or MIDI, scan the jack apps list, once for MIDI apps, and once for Audio apps, creating an array for each. This array might even include the full path to the app that is connected to jackd.
* In the Track dialog, when selecting the input, fill that widget with the results of the jackd apps scan. If it's an audio track, include all the audio programs that are connected to jackd. And the same if it's a MIDI track.
* So now, not only is the normal "Master" present as an input choice, but also the running audio apps are also available.
* Select an app from this list, such as Qsampler. This would then auto patch the connections dialog to said track input.
* If possible to also capture the program's run path, that could be stored in the project file, and the external apps could also then be automatically restarted when loading a project that includes them.
This 'might' be a very clever way to make it seem as if things are hardwired, when in fact, they are not. :))
Personally, the connections dialog works fine for me, but I was just trying to come up with a solution to the suggestions that both Alex and Domenik were talking about. At least that is the way I understood their requests.
I don't think any hardwiring to any external program would be necessary to pull this off (unless our terminology of hardwiring is in misunderstanding).
* When creating a new track, be it audio or MIDI, scan the jack apps list, once for MIDI apps, and once for Audio apps, creating an array for each. This array might even include the full path to the app that is connected to jackd.
* In the Track dialog, when selecting the input, fill that widget with the results of the jackd apps scan. If it's an audio track, include all the audio programs that are connected to jackd. And the same if it's a MIDI track.
* So now, not only is the normal "Master" present as an input choice, but also the running audio apps are also available.
* Select an app from this list, such as Qsampler. This would then auto patch the connections dialog to said track input.
* If possible to also capture the program's run path, that could be stored in the project file, and the external apps could also then be automatically restarted when loading a project that includes them.
This 'might' be a very clever way to make it seem as if things are hardwired, when in fact, they are not. :))
Does this make more sense?
Lexridge