Simon Blackledge
Forum Replies Created
-
I share a Pegasus 1 out from an iMac for editing ProResHQ at the moment.
Resolve plays in RT in the other room and so does the edit room even when working in AE on the iMac that has the pegasus on.
Never had any crashes.
Not ideal but works for now till the new kit goes in.
s
-
Thanks Jonathan
s
-
Saw an Avid take about 3 seconds before it would play only the other day..!
Not one of ours…
S
-
I’ll be using the 2008 Mac Pro for now with the external SAS netstor’s we have.
Hence externals.
s
-
Disks ?
Raid 5 or 6 ?
Why not a 12Gig HBA ?
Cheers
s
-
Thats internal ports.. for the Mac Pro I need 2x externals no ?
s
-
Try this
Mount the server fcpx folder as NFS
open FCPx
Open whatever projects you want.
Dont quit fcp-x
Mount the sever folder over afp
eject the NFS mounted one
go back to editing in FCPX – export etc without any of the NFS hidden folder rubbish showing up.
FCPX only flags the need for the project to be on a SAN when opening.. once open it can be mounted any way you wish…
s
-
Hey Neil
The NFS workaround does indeed work.
The rendering over and over is a bug in FCP-X when using Fill instead of non or FIT in Spatial Conform with some codecs or media external to FCPX library.
the folder left behind with compressor ( internal share in FCP-X) appears to also be a bug.
Local media exported to the NFS share ( so fcp-x isn’t using anything on the NFS mounted volume) still leaves behind the *tmp folder.
I’m putting the disappearing files down to use error… !
Nice 4K demo at NAB btw.. caught the vids online.
S
-
Oh plus when exporting to the NFS mount FCP-X leaves a folder behind post completion :-/
Name = (A Document Being Saved By StompUtil)
S
-
That’s 3 internal and 1 external though ? :/
The diff is 512 bytes or 4k sectors
4k has 512 emulation.
Areca can handle both fine apparently.
Cheers
S