[bryson jones] “I’d reach out to your dealer/integrator and know that the short answer is to not drag and drop batches onto the Worker Node. That will be looking at the preset root in the Worker action and not necessarily at the full path. Notice the “Relative to:” field in the Worker action.
Thanks, Bryson. That makes good sense. Do the importing in Pro, save, wait for Worker to pick it up that way.
[bryson jones] There may be a way to get that path into the action, but we direct clients to set up actions by a server query and set a metadata flag to “create proxy” to trigger the Worker. That way it gets the full path and you can also get the flag to be set to “proxy created” or something so you can track what’s done.
Virtually everything I bring in will need proxies, so finding a way to have that happen automatically is what I’m after. Probably could set that flag on import, yes?
[bryson jones] Free advice (and worth every penny.) Consider making h.264 mp4 files for proxy instead of mov. Android won’t read mov and many PC’s don’t have it installed. Most every browser can play an mp4 now and you never know what you might want to do with those proxies down the road.”
That’s actually what I’m doing… should have typed it that way! ;^)
Thanks again,
Doug Metz
Anode