fcsvr_client archive /asset/318 /dev/8

Once archived, the asset can be easily restored provided that it is still in the archive path that it was backed up to. So assuming that the asset is still on /dev/8 you could use the following command to restore the asset (the device path is implied as it is tracked in the metadata that corresponds to the asset ID:

fcsvr_client restore /asset/318

If archiving and restoring, it is never a bad idea to log that the action was sent to the queue. For example, if the asset ID were a variable of ASSET and the device had an ID of DEV then you could use the following to log that the automation had been fired off:

fcsvr_client archive /asset/$ASSET /dev/$DEV
/usr/bin/logger “Asset $ASSET is being copied to device $DEV”

Similar Articles:

• Scripting Productions and Assets in Final Cut Server
• Final Cut Server: Creating a Device
• Final Cut Server: Using Amazon S3 for Archival
• BRU Primer -> Advanced
• The Final Cut Server Command Line

fcsvr_client clone –name Emerald /project/298

If we wanted to get the ID of this project, we would then use:

fcsvr_client search –crit Emerald /project

We could then go a step further and actually create an asset in this new project by using the –projaddr option for createasset. In the below example, we’ll presume that the new project ID was 299 and then create an asset called Emerald1.mov that is stored on a device with an ID of 5 as well as provide a description and a tag:

fcsvr_client createasset –background –projaddr /project/299 pa_asset_media /dev/5/Emerald1.mov CUST_DESCRIPTION=”Emerald throwing food at daddy” CUST_KEYWORDS=”food fight”

Now to throw it all together in a little script that could be fired off through another application that can be kicked off from another application. In the below, we assume that it is a bash script that was handed a project name via $1, a device ID in $2 and a file name in $3:

#!/bin/bash
fcsvr_client clone –name $1 /project/298
MyProjectID = fcsvr_client search –crit “$1″ /project
/usr/bin/logger “Production $MyProjectID with name of $1 created”
fcsvr_client createasset –background –projaddr /project/$MyProjectID pa_asset_media /dev/$2/$3 CUST_DESCRIPTION=”Automatically uploaded file” CUST_KEYWORDS=”movie, automated”
/usr/bin/logger “Asset $3 on device $2 created in production $1″

If we had just wanted to create the asset, we could have simply used line 5, placing the Project ID in $1 by changing out $MyProjectID with $1. We could also use Transmogrifier to easily return the assetID once it has been created in Final Cut Server, allowing that to be returned to the application that might be calling up this script. This allows you to integrate the asset and production creation part of Final Cut Server with other solutions, such as a PHP web upload application, FileMaker or even another Digital Asset Management solutions.Similar Articles:

• Archive & Restore Assets with fcsvr_client
• Final Cut Server: Migrating FileMaker Metadata
• The Final Cut Server Command Line
• Final Cut Server: Using Amazon S3 for Archival
• Final Cut Server: Creating a Device

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 find whether a single item has a proxy using the fcsvr_client command along with the list_parent_links. For example, for asset 318 the following would show the other assets that you have:
fcsvr_client list_parent_links /asset/318

You can then re-analyze using the fcsvr_client analyze option (assuming a video file with the asset ID of 318):
fcsvr_client analyze –fcp /asset/318

Or, if you’re trying to work with all of the items within a given Final Cut Pro project instead of a video asset ID, use the -fcp flag along with the ID of the Final Cut Pro project (assuming a project with asset ID of 319):
fcsvr_client analyze –fcp /asset/319

You can count your assets using the fcsvr_client count option:
fcsvr_client count –recurse /asset

This allows you to loop through all the assets ($id is the increasing number in the loop) and set a proxy variable to:
fcsvr_client list_parent_links /asset/$id | grep Proxy\(3\) | awk ‘{print $2}’

Then you would simply do something like this:
if [ -d "$proxy" ] ; then
fcsvr_client analyze –fcp /asset/$id
else
/usr/bin/logger “Asset: $id already exists”
fi
Similar Articles:

None Found

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 might be located at /dev/3/dogmovies/Rudy.mov even if the actual file system path is /Volumes/MySAN/dogmovies/Rudy.mov

You can find an assets path pretty easily using the Final Cut Server client. You can also use the fcsvr_client command to retrieve it programatically. To continue with the example, let’s find the path to the file using the
fcsvr_client list_parent_links /asset/318

The output would look similar to:
Proxy(3): /dev/3/dogmovies/Rudy.mov

But if you need the actual file system path then you have a little more work to do. It’s easy enough to then convert /dev/3 to a URI if you set it as a constant. However, this doesn’t allow for future proofing the code. Therefore there is a feature that we put into FCS Transmogrifier ( http://transmogrifier.sourceforge.net ) to look up a file system path based on a deviceID: –getDevicePath. To look up the deviceID of 3 (where that Rudy.mov clip is stored from earlier in the example):
transmogrifier –getDevicePath –deviceID=3

Then you can assemble the device path with the folder name. Or, to make it easier if you’re just looking to get the path to the file, using Transmogrifier you can get that by using the –getAssetPath option:
transmogrifier –getAssetPath –assetID=318

You can also get the assetID based on a files path, (which can be helpful if you’re going to be archiving the file) using the –getAssetID option:
transmogrifier –getAssetID –assetPath=”/Volumes/MySAN/dogmovies/Rudy.mov”

Overall, trading asset paths back and forth based on IDs allows you to call assets from other solutions provided you know the ID.

Similar Articles:

None Found

• Mac OS X Server: http://www.linkedin.com/groups?&gid=138085
• Final Cut Server: http://www.linkedin.com/groups?gid=138082
• Xsan: http://www.linkedin.com/groups?gid=138084
• MacEnterprise: http://www.linkedin.com/groups?gid=1774398

Similar Articles:

• "Simple" OS X Server
• Final Cut Server: Prepare Media For Disconnected Use
• Delegating DirAdmin to Windows Clients
• Xsan: umask and Default Permissions
• Final Cut Server: Atom and FCS

• Xsanity Article on XsanDebugged
• Customizing the Final Cut Server Webstart on Xsanity
• Article on Xsanity
• Problems Opening Final Cut Server client?
• Another Widget: FCSMonitor

In the current iteration you can also record audio tracks from the iPhone and use them in workflows as well. Oh, and it can connect to multiple Podcast Producer servers to kick off workflows. Since one workflow can summon another or write data into Final Cut Server, this gives a lot of options for different ways to integrate Podcast Producer and automate a number of items from your iPhone. Great stuff and I for one am really looking forward to the next version as soon as the App Store approves it!Similar Articles:

• Podcast Producer Web Controller
• Podcast Producer Command Line
• Using Podcast Composer in Podcast Producer 2
• Podcast Producer Workflow ACLs
• iPhone in the Enterprise

• The Final Cut Server Command Line
• Customizing the Final Cut Server Webstart on Xsanity
• Final Cut Server: Prepare Media For Disconnected Use
• Final Cut Server: Creating a Device
• Final Cut Server: PostgreSQL and FCS

http://www.andre-aulich.de/wp-content/uploads/2009/06/ConSol_RCE.mov

Well, now it’s in beta. Contact them at rce@consol.de for a beta of the tool if your interest is peaked!Similar Articles:

• Artbox
• Artbox Purchased by Apple
• Final Cut Server: Atom and FCS
• Final Cut Server: iMovie Integration
• Final Cut Server: The Client

To manually configure the poster frame, open the workflow in Podcast Composer (or do so during the initial creation process). Then click on the Window menu and click on Workflow Inspector (or use the Command-I shortcut key when you’re in Podcast Composer. At the resultant screen you will see a field for Episode Poster Image. Simply drag any image that you would like to use as a poster frame for all of the podcasts created from this workflow.

The poster frame will then appear in the wiki or in iTunes for each podcast generated using the workflow that you manually assigned a poster frame for.Similar Articles:

• Using Podcast Composer in Podcast Producer 2