Currently Being ModeratedDec 31, 2013 4:09 PM (in response to Psilocybe)
Things have changed a lot with 10.1.
Projects are now seen in the Events. Click on an Event.
Find the project icon and double click to open the Project.
Project icons have a clapper baord at the top to help ID them.
Currently Being ModeratedDec 31, 2013 4:13 PM (in response to Psilocybe)
Try updated Projects.
Currently Being ModeratedDec 31, 2013 4:13 PM (in response to Alchroma)
Yes, there are a few in Updated Projects but every new Library or Event I create is done so without a corresponding Project.
Per Apple's whitepaper:
A project corresponds to an edited sequence in the Timeline. The project may be a full movie or episode, or it may be a subsection that needs to be handed off.
With Final Cut Pro X 10.1, projects are now contained within events. Placing projects in a single “transfer event” (in a transfer library) makes for cleaner organization and interchange with others working on the same production.
So for the Library AND Event that were created in 10.1 in the last screenshot I posted, where is the corresponding Project?
Currently Being ModeratedJan 1, 2014 1:59 AM (in response to Psilocybe)
An event does not have to have a project. All updated projects are in the Updated Projects event. If you wasn't them in specific events move them. When you make a new project you put it in an event. You can put it in any event in the same library or you can put it in a special event just for projects.
Currently Being ModeratedJan 2, 2014 3:28 AM (in response to Psilocybe)
Just by way of comment ... this change is counter intuitive for the way I work and it seems that projects are a complete mess to manage now IMHO.
In my head - an event is a resource to one or many projects. My workflow is to open a project and then pull in the resources I need to make that happen. Now it seems I have to dig around the events library to find the project I'm working on. How do I simply pull up a list of my projects?
I'm sure there was good reason for this but I can't fathom it and it feels poor to use now.
I've fed back to Apple FWIW.
Currently Being ModeratedJan 2, 2014 7:58 AM (in response to Tom Wolsky)
Not to hijack this thread .. firstly thanks for coming back with a suggestion. That's probably how I will manage it.
It still seems counter intuitive to me. Projects and events are not the same thing. The fact that we have to create an event to shove all our projects in, in order to view them all, seems like a hack to me. Unless there is some other way of listing all the available projects in their own and I'm missing it?
Still, in the scheme of things . I guess it's no big deal.
Currently Being ModeratedJan 2, 2014 9:43 AM (in response to Tom Wolsky)
By creating a Smart Collection within a Library with the parameters of Type > Projects we're able to view all projects across multiple events within one specific Library. That's great, but only solves 5% of the problem if we had 100 Libraries. What if we had thousands?
Because we are unable to create Smart Collections on the drive level, or better yet independent of the drive like in Aperture or Lightroom, Smart Collections in 10.1 have an incredibly narrow scope.
Currently Being ModeratedJan 2, 2014 9:52 AM (in response to Psilocybe)
You can only view the projects in a single library, not in multiple libraries. Each library should be a separate treated as a production. You might have to rethink your workflow with the new vesion of the application.
Currently Being ModeratedJan 2, 2014 10:02 AM (in response to Psilocybe)
It's more efficient because with hundreds of projects and versions from multiple productions all mixed into a single project library the organization was becoming unmanageable. People simply didn't need to see most of the projects and events and were constantly have to use workarounds or tools like Event Manager X to shuffle the folder structure around to open and close items to work with. Now productions can be opened and closed and easily isolated from each other from within the application. These are enormous efficiencies.