Bryson Jones
Forum Replies Created
-
Also an update from our tech, Kris. The Lifehacker linux one might be wrong.
Here’s a better one.
https://shellshocker.net/#systemtest
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
You have to go 64 bit Java, there’s no “shake down” to 32bit for 11.
However, your old CatDV Pro versions should work fine under the 64 bit Java.
Backup your system before you do any of this. (I know that’s harder under Windows, but maybe you have a test system?)
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
When you reveal it in Explorer, does it play in the Quicktime player or another app?
I’d recommend you try changing your CatDV Media Playback settings to use Xuggle or JMF as a test. (You may need to do additional installs to use these but they are documented on the Squarebox site.
CatDV 11 will likely solve this issue with the new player.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
I completely know that you would not, John. But many other less savvy users might, so I wanted to mention it here.
Trust that I know you guys can handle media… and lots of it. 😉
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
John,
Note that writing to the metadata in QT can have interesting side effects. The main one is that it changes/breaks your MD5 checksum. So for a lot of places, this is a no no, since it breaks the chain of command, so to speak, from the file creation/archive.
This probably isn’t a concern in your workflow but it’s something to consider.
Pulling filepath elements and writing them to the QT metadata should be fairly simple using the Worker, you can also do it after ingest for files ingested via drag and drop so if this feature doesn’t make it into 11, you are covered.
Also, the new “Actions” would likely make this possible in the client if you wanted to just write an action to do it.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
Bryson Jones
September 5, 2014 at 5:14 pm in reply to: Creating paths for Proxies with CatDV Worker and EpisodeTim, we should bring this up here to save others time and energy.
There is a conflict between the way CatDV Worker Node sends paths as arguments to the Episode Command Line. Which of course you would need in order to send the destination path for the proxy file.
Specifically, if you have to escape a space, that will not send successfully to Episode as the syntax is incorrect.
If you need to use these products together and have spaces in any of your media paths (most folks do) you need to take the command out into the shell, correct the syntax and send it from your own shell script.
Know that if you intend to do this, you or your integrator will need a bit of shell scripting experience.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
Can you explain “folders”? Do you have your filesystem folders mapped to catalogs or something?
“Is there a way to move folders containing subfolders and catalogs all at once into other folders or to the root of our organizational structure?”
This confuses me as it refers to “folders and subfolders” which are filesystem/OS items and then “Catalogs” which are CatDV db items.
The answer to all of them is the same, the Worker Node can move files to different folders and preserve or remove the file path and it can also move clips to different catalogs based on metadata. If we have more than a few catalogs of data to move, or reorganize, we tend to do it with Worker actions instead of manual moves.
For example, right now, I’m copying and renaming a set of 45,000 assets on my test machine to create a set of demo/test material. Each asset is copied to a specific folder on the drive, re-named and then moved to a catalog who’s name is based on the hour of the day that the job runs. I started with 12 assets in one catalog, I’m up to 45,000 and will let it run til I hit 500,000 and several hundred catalogs all created and named automatically.
This is a still example, but it’s useful to me and demonstrates that most any part of the catalog, clip or media file/path can be manipulated with the Worker Node.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
That’s one for Squarebox, we take the process out into our own app.
You might want to write this as a shell script and then just call it from the Worker Node. If you did that, you could write the URL back into the db using the Worker Node’s command line interface and it would probably be far easier to troubleshoot as you could set up your own error logging etc.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
As to “proxy everything” you can totally set the Worker to do everything just by setting a query to:
“if this field is blank, make proxy” but know that the minute you do that you’ll almost certainly drop in a bunch of stuff that you didn’t want proxy for. 😉
It’s so easy to just set a flag on everything by selecting all that it’s best to not have it do it “automatically”. Also, if you have 10,000 assets in, the Worker would decide what goes first, so it’s better if you just set the flags and then you can pick what goes first.
“Automatic” is great, but it needs to be in a controlled data set, nothing should ever be automatic across the whole database unless you just like watching your Worker run for weeks on end.
Also, it robs you of the ability to save temp versions of things. Setting up a server query is really interesting. Most people start with one flag/comdition to run something and then realize that that is a bit limited. The more you think the deeper your queries get. For instance:
If field 1 is set to X
Or field 7 is set to Y
But not if field 13 is blank
Or media path does not contain Z
Then do action.Beware queries like, “do this action on everything regardless.”
Final tip. Never use the “Notes” field for your own data. (The verbatim logger overwrites it.) And never use the “Status” field for anything. The Worker uses that sometimes and can overwrite your data without you realizing it. Create your own “notes” and your own status fields, preferably one for every action you do so that you can track when and what actions have happened. Also, writing a date and time to a separate field when an action runs is a great way to track automation. For every automated workflow we set up, we generally add 2 to 6 new fields to the db. Seems like a lot, but you can tell at a glance what processes have been performed on a file.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
Ok, word from Devs.
When you set up the Google auth, it had to save the credentials in the environment path, so in order to send additional credentials you’ll likely have to set up multiple virtual environments for the Google app to run, then call each of them from a separate WN action.
I’d love to know if this is something that the CatDV world at large is doing a lot. If so, we might take it on and productize a more formal Google/YouTube workflow.
A couple of years back we wrote an app that uploads, receives confirmation of the transfer, and even writes the clip YouTube URL back to the CatDV Server. We could start from that and maybe build it up if there’s a market beyond one guy in the NL. 😉
Good luck man, looks like you are pretty close.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com