Gareth Randall
Forum Replies Created
-
Hi Peter,
I would probably not bother having to switch from a single text layer to three layers. Build it as three layers from the start, and slant all the columns back in Z-space at the same time by adjusting the X rotation value of the parent group.
Making the 6 change to 7 is just a matter of keyframe placement:
Kudos to Anders for his heads-up about the “Progressive” keyframe repeat option. I wasn’t aware of that before 🙂
-
How are you animating it? With keyframes or behaviours? It’s a 2-minute job using keyframes, you’re just animating the Y position :
The keyframe pattern looks like this:
-
Split the clip at the frame where you want the retiming to start and then apply the retiming to just that section.
-
1000 names in 15 minutes means about 0.9 seconds per name. Is that really long enough to bring them on dynamically while still having time to read them? Or is the idea that the names aren’t supposed to be read individually?
And when you say “dynamically”, do you mean in lots of different, possibly random ways that will maintain an audience’s interest in watching 15 minutes of names?
In any event, as Zak has said, there isn’t a plugin that will do this. Motion can import text files for the purpose of creating credit rolls, though.
-
If you’re looking for some kind of quantifiable response – “A MacBook Pro with this spec should be able do 15 filters on 10 layers in real-time” – then I don’t think you’re going to get it. It doesn’t really work like that, since there are so many variables involved.
-
[dan gala] “what should my system be capable of handling, how many filters ect.”
That’s not really a useful way of looking at it. The only aspect of Motion’s capabilities that is directly limited by your hardware is its real-time functionality. Motion on my ancient MacBook Pro can do all the things Motion on a brand-new Mac Pro can do, it’s just that mine will run out of real-time puff much faster. -
If I’ve interpreted your meaning correctly, there are two ways of achieving what you want. Either you make the emitter a 2D layer (which means it won’t be affected by any camera movement), or you turn on the “face camera” attribute in the emitter particle controls.
-
Surely by “the red line thing” Andrew is referring to the way Motion indicates motion paths?
Andrew, just out of interest, did you not think to try keyframing the camera’s position and rotation attributes in the Inspector?
-
Hi Leng,
Those logs are all Greek to us too! They are of no practical use on a forum like this, they’re only decipherable by Apple programmers.
First off – your Mac definitely supports the minimum spec, yes? You’re not (for example) trying to run Motion on a pre-2009 MacBook using Intel integrated graphics?
If Motion is habitually crashing on startup, then it’s possible that it’s the ProKit 6.0.1 update that’s causing it. Even though 6.0.1 doesn’t contain any Motion-specific stuff, many people have reported major problems with Final Cut Studio apps after installing it (and many others haven’t).
So I guess the first step, if you do have ProKit 6.0.1, is to follow the instructions here.
If you don’t have it, or you’ve reverted unsuccessfully to a previous ProKit version, then you need to completely uninstall Motion (using FCS Remover) and reinstall. If *that* still doesn’t fix it, you might want to try a complete ground-up reinstallation of OS X.
-
Oops, I should have been more specific 😉
No, it doesn’t do it all the time, fortunately. It’s a bug that I’ve experienced a few times, but not often. Ditto the one where it takes minutes to render each frame during export, for no apparent reason because it’s not doing anything complicated.
A related bug is detailed in a post I made a day or two back, where Best mode ends up looking terrible and Normal looks fine. The really weird (and annoying) thing is that only one short part of my project is affected by that bug; if I render the whole movie at Best it all comes out looking like Best apart from that one 2- or 3-second segment in the middle.