Bryson Jones
Forum Replies Created
-
This is a common problem. We tend to be very specific in our actions going from Mac to PC and often have to do command line scripting outside of the Worker GUI to accommodate the paths.
Rolf or John, can you speak to the current state of the pathing in the Worker? If the Path Mapping is set up and consistent should this work?
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
This is quite a bit of automation. Seems like it’s all do-able but remember that when you export (note the word) you are making a new asset and so it will not, by default, receive the metadata from the original file.
If the raw assets are single files (like an mov file) you should be able to easily link the clip to the new file.
If they are MXF assets (metaclips, such as XDCAM) you will have a bit more trouble as I’m not aware of a way to link a metaclip record to a single piece of media. (I’m not saying it can’t be done.)
One way to do it is to export the asset along with an XML and move the original files to the “processed” folder with an action. Then you could pick up the exported ProRes as a new asset and import the metadata from the XML. (You’ll have to test, I think you’ll need to script some minor XML edits in order to get an importable sidecar XML file, but again, test.)
That should get you near what you want.
By the way, keep in mind that if/when the client moves to Premiere or FCPX and starts editing raw assets, this workflow might change drastically. I’d catalog those raw assets as well, just for the future. (you can hide the catalogs in a “raw” production group that users don’t see.
Hope this gets you started.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
Hey there,
I’m not sure how to do this via the GUI. I’ll think about it a bit and see if something hits me.
If you were doing it with outside scripting (You could probably just do it in the shell) I’d have the “send to web” pull the UIDs from those fields and set a flag on each of those assets through the Worker CLI. Then you could have a simple server query that watches for the “export” flag and does the action.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
Bless you for teaching.
I have to say, staffing is a huge concern of mine. “Who’s going to do all of this?” is a central question of our industry.
Know that teaching them concepts is just as (more?) important as showing them how one system works.
You can teach that concept with 2 hard drives and they will adapt that to whatever medium they find themselves working on later.
Again, thank you.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
That’s why I’m not in sales. 😉
Man, it’s been a developing thing and you should know that it’s only just getting worked out on the sales side. That post I did was part of trying to explain how the systems work with each other so that people could get a better feel of the workflow.
While quite a few end users have this workflow running, not many resellers have installed this workflow so there’s a lot of mis-information. (NSA does this as a service and I know VTG in NYC has done it themselves.)
Here’s some basics.
The SDNA plugin (Which you buy from SDNA) uses the CatDV Worker Node to communicate to the CatDV system so if you have a Worker you are good on the CatDV side.
There is no “plugin” to buy from Squarebox in order to use SDNA.
That all said, you might want to dedicate a Worker Node to the SDNA system as it makes things faster.
So, 1 SDNA to CatDV plugin from SDNA and an optional Worker Node will get you sorted for software.
If you buy the SDNA CatDV plugin, from SDNA, you might want to also purchase an install. SDNA will install the SDNA side but it’s expected that you have a strong working knowledge of CatDV Worker Node config in order to connect the two systems. (Warning: blatant plug…We also offer this to SDNA and CatDV dealers as a service.)
If the reseller seems confused, have them engage you directly with SDNA and speak to their support guys. There’s been a lot more focus on the tech than the sales and marketing side. That’s a good thing in my opinion. 😉
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
It looks like an install script failure. I’d just report that to support.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
Did you change the “NAME” field in CatDV?
If so, know that that will change the filename of the clip. It will ask you first, but be aware of this.
If you have no automation running and no other actions were performed, I cannot offer a solution.
Support guys?
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
One very important difference in these 2 systems is the ingest or import method, which varies more than the file/folder structures.
A large difference is that in Portal, a storage location is made “importable” to the server and all the assets in that storage are in the import window and you search or filter for specific assets to bring into the database. So if you have a volume that’s available for import, every asset in that volume will appear in the import list, unless you filter it. (You can see this in the software better than I can state it.)
This differs from the more “drag and drop” ingest used by a lot of CatDV users in CatDV Pro.
The CatDV Worker Node can of course watch a folder or drive but if it does, then it imports all assets in that storage by default, unless you filter as well. In the end, it’s really about how you integrate your system in both products.
If I had to characterize the methodologies used by the two systems, CatDV can lean more to a “put things where you want them and catalog them” workflow, whereas Portal comes more from the more traditional DAM viewpont of “give us your assets and we’ll manage them.”
It’s important to note that both systems can do “the other” of those 2 approaches, with integration. But the approach starts from a different place with with each software package.
Also, know that Portal is running on CentOS/RedHat so take that into account as you’ll want to have either storage shared via SMB/NFS or a fiber system that’s compatible with a Linux client. All operations are performed from a web browser. CatDV has OS X and Windows client software and automation engines but no Linux client support.
Thinking about this, if you want to import/catalog assets from an external drive it must be mounted to the Portal server and configured as a “storage”. There is no “hey, let’s catalog this firewire drive!” But that’s true of any larger DAM system. They assume a stable mount point and storage configuration. CatDV allows for more looseness, for better or worse, depending on your point of view. (Sysadmins hate “loose”, editors seem to LOVE/Demand it.) 😉
Ironically we use CatDV in a more traditional way in a lot of our larger deployments, stabilizing the file structure to increase the ability to automate and better control the assets. In Portal systems we’ve seen work done to accommodate more of a “user’s choice” of file structure. I tend to believe that the bigger the system and organization, the more you need to control the assets. This seems to be true throughout the industry as a lot of the larger DAM products use this methodology.
If you spend a million dollars on a DAM, you don’t get to put stuff where you want to. You’re paying them to manage them well for you. 😉
As in all things, some good planning and a strong deployment team are key to sort all of these things out and get the system you need.
I’ve rambled long enough. I’m tired. 😉
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
https://lmgtfy.com/?q=quicktime+windows+drive+mapping+problem
Jeff, I wouldn’t share that if you didn’t have a good sense of humor.
Seriously though, this is all over the place. We’ve watched it since CatDV v7 (Ah, the grey beard…)
I’m hoping for a fix, or someone to decide that QT is worth saving but not holding my breath.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
If you have the “other” tab exposed in the Details Panels, it should be there.
If not, look at your prefs under Details Panel and you can enable it there.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com