Hi! Thanks for your incredible work!
On 6/13/21 3:01 PM, Fred Gleason wrote:
On Jun 12, 2021, at 08:47, Alejandro Olivan Alvarez
<[email protected]
<mailto:[email protected]>> wrote:
Although, In my case, switch experiments over ASI card were
successful, switching over Jackd Interface where troublesome... but,
anyways, what I discovered is that, sometimes, you RESTART rivendell
and a given, nonworking RML SA/SR, starts to work.
It is well documented that, upon re-congig/tweak on RDAdmin, a
reivendell-restart could be needed (not always)... The thing is that,
sometimes, a rivendell-restart seems not to be enough, and the RML
SA/ST keeps having no effect whatsoever... so maybe even a full
system reboot could be needed
With the exception of (some) things related to JACK, it should never
be necessary to restart the rivendell service after making
configuration changes in rdadmin(1). If you find a situation where
that is necessary, please report it as a bug!
I'm aware this isn't the best time to test rivendell, since you're in
the middle of a major version change going qt5 ( that will be a quite a
milestone!), on top of that, I'm also aware that because of my lack of
experience in managing the Rivendell ecosystem, together with the
Debian/CentOS differences, I'm not in a good position to confidently
report on bugs that, often, aren't nothing but simple mistakes.
Today but, I've reproduced the situation where an RML SA on a running
rivendell terminal (Local Audio Adapter switch against the Jack
interface) didn't apply or was silently ignored... and then, after a
rivendell restart, a re-issue of the same RML SA set the crosspoint as
expected.
(maybe for a full caed restart... I'm speculating here)
Restarting the ‘rivendell’ service *does* do a full caed(8) restart.
Yesterday I missed very very much any way to monitor the
crosspoint/switching/routing status of a Switch device (Maybe there's
some way to get it!?!?!)... but I didn't find it. Also, there seems
to be not feed-back upon the RML execution... you throw it, and
that's all... I found myself faithfully believing it was
applied/working... so this part is incredibly hard to troubleshoot.
Agreed. There are some formidable practical obstacles however;
starting with the fact that some of the supported devices —e.g. Grass
Valley GVC 7000 protocol — provide no mechanism for reading the actual
state of the switching matrix. For those devices, Rivendell itself is
in the situation of having to fire off protocol messages in the pious
hope that they actually work, with no means for determining that that
is actually so.
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.
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.
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
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
Best regards.
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
