Bryson Jones
Forum Replies Created
-
This is a good time to mention this distinction for the Workgroup and Standalone users. Enterprise has its own user admin structure with Users, Groups and Roles that don’t appear in the other versions.
It uses these not only for management of permissions but also for changing the layouts and views that users see. For instance if you’re an admin, you might see all production assets with 6 tabs of metadata and advanced menu options. If you have a more limited role, when you log in, you might only assets from one group, see 1 tab of metadata fields, see only limited menus and even have certain fields locked so that you cannot enter data into them.
Once you get above a certain number of users… or have a few that you can’t trust not to wreck your db, 😉 you need some more granular controls.
The default account is as listed. Stay tuned for some really interesting developments in this area of the app.
bryson
bryson “at” hidefcowboy.com
hidefcowboy.com
-
I do have to agree with Rolf, manual cataloging is the way I’d do this initial ingest and then you could set up a watch for just the new files.
Once you have the metadata in, the files can move, and do all sorts of things through automation which is where the benefit really kicks in.
But the initial ingest is a lot of time for maybe not a ton of benefit.
Also, his point about moving after ingest and getting them out of the watch is critical. We never recommend anything living in a folder that is being watched and note that almost every other MAM behaves the same way. Watch a folder, find data, process and move it to another location where it will live and then update the db of the move. That way you aren’t scanning a huge folder structure looking for changes.
bryson
bryson “at” hidefcowboy.com
hidefcowboy.com
-
Spoke to Jason and this appears to be a mis-match of versions of server. I’m assuming that the schemas weren’t updated and so it wouldn’t import.
Rolf, or other support crew, can you confirm that this is the case? Can a Windows db be restored onto a Mac and vice versa as long as versions match?
bryson
bryson “at” hidefcowboy.com
hidefcowboy.com
-
Yes Nate,
We set this up for clients all the time. I’d contact your dealer and have them set it up unless you’re handy with the command line. If you are, there’s a section in compressor’s manual on using the CLI.
I’d rather not go into detail here since there’s so much potential for things to go wrong with command line scripting and I don’t want to be responsible for the questions and problems that result from the various environments, Worker versions and Compressor versions possible. (I hope you guys can understand.)
But the basics are Worker that the worker sends the path to the file as a variable via the command as well as the path to the proxy location for file output. Compressor lets you choose a setting and other job prefs as different arguments in the command.
Very do-able and yes, it gives you back your Worker Node for other operations.
Note that the new Worker (v5) will also allow you to license multiple instances so that if you have an 8 core cpu, for instance, you can have 3 or 4 Worker Nodes running on one machine.
bryson
bryson “at” hidefcowboy.com
hidefcowboy.com
-
Prepare for the worst, right? 😉
This should be a feature request/bug report. Guys?
bryson
bryson “at” hidefcowboy.com
hidefcowboy.com
-
PresSTORE has an automated workflow. That’s the main difference.
https://provideotech.org/catdv-and-presstore-archive-integration/
You can set up the Worker Node to send assets to PresSTORE and then it will report back to the db what archive the asset is in.
No typing, no typing mistakes and automated archive and restore.
bryson
bryson “at” hidefcowboy.com
hidefcowboy.com
-
Lots of metadata isn’t exposed. It only exists for internal use. From what I can see, that’s one of them.
There are tons of these items that serve different purposes but aren’t part of the actual metadata schema.
A metadata tag and a saved search is really the replacement for this as far as a way to create searchable “clip lists”.
bryson
bryson “at” hidefcowboy.com
hidefcowboy.com
-
Both of those suggestions are right on.
I also want to take a moment and plug a service here. (WARNING MARKETING SPIN COMING!!!)
My company, North Shore Automation takes on large-scale database cleanups as a service through CatDV dealers. Meaning if you’ve really got messed up data, we can help straighten it out.
For instance, in a multi-grouping, we can remove ” (double quotes) or ‘ single quotes from between records that have been imported with them and replace them with the correct delimiters for CatDV. (YouTube metadata exports with ” around keyword sets. Same with commas, slashes and most any other maddening data mis-formats including bulk date reformats etc. (12/12/12 into 2012-12-12).
This isn’t cost effective for small jobs but if you’re trying to translate a large tape library or other db into CatDV, or if you’ve done it and the formats are wacky, we might be able to help.
We’re a bit swamped at the moment and so you might have to be patient for a small project, but if you’re faced with a weeks or months long manual reformat, it might be worth getting bid. We are currently ramping up our staff to better handle these one-off jobs.
bryson
bryson “at” hidefcowboy.com
hidefcowboy.com
-
I have to say that “taking too long” is a relative thing.
How much footage, how much detail, how valuable is the footage? Right? I’m on projects now that will take years to log and that’s not an issue.
For instance, I’ve seen 2 people drop 45,000 assets into CatDV with basic logging data in 2 weeks. Not a lot of individual metadata but they got the basics.
I’ve also seen a team of 6 loggers rolling 16 hours a day (2 shifts) take almost 2 months to log 2,000 hours of footage because the level of detail was deep. (almost 2X realtime due to transcription, coffee breaks and detailed reality logging.)
Your workflow sounds solid. Be sure to catalog what goes where on the LTO tapes and you should have a decent archive with a path back to most anything you want to retrieve.
Maybe take a look at PresSTORE for the archive since you have an LTO drive already. They integrate with the Worker Node and you can send assets to archive and receive back the archive ID and status from the app without more typing. Good folks too.
bryson
bryson “at” hidefcowboy.com
hidefcowboy.com
-
That’s something that would have to be done in an outside script.
Probably the easiest way to deal with it, if you didn’t want to or couldn’t script it, would be to have your folders spill over and import into catalogs based on the folder names or something like that.
Also, doing an auto-import of a large folder that’s already full might not be best as it would take a while to run the initial import whereas doing it incrementally wouldn’t tax the system. If this is the case, try doing the first imports manually and then let the system import as the new files show up.
bryson
bryson “at” hidefcowboy.com
hidefcowboy.com