On Fri, 9 Dec 2011, Fred Gleason wrote:
> On Dec 5, 2011, at 12:54 22, Rob Landry wrote: > >> If I understand correctly, it's the transition from one state to >> another that Rivendell sees, and not merely the state of the GPI being >> grounded or not. > Correct. In fact, it's possible to configure things so that completely > different actions happen when a line goes low->high and high->low. >> It may be that if the transition happens too slowly, Rivendell won't >> see it. That could be ugly. > This will be totally a function of the particular hardware in use. If > the hardware tells the software that a transition happened, then it's > acted upon. If not, then not. No 'in-betweens' here. I'm worried about things like contact bounce. The beauty of systems that act on states rather than transitions -- if it's low, go -- is that they tend to be more forgiving of hardware peculiarities. I've run across transition-sensitive boxes that wouldn't fire on anything but a hard relay closure, and sometimes fired more than one event at a time due to contact bounce. Today I assembled an exact duplicate of my client's system in my living room, complete with Broadcast Tools ACS8.2 switcher. I'm going to experiment with it tomorrow to see what, if anything, I need to build in the way of an eternal interface. I do wish there were a way of "turning off" inputs during times when the desired satellite feed isn't on. I need to make sure that closures received during other programs don't cause events in my log to be truncated or skipped. Rob _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
