Jason Watkins
Forum Replies Created
-
Just to make sure I am doing what you suggest (I am a little confused about “re-nest” so think I am missing something):
I create a sequence at 24 and insert the 23.98 clip. Deny FCP when it asks to change the sequence rate.If this process is correct, then it plays the 23.98 clip at 24 (speeds it up) and the timecode starts to drift.
-
Been tracking down the specifics, here are the basics:
The FCP clients are mounting NFS through the Company network over the Mac Pro’s onboard NIC. The Linux server is connected to the storage over 8Gb fiber (4Gb x2), and connected to the Company network over 10Gb uplink. So, the bottleneck in the chain is the GigE from the Company network to the client. They are using this workflow just for playout of ProRes Quicktimes through FCP–not for any complicated editing with lots of files.I have tested throughput with Avids Path Diagnostic. It is showing real steady reads around 80MB/sec, with lower and choppier throughput for writes. But, we aren’t too concerned with writes…yet. Furthermore, FCP isn’t dropping frames on playout when we stress the network and storage.
In learning about this NFS stuff, it looks as though the real problems with NFS arise with higher bandwidth requirements and more complex sequences (permissions and tracking files). Since our workflow couldn’t be more basic, it looks like we are good to go forward with NFS mounts in this case.
-
Thanks Matt, just to clarify, it is 220Mb/sec (bits). So, that throughput does make it under the GigE spec. I will definitely look into the other concerns you mentioned. Thanks again, I really appreciate it.
-
Thanks for the help so far. How did you repair the permissions– individually or through Disk Utility? Also, can you explain mount scripts and what the issues are?
-
Turns out the performance guide we were looking at was for the ISIS7000. The performance guide for the 5000 looks a lot better. Here it is for those who are interested:
https://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=384751&ssdF
-
Hello Michael, just want to make sure I am reading this correctly. On page 21 of the doc, the last row of the last chart has the data rate as 45 MB/sec. They mean 45 Mb/sec correct? If it is 45Mb/sec, then it says playing 1 stream of that codec requires 11MB or 88Mb/sec. Roughly twice the data rate of the codec itself.
Lastly, how does FCP count streams on playout? If you are only monitoring V4 (no PIP or effects), and you have 3 loaded video tracks below that, is that 1 stream or 4?
-
Thank you Michael. Very helpful, Jason
-
Thanks for the help. Yeah, just looking at the 5000. When you talk about the correct NIC, are you saying the second port on a Mac Pro isn’t good enough? Also, why is there a 30% drop in FCP performance?
-
ahhhh, the sequence has to be in the same project. We have a project just for our sequences. Thanks Shane.
-
Thanks Shane. Is there something I need to do to induce the change (close and reopen the project) or should it be automatic? It isn’t happening over here–FCP 7