Rolf Howarth
Forum Replies Created
-
I don’t know the specifics of FileMaker Pro I’m afraid but you can import and export data from CatDV as tab-separated text and as XML. If you know someone who can do a bit of scripting you should be able to get one or other of those in and out of other apps relatively easily.
-
Support for multi fields was added to the Web Client in 6.6b7, available from https://www.squarebox.co.uk/download1.html
-
Are you dragging straight from CatDV into Final Cut Pro? That won’t work. That’s the same as dragging from the Finder and will always send the whole file over without metadata.
Instead, you need to drag the clip(s) onto the Final Cut Projects node in the tree navigator. Alternatively, export the clips as a Final Cut 7 XML file.
-
CatDV should be able to import the folders and automatically turn them into image sequence clips. On the import tab, enter “.dpx” into the image sequence filename pattern. This depends on you having a suitable QuickTime codec or Xuggle installed so it can import the DPX files. We plan to improve CatDV’s DPX support in a future version.
-
The latest server is actually 6.6b7 which includes a number of fixes, but none relevant to this particular error. The way event markers are stored in the database they are limited to 65,000 characters per clip. That’s normally plenty for most people but it obviously depends on your workflow.
If you really do need to store such detailed event markers in the database (and can’t work around the problem by creating subclips etc.) then you can increase the limit in the database, but you should only do that if you need to as it reduces the efficiency of the database.
You need to run the following MySQL command as the MySQL root user (mysql -u root):
ALTER TABLE catdv.clip MODIFY events LONGTEXT ;
Contact us by email if you need more help with this. We don’t really want to encourage too much direct access to the database in public because it’s so easy to mess things up if you’re not careful 🙂
-
That’s right – as the name implies the Verbatim Logger is primarily for creating transcripts linked to timecode, which you can save as text or as markers. You can also create subclips with it but that’s not its main purpose. For subclipping using the details panel may be easier – use a combination of the JKL keys, I and O, and Cmd-U to create the subclip (and Cmd-Shift-U to jump between the master clip and the subclip).
We’ll look into the worker reference movie thing but I’m a bit surprised at that as it should do the same as if you were exporting a reference movie from a subclip in CatDV, which works I think.
-
CatDV will automatically add -1 etc to clips that it has created (eg. when you do automatic scene detection) but when you import a file it just uses the name as it finds it.
-
The settle period is based on whether the file has been modified in the last X minutes according to its modification time but I agree checking to see if the size has changed might be a better way to do that so it’s something we’ll consider.
When the worker is launched there is a delay before the various watch and worker threads are started to give you a chance to manually intervene by unchecking the relevant box before they kick off.
The work queue keeps a list of files it has processed for 14 days or more but Bryson is correct and it’s good practice to have your worker job automatically remove the file from the watch folder after it’s been processed. You don’t have to delete it, move it from the drop box to a more permanent library location if appropriate.
Although you can have many jobs queued and there are separate threads to scan for new files and clips on the server, there will only ever be one job actively running at a time. You’re talking about aborting a job that’s in progress and appears to be stuck? Quitting and restarting the worker is the only way to do this I’m afraid. This won’t harm any other jobs however.
-
You need to enabled Advanced Menus on the General tab of Preferences to see less commonly used commands.
-
That’s great to hear, thanks for letting us know!