there is something missing from that explanation. The new scheduler did
not have this check and the new scheduler was introduced long after the
reference capture agent was abandoned.
Greg, you introduced this in 2018 as part of another pull request (#112)
and later declined my patch removing this again.
I don't know of any capture agent having problems with this and no one
could ever name a specific hardware except for the abandoned reference
capture agent. I also don't understand this concept and think it's a
huge usability issue since Opencast claims non-conflicting events have
conflicts with no further explanation.
I'm all for removing this.
Greg, since you make this claim again:
> […] and many hardware CAs have been observed to need that kind of
> interval as well.
…let me ask again, if you now can name a specific device with such a