Robin S. kurz
Forum Replies Created
-
[Bob Woodhead] “I’ve always dismissed the need to keep a copy of cards, as I’ve always thought of that as redundant to the imported ProRes “
I make ARCHIVES of every single card first thing and store them on an extra drive and import from them. There is no such thing as too much redundancy. Especially IF in fact your library goes south and you, like me, use the brilliant backups from FCP X itself, then you’d be potentially screwed without the archives (i.e. original media) to re-import from. It’s by far the easiest, fastest and most of all smallest form of backing FCP X libraries up. Backing up transcoded media takes up exponentially more space and there’s really no logical reason (for me) to include them, since I have the original files from which I can regenerate them again at any time if needed.
As far as the glitch is concerned: I would suspect the transcode may have a corrupt frame also. Though there’s no way of knowing whether that happened during the transcode or if it in fact was already in the original file without the actual file to check. I might try re-exporting it (even to a different codec) to see what happens.
*******************
German language FCP X training: https://vimeo.com/ondemand/fcpxtraining
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Sure. You can treat titles just like any other clip.
*******************
German language FCP X training: https://vimeo.com/ondemand/fcpxtraining
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
[Bret Williams] “No need for a gap clip.”
Oddly, I only wrote that because it was in fact showing the same effect on the OUT also. But now it’s not… hmmm… must have gotten something confused. Seems you’re right. My bad… and that much better. 🙂
Good point about the motion blur also, yes.
*******************
German language FCP X training: https://vimeo.com/ondemand/fcpxtraining
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Actually it has 4 and I admit I hadn’t used the others. And yes, I’m seeing the effect described with all but the Slide In (with just a single connected clip).
This has to do with the way that transitions are constructed (in Motion). They do whatever transition you design from an “A” layer to a “B” layer. So if you’re using one of the ones that needs an “A” to animate what’s described (Push and Swap), but it’s not provided with an actual “A” layer, rather just coming from nothing, then FCP uses the next possible layer which is whatever is below it.
But then, in the specific case of the SLIDE, if you’re in fact coming from nowhere, then using both PUSH or SWAP doesn’t make any sense anyway. Everything else you can easily do with the SLIDE IN/OUT.
[Brett Sherman] “I’ve gotten annoyed at this also. If it’s a push off, then I animate Position keyframes to accomplish the same thing.”
Why would you? Simply add a gap clip as the “B” clip, set it to OUT and you’re good.
So even though it may seem so, it’s not a bug. It’s actually pretty logical i.e. simply a different approach. Something I’d say we should be used to with X by now. 😉
It’s also the same thing that makes “adjustments layers” possible btw, so I sure as heck don’t hope they change it (without a replacement)! 🙂
*******************
German language FCP X training: https://vimeo.com/ondemand/fcpxtraining
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Something you’ll want to ask in the BlackMagic forums.
*******************
https://vimeo.com/ondemand/fcpxtrainingSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Whereby, as described above, you have to clearly distinguish between EFFECT and TRANSITION. You write effect, but then describe the use of a transition.
*******************
https://vimeo.com/ondemand/fcpxtrainingSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Is this one of the DEFAULT transitions or a CUSTOM one? Because a) that obviously shouldn’t happen and b) isn’t in fact happening here with your example “Slide” transition. It CAN happen with (some) titles though, due to the way they are (sometimes, not always) constructed in Motion. Meaning any effect you apply to a title will carry through to the layers below it in an “adjustment layer” type fashion.
I’m guessing it’s a custom transition? In which case I would suspect it was simply put together incorrectly in Motion. A screenshot may also bring more clarity, if it’s in fact a default transition and the info WHICH it in fact is to be able to reproduce (or not).
*******************
https://vimeo.com/ondemand/fcpxtrainingSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
[Gareth Randall] “FCPX’s framerate conversion from 23.98 to 25fps will *not* do any frame interpolation or blending, nor will it just repeat one frame every second?”
Yes.
[Gareth Randall] “Can FCPX cope with that and allow me to manipulate each of the audio channels individually?”
Yes.
*******************
https://vimeo.com/ondemand/fcpxtrainingSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
You need to export them using the relevant “as Roles” settings in the settings pane.
*******************
https://vimeo.com/ondemand/fcpxtrainingSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Simply import and use the Retime menu to set to “Automatic Speed”, yes.
*******************
https://vimeo.com/ondemand/fcpxtrainingSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.