>btw, what was the biggest reason to change to XML in ardour? >it used guile once upon a time.
i didn't like the fact that the entire main() call had to be encapsulated within a guile invocation (given what ardour does with memory, threads, scheduling, etc, etc). i also didn't like having to require guile be installed, and lastly, perhaps most importantly, ardour was going to use XML for data files (session state information etc) to further inter-operability, and so we decided to switch to XML throughout. >this can be implemented better once when we have an ordinary-mixer >API. the problem was that the action to do is different for each >card, and it's not abstracted (nor unified) so far. >the higher abstraction will absorb such a difference. understood. i'd just to see this as a goal of whatever changes you make. ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
