Bryson Jones
Forum Replies Created
-
Tim, I can speak to part of this, although I’d love to hear from the original poster as well.
You cannot “drag” a drive into CatDV. If you do, things may be processed incorrectly (how could it process every type of file correctly, without direction for instance?) And it will most certainly crash from running out of memory. This is documented here dozens of times to the point where we specifically note when training a new user. CatDV’s advanced media analysis keeps it from handling a full drive scan, much like you’d never drag a whole volume into FCP or Media Composer.
Contrast this with NeoFinder that is a “drive cataloging” program aimed only at indexing the contents of a drive. It’s fast, but not as data rich, however, if you just want to know what’s on a drive, it’s perfect for that.
I believe the user is wanting to do what my client wanted, just dump the contents of a drive into CatDV for sorting later. While not a best practice, I can see why they’d want to do this.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
We actually don’t retain the thumbnail in the CatDV side at all, only in the external web system.
In CatDV, they must be set manually.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
Carla, as discussed yesterday, the permissions go:
Group/Catalog/Clips
If something is in a catalog, you must grant access to that entire catalog. To do certain workflows in CatDV, it generally involves the automated move of clips through a set of catalogs. (This is one of the first “automations” I even had to do.) There is no ACL or clip by clip permission to view or block on a clip by clip basis.
That said, a lot of MAM systems lack this as it’s hard to administer. (Think of the work to tag each and every clip with permissions!) There are several ways to implement a limited access workflow and this is where training, planning and assistance really kicks in. You have grown beyond dragging a few clips into CatDV.
The forum here is great but a workflow like this generally involves several brainstorming sessions, drawings, lists and other documentation and an intimate knowledge of your storage, server and security environment/protocols. We’ll try, but that’s hard to do in a public forum.
CatDV, along with your storage and server permissions and a bit of automation can produce some intricate workflows.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
This cannot currently be done. We have a client that has requested it as well. We extract them for Approval-Q using an external clip but it would be great to either do what you ask or let us attach a still as a thumbnail.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
We’ve had a project sitting for a couple of years in our queue just waiting for a client. The import xslt for this isn’t trivial as neofinder didn’t output XML. ( If that changed that’s even better )
This can be done with some text cleanup and an xslt.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
As a general rule, we split our Worker Actions as much as we can. This seems strange to new users but when you’re troubleshooting it’s far easier to see what’s “breaking” when each action only does one or two things.
Worker Node can say “failed to publish” for instance, and that could be either catalog having permissions issues. Worker won’t way which.
If catalog A and catalog B publish with separate actions, then you know where the problem lies immediately. This was taught to me years ago by Sir Kevin Duggan and it’s a smart way to work although your mileage may vary.
So you’re making a copy of these clips for viewing? They are then deleted after the R&A process is done and no metadata is retained? Just so I’m clear about the workflow.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
For the record, that would create 2 copies of the asset and metadata on those 2 copies would be tracked separately.
This is an important tenant of working with catdv as an asset manager, one clip, one catalog, one group.
To leave that structure can make for issues with your metadata unless you have a way to track that those 2 assets are the same and to publish or sync the metadata between them. You can of course have another action that copies a clip into another catalog and group (note that both are necessary.) this is something that we cover extensively in our training sessions, with drawings and examples and it’s still hard for new users/admins to grasp.
Those are the facts, as I see them any one who has more info, please jump in. Now, the opinion.
This would take a large amount of scripting and tracking and really gets away from the basic idea of the mam, keeping the metadata attached to the master asset.
This is only my opinion and experience, and you may have another way to use this in a workflow, of course.
Preserving this idea requires that you be very crafty as you do review and approval inside the traditional CatDV group structure. Our clients tend to use outside solutions for R&A. In the end, which one is the “real” clip now? As long as you keep that straight, you’re ok.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
Excellent work guys.
One note to users, you might need to add the port number to your server setup to get this rolling.
ex: xx.ipa.ddr.ess:port# or something like 8.8.8.8:8085
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
Excellent news Tim, that’s where the source and the support should be, with the archive system.
I’ll keep this in mind if people ask about BRU and CatDV.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
TIm, could you post more info on the Dax system?
It’s been a long time since I heard anything out of them and was wondering if it was still available through the US distribution. The Atempo plugin is only available from the UK these days and Dax is also absent from the US price list.
Thank you,
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com