Definitely, they'll also throw a curve ball at you years after you've been using it.

I had a conversation that went a bit like this not too long ago:

"Rivendell keeps not playing backups, its done this several times now you need to fix it, we might have to use something else if it won't even work"

To explain backups are pre-recorded links we use in case we can't find presenter cover.

What actually happened was several times was 4 in nearly 4 years. The first time someone loaded the backup in the wrong day. The second time, someone somehow changed the log in the studio to something that was 3 weeks old and obviously it was on the wrong log when the backup should have played.

The final 2 times in 2 weeks was someone decided the best way to add these backups was to drag them into the Weather import folder (we have a backup folder specifically for this but that was too difficult obviously).

I have a cut expiry of 2 days on this folder and purge of 6 as we don't need to keep them all available to play on air. So the backup would be added and 2 days later it wouldn't play.

There is a tendency to have to keep justifying things that I don't really understand for some people. Its always the "systems fault" when its something "new" even years later.

Wayne Merricks
The Voice Asia

On 21/04/15 13:06, John Anderson wrote:
AMEN...

just went through a fairly painful experience with some folks, who
couldn't figure out WHY Rivendell didn't work exactly like something
they think they REMEMBER from 7 years ago...

Nine times out of 10, the equipment isn't the problem...LOL!

On Tue, 2015-04-21 at 12:32 +0100, Wayne Merricks wrote:
Especially early on, if there is one thing that
you can't do or haven't thought of people tend to write off what
you're trying to introduce so be careful how you approach a change and
try to think of all the questions and answers up front.

_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Reply via email to