Rivendell 2.19.3 running on CentOS 6.10, most recent kernel update done last
week…
Any ideas why a Log Exception Report would be inaccurate? In generating logs,
for example, for Monday (tomorrow), it lists a whole bunch of cuts as “not
playable” yet when I check them individually, they are valid cuts with eligible
date ranges.
in His service,
BJ Mora for GraceRadio at graceradio.net
KGCE-LP/Modesto NOW at FM 107.9!
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
