Problems Rendering in Motion 5

Hi

This question has been posted a few times but with no satisfactory answer. I'm hoping we can finally get to the bottom of it. Why doesn't Motion 5 render properly? Below is what I and a lot of other users have noticed - unacceptable 'banding' in gradients. On the right is a simple gradient rendered in ProRes from Motion, pretty obvious banding [there are quite a few other examples already posted]. On the left is the same project recorded with snapzPro using proRes. No banding at all. There is also a colour change in the motion render, the snapzPro version is exactly what I see in Motion. Once it is rendered the colours are darker and there is that awful banding. Looks exactly like a Motion 4 8-bit render. Trouble is you could change that to 32 bit floating point in Motion 4 and fix it. Motion 5 is supposed to do that by default. Sure doesn't look like it! Threads posing this question just seem to fade out, as if the posters have just given up on Motion 5 and gone back to 4. I might have to do that to. This is completely useless. I find it hard to believe this is not THE hot discussion topic, what on earth is going on in Motion? The codec itself is obviously not the problem it is something Motion is doing or not doing. Is this something that only affects a few users or have people simply not noticed? I would like to find out. If it is just a few of us then the computer may be faulty. If it affects everyone then it is the software. I love the software but I cannot use the output! Help, please?

User uploaded file

Posted on Oct 15, 2011 6:07 AM

Reply
19 replies

Oct 16, 2011 5:59 AM in response to Balaclava_man

I just did a series of tests, and yep, there's some banding. Not sure what the fix is, but will be investigaing it, and contacting Mark Spencer about it, see if he has any suggestions. I tried exporting as ProRes HQ, premultiplied and now, ProRes 4x4, I only get different variations of banding. Very odd. Also, fill out the feedback page, let Apple know, they actually read and track those.

http://www.apple.com/feedback/motion.html

Oct 16, 2011 7:43 PM in response to BenB

I, too, have had serious problems with gradient banding while exporting projects, and it does not seem to matter what the render settings are. I find that with the project still in Motion 5 (prior to export), the image looks perfect until you hit "play", then you can see the banding. Hit "stop" and the image looks perfect again. It's weird. And unfortunate. Thanks for contacting Mark Spencer; he seems to be the one --or one of the ones-- who would know what to do in this situation. I look forward to his response.

Feb 2, 2012 3:11 AM in response to Cheesenightmare

Sounds promising and I will definitely try that but I am not sure you are right. I can do a screen capture with Snapz pro using the ProRes codec and it comes out perfectly. Exactly as it looks on screen in Motion. So the codec itself can't be the issue. Its something to do with the way motion itself renders. This sounds like another work around not a fix. But if it works its a start. Thanks a lot.

Feb 2, 2012 7:04 AM in response to Cheesenightmare

I have a fairly complicated Motion 5 project at 30fps that exported out of Motion with quite a bit of unwanted gradient banding. I took your suggestion and chose "Send to Compressor" and used the Quicktime Animation preset. Well, the exported video looks phenomenal (NO gradient banding AT ALL) --but Compressor changed it to 26.62fps. I opened it up in Quicktime and did a test export as an H.264 file at 29.97 fps, but the result was still 26.62fps and some of the gradient banding returned.


If Compressor would have left my frame rate alone the export would have been perfect. It LOOKED amazing! But it cannot be used of that frame rate. Have you experienced this at all?


NOTE: Is it possible that the new Motion update changed my Project Properties from 29.97fps to 30fps, which then somehow screwed up the frame rate when I sent it to Compressor? To tell you the truth, I am certain that I originally created the project at 29.97fps, since I am always using either 29.97 or 59.94fps in my workflow; however, post-update the project shows up clearly as 30fps in the Project Properties window. This is weird.

Feb 2, 2012 1:53 PM in response to Cheesenightmare

I've been working with someone on another forum and while we do not (yet) know why Compressor changed the frame rate, he did offer a solution:


Duplicate the "Animation" preset in Compressor and change the frame rate from 100% of original to your specific project frame rate (29.97 in my case), then make sure to set it to the "best" quality --it is lower by default. I tried this and it worked for me. Just know (as I recently learned) that the "Animation" codec requires a lot of horsepower to play --again, I don't know why-- so I used Quicktime to convert it to ProRes 422 HQ, which imported into and played just fine in Final Cut Pro X (use ProRes 4444 if you need to preserve any transparency).


I hope it helps! (If so, I don't deserve any credit. Someone else helped me through all of this)

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Problems Rendering in Motion 5

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.