move control app launching back into audio backend to allow ASIO/CoreAudio model...
authorPaul Davis <paul@linuxaudiosystems.com>
Tue, 10 Sep 2013 01:23:12 +0000 (21:23 -0400)
committerPaul Davis <paul@linuxaudiosystems.com>
Tue, 10 Sep 2013 01:23:12 +0000 (21:23 -0400)
commit2a8923402776a4542de5d8b79cb101b1c997c36d
treedd98c854daa2994f5703cafb2115a9ccade6fbc1
parent29c9d94dbe76f94e8126550fcb9513182b17fbb5
move control app launching back into audio backend to allow ASIO/CoreAudio model to work; push initial state of AMS dialog to backend

Issues remain with the basic model of the AMS dialog - when is
newly chosen state pushed into the backend (which can then
modify the control app button sensitivity. This is a special
problem for this button because APIs like ASIO and CoreAudio
probably don't allow us to launch a control app for an arbitrary
device, but only one actually in use. In this sense it is
different from properties like available buffer size etc, where
we can typically query without actually using the device.
gtk2_ardour/engine_dialog.cc
gtk2_ardour/engine_dialog.h
libs/ardour/ardour/audio_backend.h
libs/backends/jack/jack_audiobackend.cc
libs/backends/jack/jack_audiobackend.h