I find it funny that when I go into Library to "record" something, the system picks up the audio just fine, but RDAirPlay does not. I'm interested in trying out "RDCatch" to see if that records audio as well.
Fred, do you have any ideas by chance? Ryan On Mon, Jun 14, 2021 at 9:09 AM Fred Gleason <fr...@paravelsystems.com> wrote: > On Jun 14, 2021, at 04:28, Alejandro olivan Alvarez < > alejandro.olivan.alva...@gmail.com> wrote: > > Mmmm... I get the point... I have no experience on those devices, but I > understand what you're depicting is kinda hard situation to handle from a > sysadmin / programmer point of view... hopefully those things feature some > way to check their status on their own. > > Most of them have some sort of external mechanism (physical or virtual) > for ascertaining matrix state. Not all of them include that capability in > the control API for third-party applications though. > > The one big exception though is the ‘Local Audio Adapter’ driver (the very > one that you’ve been attempting to troubleshoot), as that one exists as a > purely internal Rivendell construct. Hmm… > > I'm aware that, although easy to say, implementing even a basic cli > capability of 'status report' on you internal audio routing/switcher daemon > (I guess caed?) would imply rather hard-to-implement features, such as some > kind of volatile or persistent storage on crosspoint status, levels, etc, > etc... all that on a very 'core' part of rivendell, and not of much help > (if any) on those 'autistic' devices. > > What say we add some reporting to syslog for the ‘Local Audio Adapter’ > driver, so one could at least get some feedback on what Rivendell thinks > the state of the routing matrix is? It wouldn’t be terribly useful > operationally, but could simply troubleshooting at least. > > It would be very nice but (let's dream! :-), in the future, to have some > kind of equivalent to the GPIOMonitor but for the internal audio > routing/crosspoint (caed?) engine > > Very unlikely to happen in Rivendell, unfortunately. However, you might > want to check out the ‘Drouter’ project, which provides exactly that. > Rivendell has a switcher driver that will interface to it (’Software > Authority Protocol’). > > https://github.com/ElvishArtisan/drouter > > Currently limited to Livewire devices, but there is some talk of adding > support for others. > > 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 > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev ---------- Forwarded message --------- From: Ryan Kin <k1n9h...@gmail.com> Date: Sat, Jun 12, 2021 at 1:31 AM Subject: [RDD] Switch Taking on ASI6114 To: rivendell-dev <rivendell-dev@lists.rivendellaudio.org> I've done so many taking sources of Rivendell through the computer in my time of using Rivendell but recently, I'm not able to take the source... My soundcard is an ASI6114 and my line code is "ST 0 0 0!" and switch off code is "SR 0 0 0". What am I missing? Thanks in advance!
_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
