Hi!
On 6/13/21 2:47 PM, Fred Gleason wrote:
On Jun 12, 2021, at 08:29, Alejandro Olivan Alvarez
<[email protected]
<mailto:[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.
Aha... It is fun if, upon having AudioScience ALSA package/driver
installed (which conflicts whit HPI-only driver package)... You can use
RDAlsaConfig as it detects and allows you to declare as ALSA useable any
ASI card (that I have tested) in Rivendell.... Afterwards, you go to
RDConfig -> Host -> Audio Resources and ...tada!!! you'll see the card
twice!!! first as reachable through HPI API, and second through ALSA :-P
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!
I think I understand what you're refering to .... The thing is that,
through HPI, the number of Inputs/outputs do match 'only' the number of
physical Inputs/outputs of the card, which, may or not (In my experience
usually not) match the number of of actual PCM inputs / outputs
supported by the card.
For instance, here I'm testing with an ASI5810 and an ASI5720, which
both feature 4 PCM playbacks and 2 PCM records (although both having
different number of physical in/out numbers and types), so, from an ALSA
point of view, both feature 4 playback/outs and 2 record/ins, which can
be used, and then routed, using the ALSA mixer tomanage the card
internal router, to/from any of the card's analog/digital physical
in/outs (Mostly the way Windows users know to use ASI cards through the
ASI manager GUI)
By contrast, from HPI/Rivendell's point of view, apparently only
'physical endpoints' seems to matter... So, ASI5810 has 'only' 2 inputs
/ 1 output , and the ASI5720 fatures 'only' 2 inputs / 2 outputs.
I agree but, that, given Rivendell's perfect integration with Jack,
providing plenty of in/out, the best approach is to completely forget
about ALSA PCM<->physical routing stuff and stick to rivendell's native
HPI support.
|---------------------------------------------------------------------|
| 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
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
