[Otto Mores]

Oh, sure. I can work around it.

Just trying to figure out what the heck is going on. As I wrote earlier, my Mac is exhibiting some odd behavior and that may be part of the problem.

Today I was suspicious of some kind of permissions issue or different user accounts that might be confusing Motion but I never figured it out. Probably a dead end.

Hey, thanks for your interest.

[Otto Mores]

I’m having exactly the same problem. See this thread:

https://forums.creativecow.net/thread/170/875260

Motion is suddenly very confused. It’s probably something simple. If you figure it out, let me know.

Thanks!

[Otto Mores]

An odd coincidence. Looks exactly like the same problem only I was trying to use a different codec.

Thanks for the hint. It does seem that Motion has become confused and may be assigning a codec that is off by one menu choice. Only I can’t get it to render H.264 no matter what I choose.

And now I see that it is confused about frame rates, too. A few of the built-in Apple render options work. I just can’t change the settings any more.

If anybody has a fix, please chime in.

Except upgrading. I’m in the middle of a project so that isn’t much help. 😉

[Otto Mores]

Thanks for your reply, Bret.

Good questions. The most obvious being why Motion 4. The answer is that it requires OSX 10. My fairly new MacBook Pro had a problem upgrading, which forced me to restore the older system.

The other reason is that I rarely use Motion. It was just appropriate for a small job. And now that I started the project in Motion, I need to finish it.

Of course you are right about writing to a pro format but I’m sending many small updates to a client and it’s more convenient to send tiny files until the final output is rendered.

Mostly, I can’t upgrade the system until I get this project off and I became curious.

I’ve looked all over the place and I can’t see the problem. Doing a Spotlight search for H.264 returns nothing useful. A search for DVCPRO, however, returns scads of component looking doodads. Either I don’t know what I’m looking for or it’s not there.

I can work around it. Just thought somebody else might have bumped into this and knew what would cause Motion, QuickTime, Compressor or whatever to forget how to write only H.264.

Thanks!