1 2 3 Previous Next 35 Replies Latest reply: Dec 4, 2012 7:41 AM by Tom Wolsky Go to original post
  • 30. Re: "Duplicate Project" issues with 10.0.6
    Nexus7 Level 1 Level 1 (0 points)

    For me it's easier to do it this way:

    1. Drag the project in the library to the new volume. Select just the project in the dialog.
    2. Drag the event in the library to the new volume. Wait until copyingis done.
    3. Click the button "Modify Event References" in the inspector and move the new volume to the top.
  • 31. Re: "Duplicate Project" issues with 10.0.6
    Luis Sequeira1 Level 5 Level 5 (5,625 points)

    Nexus7 wrote:

     

    For me it's easier to do it this way:

    1. Drag the project in the library to the new volume. Select just the project in the dialog.
    2. Drag the event in the library to the new volume. Wait until copyingis done.
    3. Click the button "Modify Event References" in the inspector and move the new volume to the top.

     

    I don't think this will replace aliases in the event with the actual movie files.

     

    I, for one, think that the current behavior, while perhaps not well reflected in the wording of the available options, makes sense. Think of it this way: it is perfectly possible to have media, events, and projects all in different drives, or several combination of those (say, projects and events in one drive, media in another). That is especially significant if you have a *lot* of media.

     

    In that case, you probably have your own backup method for your media drives, and don't need or want to have extra copies of (*large*) media drives backed up alongside your events - so in that case you DO want to keep aliases, not media, in your event backup. The current state of things allows for that. And if you really want to replace the aliases with copies of the media, "Organize Event Files" is there for you too.

     

    Maybe a better way would be to add another option when copying or moving projects/events, or just to rephrase the current options so that they are not misleading.

  • 32. Re: "Duplicate Project" issues with 10.0.6
    Tom Wolsky Level 10 Level 10 (106,180 points)

    It is not a bug. It is by design. It helps SAN users working with multiple editors to share projects and events while using a single source location for media. It no longer requires media duplication to share changed and updated events or projects.

  • 33. Re: "Duplicate Project" issues with 10.0.6
    Nexus7 Level 1 Level 1 (0 points)

    Tom Wolsky wrote:

     

    It is not a bug. It is by design. It helps SAN users working with multiple editors to share projects and events while using a single source location for media. It no longer requires media duplication to share changed and updated events or projects.

     

    Ahhh! A duplicate function that doesn't duplicate is... a feature! Wow! 

     

     

    Fact: It doesn't do, what it has be done before. It doesn't do what it name promises. It doesn't that, whats written in the manual. So it's a bug.

     

     

    P.S.: And as i wrote previously the "Move Project" function is also affected by this bug. If you use it in the common way and the FCPX manual suggests, you're in risk to loose all of your media data.

     

     

    P.S.: Fact: Not all are affected by this bug.

  • 34. Re: "Duplicate Project" issues with 10.0.6
    Nexus7 Level 1 Level 1 (0 points)

    Luis Sequeira1 wrote:

     

    I don't think this will replace aliases in the event with the actual movie files.

     

    This was no assumption. I've tested it, and I use this method.

  • 35. Re: "Duplicate Project" issues with 10.0.6
    Tom Wolsky Level 10 Level 10 (106,180 points)

    It does duplicate. It duplicates the alias links to the original media. Luis gave you the solution for what you need to do if you want to copy the media rather that the aliases in the event folder.

     

    No, it doesn't do what it did before because a lot of users working in large facilities badly needed to have this changed.

     

    The manual unfortunately has not been updated.

     

    Yes, the move function has the same behavior and the same solution.

     

    If your media had been in the event in the first place this would not have been a problem. For many users working in single user environments, importing from cameras, the media is stored in the event and this change in behavior does not affect them.

1 2 3 Previous Next