From: Pieter P. <pi...@jo...> - 2008-10-27 22:40:13
|
Daniel Wagner wrote: >> would it be possible without too much pain to check for the streaming >> state and grey out those controls which are currently not available? >> that would spare the users a lot of confusion. > > I have a patch here which implements a dbus server which exports the > streaming state. This would be needed also for a workaround for the > fa101. Though I don't know if Pieter likes my approach. Basically it > adds a dbus server into the libffado part direclty. But first I have to > test it and get it working. I would prefer to not have the DBUS server in libffado. I would like to keep libffado itself as free as possible from unnecessary dependencies. That's why I went through the hassle of creating a control abstraction in libffado that is used by the dbus server. If it is merely checking the state of the streaming subsystem, it can be done quite easily without very large code changes. It's just a matter of adding a new control element in the 'generic' portion of the control tree that exports the stream state. As far as I know it is possible for all devices to figure out whether they are streaming or not, without actually being the streaming client. For bebob's one can look at the IEC plug status. > >> more specifically, those options which *are* available but would kill a >> running jackd should be greyed out or at least protected by an "are your >> sure" dialog (for instance, the (de-)activation of additional adat ports >> or the change of sampling rate). >> >> if it's not too hard and intrusive, i would like to suggest such a >> feature for 2.1.... > > Well, I really like to have this in 2.0. I'd like to have a correct > mixer app for the fa101 before we start improving it (such as 'better' > scale for the faders etc). I don't want to include any major changes in the 2.0 codebase anymore. A DBUS server in libffado qualifies as major. Greets, Pieter |