[RDD] Log Locking

Patrick patrick at scnv.net
Thu Jun 22 19:32:01 EDT 2017

Today someone was voice tracking and another person went into the log editor accessing the same
log. I believe the way the log editor works is the entire log is loaded in and then written back when
done, causing any voice tracks recorded during that time to be overwritten.

If this is true, would it be a good idea to place some kind of lock on the database when someone
is voice tracking that prevents the log editor from opening the same log, at least without some kind
of warning message?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3854 bytes
Desc: not available
URL: <http://caspian.paravelsystems.com/pipermail/rivendell-dev/attachments/20170622/49715684/attachment.p7s>

More information about the Rivendell-dev mailing list