Robin S. kurz
Forum Replies Created
-
[Neil Goodman] “Custom frame sizes up to 8192×8192 since v8.4.”
Oh wow… already?? ;-D
Thanks for the heads up. My bad then. Don’t follow all the intricate details of their incremental updates. Especially since we just killed Avid at two schools and that being one of the top reasons why. Bummers. About 6 months too slow. (actually more like six years, but who’s counting :D) Cheers.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Tim Wilson] “but I completely agree: AE users are every bit as resistant to UI changes in particular.”
Yeah. Let’s just e.g. bolt a SIXTH tracker onto AE with a SIXTH tab and SIXTH way of making it work. That’s just so much more intuitive than finally biting the bullet and growing the maracas to make some real improvements and changes that affect the entire app in a positive way in the short AND long term. *sigh*
Like it or not, that’s simply not an approach (as we can see) that Apple would consider. They have expanded the functionality of things such as the stabilizer and optical flow, without ANY new menus, mandatory selections or convoluted tabs to deal with. Zero. Additions/improvements were either automatic or essentially transparent. I absolutely LOVE AE as a whole, having used it since somewhere around ’93, but MAN has it (along with all the rest), for me, become a confusing, over-tabbed patchwork of some sort of bizarre race to the Feature List Mount Olympus, with little regard for the users or (improved) usability… just PR. And still it’s exponentially slower than that (one time!) $49 dollar app I have running on the side, that does near any and everything in real-time since 2005. Hmmm…
[Jeff Markgraf] “On the other hand, v8 has some good, long-needed improvements.”
Far too little, far too late (as in 10+ years), no? And still… NO editing above 4K. Oh boy. Sorry, but even Avid can’t exist without making actual money, which they haven’t in something like TEN YEARS? Good luck with the “not going away any time soon” part, catering to such a microscopic part of the industry. Quite the optimism imho. But we’ll see.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[John Davidson] “I need to think about how to clearly demonstrate the best workflow for what you’re trying to acheive.”
Well, from what I’m seeing, the only way is as described: set IN at the very beginning, OUT at the very end, click “Add keyword” or hit KK. That does what I want and need. My point is simply, that one shouldn’t have to got through the process of setting the in and out, just as it is in FCP. There I select a clip and hit CTRL + 1-9 for any given keyword. No in or out needed, but optional. With KFP it’s not optional.
[John Davidson] “The GREAT thing about this app is the developers are listening”
Very true. And I am also in contact with them, since we have a relatively large installation that I’m trying to implement at my university, that I am obviously very eager to have work out as well as (I’m sure) it can.
[John Davidson] “It’s filling in some holes in Finder and that’s a big deal, IMHO.”
Interesting take. Because I’m not sure which hole in the FINDER it’s filling, but certainly which holes from e.g. the EOL’ed FCP SERVER it’s filling, aside from the imho VASTLY overpriced MAM market (whether it’s generally intended as a different use case or not). I, too, am most definitely interested in it succeeding also! Even with its little quirks (that obviously every app has, especially at such an early stage) I think it is highly promising also. Again, very much looking forward to learning more from your demo! 🙂
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[John Davidson] “Robin, please read the first part of that sentence again. “
Ah, sorry. My bad, yes. All the damn acronyms. Getting myself all mixed up. 😉
[John Davidson] “Of course Keyflow add tags to finder. That’s the point of it. “
Yes, I realize that. And that’s not a bad thing per se… if that’s what you want. Only the whole point arose from my saying that one can’t simply keyword an entire clip without the imho (in that case) tedious ins and outs. To which you suggested that that’s what the tag are for. My counter-point simply being that that is a very bad substitute.
[John Davidson] “I think you’re best served by waiting for the presentation to go online.”
I will definitely follow it and let you know. 😉 There are many more aspects of KFP that I’m very curious about and need more infos about. Thanks! Either way, I most definitely think it’s a brilliant, if maybe a bit unpolished here and there (anything but unusual for a v1.5 product of course), and unrivaled app in it’s feature-set and FCP X integration! Obviously I don’t have to even mention the price… 😉
Cheers,
RK____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Bill Davis] “This is your view from the outside. […] …it’s fair to assign more weight to the opinions of people who actually have experience with how a system really works, over the opinions of those who don’t. “
Bingo. Can’t wait for the day when the usual suspects actually start making comparisons and judge things that they are factually even in the position to objectively do.
[Bill Davis] “and $399 App Store software”
Actually… either $299 or $397 ;-D [scnr]
(assuming you’re referring to just the Apple suite of apps)– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[John Davidson] “those tags do not affect the file on the finder level.”
Sorry, but I respectfully disagree. In fact that’s a feature that Matt Geller explicitly points to in his demos.
Before:
After entering tags in KFP:
[John Davidson] “There is no way you will end up with 1000 tags on a Finder file.”
Okay, poorly worded on my end I guess. I didn’t mean on the file, but rather in the sidebar of my Finder windows where the tags are listed. I would get a new tag in that list for every new one I assign in KFP, potentially resulting in thousands over time, yes. Again, something I personally would not want to happen. Tags are tags, keywords are keywords. And as I said, it’s not like I CAN’T use the keywords as described, it’s just tedious and unnecessary imho to have to set an in and out first if it is to be assigned to the entire clip.
[John Davidson] “An fcpxml file is not media, it’s like a document, and those can’t actually be stored ‘in’ an FCPX Library.”
Once again I’d have to say you’re wrong OR we’re talking about two different things. Because otherwise, what is this?
… and what is it for, if not to save my edit along side the master when sending to KFP? What, in your view, is in the XML that KFP creates (and stores) if not the edit? In fact, if KP DIDN’T save/archive the edit, then I would say it is near useless for me. But… I know that it does. Like I said, I can have it shown in the Finder and double-click that and it opens as it should in FCP X with my project/edit in tact! (only the media is offline for some odd reason) So why not be able to do that directly? It seems to me, that that is the way is was even imagined to work (and imho make the most sense by far), only it doesn’t for some reason.
[John Davidson] “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.”
But then that’s what both Resolve, XtoCC and others do, no?
[John Davidson] “it’s confusing for everyone.”
I’m not confused about the functionality per se, I’m just very confused over some of the, imho, illogical implementations. Cheers!
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
Nailed it.
-
[John Davidson] “Ah, ok, REGULAR keywords are added in the ‘info’ pane, not in the annotation window.”
Erm… okay. So you’re saying that “keywords” on entire clips are in fact FINDER tags that then, assuming I remember to select the “Create keywords from Finder tags” option, turn into actual Keywords when imported into FCP? Hmpf… not good. Since that means that with every “Keyword” I create, I’m adding yet another Finder tag to my (already very long) list. Effectively adding up to hundreds if not thousands of Finder tags over time! A no-go imho. Especially since I could essentially make a single keyword for the entire clip (ONLY within FCP and KFP) by hitting i and o at each end… only that is unintuitive and unnecessarily tedious. I’ll definitely have to write them about that.
[John Davidson] “Adding straight up finder keywords is probably the easiest thing about he whole app.”
Which may be great for some, just not me or my workflow. I use Finder tags for entirely different things and would like to keep them separate and not mix them up.
[John Davidson] “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.”
Wait… so XMLs within KFP are effectively of no use to me, aside from maybe for archival purposes?? That makes little to no sense to me. I don’t get why selecting “Send to FCP X” on an XML doesn’t simply act as if I double-clicked it in the Finder… which I can’t do, since it’s hidden away in the KFP library. I’d have to reveal first, then… no. And that doesn’t really explain the confusing error message that I get when I try that and which I still don’t know how to interpret either.
Then make it inactive for XMLs? Or at least come up with something more explanatory.Logically I expect it to open as described. And if I “Send to FCP 7 or CC” for it to convert to legacy XML (e.g. like Resolve or XtoCC, even if not as good), then open either app the same way. *sigh* Clearly got my hopes up too soon.
Oh well. The trials and tribulations of the early adopter I guess! Cheers.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Jeff Markgraf] “Great contribution, really on point.”
“In Internet slang, a troll (/ˈtroÊŠl/, /ˈtrÉ’l/) is a person who sows discord on the Internet by starting arguments or upsetting people, by posting inflammatory,[1] extraneous, or off-topic messages in an online community (such as a newsgroup, forum, chat room, or blog) with the deliberate intent of provoking readers into an emotional response[2] or of otherwise disrupting normal on-topic discussion,[3] often for their own amusement.”
Yup.
-
[John Davidson] “Our FCPWorks presentation should be online after NAB.”
Very cool… keep us posted! 🙂
[John Davidson] “The keyword needs an in/out so that the range can be defined in fcpx tagging.”
Yes, if I want a RANGE based keyword that’s fine. But 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.
[John Davidson] “Otherwise you can just add a marker in keyflow and it will go to Premiere or FCPX when you crank out an xml.”
Okay, as far as the XML thing is concerned, that’s another thing. I’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?? Which of those are relevant to the selected XML are noted in the XML, no? And even if I do select something, only THE MEDIA that I selected shows up in FCP, not the project from the selected XML. What am I missing?? So can I not send a project from X to KFP and then to 7 or CC as I simply assumed was part of the whole new XML support? What am I missing (or misunderstanding)? I have yet to get AN XML over to Premiere or 7. Sending simple MEDIA is not a problem and yes, markers are preserved, which is very cool. Cheers.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!
