BROWSE CATDV SUPPORT MANUALS
- PRODUCT MANUALS
- CatDV Clients
- CatDV Server
- CatDV Server 7.1 Manual
- CatDV Server 6.x Manual
- Worker Node
- CatDV Worker 5 Manual
- CatDV Worker 6 Manual
- Getting Started
- Configuring the Worker
- Configuring the Worker
- Work Sets and Watch Actions
- File Triggered Tasks
- Pre-Processing
- Importing Media Files
- Automatically keeping catalogs in sync with a disk or folder
- CatDV XML batch files (v1)
- New CatDV XML files (v2)
- Metadata Extraction Rules
- Exporting watch definitions
- Server Triggered Tasks
- Specifying a Root Folder
- Job Definitions
- Variable expressions
- Regular Expressions
- Naming Files
- Transcoding
- Exporting Stills
- Batch operation
- Batch vs individual operations
- Offline workflows: batch import and reanalyse media
- Development mode
- Hints and tips for developing efficient Worker Node scripts
- Command Line Interface
- Configuring the worker via XML
- Support
- Web Client
- Other Products
- Amazon Plug In
- Azure Plug In
- Black Pearl Plug In
- Adobe Premiere Integration
- FCS Import Tool
- Live HTML Publisher
- Installing Live HTML Publisher
- Using Live HTML Publisher
- Introduction
- Installation on Apache Tomcat
- Installation under Oracle OC4J
- Installation on Other Platforms
- Upgrading Live HTML Publisher
- Troubleshooting
- Overview
- Customising JSPs
- CatDV Tag Library
- Displaying Objects and Lists
- Configuring Live HTML Publisher
- Live Capture Plus
- Tricaster Plug-in
- CatDV ADA Archive Additions
- CatDV StorNext Archive Additons
- CATDV TUTORIALS
- Video Tutorials
- Tutorials
- Media Formats
- Ingest
- Transcoding
- Getting Organized
- Getting started with CatDV
- Benefits of CatDV catalogs
- Setting up Custom Metadata
- Ensuring Consistency: Picklists
- Customising Catalog Display
- Customising Event Markers
- Customising Metadata Display
- Verbatim Logging with CatDV
- Customising Clip Previews
- Managing Thumbnails
- Adding OSX colour tags to files using a Worker action
- Consumer Digital Photo Workflow
- The Bulk Edit Tool
- CatDV Pegasus
- Editing and Finishing
- Collaborative Workflow
- Media Delivery
- Archiving
- Technical Topics
- Using the Server Control Panel
- Setting Proxy Paths
- Desktop Streaming Proxies
- Migration to CatDV
- Large Metadata fields
- Printing CatDV Preferences
- CatDV Web Access via a DMZ
- Guidance on Filenames
- Optimizing Tables in MySQL
- Fixing Worker Command Failures
- Guidance on running CatDV Server in a VMware virtual environment
- Resilience & Housekeeping
- Technical Support
- FAQs
- All FAQs
- Catdv on Windows with apple QuickTime
- Server 7 Upgrade Procedure
- Server 7 Web Proxy Path Mappings
- Server 7 Upgrade Procedure
- Adobe Premiere Panel Plug-in Manual Installation Guide
- Removing CatDV Server from OSX
- Auto-starting MySQL on Yosemite
- MySQL Permissions Fix
- MPEG2 Playback Disabled
- Limitations when using CatDV Clients inside Virtual Machines
- CatDV on Yosemite (OSX 10.10)
- Shellshocker bash vulnerability
- Send to Adobe CC 2014 not working
- CatDV and Heartbleed
- Can’t find Quicktime for Java
- XDCAM/AVC playback problems
- CatDV on OSX 10.9 Mavericks
- Dates prior to 1970
- Cache-A “Failed to Get Drive List”
- Proxy Path Searching
- Location of Log Files
- Clip Viewer plays black video
- Worker Tips
- Java Security Issues
- Exporting Logs to Support
- Failed to Get Clips: 500
- Working with AVCHD .mts files
- CatDV on a PowerPC Mac’
- playing RED .r3d files
- Troubleshooting Web Client Proxies
- Worker Repeating Actions
- Unknown Type 49
- Pink and Green Stripes
- Problems with Cache-A
- Third Party Codec Crashes
- Remote Installation
- Slow Database Startup
- CatDV Pro is damaged …
- Client
- Catdv on Windows with apple QuickTime
- MPEG2 Playback Disabled
- Limitations when using CatDV Clients inside Virtual Machines
- CatDV on Yosemite (OSX 10.10)
- Shellshocker bash vulnerability
- Send to Adobe CC 2014 not working
- CatDV and Heartbleed
- Can’t find Quicktime for Java
- XDCAM/AVC playback problems
- CatDV on OSX 10.9 Mavericks
- Dates prior to 1970
- Cache-A “Failed to Get Drive List”
- Proxy Path Searching
- Location of Log Files
- Exporting Logs to Support
- Working with AVCHD .mts files
- CatDV on a PowerPC Mac’
- playing RED .r3d files
- Unknown Type 49
- Pink and Green Stripes
- Problems with Cache-A
- Third Party Codec Crashes
- CatDV Pro is damaged …
- Adobe ExtendScript Toolkit Will Not Install
- Server
- Server 7 Upgrade Procedure
- Server 7 Web Proxy Path Mappings
- Adobe Premiere Panel Plug-in Manual Installation Guide
- Removing CatDV Server from OSX
- Auto-starting MySQL on Yosemite
- MySQL Permissions Fix
- Limitations when using CatDV Clients inside Virtual Machines
- CatDV on Yosemite (OSX 10.10)
- Shellshocker bash vulnerability
- Send to Adobe CC 2014 not working
- CatDV and Heartbleed
- Exporting Logs to Support
- Remote Installation
- Slow Database Startup
- Glacier Vault
- Worker
- Limitations when using CatDV Clients inside Virtual Machines
- CatDV on Yosemite (OSX 10.10)
- Shellshocker bash vulnerability
- Send to Adobe CC 2014 not working
- CatDV and Heartbleed
- Proxy Path Searching
- Location of Log Files
- Worker Tips
- Exporting Logs to Support
- Worker Repeating Actions
- Unknown Type 49
- Problems with Cache-A
- Third Party Codec Crashes
- Worker Backup Plugin
- Web
- Server 7 Upgrade Procedure
- Server 7 Web Proxy Path Mappings
- Limitations when using CatDV Clients inside Virtual Machines
- CatDV on Yosemite (OSX 10.10)
- Shellshocker bash vulnerability
- Send to Adobe CC 2014 not working
- CatDV and Heartbleed
- Exporting Logs to Support
- Failed to Get Clips: 500
- Troubleshooting Web Client Proxies
- Web Proxy Support Page
- All FAQs
The worker node configuration is stored in an xml file. Normally the configuration file is edited via the worker user interface but it is also possible to edit this file directly.
The configuration file has both common definitions, such as the IP address of the CatDV workgroup server to which clips are published, and one or more workset definitions which contain lists of watch folders and actions to perform on files that appear in them.
The configuration file is called worker.xml and is in the home directory of the user running the woker software (eg. /Users/joesmith or C:Documents and Settingsjoesmith).
In normal use the config editor will be used to edit the worker node configuration. There may be situations when it is useful to edit the config file manually however, so the file format is documented below.
For example, the following configuration file implements a Drop Box folder on the desktop where any movie files are converted to MPEG-4 files and are then deleted. Scene detection is applied (a separate MP4 file is create for each scene) and the clips are published to the “AutoPublish” catalog on the server. Any JPEG images in the drop box are also published to the server and moved to the Images folder.
<config>
<server host=”localhost:1099″ reguser=”Joe Smith” regcode=”ZVAD-…-7VKC” />
<format name=”My MPEG4 settings” exporter=”mpg4″ settings=”*mpg4++++++++++%01+++%04%B7sean+++%01+++%14++++++%01%9Evide+++%01+++%0F+++++++%22sptl+++%01++++++++mp%3++%20++%03++++%20tprl+++%01 …”/>
<workset lockfile=”/Users/joesmith/workset.xml”>
<watch folder=”/Users/joesmith/Desktop/Drop Box” recurse=”true” period=”60″ settle=”300″ fileOp=”delete” pattern=”*.mov” regex=”false”>
<job name=”Custom mp4″ publish=”true” catalog=”AutoPublish” thumbSize=”2″ analyseOther=”true” >
<convert dest=”/Users/joesmith/Desktop/MPEG4″ destName=”parent” format=”My MPEG4 settings”/>
</job>
<watch folder=”/Users/joesmith/Desktop/Drop Box” recurse=”true” period=”60″ settle=”300″ fileOp=”delete” pattern=”*.jpg”>
<job name=”Publish jpg” publish=”true” catalog=”AutoPublish” thumbSize=”3″ fileOp=”move” fileDest=”/Users/joesmith/Desktop/Images”/>
</watch>
</workset>
</config>
As this example illustrates, it is possible to configure the worker node to automatically delete files in the watch folder after they have been processed (as this may form a valid part of the workflow). Take great care therefore when configuring such workflows, and make sure the root of the watch folder is set correctly!