Forum Replies Created

Page 25 of 48
  • So true Oliver. It helps people stay more organized. And for someone like myself with a background in computer science and develops FileMaker and SQL based databases perhaps that’s why I like it. I am playing IT person so much it’s nice to have something that can help manage things when other users don’t have the care for organization to the extent that I do or at least try to.

    Tangier

  • Haven’t had any issues using managed libraries even in a multi editor workflow. In some ways I prefer it. It’s just the steps in sending a simple project. Though I am not working on a SAN and perhaps some of you are.

    Tangier

  • Thanks Oliver. I’ll look at those and give it another try. I’ve been used to working with managed libraries, but am open to not doing so. Pre FCP X my media was always separate from my project file. That’s not to say that there aren’t benefits to a managed library, but definitely worth exploring.

    In the meantime, using the backup file has worked like a charm.

    If I didn’t have to worry about sending a project with color correction done, I could just use XML. Problem solved.

    Tangier

  • I will run another test again, but I’ve done it several times already. Folks (on that linked thread) pointed out that there is a difference in the way the copy project behaves depending on whether the library is managed or unmanaged.

    Tangier

  • I missed putting in my above reply that I meant if you have both options unchecked. I left the word “unchecked” out.

    Your scenario is exactly what is discussed on the Larry Jordan link I posted. My libraries are managed. Yours are not. I mentioned that as well near the bottom of my last reply – which I realize also should have been edited (typing too fast to get my thoughts down).

    I said, “I could not use unmanaged libraries as well, but I’d have to delete render files and such to keep the library small before sending it to someone else a transfer library”

    It should have been : I could use unmanaged libraries as well, but I’d have to delete render files and such to keep the library small before sending it to someone else a transfer library.

    Tangier

  • I and the producer do have copies of the same library. The problem Oliver is that there is no way that I can currently see that FCP X can just send only the project, even inside a library as is required, without at least copying the original media. When you create that transfer library File > Copy Project to new Library to create a new Transfer Library, even with the two options of bringing over proxy and/or optimized media, FCP X will still copy the original media into the new transfer library and it says it’s going to do that. I don’t want the media. The producer already has it. It’s making a large transfer library with files I don’t want and makes it even more difficult/time consuming to send to someone.

    Sure I could let it copy all of the original media into the transfer library, then delete all of the media (either using FCP X or at the finder level inside the library package.

    This is why someone on that link (I’ll paste it below) had to explain a workaround using the backup file. It seems this is the best solution so far. It’s sad to have to go through all of this just to send the project. A previous version of FCP X before the library model had the option of just duplicating the project only without media. I could not use unmanaged libraries as well, but I’d have to delete render files and such to keep the library small before sending it to someone else a transfer library.

    One cool thing I use to make sure libraries are ion sync is I use Decimus Synk. It goes inside the library package and compares everything and makes sure they’re in sync. However I only do that when I have both drives near me or I and the other person are on the same network. It’s a fantastic part of my workflow.

    Here’s where I could be drastically wrong, but I don’t think so just yet. If I copy the project to a new transfer library, having every option unchecked and FCP X still saying it’ll copy the original media into the library, then perhaps the size of the library that’s showing up in the Finder is not real. Rather it’s counting symlink as media and calculating the size of the original media though it’s not actually there – hypothetically. However when I go into transfer library package, that’s not the case. The media is in fact there.

    Here’s the method I found on Larry Jordan’s site from Chris:
    “I seem to have found a workable solution to allow for transferring of events and projects between editors with managed libraries – exchange the backup file!

    A hack, but it works. For example, both my assistant and I have the same managed library of a shoot. At this stage no editing has been done so no projects. She edits, making a few projects, events, whatever. When she is finished she lets me know and gives me the latest backup file. I open up that file – double click in the finder. Although this opens, usually it says that the original media data can’t be found so it opens as a new library with all the files highlighted in red as unconnected clips/media. All I have do then is drag the projects that my assistant made to the library I have with the media in. Everything is automatically connected. Perfect!

    And to make things even easier, we are storing ours backups on dropbox so all my assistant has to do is make sure that it has backed up recently by checking the time code on the backup file name and then I just drag that backup file to, for e.g., the movie folder of my mac and then double click from there.

    Seems to be a solution for sharing projects between editors both using a managed library in 10.1 anyway.”

    Tangier

  • Tangier Clarke

    November 9, 2015 at 10:20 pm in reply to: Can Premiere Pro CC batch sync clips?

    Thanks. Perhaps I’ll have to give it a try myself. I am not interested in a timeline of any kind being generated. I am only looking to be able to throw a bunch of video and audio clips at it and it give me back new separate multicam clips (where it could find clips that fit that profile); since it cannot provide merged clips.

    Tangier

  • Tangier Clarke

    November 9, 2015 at 9:49 pm in reply to: Can Premiere Pro CC batch sync clips?

    Does this feature distinguish between clips that only need to be merged vs. ones that need to be made into multicam clips?

    Tangier

  • I apply a still to the drop zone and nothing shows up. It’s not reflected in the generator on the storyline. However when I open the generator in Motion (from FCP X) and try applying a frame to the drop zone it works perfectly.

    Tangier

  • You’re right. I should have been more clear about what I meant. It doesn’t absolutely require the timestamps for syncing, but rather it tremendously helps for organizing the content in list view to prepare for syncing.

    I could use the slates from the picture and listen to various audio, and try other sifting methods to label the shot/take etc just to be able to sort the clips in a way that I can identify which to sync or multicam.

    -how’s that for a run on sentence

    Not ideal, but yes it’d doable. If FCP X had the batch capabilities of PluralEyes, we’d be golden.

    Tangier

Page 25 of 48

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy