On Fri, Nov 14, 2008 at 03:47:17PM +0200, Hannu Savolainen wrote: > There is no point in letting any application to change such settings so > it has intentionally been made pretty much impossible.
If you think this applies to my situation you are wrong on all accounts. 1. It not "made pretty much impossible" in ALSA, all it takes (on the command line) is an 'amixer sset'. 2. I am the system administrator. I may want to use an application to do part of my work. 3. The studio wiring can change at any time. There are four PCs, four ADI648s and MADI connections between them are made via an RME MADI switch. This is controlled by software as well. MADI wiring is in function of the current project or session. 4. If ALSA would allow me to set "Sample Clock Source" to "AutoSync", "Preferred Sync Reference" to "MADI" and "System Clock Mode" to "Slave" AND ENSURE THEY STAY SET LIKE THAT then I wouldn't have to touch them. But it will switch to "Internal 44.1 kHz" and "Master" whenever there is no MADI signal on the input and it will *not* go back to the original settings when a signal is present again. Since the MADI links are switched, this can happen and it should not leave the system in an inconsistent state. Hence I do have to monitor these settings permanently and take action when they are wrong. Ciao, -- FA Laboratorio di Acustica ed Elettroacustica Parma, Italia Lascia la spina, cogli la rosa. _______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
