• Final Cut Server

    Analyzing Assets with fcsvr_client in Final Cut Server

    Sometimes Final Cut Server can’t create proxies as part of the analyze phase of ingesting an asset. Maybe it’s busy, maybe it’s doing too large a batch or maybe it’s just having a hard day. Either way, sometimes it just doesn’t analyze like it’s supposed to. Therefore, you can analyze an asset using the fcsvr_client command. This allows you to find assets that currently do not have a poster frame or a proxy and regenerate them. Typically, you would right-click on the asset from the GUI and then click on the Analyze button to re-analyze, but what if there are a lot? Then you’d want to automate it. You can…

  • Final Cut Server

    Asset Paths In Final Cut Server from the CLI

    Final Cut Server devices are locations where files are stored. Locations are then set using that device as a relative path within Final Cut Server. For example, if you have a device called MySAN it might end up being /dev/3. When you import an asset into Final Cut Server, the asset is given an asset ID. For example, you might upload a movie called Rudy.mov that might have an asset with ID number 318 (asset numbers are assigned from Final Cut Server when the asset is imported. But once the asset is imported the location path in the database is then stored relative to the device. So for example, Rudy.mov…