![]() ![]() (You may occasionally get a dialog saying the template was changed by another app, or something like that - Ignore.) You don't even have to restart Motion, when you go back into it, you will find in the Project Inspector that the framerate and duration has been updated. Do not change any of the tags or their location (line and spacing formatting) in the file. ![]() ![]() Most templates are 10 seconds long, so 30 x 10 = 300 frames: ![]() Look up another couple of lines for duration, example:Īnd change the duration to the #of seconds (project length) times the new frame rate. So it's hard to tell if it's just a tool to could occasionally fix a problem or if it can be integrated as the final part of any workflow to speed up the process without sacrificing the final quality.Īny opinion or feedback would be appreciated.Ĭhange the 60 to 30 (or any other frame rate that Motion supports). MotionVFX have amazing products but they don't communicate much about them and I can't seem to find anything relevant about this converter online. Of course, I could give it a try on my own, and I will but even though it would work with a handful of test cases, I can't be positive it always will and I don't wan't to spend dozens of hours on projects to see that I have to do re-do them all over again eventually because the conversion was not accurate after all. But it seems way too good and über convenient to be true. I could work comfortably a lower FPS and then, when it's finished, convert at a higher one that would smooth things out as a final touch. If this can work, it would be a game changer in terms of workflow (and horsepower). MotionVFX has a frame rate converter for Apple Motion called MFPSConverter.ĭo you think I could work a whole project at a low(er) frame rate and when the project is over, increase the FPS at once without getting any artifacts (issues with tweens, keyframes, animation curves, transitions, etc.)? I know that.īut still, AE is getting there eventually, Motion isn't.Īnd even at 30 FPS, which is a standard online, I only gain a few frames per seconds, but it's not much better in terms of playback anyway. All I can see is a slow motion/lagging animation which prevents me from working efficiently. I will gain some FPS but just a handful, really. Pre-caching in RAM (command + R) doesn't seem to help much. With Motion, when the sequence is heavy, whatever I do in order to optimize the preview, it won't read it at its nominal speed. I will always be able to preview my sequence as it was intended. The reason is that whatever I throw to AE, it might have to pre-cache in RAM for a while but eventually, it will read in real time my sequence on the timeline just fine. However, something bugs me a lot: With small to medium projects, Motion previews faster and cleaner than AE, which is cool, but past a certain threshold, on heavy duty projects with which both are having a hard time, AE has a clear edge. So far I used to use After Effects for my motion graphic projects. Not the fastest setup out there but it's not the slowest neither. The Graphic Card is a Radeon Pro Vega 56 8 Go. I have an iMac Pro 3,2 GHz Intel Xeon W 8 cores and 64Gb of RAM. Enligh is not my native language so bare with me please. ![]()
0 Comments
Leave a Reply. |