[Alan Okey]

[Rob Grauert] “I sort of remember someone saying, “Motion is RAM intensive.””

Motion is RAM intensive for working within the app, but rendering speed it is GPU-bound. Looks like the ATI Radeon HD 3870 is the current king of the hill for Motion:

https://www.barefeats.com/harper16.html

[Alan Okey]

Sounds like maybe it wasn’t 24pA, but regular 24p. That might explain the failure of FCP to “remove advanced pulldown,” because perhaps it wasn’t advanced pulldown.

[Alan Okey]

Thanks for the tips. I’m already on board with optimizing stills before import, but it’s good to know about rendering workflow.

I imported the sequence of the project I finished in FCP and checked it out in Motion. It was, frankly, a mess. I suspect that Motion doesn’t like nested sequences. The project was huge, and in some cases the keyframes for certain motion parameters were totally out of whack. For example, one group that occurs about a minute into the piece had its motion keyframes right at the beginning. Crossfades didn’t survive the translation, as there were no opacity keyframes. Also, in some places a clip or still was split over two different groups, seemingly arbitrarily.

I’m guessing that it would be much better to start a project in Motion by importing the finished audio track and then building everything on top of it within the application rather than trying to import FCP sequences.

[Alan Okey]

You are correct – Final Cut Studio does not come with Flash encoding out of the box. You need to purchase a third party application to encode Flash video, whether it’s Sorenson Squeeze, Telestream Episode or Adobe Flash (with Flash Video Encoder).

Here’s a link to a relatively inexpensive encoder you might try:

https://www.macvide.com/Macvide_VideoFlash_Converter/

[Alan Okey]

Is there something about “file>export>Quicktime Movie” or “file>export>Export using Quicktime Conversion” that eludes you?

[Alan Okey]

[Steve Hansen] “Also, if there is another camera similar in features and price that you recommend as well, I’d love t o hear about it “

The Sony CineAlta PMW-EX1 is an excellent camera as well. It works seamlessly with Final Cut Pro and is capable of recording beautiful images.

https://www.videomaker.com/article/13683/

[Alan Okey]

[Sean ONeil] “If that’s true, then it’s a bug in Color. “

It’s not a bug, and it’s not Color’s fault. It’s Apple’s driver optimization. Apple writes its own drivers for both ATI and nVidia cards. For whatever reason, apps that leverage Core Image run faster on ATI hardware.

https://barefeats.com/harper16.html

[Alan Okey]

The X1900 XT is notorious for this, simply search the Mac Pro forum on the Apple Discussions pages on Apple’s website. You’ll find plenty of complaints about this card and how it eventually cooks itself over time. Pretty poor thermal management design by ATI.

[Alan Okey]

D’OH! I just reread the OP’s post and he is indeed using a Mac Pro, not a G5. So much for that theory…

[Alan Okey]

[Bob Zelin] “What kind of mixer are you using ? “

Bob,

I think he’s talking about the software mixer panel tool in FCP. It’s conceivable that his G5 doesn’t have enough CPU grunt to simultaneously decode ProRes and perform real-time audio mixing during playback. In other words, it might be a question of CPU capacity rather than disk badwidth. After all, the G5 isn’t supposed to be fast enough to encode ProRes during live video capture, so it might be related…