Capsule Media \/ PODASS highly recommends regular maintenance of Avid projects, bins, and the Unity Attic to keep your team’s project data safe. Good maintenance practices help your team avoid worst case scenarios with project data. Anyone collaborating on shared storage can benefit from understanding these principles and keeping your team honest about regular maintenance.<\/p>\n

Keep Ingest and Edit Projects Separately<\/h2>\n

Each Avid workstation regularly searches for changes to bins of its open project. The more bins in a project, the greater the indexing task. We recommend the following when segmenting your assets into different projects and bins:<\/p>\n

\n
• Create a project for editing and a separate AE project for ingestion. For episodic content use one project per episode.<\/li>\n
• If your workflow is using a shared \u201cbin locking\u201d AVID server within Capsule Media\u2019s facility or in one of Capsule\u2019s data center locations use separate editing projects and Ingestion projects.<\/li>\n
• If your project involves \u201cPOD\u201d workflows we strongly recommend<\/strong> that each editor use individual projects. The \u201cPOD\u201d servers function identically to our main facility servers. Including bin locking features. However, depending on where a POD is in the world, and what connection speeds are available, each POD will sync at different intervals. Generally, PODS will update sync within 5-20secs with each other. However, depending on connection speed, sync can be delayed. Especially if a POD loses internet connection for a period of time. Therefore, it is possible that one editor could open a bin that is in use by another editor. (Both editors open same bin before sync update.) They will both have write access and can potentially save over each others work. As projects progress, they can grow to large data sizes. Especially if there are a number of editors on the project. Sync can then be delayed somewhat over slower connections due to the total size of the project updating.<\/li>\n
• Avoid accessing bins from other projects. Copy bins from one project into another instead. If you do access external bins, remove them from “Nexus Bins” folder when you are done (The folder is located at the bottom of the project window)<\/li>\n
• Avoid dividing content excessively into separate bins and folders. For content like archival, use metadata and bin columns to segment data instead of separate bins if possible.<\/li>\n
• Never permit bins to exceed 150 MB<\/strong>. AVID will become unstable with excessively large bins. More so with a lower performance workstation. Archive old sequences to “archive” bins and keep them closed when not in use.<\/li>\n
• Delete bins that are no longer necessary and regularly clear the trash<\/li>\n<\/ul>\n

  Cycling Out the Unity Attic<\/h2>\n

  Avid creates a Unity Attic folder on the root of the project’s drive for bin backups for your entire team. Though the attic is a great tool, it is not infallible. We recommend assistant editors cycle out the attic out once per week to keep bin saving quick and reliable.<\/p>\n

  Recreating the attic is easy! It’s not necessary to have everyone sign out of the project before cycling the Attic out. Simply rename the Unity Attic with a useful suffix (e.g. “Unity Attic_YYYYMMDD”) and the next time a background bin save occurs (on any workstation) Avid will create a new Unity Attic. Old Unity Attic folders should be retained until no longer needed by your team.<\/p>\n

  Regular Project Backups<\/h2>\n

  Don’t rely exclusively on the Attic alone for your daily bin snapshots. We recommend assistant editors compress, date, and archive the project folder daily to at least two locations (e.g. a backup folder and a cloud drive space)<\/p>\n","protected":false},"excerpt":{"rendered":"

  Capsule Media \/ PODASS highly recommends regular maintenance of Avid projects, bins, and the Unity Attic to keep your team’s project data safe. Good maintenance practices help your team avoid worst case scenarios with project data. Anyone collaborating on shared storage can benefit from understanding these principles and keeping your team honest about regular maintenance. […]<\/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-901","post","type-post","status-publish","format-standard","hentry","category-avid"],"yoast_head":"\n