[John Davidson]

[Tim Wilson] “Software, it’s Resolve and Keyflow Pro”

Thanks for mentioning KeyFlow Pro Tim. I don’t think the world really gets what this application is capable of, but I think the next few updates are going to blow minds.

This is me, Monday, in an Uber screening footage from the office Keyflow Pro server over an LTE connection. At the same time the team in office were logging SOTS with markers so I could write scripts and build a storyboard. This is not a screen share, this is an actual client to server connection. No cloud needed.

John Davidson | President / Creative Director | Magic Feather Inc.

[John Davidson]

FYI that problem is fixed. Users can now edit remote libraries. With a little port forwarding, they can work remotely over the Internet. Why go to the office.

John Davidson | President / Creative Director | Magic Feather Inc.

[John Davidson]

Presentation was Monday. Just got back to work today so i’m a bit wiped out. Fcpxml that points to a few media clips and keywords is vastly simpler than xml that contains project data, generators, titles, etc. When you then convert those XML’s to a completely different format for a different NLE, it gets even more complex. And then those applications change their formats for XML processing….it’s a constantly moving collection of targets that all have to be maintined to keep that function working. That’s why you have XtoCC which costs $50 just for that single feature. However, it’s entirely possible for them to be able to focus on extracting data from fcpx xml’s (and potentially libraries) that contain all the keywording done inside the libraries. I suspect that will be a 2.0 feature though, because we’re talking about a lot of coding that needs to be done and tested before it works right.

I’m going to make a new thread and share some updates.

John Davidson | President / Creative Director | Magic Feather Inc.

[John Davidson]

They’re going to add the ability to FCPX Keyword tag a file without In/out needed. These won’t show up on files at the finder level. I have requested they also give FCPX keyword options in Smart Media boxes.

FWIW looking around at NAB there are so many media management applications – and this is the only one on the mac app store and probably the cheapest. Very interesting.

John Davidson | President / Creative Director | Magic Feather Inc.

[John Davidson]

[Robin S. Kurz] “To which you suggested that that’s what the tag are for. My counter-point simply being that that is a very bad substitute.”

I need to think about how to clearly demonstrate the best workflow for what you’re trying to acheive. It’s annoying when I haven’t had coffee (sorry!) but on the other hand demonstrates the overall confusion as to what the App does and doesn’t do.

The GREAT thing about this app is the developers are listening – and they’re able to make helpful changes very quickly.

FWIW, I haven’t been paid by Malgn (keyflow’s creator) and am not receiving anything for the trip to NAB. I’m supporting them because I see the promise of this app and want it to succeed. It’s filling in some holes in Finder and that’s a big deal, IMHO.

John Davidson | President / Creative Director | Magic Feather Inc.

[John Davidson]

Robin, please read the first part of that sentence again.

“When you tag something in FCPX, those tags do not affect the file on the finder level.”

See that first part? I’m talking about FCPX. Of course Keyflow add tags to finder. That’s the point of it.

In finder, assign keyword tags to show up in the sidebar of finder preferences.bthats how you keep the list from getting long. The reality is though that Keyflow mostly replaces finder.

I think you’re best served by waiting for the presentation to go online.

John Davidson | President / Creative Director | Magic Feather Inc.

[John Davidson]

When you tag something in FCPX, those tags do not affect the file on the finder level. All your work done on that file via FCPX exists only in FCPX. Keyflow lets you tag files for a more permanent searchable solution – just like finder already does (but better).
There is no way you will end up with 1000 tags on a Finder file.

If you want to open any file right click and select ‘open with’, and then select Final Cut Pro X from the list. This is identical to Finder’s right click option for opening a file. No reveal in finder needed.

‘Send to Final Cut Pro X’ CREATES an fcpxml file from the selected files you highlight in keyflow. An fcpxml file is not media, it’s like a document, and those can’t actually be stored ‘in’ an FCPX Library. The error dialogue should say:

‘Keyflow can only send audio, video, and image files as fcpxml.’

I think that it would be pretty magical for it to be able to convert xml files across complex video systems but that’s far beyond what this app is designed to do. I’m covering as much as I can Monday. The complexities of Finder Keyword Tags, FCPX Keyword Tags, Keyflow Tagging, etc – it’s confusing for everyone. I’ll try to help clarify that Monday.

John Davidson | President / Creative Director | Magic Feather Inc.

[John Davidson]

[Robin S. Kurz] “if I simply want to keyword (not TAG) an ENTIRE clip, having to first set an in and out seems counter intuitive. That needs to reflect the same way it works in X imho.”

Ah, ok, REGULAR keywords are added in the ‘info’ pane, not in the annotation window. ‘Annotation’ is for FCPX keyword range tags
and markers. Adding straight up finder keywords is probably the easiest thing about he whole app. Just type or delete additional tags in the tags window on the the right side of the screen.

[Robin S. Kurz] “‘m trying to wrap my head around WHY, when I try to simply send an existing (either sent or imported) XML from KFP to either FCP X or even PPro or 7, I’m told I need to “select among the video, audio and images” first?”

The XML keyflow generates can only include information about the files and the data you add to them, not projects. Keyflow doesn’t actually create projects for you. It can manage xml’s of projects created by FCPX. Basically, it’s the equivalent of dragging the files onto the FCPX icon.

That help?

John Davidson | President / Creative Director | Magic Feather Inc.

[John Davidson]

Our FCPWorks presentation should be online after NAB. We’re making an effort not to use any footage that we don’t have clearance for so they can post it online.

The server elements are great – now you can keyword tag, annotate, and adjust metadata plus a whole lot of other things. The keyword needs an in/out so that the range can be defined in fcpx tagging. Otherwise you can just add a marker in keyflow and it will go to Premiere or FCPX when you crank out an xml.

What I find to be great about Keyflow is that now your metadata lives on outside of your FCPX library, often in the finder level. No more wasted time tagging the heck out of footage and then just forgetting about it. This is especially useful for shoot media that you might reuse later, but it also applies to things like rampant design elements, 3D model libraries, renders, sound effects, etc.

John Davidson | President / Creative Director | Magic Feather Inc.

[John Davidson]

You’ll be surprised to learn that for many shorter clips (like Rampant design media for example) the preview file is actually smaller than the alias file that points to the original if you don’t create a preview – and your preview file will actually play back mxf, avid, photo jpeg qt’s. They’re actually kind of awesome.

John Davidson | President / Creative Director | Magic Feather Inc.