rationale behind Library/event/project hierarchy

Can someone please explain the rationale behind this structure? I could not find anything in the documentation that explains why it is organized this way. I'm sure that there must be sound reasons, but they are not obvious to a new user, even one like myself who years ago used Video Toasters, AVID workstations, Premiere and so on. In the old days you began with what Apple now calls a Project, and the files necessary to the project were organized under that. That was intuitive and simple. Apple has inverted that process, beginning with the Library, and added a hierarchical layer, Event. To new users the creation process seems backward, and the Event layer seems redundant.

MacBook Pro 15″, macOS 10.14

Posted on Dec 24, 2021 4:08 PM

Reply

Similar questions

7 replies

Dec 26, 2021 11:22 AM in response to terryb

Thanks for this, it partially answered my question. I still don't understand the reasoning behind this backward-seeming process, but the nomenclature explanation was helpful. This is not addressed anywhere that I can find. The nomenclature as "explained" in the documentation is confusing, as the levels of the hierarchy seem to have overlapping definitions.

Dec 26, 2021 11:30 AM in response to melonmtn

in FCP, the File dropdown menu is organized like this: File>new>Project, Event, Library. To me, this implies the hierarchy. First, you would create a project, then you would create an event in that project, then you would populate it with the Library. That is the exact opposite of the actual hierarchy and the correct procedure. Why would they organize this upside down?

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

rationale behind Library/event/project hierarchy

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.