Bret Williams
Forum Replies Created
-
I don’t have any yet! Just looking into it so far-
-
Can you just replace the bad files?
-
Yes, it does copy the files… almost instantly. AND through the magic of hard links/sym links these files use the same media. They’re not aliases. They are real files. But both copies of the files point to the same data source deep in the OS. This isn’t a finder thing. The data won’t be deleted until you delete both copies.
-
You can do that or you can highlight the project and choose to copy/duplicate the project to a new library via the file menu.
-
Unfortunately it’s been this way about a year and a half. I don’t think Apple cares. But your link and video are great. I’m working on some motion template ideas for videohive. If I include FCP X generator versions, I’d like to include a link to your article/video in my support docs if that’s alright with you. I’m leaning away from doing any drop zones that aren’t at the beginning of the template due to this bug. I don’t needs an inbox full of complaints that they can’t get the drop zones working.
BTW I’ve made good use of your bullet point plug/template a few times. Even found a way to adjust the timing by compounding it and adding hold frames between the different lines.
-
Copy the project to a new library. It doesn’t take up any more space as long as it’s on the same drive.
-
I wonder what setting you used? For example for my test earlier, I used XML 1.5 and chose Basic. I know that certain things don’t come across to Resolve if you use the wrong setting. Perhaps you don’t get the color settings if you use extended or something. Opposite to common sense, I’ve heard the best to use is the basic or general settings.
-
Transfer libraries are probably your safest bet. But if the XML works for what you’re doing I’d try that. Can always send a low res QT with it to make sure things match up.
-
Just did a quick test and color board info comes across just fine. I’ve never seen anything that doesn’t come across FCPXML going between FCP X and FCP X. The aforementioned concept certainly works, but just export the project as an xml and bring it back in on the client’s end.
-
Simply do what you said and copy the project to a new library. It will be instantaneous if it’s on the same drive as it actually uses hard links to duplicate the media without taking up any space. This of course is only the case if your media is internally managed. If it’s externally managed then the new library will be empty anyway and you’re ready to go. But if the media is internally managed, you just need to consolidate the media out of the library to a separate folder. Like I said it doesn’t take up any extra drive space or much time. Your client should open the library and copy the project to his library.
XML doesn’t carry color board info?