Bret Williams
Forum Replies Created
-
I can’t see a reason to do this. I also can’t see a reason to use MPEG streamclip for anything anymore. Does it even run on Yosemite? They quit working on that app 5 years ago didn’t they?
-
So you’re keeping your libraries in your local user folder? What would be your plan when your internal hard drive crashes? I’ve had very few externals fail. aLmost always the internal which gets too hot, directories get corrupt, etc.
-
I’ve never heard it recommended that you put the library on the internal. In fact, that’s kinda nuts. Just the render files and such would eat up tons of space. Leave your internal for apps only IMO. I keep the library in the raid 5. It’s added security, and since the library also contains render files and such, those files need to be on a performance drive. Although if you have an ssd then that’s probably better performing than my raid!
But there certainly isn’t a performance issue with having your project or Library on the raid with your media.
-
In a similar way I do what you’re talking about quite a lot. 500gigs wouldn’t be unheard of. In fact, I’m often copying 100gigs here, 100gigs there, during a project as a client brings more and more media. Usually my file structure is completely different than theirs. Usually just set the media to copy to my raid, go to lunch, then come back and relink in a matter of minutes. I can’t imagine your media was more than 1TB, but probably much less since it wasn’t ProRes. ProRes would be about a TB for 15hours. So no, it’s not normal that X would have so much trouble or that it would take any longer than 7 in my experience. Quicker if anything.
That said, you could have avoided any relinking at all by giving the client a library with all internal media. When I archive a project and hand it to the client, that’s what I’ve switched to doing. I can rest knowing that when they decide to open the project someday that there will be no relinking necessary. When it’s internal, the links don’t point to a particular drive, but to the library itself no matter where it lives. So instead of you copying a library and it’s external media to a portable drive to hand off to the client, you would simply copy the library to the portable, then open it up and consolidate the media (in library inspector panel) to the library itself. Unfortunately you lose all the folders/organization of the media that previously existed when it was external, but do you need it? At some stage it’s the keywords and organization IN the library that is what matters.
-
Other than FCP X being more picky about the media being an exact match in name, type, TC, and size than FCP 7, X has been the same or faster. In fact it’s much better at finding the media. All you have to do is point it to the root folder and it will dig down. So if your drive is the same structure, and is a copy, there should be no problem at all. Just select all the media in the library and relink. When it asks for the first file just point it at the root folder of the media you gave them. If perhaps they’re trying to relink 1 by 1 then that would take awhile…
-
First time I saw the magnetic timeline it reminded me of the Casablanca. How do I even remember the name of that monstrosity?
-
Except when you’re actually do a ken burns type photo montage where you don’t want easing.
-
Obviously you can’t animate a pan in the media window. My problem is that only s stereo clip will pan in a stereo track. I’ve read the manual on it and honestly it doesn’t seem to correlate. It’s definitively not intuitive. I’ll have to revisit it on another project. Resolve was pretty backward on some simple things so I had to do the project in X.
-
Don’t know about that. Just a day ahead with same problems!
Have you found the ofx effects panel yet? I installed universe premium just to have a set of basic transitions, generators and effects. But the effects aren’t in the same place. They’re in the color panel.
-
I had the exact issue with synced clips coming across incorrectly in 12. There were a number of issues. First, the disabled tracks were enabled in 12. But I also had to “open in timeline” the clip where I discovered more audio tracks that needed to be disabled. So it seems that a synced clip is being considered a compound, and at the same time attaching the synced audio outside the compound. Basically it’s a mess. So I deleted the “scratch” clips in resolve by option selecting them. Then I decomposed the clips in place which exposed all the compounded audio and then deleted those. Finally I was left with the video and the synced audio which I relinked back to their video one by one with cmd option L.