Skip navigation
This discussion is archived

Multiple servers for transcoding (FCS)

3657 Views 4 Replies Latest reply: Aug 8, 2010 1:29 AM by vjnews RSS
vjnews Calculating status...
Currently Being Moderated
Aug 5, 2010 9:30 AM
Hi All,

Is it possible to use multiple servers for transcoding files in FCS? If so, please help me this topic urgently (Configuration etc). As we have heavy flow of ingest files to SAN & i want to make proxies of the same. Please reply soon!!

Best Regards,

Mac OS X (10.6.4)
  • Nicholas Stokes Level 2 Level 2 (490 points)
    Currently Being Moderated
    Aug 5, 2010 3:24 PM (in response to vjnews)
    For Final Cut Server (FCSvr) all transcoding can be clustered using an Apple Qmaster cluster.
    So add a couple of Xserves cluster them using Qmaster, configure FCSvr to use this cluster and all transcoding will be handle distributively over this cluster.

    Hope this helps.

    Nicholas Stokes
    XPlatform Consulting
    8 Core Mac Pro, Mac OS X (10.6.4)
  • Daniel Harrell1 Calculating status...
    Currently Being Moderated
    Aug 6, 2010 7:26 AM (in response to vjnews)
    I have tried this several ways, in several iterations, and have never gotten it to work successfully. I always have to go back and set Final Cut Server to use its own sever for generating proxies. I have an XSan with several servers as XSan clients (so no AFP share), I even moved the Proxy bundle onto the XSan so everyone had access to it, but still get hiccups and artifacts in my proxies. If you get it to work, please post back here. I'd like to know.

    Daniel Harrell
  • Andre Aulich Level 1 Level 1 (30 points)
    Currently Being Moderated
    Aug 6, 2010 9:47 AM (in response to Daniel Harrell1)
    Actually it's quite easy to use a Compressor cluster for Proxy generation and other encodings in FCSvr. One thing you might want to consider, is that you need to tell the cluster controller to use an Xsan volume for the temporary storage.

    This way the other cluster nodes can access files via Xsan without the cluster controller needing to share the cluster storage through NFS, which is dramatically faster.

    Yet, if you use Xsan as the cluster storage, after a reboot of the cluster controller it can happen, that qmaster starts before Xsan and therefore doesn't find the Xsan volume. If this happens, qmaster creates a local directory with the same path like the cluster storage, which a) leads to the fact that qmaster stores temporary data on the boot disk which is slower than Xsan, needs NFS resharing and can fill up the boot disk easily, and b) prevents your Xsan volume from being mounted, as Xsan detects, that there is already a folder in your local filesystem at the place where Xsan should usually be mounted.

    To circumvent these issues, you need to rewrite the qmaster launchd job at /Library/LaunchDaemons/ to look something like this:

    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "">
    <plist version="1.0">

    where /Volumes/XsanVolume/Qmaster needs to be the Xsan path to your temporary qmaster directory.
    Now qmaster waits for your Xsan volume to be mounted before it starts itself.

    Hope this helps.


    MacBook Pro, Mac OS X (10.6.4)


More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.