On Jun 12, 2021, at 08:29, Alejandro Olivan Alvarez <[email protected]> wrote:
> Also, recently, re-reading my emails with AudioScience engineer (I worked > with them for an independent Linux project on my job) I realized the > AudioScience ALSA driver provides BOTH (and not 'either' as I had on my mind) > the HPI interface AND the ALSA interface, Interesting! My understanding has always been that it’s ‘either/or’ as well. > so I can use and AudioScience card as Jackd interface (as ALSA interface), > AND let rivendell detect it as an HPI interface, AND enjoy the powerful > Audiocience PCM internal routing abilities (I think, rivendell does not takes > advantage of that, but you can harness all that power with any ALSA mixer)… Rivendell in fact makes extensive use of that ‘anything to anywhere’ architecture, but does so *internally*. It most intentionally does *not* export the arbitrary capability to the end user, because doing so opens up all sorts of opportunities for the user to get the mixer subsystem into inconsistent states. For this reason, I would *not* recommend using the ALSA capabilities simultaneously with Rivendell, Cheers! |---------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |---------------------------------------------------------------------| | A room without books is like a body without a soul. | | | | -- Cicero | |---------------------------------------------------------------------|
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
