Charlie Austin
Forum Replies Created
-
[Marcus Moore] “How are you manipulating more than one primary clip at a time? Or are you just looking for a “tilde-lock” option?”
Can’t speak for David, but if you want to do a swap edit, like move a clip 7 shots earlier in a cut, the tilde key will disconnect things from the clip you’re moving, but all the clips connected to the 7 shots that move in the swap move with them. Which, in my case, i didn’t want them to. You can work around it, but it would be nice to temporarily “disconnect all” if you need to.
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
That’s pretty awesome. 🙂 i wonder if it’ll be a free update… :-/
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Franz Bieberkopf] “I’m going to go out on a limb and hazard a guess that we’re all out of our depth here”
Heh… I think it’s a very sturdy limb you’re on. 🙂 I actually just opened an X project database in an SQLite database browser. I don’t know what any of it meant, but it looked cool…
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[David Lawrence] “Agreed. I think the “fixed lanes” idea is interesting. But I would go further and allow multiple primaries in a “fixed time” window. If they did that, they could keep everything else the same and it would work for me as well as for you.
Fixed Lanes – or ability to assign a kind of Z order to clips – and grouped Roles would pretty much do everything tracks currently do… for me. If you need to add a crossfade and don’t want to use the fade handles you can create secondary’s, as you can now. They’d just stick with their group. In a perfect world, Roles become sort of “invisible” compound clips. In other words all clips for a role would stick together as a group, which could be routed to a mixer or FX send/return if needed. Click a “minimize” button and all the visible clips in the “container” would shrink to single, locked in time (compound) clip, but one which could be expanded *in the timeline* it resides in for further editing if needed.
[David Lawrence] “Is there a way to make all connected clips stay put if you want? Something like Shift-tilde? That would make a big difference for me.”
That would be a good thing. They should have a role based option to enable/disable connection, like snapping, if you want. This would be handy, especially for music that’s all chopped up and thus connected to random “parent” clips. Stuffing it into a CC is a workaround but you have to keep breaking it apart and remaking it to adjust cuts. The imaginary scenario above would also solve that since, once collapsed, the MX role would be locked to time.
Maybe they’ll do it. I’m pretty sure FCPX isn’t done yet. 🙂
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Aindreas Gallagher] “you don’t have any truck with david’s reading of the point that the fundamental issue might lie with the core data model itself?
Nope, because it doesn’t say there’s a problem with the Core Data model, it says there’s a possible problem with the iCloud Core Data synching model.
[Aindreas Gallagher] not to mention that there’s four guys and a cat at apple handling the whole thing?”
A cat?!? Crap! I guess I need to go re-read the article again…
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[David Lawrence] “The connection is here:
“Some issues with iCloud Core Data are theoretically unsolvable (stemming from the fact that you’ve put an object model on top of a distributed data store) and others are just plain bugs in the implementation…”
“Because of this there is a lot of fragility to the implementation, and I’m not sure it will ever scale well to larger data sets…””No, it’s not. The statement is about iCloud Core Data. “Some issues with iCloud Core Data are theoretically unsolvable…”. You are making the connection.
[David Lawrence] “I believe the same is true with the magnetic timeline’s hierarchical, single primary, parent/child, relative time model. I don’t think it will scale. Without absolute, external time, I don’t see how it can ever really support parallel, independent media streams such as multi-channel audio in a DAW. I don’t think roles will ever be enough. I believe the absolute, external time frame of reference is essential.”
That;s a lot of believing. 🙂 I beleive that X supports “parallel, independent media streams such as multi-channel audio in a DAW”. You just can’t run them through a “mixer” yet. Admit it, you just don’t like the timeline. 😉
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Steve Connor] “[Gary Huff] “And this is why it’s hard to take fanboys seriously.”
Because they have a sense of humour?
“Clearly yes. Pointing out tenuous possible flaws in software you don’t like is serious business!
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Aindreas Gallagher] “thats from a dude who really knows. Thats how the database problem pertains to the FCPX timeline model in operation.
Clearer for you now? :)”
Um… no. That’s the opinion of a guy who knows, which may well be correct. I don’t know, and neither do you.
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Aindreas Gallagher] “Even John Gruber was caught by it. And he’s the biggest Apple booster in the business.”
Yes, he was. “Devastating piece by Ellis Hamburger for The Verge on the calamitous state of iCloud Core Data syncing“
Didn’t see anything about Core Data itself, but I guess I don’t have the right glasses on.
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[David Lawrence] “What these developers are saying is that Core Data syncing is potentially unscalable and ultimately unfixable because the model itself is broken.
I would argue that this may also be true for the FCPX magnetic timeline in its current form.”
I’m interested in how you make the connection from “Core Data syncing is potentially unscalable and ultimately unfixable” … to the magnetic timeline?
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~