EMC Isilon and Final Cut Pro X Workflows - Data Storage ... ISILON AND FINAL CUT PRO X WORKFLOWS Collaborative editing with Apple FCP X on EMC Isilon Scale-Out NAS ABSTRACT An overview of Apple’s Final Cut Pro X ...

  • Published on

  • View

  • Download

Embed Size (px)


<ul><li><p>EMC ISILON AND FINAL CUT PRO X WORKFLOWS Collaborative editing with Apple FCP X on EMC </p><p>Isilon Scale-Out NAS </p><p>ABSTRACT An overview of Apples Final Cut Pro X collaboration features and ways to implement </p><p>workflows for collaborative editing on Scale Out NAS with Apple FCP X </p><p>EMC WHITE PAPER </p></li><li><p>2 </p><p>Copyright 2014 EMC Corporation. All Rights Reserved. </p><p>EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without </p><p>notice. </p><p>The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with </p><p>respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a </p><p>particular purpose. </p><p>Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. </p><p>For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. </p><p>All trademarks used herein are the property of their respective owners. </p><p>Part Number H13204 </p></li><li><p>3 </p><p>TABLE OF CONTENTS </p><p>ABSTRACT 1 </p><p>EXECUTIVE SUMMARY 4 </p><p>AUDIENCE 4 </p><p>PREMISE 4 </p><p>Apples Final Cut Pro as a professional Post Production tool 4 </p><p>ADVISORY 4 </p><p>TECHNICAL FEATURES OF FINAL CUT PRO 4 </p><p>HOW APPLE FCP X USES LIBRARIES TO MANAGE MEDIA 4 </p><p>SHARING LIBRARIES IN APPLE FCP X 5 </p><p>SETUP 5 </p><p>NETWORKING 5 </p><p>Mac OS Client configuration 5 </p><p>Mac OS Client NFS configuration 6 </p><p>REFERENCES: 6 </p><p>Final Cut Pro X in a Shared Environment 6 </p><p>FCP X 10.1 Media_Management 6 </p><p>FCP X Manual 6 </p><p>OS X Best Practices for Isilon: 6 </p></li><li><p> 4 </p><p>EXECUTIVE SUMMARY This document addresses the integration of Final Cut Pro X with Isilon Scale Out NAS and describes the workflow. </p><p>Note: This document is an overview of workflows and options for collaboration. It is intended as a guideline and an introduction to </p><p>the topic and wont cover all possible scenarios. </p><p>AUDIENCE </p><p>This EMC perspective document is intended for technical audiences, specifically IT Admins and Consultants working in the creative </p><p>space. </p><p>PREMISE </p><p>APPLES FINAL CUT PRO AS A PROFESSIONAL POST PRODUCTION TOOL </p><p>Since the early 2000s, Final Cut Pro has developed a large and expanding user base. It had made inroads with film and television </p><p>editors who have traditionally used Avid Technology's Media Composer. 1 According to a 2007 SCRI study, Final Cut Pro made up </p><p>49% of the United States professional editing market, with Avid at 22%. A published survey in 2008 by the American Cinema Editors </p><p>Guild placed their users at 21% Final Cut Pro (and growing from previous surveys of this group), while all others were still on an Avid </p><p>system of some kind. </p><p>With the advent of Final Cut Pro X in 2011, Apple changed the way that professional users interact with Final Cut for editorial. Where </p><p>previous versions were able to access any type of storage, local, DAS, SAN or NAS, the new version initially limited the locations </p><p>where project files and project elements could be stored and used in place to local, DAS and SAN locations. With Final Cut Pro 10.1 </p><p>Apple introduced a new and more flexible project management model based on Libraries </p><p>This document outlines some of the options and steps involved in leveraging Final Cut Pro X for collaborative edit using Isilon Scale-</p><p>Out NAS as the shared storage. </p><p>ADVISORY In order for the FCP X functionality to be available via Scale-Out NAS, you have to set the correct mounting </p><p>parameters, these can be found in the configuration guide under: MAC OS CLIENT NFS CONFIGURATION </p><p>TECHNICAL FEATURES OF FINAL CUT PRO Final Cut Pro X is a hybrid of a new user interface for editorial and powerful technology that makes it a valid solution for M&amp;E </p><p>workflows. </p><p>The feature that make this product important to Professional M&amp;E customers include: </p><p> 64-bit architecture </p><p> ProRes Edit full-frame, 10-bit, 4:2:2 and 4:4:4:4 HD, 2K, 4K, and 5K video sources including ProRes Log C from ARRI ALEXA </p><p>cameras </p><p> Grand Central Dispatch faster processing through the use of all CPU cores. </p><p> Native format support, including REDCODE RAW, Sony XAVC, AVCHD, H.264, and AVC-Intra. </p><p> Resolution independencesupport for image sizes to 4K and beyond. </p><p> Background processing, rendering, transcoding, and moving media. </p><p>HOW APPLE FCP X USES LIBRARIES TO MANAGE MEDIA FCP X 10.1 changes how users work with Events and Projects. Instead of accessing individual Events or Projects, these are contained </p><p>in .bundle files called Libraries. </p><p>Libraries can contain consolidated media, which Apple calls Managed Library", but they can also reference external media. This is </p><p>where things have changed in a way that is beneficial for sharing. </p><p> 1 http://en.wikipedia.org/wiki/Final_Cut_Pro </p><p>http://en.wikipedia.org/wiki/Avid_Technologyhttp://en.wikipedia.org/wiki/Media_Composerhttp://en.wikipedia.org/wiki/Final_Cut_Pro</p></li><li><p>5 </p><p>A single library can now access media externally without copying data to the events. Libraries can also back up automatically which </p><p>was the other concern for customers that were working with FCP X. </p><p>In a shared environment, you have a personal library to work with projects and you can then a) backup and/or restore projects from </p><p>a shared location and b) copy and share projects from one user to another, either by copying from one library to another or by </p><p>leveraging a transfer library. 2 </p><p>SHARING LIBRARIES IN APPLE FCP X Media that you import into a specific library is stored inside the library and is referred to as managed media. Media can also be </p><p>imported or copied to any location on a connected volume and linked to the library as external media. Multiple users can access this </p><p>external media instantly on Isilon Scale-Out NAS. </p><p>1. To hand off new events to a working library by copying </p><p>You can copy new events from your working library to another editors working library located on shared storage. For example, an </p><p>assistant editor can use this method to update the primary editors working library. </p><p>1. On the destination system, close the working library on shared storage or the storage area network. </p><p>2. Open this library (the destination library) in Final Cut Pro on the system you want to hand off from. </p><p>3. Drag the events you want to hand off from your library (the source library) to the destination library you opened. </p><p>o When you copy an event to the library, all of the clips in the event are copied, whether or not theyre used in a project. </p><p>o If you copy a project to the library, only the clips needed for that project are copied. </p><p>o If youre working with external media on shared storage, no media files are copied. </p><p>4. When copying is complete, select the updated destination library in the Libraries list and choose File &gt; Close Library. </p><p>o The second editor can then open the updated destination library on his or her system and continue working. 3 </p><p>SETUP </p><p>NETWORKING </p><p>A VLAN or dedicated network infrastructure is highly recommended to ensure adequate performance for the intense workloads </p><p>creative workflows generate. When working with 2K, 4K resolutions or above, 10 Gigabite networking is mandated. For current </p><p>generation MacPro workstations, a Thunderbolt to 10 Gigabit adapter like the ATTO Thunderlink NS 2102 (SFP+) is needed. 4 </p><p>MAC OS CLIENT CONFIGURATION </p><p>Note: Detailed instructions for OS X Specific optimization for OS X are contained in the Best Practices Guide: </p><p>https://support.emc.com/docu51273_Using-Mac-OS-X-Clients-with-Isilon-OneFS-7.x.pdf?language=en_US </p><p>The main prerequisite for the OS X client is that the mount that hosts the Library is mounted via NFS. The media share can be </p><p>mounted via NFS or SMB (Figure 1). </p><p> 2 http://images.apple.com/final-cut-pro/docs/Media_Management.pdf Managing Media with Final Cut Pro X Libraries 3 http://images.apple.com/final-cut-pro/docs/Media_Management.pdf Managing Media with Final Cut Pro X Libraries 4 http://www.attotech.com/software/files/techpdfs/TechSheet_Desklink_TLNS2102.pdf </p><p>http://images.apple.com/final-cut-pro/docs/Media_Management.pdfhttp://images.apple.com/final-cut-pro/docs/Media_Management.pdfhttp://www.attotech.com/software/files/techpdfs/TechSheet_Desklink_TLNS2102.pdf</p></li><li><p>6 </p><p> Figure 1. Mounting the filesystem that hosts the FCP Library. </p><p>MAC OS CLIENT NFS CONFIGURATION </p><p>Alert!: FCP X wont open libraries on shares that arent mounted using the parameters below! </p><p>There is one critical modification to the OS X NFS configuration thats necessary in order for FCP X to recognize the share as a valid </p><p>mount for a Library. The NFS mount has to be configured to only use local locks. The Best Practices guide for OS X offers optimized </p><p>settings, which are modified below to include the correct locking option for FCP X. </p><p>By creating a nfs.conf file within the /etc directory of Mac OS X, the Finders mount parameters are tuned for performance for Final </p><p>Cut Pro Mac clients using Isilon via NFS. </p><p>To create nfs.conf settings that are applied via the Connect to Server mount method, the nfs.conf file should contain this line: </p><p>nfs.client.mount.options=nfssvers=3,tcp,async,locallocks,rw,rdirplus,rsize=65536,wsize=65536 </p><p>For additional performance, latency in NFS write operations can be reduced further. This is accomplished by modifying the nfs.conf </p><p>file to include this additional line: </p><p>nfs.client.allow_async=1 </p><p>REFERENCES: Final Cut Pro X in a Shared Environment http://www.10dot1.co.uk/content/FCPXInASharedEnvironment_FINAL.pdf </p><p>FCP X 10.1 Media_Management http://images.apple.com/final-cut-pro/docs/Media_Management.pdf </p><p>FCP X Manual http://manuals.info.apple.com/MANUALS/1000/MA1604/en_US/final_cut_pro_x_user_guide.pdf </p><p>OS X Best Practices for Isilon: https://support.emc.com/docu51273_Using-Mac-OS-X-Clients-with-Isilon-OneFS-7.x.pdf?language=en_US </p><p>https://support.emc.com/docu51273_Using-Mac-OS-X-Clients-with-Isilon-OneFS-7.x.pdf?language=en_US</p></li><li><p>7 </p><p>APPENDIX </p><p>LOCAL LOCKS AND USAGE WITH NFS. </p><p>Final Cut Pro X requires NFS local locks to be enabled. What follows is a technical discussion on some of the implications and </p><p>conditions that apply to local locks. For most use cases this will not have any impact on the workflow or the usage, as the process for </p><p>Library sharing as described in SHARING LIBRARIES IN APPLE FCP X doesnt involve more than one user accessing their personal </p><p>Library at any time. Concerns arise when the Library is being backed up using backup methods outside of Final Cut Pro X or </p><p>otherwise manipulated by an application or another user while it is being actively used by the Library owner as this may lead to data </p><p>inconsistencies or data loss. </p><p>Note: Perform all file locking operations locally on the NFS client (in the VFS layer) instead of on the NFS </p><p>server. This option can provide file locking support on an NFS file system for which the server does not support </p><p>file locking. However, because the file locking is only performed on the client, the NFS server and other NFS </p><p>clients will have no knowledge of the locks. Note: mounts which are both soft and read-only will also have the </p><p>locallocks mount option enabled by default - unless explicitly overridden with a lock option (for example, </p><p>nolocks or nolocallocks ). 5 </p><p>locallock instructs NFS client to avoid NLM calls, so all locks happen on client side, and for LKF then all LK calls would be shared </p><p>(read "not exclusive"). This means, the applications can lock files, but such locks provide exclusion only against other applications </p><p>running on the same client. Remote applications are not affected by these locks. </p><p>With locallocks enabled it is theoretically possible for something on the local machine to contend with FCP, like a local backup </p><p>daemon or a search indexer. While this is not a behavior that has been seen in test environments it could occur in a deployment </p><p>scenario and the solution in that case is to include the FPC X Library from the particular services or applications search path. </p><p> 5 https://developer.apple.com/library/mac/documentation/Darwin/Reference/Manpages/man8/mount_nfs.8.html </p></li></ul>


View more >