-
A couple new things in iMovie
Just playing with iMovie since it supposedly contains the hidden code for FCP X 10.1.
I found just a few things that I think are new that don’t exist in X yet. Nothing super special. Just noted.
Show used ranges. Sweet. And it changes as you open different projects. It’s the little orange line at the bottom.
Custom speeds
And this little clip trimmer shows how much head and tail you have when doing a slip/slide. I miss how in FCP legacy during a slip you could see a ghost image of how much clip you had available on either side.
-
21 Replies
-
Considering you mocked me for talking about this, I’d like some attribution here.
-
All great stuff. I think “Used Ranges” is one of the reasons why Apple decided to combine the Project/Event structure into a single “Library’ structure. With them separated, you couldn’t have Project info write back to the Event database. It was pretty much a one-way down stream of metadata from Events to Projects. So this opens up some great enhancements. Probably in Media Management as well.
-
I thought it might have been in there. Either it was too long a read for me to remember or I didn’t finish it all.
-
I mocked you or Andy mocked you? I’ve always found the iMovie, shared or not shared code, FCP botched launch, FCP X is/isn’t iMovie Pro dialog fascinating. The whole thing is a bizarre moment and time in Apple’s history for sure. I definitely find the new iMovie sharing FCP X.1’s code to be quite interesting.
-
Since 2011, the two have shared basic concepts, but no code.
Now, iMovie basically contains walled-off code for FCPX, Motion, and Compressor. Andy Mees recently discovered you can pull FCPX XMLs into iMovie and they open with a fair amount of fidelity.
In this particular instance, iMovie just happened to make it out the door first. But who knows how old that version of 10.1 hiding inside iMovie is…
-
Alex has done, like 4 articles now, pulling the code apart. Some really great snooping on his part.
If only half of it ends up being in the 10.1 release it will be a huge update.
-
Yeah, I’m sure when X.1 comes out it will be newer code. There will always be a disparity. Which leads me to believe that it’ll still be a one way trip from iMovie to X. There’s just so much that is unsupported in iMove. You can only have one title track and 2 layers for example. Even if it just ignored things it didn’t support it wouldn’t be very functional. But I’ll have to check out the Andy Mees XML post.
-
This mirrors my thinking as well.
And re-enforces my belief that Apple never got lost in the mindset of just “adding features” to the storyline editing module.
From virtually day one here, I’ve been arguing that the real excitement about X is how it works before and after the storyline (as much as I LOVE the speed and agility of my storyline operations these days!)
They’ve apparently been spending as much time on how X sits in the middle of a cohesive workflow – as they have trying to re-capture the historic way of operating for editors who prize “operational comfort” over new capabilities.
Can’t wait for 10.1. This is truly FUN seeing what Apple has been working on!
Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.
-
I just finally grasped the whole new Library system in iMovie. And now that I do, it’s pretty hilarious.
Apple has added a new feature which groups events and projects together called Libraries. Wow. Cool. But pretty funny when you think about it…. Now, we have an overriding element called a Library. Inside the “Library” we have both Events and Projects contained within in it. You must open a “Library” to begin working. You can open multiple “Libraries” at once. See where I’m going? If you go back to Legacy nomenclature it starts to look real familiar. Let’s call a Library a Project. Let’s call a Project a sequence. Now lets call an Event a Bin. So, in the new version of iMovie, you must open a Project (library) to begin working. Inside your Project (library) are Bins (events) and Sequences (Projects). You can have multiple Projects (libraries) open at once! Wow! Nobody has ever done that before! Except Apple from 1999-2011 when it was called FCP 1-7. 🙂
Now that Events are grouped into a library, it will be more common to use them as bins. Previously I would have one Event with folders and keyword collections. And also in new iMovie, projects don’t actually exist separately within the library. Each project (sequence) lives in an Event. Just like a sequence in legacy had to reside in a bin (or the root browser, which was just a bin fwiw). It will just seem natural to create an event called “sequences” and put all of that library’s projects in there instead of the project library folder one would normally create in X.
The neat thing, is that when you have two projects (libraries) open you can share the media from each’s events (bins)! Couldn’t do that with multiple projects open in legacy…. oh, wait. Of course you could. Isn’t this fun?
It is really nifty that you now have an all projects (sequences) link and an all events (bins) link. That is actually going to be extremely handy if you have two projects open. And if you utilize footage from another library (project) it automatically copies the footage to your library and puts it in the bin (event) where the sequence (er project) resides. That’s great. Unless you just wanted to use 3 seconds from an hour and a half 4k file or something. it copies the whole media file, not just the used portion. So you’ll never have the problem of opening a project and the media being missing because the event isn’t mounted. It’s impossible. At least in the iMovie variant that exists now. I assume there will be more copy or link options in X so we can screw it up.
This new format, if implemented in X, leaves a question about where keywords will go. Will they be pertinent to the library, or to the event? I usually just use one event for a project. But if I’m more apt to utilize events as very powerful bins, I’d rather the keyword collections live outside the events, but inside the library. It would make sense since all the events in a library must get mounted. Really makes more sense for logging footage across events as well. You could have a library called football, and an event of reach game, and keywords would span all the events. Stuff like nice pass, good sack, etc.
So to rehash, a library is now like a legacy project, or perhaps sorta like a folder containing multiple events that you can mount or unmount as a group. And there’s no more project library. Projects reside in events.
Here’s a screenshot to make it all make so much sense
-
Bret,
That’s pretty cool, thanks for doing all the leg work. I have always worked very hard in naming my Events and Projects so that it’s easy for me to match them up when I need to go back in time, but this system would be much easier to keep everything together in a simpler, less “needing to be clever in a naming convention” kind of way.
Starting new Libraries with Events and Projects should be very easy. My question would be as to how go back over the last 2 years and re-organize into Libraries. My guess is that you would load up all your Events and Projects, open 10.1, create/name the new Libraries and then drag and drop your older Events and Projects into the appropriate Libraries.
I guess we’ll find out in the next couple of weeks.
Thanks,
Dave
Reply to this Discussion! Login or Sign Up