On Dec 15, 2011, at 1:34 AM, Fred Gleason wrote: > That 'built-in' facility is deprecated and hasn't been actively developed for > years. I'd strongly recommend moving to the Rivendell Loadable Module (RLM) > facility.
Good to know. I'd heard mention of RLM before, but never actually looked into it. Guess I should! In other news, I think my bug might be a feature :-) After noticing that the problem was especially bad during one particular shift, I drove up to the studio and observed the guy in question. Turns out I'd see a new UDP packet hit my script every time he'd Make Next or Add Next - and since he takes a lot of requests during his shift, there was a lot of that going on. It was then that it occurred to me. If I was actually using the "Next" part of Now & Next, I'd probably want Rivendell to send a new packet every time the next cart to be played was changed. Giving the benefit of the doubt, I'd say the fact that I didn't actually include any Next variables in my UDP string is irrelevant - Rivendell is still doing its thing and sending a new packet each time the Next data would change. (If that explanation makes any sense...) So I think I'll just take the easy way out, and modify my script to check for duplicate data in each incoming packet. If it had been some misconfiguration in Rivendell I'd have preferred to find a "right" way to fix it. But since I'm now relatively sure it's not, I'll just make the hack on my end and call it a day. Thanks for all the responses... --------------- Keith Thelen Kanabec Systems _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
