Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/podass/public_html/wp-includes/functions.php on line 6114
Warning: Cannot modify header information - headers already sent by (output started at /home/podass/public_html/wp-includes/functions.php:6114) in /home/podass/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/podass/public_html/wp-includes/functions.php:6114) in /home/podass/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/podass/public_html/wp-includes/functions.php:6114) in /home/podass/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/podass/public_html/wp-includes/functions.php:6114) in /home/podass/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/podass/public_html/wp-includes/functions.php:6114) in /home/podass/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/podass/public_html/wp-includes/functions.php:6114) in /home/podass/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/podass/public_html/wp-includes/functions.php:6114) in /home/podass/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/podass/public_html/wp-includes/functions.php:6114) in /home/podass/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":894,"date":"2022-11-25T20:47:40","date_gmt":"2022-11-25T20:47:40","guid":{"rendered":"https:\/\/www.podass.com\/?p=894"},"modified":"2022-11-30T16:51:20","modified_gmt":"2022-11-30T16:51:20","slug":"avid-bin-sharing-and-locking","status":"publish","type":"post","link":"https:\/\/www.podass.com\/2022\/11\/25\/avid-bin-sharing-and-locking\/","title":{"rendered":"Avid Bin Sharing and Locking"},"content":{"rendered":"
Avid bin sharing enables\u00a0bin locks<\/strong>,\u00a0which bind read\/write access to one user at a time. The system is robust but can malfunction, so this article will cover the two most common problems your team may encounter. If you need help enabling bin locking in a project you are opening for the first time, check out Avid Project Sharing Basics here.<\/p>\n
Understanding Bin Locks<\/h2>\n
When an unlocked bin is opened by an editor, a\u00a0.lck file<\/strong>\u00a0is created in the project folder, and a green lock icon appears in Avid for that editor. The icon indicates that they have\u00a0read and write<\/strong>\u00a0permissions until they close the bin. If a second editor opens the same bin while it’s locked, they’ll see a snapshot of the most recent save of the bin, with a red lock icon indicating\u00a0read only<\/strong>\u00a0access. If an editor would like to open an unlocked bin with read only permissions, they hold\u00a0option\/alt<\/strong>\u00a0while opening the editable bin.<\/p>\n
False Bin Locks<\/h2>\n
When Avid crashes or is forced to close, the software may lose track of what bins it had open. When Avid relaunches, it may not clear the\u00a0.lck\u00a0files<\/strong> it created before the crash. “Stale” bin locks may be deleted using Finder,\u00a0as long as you confirm the bins are no longer open on the workstation that created the .lck file(s.)<\/strong>\u00a0If an editor has any doubt whether or not a bin is open on their workstation, they should close out of Avid Media Composer on the workstation until the lock file is deleted.<\/p>\n
Missing Bin Locks<\/h2>\n
If your workstation opens bins without green and red bin lock icons,\u00a0stop editing!\u00a0It’s important to fix the problem as soon as possible to prevent data corruption.<\/p>\n
\n
Create a new bin, copy all of your recent work to it, and save it as a backup.<\/li>\n
Ask all other editors that may be in your bins to do the same<\/li>\n
Open Avid Settings > Project > General<\/li>\n
Check the box for Enable Bin Sharing on 3rd party storage emulating Avid Nexus \/ ISIS<\/strong><\/li>\n
Confirm at the dialog box to close all bins<\/li>\n
Open your bins again and check for bin lock indicators (if you still don’t see them, restart your workstation.)<\/li>\n
Once bin locks are re-established, replace any outdated sequences in the original bins using your backup bin<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"
Avid bin sharing enables\u00a0bin locks,\u00a0which bind read\/write access to one user at a time. The system is robust but can malfunction, so this article will cover the two most common problems your team may encounter. If you need help enabling bin locking in a project you are opening for the first time, check out Avid […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[7],"tags":[],"class_list":["post-894","post","type-post","status-publish","format-standard","hentry","category-avid"],"yoast_head":"\n
Avid Bin Sharing and Locking - Podass<\/title>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\t\n