Get your own customer support community
 

Final Cut Server on MatrixStore "Head" Node

When using Final Cut Server with MatrixStore, FCPSrv is Installed on the "Head" node of MatrixStore (where matrixstore server is installed)? Can I use all nodes as Qmaster cluster (for encoding through fcpsrv)? Can I capture (ingest) directly to the MatrixStore Archive (appearing archived in FCPSrv) or I have to capture Local, archive in FCPSrv, and then delete the Local files?
Inappropriate?
1 person has this question

  • Inappropriate?
    We recommend to install FinalCutServer on a dedicated machine, not a MatrixStore node. FCS is meant to be used by multiple users and for that reason (and because all its actions consume a lot of CPU and memory) we normally install FCS on a separate machine.

    Our MatrixStoreConnect software (FTP frontend for FCS for example) can be installed on any machine, works particularly well installed on FCS machine.

    The concept of Head node is our intarnal term. End user don't know which machine at the moment is considered as main. All nodes in a cluster are equal :)

    Yes, you can try to use MatrixStore nodes as Qmaster cluster. Actually is could be a good way to utilize machines when MatrixStore is not used. We do not recommend that though as we did not test that.
    Encoding is really expensive operation - may happen that node may run out of memory, stop respond etc...
    Besides for security reasons we disable some services from OSX during MatrixStore node instalation. If QMaster relies on them it may not work...
    But as a start it may be a good idea to use for example only 2 out of three MatrixStore nodes as QMaster machines. You are welcome to test that...

    You cannot ingest directly to MatrixStore. It is used as an archive device so prefered way of working is put your data on local disk, SAN etc.. edit it and archive using Dropspot or FinalCutServer. The last one can automatically delete the local copy so you don't have to do this manually.

    Hope that helps.
     
    silly
User_default_medium