Robin S. kurz
Forum Replies Created
-
Exactly.
The only reason I can think of for doing that… well… let’s not go there. 😉
-
You simply assign (the same or different) keywords to each segment. After that they will show up as individual clips (or “sub-clips” if you will) in the collection.
-
Sounds to me like your Spotlight database is simply not up to date, for whatever reason. You might want to try switching it “private” and back to get it to re-index.
-
Actually, the system requirements for FCP X were Mac OS X Snow Leopard or Lion all the way to v10.0.9. The only thing that changed along the way (with 10.0.3 I believe) were the GPU requirements. v10.1.x requires OS 10.9, yes.
-
I’d personally update the project to your 10.1.x first. Because the colorist, who will most likely have 10.1.x himself, will obviously have to do it either way if you want to leave the XML (or whatever) export up to him. Aside from the fact that the newer FCP also has a *much* improved XML than the (very) old 10.0.6 (whereby I have no clue why someone would want to stick with such an ancient version, especially since all updates are free, but that’s beside the point). Many more parameters and settings (e.g. color and sound) are supported i.e. carried over.
After converting I would simply set the libraries storage location to itself and consolidate. That way you know everything is included when you copy it over to an external drive (which I would *also* do from within FCP btw!). Though things such as titles are not retained. And if the colorist is using FCP X, then I’d say it’s very likely he also uses Resolve.
-
I would bet that it in fact slows you down instead.
-
Though I couldn’t tell you HOW off the top of my head (a lot has changed), I would think that theoretically, yes, it should work. Because they both use QMaster for the render distribution. But to be honest, I *highly* doubt you would even notice *any* improvement of any kind. A machine with 2GB RAM will be so old and limited, that its speed will never be able to compensate for the overhead time the distributed rendering requires in addition to the rendering itself. I’d say it’s a complete waste of time to even try.
-
[Frank Valtellina] “”Color corrections pasted between clips are retained during Share” but I didn’t have any issue…”
It was a big one. If you pasted color attributes from one clip to another, the correction was gone upon export.
[Frank Valtellina] “but you can’t apply any effect to the clip in the browser”
If I recall correctly, in versions <10.0.6(?) you could apply effects to clips in the event browser. Those are now retained when and if you update.
-
😀
Good point. Edited for “clarity”. 😉
-
This is “just” a bug fix, right? Or has anyone spotted anything beyond that?