-
Nedko Arnaudov authored
Parameter order doesnt matter for jackd but does for jackdbus. jackd sets parameters (via Control API) in the order they were specified at commandline. Thus, the jackd user is expected to specify parameters in correct order. This is not good solution for jackdbus though. jackdbus settings persistence in ~/.config/jack/jack.xml stores parameter in the order they are defined by the driver. OTOH the D-Bus interface itself suggests no particular order. For example the user can change only one parameter via the jack_control tool. Other parameters either have their default values or the ones that were previously set are used. The particular ordering problem this changeset aims to fix is that when user specifies capture/playback device and device, the first one(s) is/are ignored. This happens because the device parameter is set after the capture/playback device parameters. The alsa then uses the string from the device parameter for both capture and playback devices, despite the user wish to override one or both of them.
3b12bcf1