infra-clients are about those client applications that are not coded with specific jack-session support but you want to let them get automatically started when loading a previously saved jack-session.
for instance, qsynth has no jack-session support. if you save a session where qsynth participates, next time you load that session you will see that qsynth don't get automatically started so that you'll ought to launch it manually at least once.
that's the trick of infra-clients: you set the corresponding command executable for missing client names on session load. you probably would notice that qjackctl automatically adds suspect missing client names when saving a session, the ones marked with a small white cross on a red circle. you are then suggested to edit and set their respective launch command line immediately, otherwise it won't get run when loading the just saved session and, also important to note, won't get saved through next time you run qjackctl.
thus, the infra-client table is a map that associates client-names to their corresponding launch command line, as shown on the bottom-half pane of the session window. it gets implicitly saved on configuration file so it lives, better said survives, across qjackctl runtime cycles.
infra-clients are about those client applications that are not coded with specific jack-session support but you want to let them get automatically started when loading a previously saved jack-session.
for instance, qsynth has no jack-session support. if you save a session where qsynth participates, next time you load that session you will see that qsynth don't get automatically started so that you'll ought to launch it manually at least once.
that's the trick of infra-clients: you set the corresponding command executable for missing client names on session load. you probably would notice that qjackctl automatically adds suspect missing client names when saving a session, the ones marked with a small white cross on a red circle. you are then suggested to edit and set their respective launch command line immediately, otherwise it won't get run when loading the just saved session and, also important to note, won't get saved through next time you run qjackctl.
thus, the infra-client table is a map that associates client-names to their corresponding launch command line, as shown on the bottom-half pane of the session window. it gets implicitly saved on configuration file so it lives, better said survives, across qjackctl runtime cycles.
hth.
cheers