Robin S. kurz
Forum Replies Created
-
I don’t get it. For what you’re doing/trying to do extremely little changes. If anything really. You import your media to an external location WITHOUT generating the proxies upon import, after which you’re out of the import window. After which you simply switch your storage location for media i.e. proxies (all without re-entering the import window) to the library and kick off the creation of the proxies. Done. In older versions you would not have been able to even do that. So how has anything been removed and isn’t in fact better?
But yes, I agree that having original media, optimized AND proxy grouped into one location setting (at least the original should be different from optimized and proxy) isn’t the most ideal in every situation. But then, you can make them different by switching as described. It could just be easier to do I suppose.
-
[James Culbertson] “why would daisy chaining the two R4s not work?”
Because one is TBo 1 and the other TBo 2.
-
As opposed to any other NLE I’ve used, where there was none at all? 😀
And if you’re using the fade handles, you have four different curves to choose from. Seems pretty unlikely to me that none of them wouldn’t suffice.
-
[Fabrizio D'Agnano] “it’s a pity that at least one of the features was already there and was killed”
Which? I don’t see any features that were. Maybe moved, but not REmoved.
-
By the way, there’s a demo version of FXFactory and every single plugin they sell through it. So you really don’t even have to ask. 😉
-
Seeing that it’s a collection of a huge range of filters, I don’t know how one could make any blanket statement about it. If you mean any in particular, and I have many, then I could comment on the individual ones. But then the individual ROI will be different for everyone either way.
-
[Adam Schoales] “it sounds like other people get where I’m going with this”
Not sure where the plural is coming from. ;-D
[Adam Schoales] “The latest update of FCP meant you could store those proxy files OUTSIDE the library”
See, that’s where you’re losing me i.e. the confusion and problems begin, because you do not have to save the proxies externally. As I’ve been saying all along, you simply store them WITHIN the library, copy THAT (if even needed) back and forth, done. And if that is too much, just copy the Currentversion file each time. Done. But unless you need to be editing the exact same project on multiple machines, I don’t even see why you would want or need to.
[Adam Schoales] “(like a FCP 7 project file)”
Not exactly a fair comparison, since in 7 you’d more than likely be working with nothing other than the originally ingested media that could also sit anywhere. Just as you can with the current version of X, only it’s called a “library”, in which case, as described, it would also be very small. No difference. X has in effect caught up with 7 in that exact respect. Your problem is with the proxy files, which I personally never once used in 10 years of 7, did you? Using 7’s proxy feature was a huge PITA and essentially useless IMHO.
[Adam Schoales] “THE PROBLEM is that when you open up that library on a new machine, your media goes offline.”
Yes, of course. Any media you don’t in fact have goes offline. If it’s the original or optimized media, then you can simply reconnect. If you want to work with the proxy media (which you can’t explicitly reconnect on its own, no) you simply save that to the library, after which there is no relinking needed. It is recognized automatically wherever you take it.
[Adam Schoales] “I copy over the library folder, and the PROXY MEDIA folder”
Exactly. And all I’ve been trying to tell you the whole time is that THAT is your error in logic or maybe just misconception. There is no need to store the proxies externally i.e. if you don’t, but rather IN THE LIBRARY, then your problem is solved as described above.
[Adam Schoales] “AT THIS POINT one would assume that final cut should go “okay, original media is missing, but I see the proxy media folder, so let’s reconnect those proxies to there”.”
And it doesn’t work that way. As I’ve said before. X looks into THE LIBRARY first and foremost for any and all media. If it finds original media (or their aliases that lead to it) it uses that. If it finds optimized media (or aliases), it uses THAT, even if there is no original media. If it finds PROXY media (or, again, resolvable aliases), it will use THAT (if you switch). The only difference between the three is, that you can ONLY reconnect the original and/or the optimized. Both with the reconnect media command. Proxy has no such command. If the actual proxies are not IN THE LIBRARY and it cannot resolve the aliases, game over. The only real problem you in fact have (or may be just creating for yourself?) is that there is no extra “reconnect” command for proxies. Good? Bad? I don’t know. From the way I understand the logic and use it myself it isn’t necessary either. Again, for me. Even though I do exactly what it is you’re doing all the time. If that is something you feel is essential for your preferred workflow (i.e. the way it can/does work isn’t suitable) then you need to send feedback accordingly.
Mind you, I say that sincerely. I’m not trying to be combative. I’m merely trying to tell you how it can work and how it works superbly… for me in the same situation. And from what I gather, you’re not in a multi-machine situation either. In which case, now that I’ve thought about it, that could prove to be very helpful, yes, to avoid constant copying.
Bottom line: you simply need to store the proxies in the library and work from there wherever you are. That way you can easily switch to the original media when and if needed in the office and to the proxies no matter where you are. Bingo. Things work exactly as you’d like. Or rather, in this case and at the stage you are at, you simply modify the library settings to store the proxies in the library and CONSOLIDATE.
[Adam Schoales] “As a result, I’m forced to return to a workflow from prior to the latest update in which the original media is stored outside the library and referenced, while the proxy media is generated and kept INSIDE the library file. Now that library file is not a tiny file, but rather ~100 GB.”
Not true. You couldn’t have done it any other way with previous versions either. If anything, then only much more constrained (with X <10.1) than it is. It’s data you’re having to copy (really only once) either way. I don’t see how it’s relevant whether that media comes in a (separate) regular folder or along with the library that you’re copying. And since these, from what you’re saying, already exist in both locations, why would you want or need to recopy them every time? Simply work from the one copy no matter where you are, as described above, and you’re good, no?
-
[Bruce Breidbart] “with 8gigs of ram”
That’s just barely enough for normal operation with any recent OS. And yes, as Mark said (and the name RAM PREVIEW implies), you can only render as much of the timeline as there is available RAM. Subtract a rough average of 3-4 (or not even occasionally more) GB from that for the OS, and you get a better idea of what you’re in fact left with in Motion.
-
Sounds like you might want to look into using Auditions also, instead of replacing thing entirely. Pretty much exactly what they are for, too.
-
I see no reason nor advantage in using multicam for a single clip.