I'm new to Rivendell myself, so I was waiting a bit to see if anyone else would have something helpful to say... all I can contribute is that you're not alone... we have similar problems. In spite of all of our efforts to make sure playlists are open in only one place at a time, we just discovered a problem in Saturday's playlist... fortunately the AM announcers are still in the building so we were able to just nuke the messed up playlist and start over from the music import and have the morning team start over. In my latest discussion with Fred, he was going to add some warning screens if a playlist was already open somewhere else when you opened a playlist for editing or tracking.

Tim Vik
KXXO

On 08.11.2017 13:05, Brad Beahm wrote:
Hi Rivendell gurus,

I'm wondering if a problem I'm experiencing is a software bug or
users not following best practices.

My setup is a 2 machine setup. Machine 1 acts the server and runs
RDAirPlay for  station 1's playback. 
Machine 2 is a client and runs RDAirplay for station 2 playback.

I've had trouble when two people are using the RDLogEdit voicetracker
to voicetrack the same log. (VT Markers get imported into the log at
specific places from external music scheduler import)

If user 1 on machine 1 is doing voicetracks at the same time as user
2 is doing voicetracks on machine 2, sometimes user 2's voicetracks
are never saved. 
Not only are they never saved, other items in the log for that hour
are deleted. I can't nail down a pattern exactly. Sometimes we lose
the next item following the missing voicetrack, sometimes we lose an
item or 2 or 3 further down in between voicetracks. 

Tracks are only ever lost for the hours user 2 is recording on
machine 2. No items are ever lost for user 1 on machine 1.

This problem occurs infrequently, maybe only 10% of days, but when it
does happen, it really messes stuff up!

Can someone explain the process in which the log is written when
voicetracks are are recorded? And is there a user procedure or
software fix that can remedy this problem in the future?

Thanks so much
Brad


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

Reply via email to