Workflow as proposed by Steve and Mark in the 10.1 Part 3 video

What do I not get is the work flow proposed by Steve and Mark in the 3 part 10.1 Ripple Training video.
They say you go into the UPDATED Projects folder, manually drag and drop the clapper-board [symbol for projects] into the right folder containing the clips you used to create the project.

My issue is with this work flow, it seems counter=productive to have updated the projects and events into a library, to have to drag and drop from the new what can only be called a temporary library folder back into the original folder.

I have yet to see any link between the media in the Updated Projects window and the media in the Libraries window on the left.

Mark and Steve then move the 2 projects [clapper-boards] into the right folders on the left of screen, then proceed to delete the Updated projects folder, making this Updated Folder a temporary folder?

Surely this is not right...Or is this just a patch method until the engineers at Apple code for 10.1.1?

This is how "updating" works. And I think you're referring to an Event, not a folder. Very different things. The "update" process has to translate a lot of things. The nature of these things often are like this. After you update, and arrange your already existing Events and Projects that need to be updated to the new database format, you'll never do it again. You'll simply create new Libraries, Events, and Projects from then on, there will be no "updating" process.

Maybe it is the terms used, the icons used, somehow there is a lost in translation here, not me, I am 100% English speaking, my only language.

I have watched the Ripple Training video a number of times and to my Aspergers brain, it makes zero logical sense to have the temporary updated projects folder/library then to have to destroy it 90 seconds later with dragiing and dropping the projects hopefully into the right library for that project.

Why not use meta-data, just add a way, I am not an engineer, a confuded user, a meta-data link as that is what FCP X loves, to link projects with events with libraries, so when an update is done, the right clips find the right events, find the right projects all housed in the same library, if 2 events/media are linked to 2 or more different libraries, then use the Hardlink method to show libraries with correct media, and never have to see this confusing updated projects folder.

(with the caveat that my main system is still on 10.0.9, as I've just delivered my last project of the year this morning and no way am I updating before my client's signed off! ...)

Why do you have to move anything out of 'Updated Projects'? Surely that's just where 10.1 puts everything to start. Yes, it could use the 'primary event' metadata attached to each project, but if we're honest that was always a bit flaky, mostly on account of it having no real effect. Better for 10.1 to echo the previous system as much as possible (keep projects and events separate), and allow you to clarify the connection if you wish.

If you want to move projects elsewhere, because them being elsewhere would make more sense to you, then go right ahead. But if you want to leave them where they are, leave them where they are. Then Projects are up at the top of the screen rather than in a weird wide box where the timeline should be, but nothing else has changed.

One of the things I think I'm going to like about the new approach, incidentally, is that it's less prescriptive. The previous Events/Projects enforced separation made archiving projects once completed a bit more messy than it needed to be. Libraries should be simpler in the long term, but we'll see.

Would be so handy to have Steve and Mark explain why they moved the projects out of updated and went on to delete that folder? As a newbie, it seems to me that is the method most preferred by Apple, as Apple recommend them in feedback feddback, which if is the case, then it stands to logical reason 10.1 is a 50% complete update, that they did not have time to finish the update segment of the 10.1 update, and were forced to leave the user with this "updated projects folder/library.

Perhaps its because there is no ¨standard¨way of storing projects or events. I stored my events by date, then client, because it seemed logical at the time, but projects by month and client.

I spent no more than an hour yesterday reorganising along the lines Steve and Mark suggested (on 4 external drives) - moving projects into the relevant event folder (with the associated media), then, as a second stage, creating new libraries with client/project names, and moving events into them.

I am much happier with the new layout - but at the end of the day - its like how long is a piece of string? - There are many correct ways to sort and store productions - just pick one you like - you can always change it later!

Justine,

X does this on updating from the old paradigm because there's no explicit link in 10.09 between Projects and Events. So it can't know where to put the projects - imagine you had a project referencing 3 different events - where would it put the project in the new file structure? So, as a one off thing it places them in a logical place - a single container for all projects. Now you may well want to have a collection or folder within each event for your Projects relating to that Event. Or you may want to have a top-level 'Event' in the library to contain all sequences - the choice is yours now. So absent of any way of telling what projects go with what events - I can't really see how they could've done it any differently. And as pointed out, this is a one time only thing - after update you'll not have to do it again.

So it's not a 50% finished product - just because you don't get how it works it doesn't mean it's broken...

Today at 4 pm Pacific time Steve and Mark are doing a live Q/A stream o. YouTube.


Personally, I can't wait

"My issue is with this work flow..."

It is NOT a work flow. It is a byproduct of the conversion from the old organization to the new library based organization.

You are going to have to figure out a work flow that works for you. That may mean putting projects in the same event that references the media, but it doesn't have to. I can see how some might like a separate event for projects.

To repeat what others have written. UPDATED PROJECTS is NOT a folder. It is an event. Apple put created that event and put all projects there as part of the conversion. You can move them to different events if that is what you like. Or you can keep them there. YOUR choice. Either choice is valid.