-
Development
-
iMovie used to be 32bit vs FCPX 64bit.
That has probably changed with this new version, though.
-
[Jeremy Garchow] “That has probably changed with this new version, though.”
It has. It’s 64 now..,
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
so that largely resolves music based edits then right?
seriously though – exactly how seductive is that tagging system? bins spontaneously made out of free form compound attribute phrases from recall?
are you kidding me?In a way – why aren’t more settled industry production participants (without anonymity and weird training aspects) simply and calmly putting FCPX obviously to work in visible uncontentious scenarios? Why aren’t they doing that? It’s easy to do and it affirms the software. below the line is everywhere.
Why isn’t it just being put selectively to work to analyse it? Isn’t anyone curious at all? Given it desperately needs the analysis?
if the industry keeps calling FCPX the red headed step child, and keep stomping, the entire red headed child is potentially likely to die.
bad, say hulk, that loss to all.
https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics
-
[Aindreas Gallagher] “so that largely resolves music based edits then right?”
A COW user showed me in early Larry Jordan training, like, the first fcpx training to hit the market, the disconnected “Soundtrack” was in a training module, but that feature never made it to the fcpx official release and was later ammended, so it must have been an iMovie Pro leftover.
[Aindreas Gallagher] “Why aren’t they doing that? “
How do you know “they” aren’t? 🙂
-
[Charlie Austin] “[Jeremy Garchow] “That has probably changed with this new version, though.”
It has. It’s 64 now..,”
Aha!!!!!
Therefore by the impeccable logic that has so often been so devastatingly deployed by the “FCP X is not based in iMovie” crowd, the only possible conclusion we can draw from this is that the new “iMovie” has absolutely nothing in common with the old “iMovie”.
Nothing.
Not one shred of code.
Not one single point of comparison.
Now that’s weird.
But so obviously true as not to require any further discussion.
For those of you to young to remember, it was always definitively argued that because FCP X was 64 bit and iMovie was only 32 bit there was self-evidently nothing that they could possibly have in common.
Despite the apparently self-evident fact that the entire design underpinning of both products was identical at the point of X’s launch.
Instead we now have the rather bizarre scenario of folks arguing that the new iMovie is based on X – and of course wouldn’t look remotely like X if X hadn’t come first!!!!!
The world is a very strange place …
Simon Ubsdell
http://www.tokyo-uk.com -
[Simon Ubsdell] “The world is a very strange place”
Yeah.
Like it was said two years ago, this stuff doesn’t really matter, does it? So what if X is based off iMovie or vice versa.
iMovie can now take Motion templates. Perhaps iMovie, in a shocking turn of events, is now iMovie Pro
https://blog.alex4d.com/2013/10/23/fcpx-motion5-imovie-2013/
Jeremy
-
[Simon Ubsdell] “For those of you to young to remember, it was always definitively argued that because FCP X was 64 bit and iMovie was only 32 bit there was self-evidently nothing that they could possibly have in common.
This argument was likely made by the same people who argue that FCPX was perfect when it was initially released, and to this day has absolutely no problems or shortcomings at all. It’s pretty self-evident that those people were/are wrong. 😉
[Simon Ubsdell] “Despite the apparently self-evident fact that the entire design underpinning of both products was identical at the point of X’s launch.
Instead we now have the rather bizarre scenario of folks arguing that the new iMovie is based on X – and of course wouldn’t look remotely like X if X hadn’t come first!!!!!”It’s pretty obvious, to anyone with eyes, that the design of FCP X was based on iMovie. Timeline, UI, event/project structure, skimming, magnetism, etc, etc. But, and I say this as someone who enjoys poking around in app packages, the guts of the 2 were very different. QtKit vs A/V foundation and totally different Plugin architecture were the biggies, but there were an enormous amount of fundamental differences, despite the similar look and feel.
Now, other than the vastly simplified UI, not so much. Maybe iMovie and X have a symbiotic, leapfrogging relationship…
A- Try out concepts in iMovie 8 -> build a brand new app, FCPX, based on those concepts.
—launch FCPX and make improvements over time. Meanwhile…
B- Rewrite new iMovie based on FCPX code and try out new concepts -> Use new concepts in FCP X ???
—I guess we’ll see in December… Maybe they’ll put “Pro Quality” Trailer Templates in X, and we’ll all be out of jobs. lol————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Charlie Austin] “Now, other than the vastly simplified UI, not so much. Maybe iMovie and X have a symbiotic, leapfrogging relationship…
A- Try out concepts in iMovie 8 -> build a brand new app, FCPX, based on those concepts.
—launch FCPX and make improvements over time. Meanwhile…
B- Rewrite new iMovie based on FCPX code and try out new concepts -> Use new concepts in FCP X ??? “That sounds like the most sensible description for sure.
But there will always be folks to whom it is an article of faith that the two could never have had anything in common.
In the case of FCP X, sure the guts are different, but what is really distinctive about X as against every other NLE out there? Its fundamental design concepts. And to argue that these didn’t derive directly from the iMovie development path has always struck me as highly perverse.
How you build an app is one thing – what you are building is quite another thing. Two apps can be built entirely differently and yet be driven by an identical design concept.
(Coincidentally, I’m doing that exact same thing this week (albeit on a scale vastly more modest than X) with one of my commercial products – taking it from something only accessible to X users and making a version that will work in Premiere and Ae. Entirely different build methods – the same end product.)
[Charlie Austin] “Maybe they’ll put “Pro Quality” Trailer Templates in X, and we’ll all be out of jobs.”
They’re already much too good for my liking 😉
Simon Ubsdell
http://www.tokyo-uk.com -
[Jeremy Garchow] “Like it was said two years ago, this stuff doesn’t really matter, does it?”
Revisionist 😉
Simon Ubsdell
http://www.tokyo-uk.com -
…and all I asked was “Does anybody know how long ago they started building this thing?”.
seems about 2 years before the first “Beta” release in 2011. I wonder if they will dare release 10.1 without more thorough testing. Trouble is how can they when it’s all so secret? How can they test thoroughly without releasing official Beta and testing broadly? I think that’s a problem for Apple. Is it Paranoia? or stupidity?
Reply to this Discussion! Login or Sign Up