Motion 3 Sluggish

Motion 3 has been working fine for me for a long time, but suddenly everything is just unbearably slow. I can not even preview in the canvas anymore. Frames will suddenly jump and the playback is herky jerky. Or it will take sometimes 10 seconds to advance 1 frame at a time during playback.
Does anyone know what I could do about this?

Have you tried rebooting?
-DH

Similar Messages

Motion sluggish and sometimes unresponsive

Let me preface this post by saying that I have taken an apple certified class in motion and have supposedly learned the tricks to optimizing how the program runs.
I am having problems with the sluggishness of motion. I have been working on a project that consists of several layers of titles that glow up on the screen then flyoff in a matter of about 2 seconds each. there is no background layer but the total of layers is about 11. the total time of the entire thing is 18 seconds. While I was working on this, I would uncheck many of the layers that I didn't need to view try to improve the performance and I would set my in and out around about 5 or 8 seconds at a time to also try to improve performance. Motion was still very difficult to work with. Render times were upwards of 20 minutes each and when I tried to play the ram preview I had created, it was still sluggish, making it difficult to actually see how my changes were affecting the project. Exporting would be the only way I could actually view it in real time but tht would take about 45 minutes.
I didn't have any other programs open at the time. I have 4 gigs of Ram which should be enough right?
It took me all day to finish this 18 second piece when I honestly could have done it right in final cut with Boris 3d titles and a few aefects added to the end of each layer and it would have taken a lot less time. Is there something I'm doing wrong? I am rapidly losing faith in this program as it seems to take forever to do the simplest animations.
PLEASE HELP!!!!!
PS- I am working with Motion3

What's your video card?
Sometimes I notice a major boost in performance by clearing my RAM preview from memory. Mark->RAM Preview->Clear RAM Preview. Sometimes I get as much as 3G back and it runs pretty well.
Make sure you remove your motion blur effect if that's on. That's a major killer of course.
There ARE some effects that if applied to the wrong thing cause Motion to drag. What other effects are you using?

Motion sluggish, not responding

Hello. I'm at a total loss. I've been trying to work on the same simple shot for the past two days and have gotten nowhere. I import the files I'm working with -- one still (png) and six video clips (all pro res 4444) -- with no problem. Then I apply a Match Move to all six clips. I can apply the move to the first two clips without a problem, but as soon as try more than that Motion become very sluggish and eventually reaches a point of complete non-responsiveness. I have to Force Quit.
The other day I completed a far more complex shot with more clips (all pro res 4444) and that had numerous Match Moves without a problem. I don't know why this project is being so problematic. I even trashed it, re-made my pro-res movies and started over only to run into the same issue. Any thoughts or suggestions would be greatly appreciated as I need this finished by tomorrow. Thank you!

I don't have a clue as to what's causing this, but I'm guessing you're combining these four clips with the PNG, either by MatchMove, or Stabilize?
If that's the case, I'd do it in multiple passes, to get the job done. Do one pass, render it out to a quicktime, bring that into a new project, add more, if necessary, rinse/repeat...
Would that work?
Patrick

WORKAROUND! - Sluggish Motion V 4.0.1 on Mac Pro Nehalem 2.97 GHz 16 Vcore

Hi guys, like several people on this forum and others I been very frustrated with the performance of both Motion.app version 3 and now Motion.app V4 .0 .1 (latest update) on my 2009 Mac pro Nehalem 2.97 GHz 16 Vcore 12GB with the ATI Radeon 4870 graphics card.
I have two workarounds that may be of assistance in relieving this issue. They work for me however before I discuss what they I'd like to set the scene.
Like many of us, I have trawled this forum and many others including COW and so on mostly relying on those 10-12 (the dozen or so) excellent tips from people like Mark Spencer and others. This includes the usual things like turning off rendering options that make heavy use of CPU/GPU etc.
Caveat: I'd also like to note here that this performance sluggishness has absolutely nothing to do (and is completely unrelated to) I/O performance nor is it related to memory usage. The reason I say this is because during some testing and the normal practice I keep all a Motion.app cache files (autosave, cached files etc) out on a very fast PROAVIO EB8NS disk array with ATTO R380 HBA onto SAS paths where this box is capable of over 450 MB per second measured with Kona system test tool. Additionally I have 12 GB of memory on this Mac pro which I assigned 70% of it to be available to Motion.app V4. The sluggishness Motion.app V4 is not manifest itself through the usual items such as excessive virtual memory page in/out or swap in/out activity. In fact in this scenario I describe below in my system when nothing else is running the former is non-existent! Additionally I also want to know that Motion.app V4 in my scenario/situation/environment is definitely and certainly NOT impacted by insufficient I/O bandwidth..
However, like many people, who have the same or similar setup to myself, we experience severe delays the most basic Motion.app UI such as: selecting an item, scrubbing through the timeline, performing any kind of transform etc etc. Many of us trying to diagnose this problem (looking for any kind of diagnostics or messages etc) have noticed that with the exception of one single core, the remaining cores to do very little (idle or just barely moving) whilst the remaining single core is taking out at 100% constantly.
Many months ago whilst really bogged down with this problem trying to complete a project, I contacted Mark Spencer who politely explained that notion exploits the on-board graphics card (in my case the ATI Radeon HD 4870). After frustratingly trying to improve the performance of this and completely reinstalling Final Cut Suite in a different brand-new (at the time MacOS X 10.5.6), I found that there was little difference.
I am mentioning all this because, I know that a few colleagues have had a similar problem and have not found any satisfaction in looking at this despite many well-informed forum users who offer excellent advice.
At my wits end (currently), I took a few days to try and isolate what the problems may be caused by (what exacerbates this severely degraded performance). This user interface sludgy degradation is manifested through the UI also has the (spinning beach ball).
I isolated pieces in some of the Motion.app projects and started to ISOLATE (Control-I) what I thought were quite complex layers and individual objects but to no avail. I then resorted to completely deleting them with some improvement in performance (noticeably less sluggyness) however it still was not lightning fast as I expected considering it I was in draft mode, 720 p resolution, with lighting, shadows and reflections completely turned off in the view.
*Motion.app BEHAVIOURS*: after some hours and a great deal of trial and error (non-productive work time I might add) it occurred to me that some of the Motion.app behaviours in particular place in the layer with as few as five objects in the layer (behaviours such as "Motion.app path", "wriggle", "oscillate" and even good old trusted "throw" seem to be the culprits in this particular layer.
I will note well here at this point, but of course "camera layers" does seem to be affected at all with the basic movements such as Dolly, frame, sweep etc. I have some sets up to 4 or five cameras which seems not to bother Motion.app at all!
*OBJECT SELECTION (S):* yes this also seems to have some degrading impact on playout, scrubbing and so on. Interesting I thought.
Workarounds: here are a few things that I know that work to get around some problems of working where Motion.app is extremely SLUGGY in the user interface (UI). Perhaps someone has already noted these on a forum or posted on however I couldn't find them.
So my workflow/practice here is to do the following when I'm manipulating objects (placement, set up, applying filters, adjusting timeline, and so on):
+WORKAROUND #1+: *DISABLE the behaviours* in the layers where you are performing any object manipulation. In fact we have many objects in many layers where the topmost layer (a group of nested layers) contains any behaviours, I would suggest you disable those whilst you work on that particular layer.
It's a very simple stylus click to enable the BEHAVIOURS layers that you have been working on to see what the effect of those behaviours when you want to play them out in the player/canvas.
I have no idea why such trivial behaviours cause my very expensive Mac pro to nearly lock up whilst in Motion.app version 4 and also version 3. Anyway is definitely works on me.
+WORKAROUND #2+: *DESELECT ANY ITEM IN THE CANVAS* (in any view) when attempting to play out whilst in the canvas. Again I don't know why having one or more items (including the camera) insert would have such a drastic impact on the performance of Motion.app to play out what I think is a frivolous range, however this really works for me.
*How to measure the performance or how to monitor the performance/usage of the ATI Radeon HD 4870 graphics card from MacOS X?* I would like to know exactly what this is doing on my system when one of the CPU cores is pegged out in 100% servicing requests from Motion.app. I can't find utility (which am willing to pay for) that sees the ATI Radeon HD 4870 graphics card. One I thought would have is an application called atMonitor.app (http://www.atpurpose.com/atMonitor/) which seems to do a pretty good job on my uni body MacBook Pro and wife's Macbook Air.
It would seem that any of the utilities don't seem to see the ATI Radeon HD 4870 or if they do and they initiate commands to it that the ATI Radeon HD 4870 and doesn't respond or send any replies status information. (Beats me I'm not a technical person these days)
Summary: I would be very interested if other people who have a similar if not pretty near exact setup as myself have found these two suggestions useful. I have tried some of these Motion.app projects on my MacBook Pro uni-body and with some difference the MacBook Pro exhibits similar sluggyness to this Mac pro.
W
Hong Kong

Mark, I took your advice and reinstall Final Cut Suite Version 3 (including Motion.app version 4.0.1) onto a completely different and I'm used file system including a brand-new install of MacOS X snow leopard 10.6.1, which I believe is the most recent update.
To be clear, I have all the latest Pro Applications updates as well apply to this brand-new system.
So here is the *bad new*s.
*Using exactly the same hardware configuration as I described in this theme of woe, I launched Motion.app V4 .0 .1 and opened up several of the projects that I'm having trouble with that is issued.*
Simply, the symptoms and observation I described in this thread exists with a brand-new installation.
Anyway looks like I have a backup/another instance available Final Cut Pro in case my main production image has trouble.
Once again, as I described initially in this thread, I used the two workarounds to overcome the consistent and overwhelmingly an exaggerated 20 seconds lag on average interactions with Motion.app with the success that I'd described previously.
In another thread back in September 2009, a forum poster mentioned that he felt that the camera framing behaviours were the root of this problem. And to this end he advised converting these behaviours to keyframes using the command-K ("convert to keyframes") to overcome his misery.
This indeed does work very well. So this is the third workaround and I'm starting to use.
Further I have done some more hard comparisons with my 2009 MacBook pro uni-body 2.93 GHz with a standard arrangement of 4 MB of memory and the usual disk internally. *To my great surprise*, I found that the projects that I'm having a lot of trouble with were much more responsive not only with the camera framing behaviours (which I'm not particularly having any trouble with), but the layers that contains a simple transform behaviours such as "motion path", "wiggle", and so on did not seem to bother the Mac book pro.
I watched the CPU cores on the Mac book pro maybe go to 80% while the project was loading, and also whilst I gingerly navigated through the project although feeling a little sluggy was far less in orders of 10 to 20 seconds faster than this Mac pro Nehalem with all the bells and whistles on my earnings embedded within it.
Now I'm starting to wonder, as Andy pointed out, +maybe there is some trouble with the hardware in this system+. I really could not know how to determine if this is the case. However before I draw this conclusion finally, I noticed that there are a lot more people out there with the same consideration as I have that have this same problem. It's not narrowed down to those owners with the ATI Radeon HD 4870 graphics card, however these seem to be the bulk of the people who are trying to do things that are getting a fair amount of forum time (like me).
There certainly seems to be something of an issue as there are some symptom dumps for Motion.app but only one or 2 to over this period that seemed to be triggered by something on this machine. And like many on this forum I gave up reading dumps for a living back in the 1990s.
I would really like to know how I can diagnose this problem before I had to pack this Mac pro up and carted back to the local Apple care centre here in Hong Kong (which means I won't have it forever while, which means no income). Yes I can use my Mac book pro uni-body which is I might end up doing.
_Oh, and this little gem._ I find that if I invoke the "timeline pane/window" (command-7), that it can take up to 2 seconds to refresh the screen. It is amazingly slow and feel like there is definitely something wrong.
If I have a simple motion project by that I mean some simple plates some moving text and no real 3-D except for one little camera Motion.app V 4 seems to work quite okay.
The sets that I'm working in at about eight or nine cameras over the timeline and maybe three or four sets in the project. This is not the work I think especially when most of the moving here is a few objects wobbling around in 3-D space and quick camera moves using the camera framing behaviour.
In summary, having spent what seems to be 40 or 50 hours messing with this issue are not doing anything productive, I've come to the conclusion that there is definitely something wrong with this setup that I have. However having had no problem with that up until now (I know actually I had some problems back in May 2009 with it but it seemed that install a Final Cut Suite version 2 completely fixed it.
And I am totally surprised that my Mac book pro uni-body if pressed can do the job that I want.
Therefore Motion Forum users, I really don't know what else there is to do other than to poke around over time and eventually something will fix this because it is really very frustrating and like many of us on this forum I did endeavour to pay for/put capital funds into a system highly recommended by many that uses Apple production applications than I expected it would work.
By the way, I noticed when I use Nuke version 5 and Shake V 4.1 and even Maya PE, I don't have these issues but will concede that I doubt whether the use applications take advantage directly of the GPU arrangement in the graphics card like Motion.app does.
That's all I have.
Any other thoughts are most welcome.
W

Motion 4 is sluggish. No preferences to trash

Hello,
Probably somewhat of a beginner's question here but I need a little guidance. Motion's been very sluggish of late. Even straightforward operations with a few layers and no serious animation move along at a snail's pace, significantly slower than what I'm used to. I've never trashed the preferences so I thought it might be worth a try. But there was no com.apple.motionapp.plist file to be found. Is that unusual? Could it hiding out somewhere?
Jagr

I don't have that file only motionapp.plist and motionapp.LSSharedFileList.plist. There should be no problem deleting it also, but I would not empty the trash until you confirm Motion rebuilds it after relaunch. You can download preference manager from Digital Rebellion, it's free, and use it to delete your motion prefs.

Final Cut Pro is Sluggish

This is only my second post to forums, so again, forgive me if I break protocol.
I have Final Cut Pro 4.5. For the last three years it has been doing great. No real problems (a couple of the original audio filters crash FCP when I run them) but I've steered clear of them or used them in Soundtrack with no problem.
But that's not why I'm writing. About three weeks ago, I noticed that after about half an hour or so of editing in Final Cut, it would start to get sluggish. Even moving the scrubber would take a few seconds. I have 1G RAM and have had it since I got the computer three years ago. NO problems until just recently. When I restart FCP it runs fine again, until about another half hour in to it.
Let me know if any additional info is needed and I will do my best to supply it.
Thanks!
Brett

Thank you. I have tried to repair Permissions in Disk Utlity and did the whole Delete Preferences thing. Found those on the boards here before I posted. Sorry, I should have mentioned that. My bad. I will try the Applecare disks. Didn't know about those.
As for more details, it is FCP 4.5, I just loaded OS 10.4.10 But this strarted BEFORE the install. I bought Tiger because I thought it might help (and I wanted the New iLife). Quicktime version 7.2. I have three hard drives, Two are in the PowerMac Tower itself (came with them 250G each) and I have one External USB drive, but I use this one for archiving only, none of my footage is on it. Uh, let's see. My favortie color is blue, I like long walks in the park and my Apple MOTION doesn't work any more after my install of Tiger, but I already posted about that in the Motion discussion area.
I really can't think of much else. I will try the Applecare and report back what happened.

My trackpad is sluggish and jerky

I have a MacBook Pro (Summer 2010) with a dual-core 2.4Ghz processor. I am relatively new to Apple MacBooks (having been a Windows user for a number of years).
The transition from Windows to Apple is not that smooth or easy, I'd have to say!
What I am currently finding difficulty with is the trackpad. The experience is just not anywhere near as good as the most modest current Windows laptop.
What! I hear you say?
My experience is that the trackpad is sometimes sluggish, sometimes jerky, the cursor sometimes sticks momentarily.
This affects my experience of Lion - so that, for instance, scrolling down through a document, I find that the scrolling motion stops, a dialogue box opens asking me what to do with the current page (reload, etc - five or so options). The vertical scrollbar at the right of the screen appears, and I decide at this point to scroll down the document using the scroll bar (which I am sure is not what is intended for the Lion experience).
I run Windows 7 on Bootcamp - and the experience on Windows 7 is again sluggish, jerky, sometimes intermittent.
I am wondering if the trackpad is faulty, or if I need to reset it in some way.
The experience is as if the trackpad (or even the cursor) was had been smeared with (digital) jam (which it hasn't!).
Can anyone help? Or am I barking at the moon?

Hi there. This problem is talked about in at least four discussions on the apple support site, and none of them have a clear "silver bullet" answer.
However, my own experience with this problem (in my case, I'm lucky, it comes up more rarely) ... plus some of the responses, points to one thing at least:
The "jerky, sluggish trackpad" problem sometimes happens when the computer or its network activity is at a high pitch. Whether it just bogs down the CPU, or if instead it's creating some extra wifi interference or something (ok, that one does sound doubtful) who knows. But it's good to look at what kind of heavy network or CPU process might be going on during that "sluggish trackpad" time.
In my case, what triggered the jerky-trackpad symptom was when I had my Picasa application do a big sync which involved uploading 500 photos to google's servers. When that process ended, the trackpad was smooth as can be.
And what could it be in your case? One person with the problem said that they just got their computer. That brings to mind the fact that when your computer is newly installed, it needs to do a big indexing of your hard drive for the "spotlight" search tool in the far upper right of your Finder screen. When it's indexing, a moving dot appears in the middle of the magnifying-glass icon. OR... any other big process. Consider quitting all apps other than the finder... stopping a big download or upload or bit torrent (heavens no!) process.... thinking about oddball apps you have installed... etc.
Anyway, this is just one possibility for the trackpad problem... one that proved relevant in my case.
Eric

[Partially SOLVED] Wiimote buttons work, motion does not...

Followed all the tutorials on the wiki and the wiimote is recognized just fine... all the buttons seem to work (terminal shows output when I press dpad, A, B, +, -, home, 1 and 2) but I am not getting any motion out of moving it in the air. I have a wireless sensor bar and wmgui detects everything just fine... just not sure what I'm mising config-wise that is not allowing me to move the cursor around the screen as I move the wiimote through the air. Any and all help is appreciated!
Last edited by CPUnltd (2011-02-25 04:14:50)

seriously interested in getting this to work properly with the sensor bar! I just tested the dolphin-emu that is in the AUR repo... can confirm this build works with Need for Speed: Hot Pursuit! Renders In-game and menu graphics just fine, cinematics are a bit screwy, and sound seems fine... plays a little sluggish on my dual-core (2.1) AMD laptop w/ 8GB DDR3 (but that might be due to the rom being on a flash drive and not the internal SSD). Hope development is still continuing! Haven't tested any GameCube games yet... If anyone knows of a good tool to rip GC games with, I'd be more than happy to play with it.

Motion still fragile after installing it in a MacPro

OK so we've had the FCP update so where is the Motion update. As a Pro user of this software I am very unhappy with Motion as it stands at the moment. I sent a request to Apple as I cannot use Motions keyframes anymore. This has been since I bought the MacPro and the Intel chipset. I have a 3 Ghz MacPro with 6 Gig of ram, it should be a flying machine and it's far from it...the only programme to benefit from all this power is compresser. Well I for one rejoice in the forth comming Premiere Pro for Mac due in mid summer, appart from audio conforming, Premiere Pro was streets ahead of FCP.
Apple needs a kick in the butt to get all it's apps running properly with Intel as FCP, Motion, Studio Pro and Aperture all run sluggishly in my MacPro.

Is it possible to be more specific about the
problems? You mention you can't use keyframes
anymore. What happens when you try to use them?
If I try to use keyframes I get so far then the programme quits to the desktop, no warning.
You also mention that programs are slow (aside from
compressor). What is slow, and what are some examples
of slow-ness?
Slowness I compair to my other Macs, I have a 24" 2.16 Ghz Duo core Intel iMac (2GB ram & Nvidea 7600 GT card))which runs Aperture much faster than my MacPro ? Faster being...If I change a slider to adjust the highlights it works instantly with no delay on the MacPro I get a delay and sometimes the beach ball of death for a nano second.
My MacPro has 3Ghz Duo core, 6 GB ram, ATI Radion X1900 XT card running two 23" Apple HD displays...and in Aperture I get lesser real time responce than in my 24" iMac ???
FCP-5 I was under the impression that a lot of things turn real time the more processing power you give the programme, I can on occasions get red lines above disolves !
The main difference between my previous G5s and MacPro is the amount of beach balls I am now seing when doing simple tasks that are no problem to my previous G5.
What have you done to try and correct this? Have you
trashed preferences, reinstalled the software, tried
using a different user account, repaired persmission,
run a hardware test, or rebuilt the system?
I have repaired permissions, re-installed Motion, ran Tech tool deluxe.
We're here to help, but when your system is acting as
a the exception to the rule, it helps to have these
kinds of details.

Motion very Slow - help!

I've got a 106 frame clip with 2 layers of particles on it. It plays back very slowly and any time I try to change a parameter, I get 10-20seconds of the rainbow ball. I've read a number of threads about sluggish Motion and no matter what graphics card they are using, whoever answers the question always says their card is too slow. I've got 4.5 GB of RAM and an Radeon x850 card. I find it very hard to believe that this kind of hardware would result in such incredibly slow performance. I hope I'm doing something wrong in Motion (just started). Any ideas? Thank you.

Heya,
There are a number of things that can slow down a project by impacting either or both of the CPU and GPU. Let's talk about particle-related ones:
On the GPU side:
Are your particle elements too big? i.e. are the particles persisting/moving way off-screen? if you don't need them to live that long, try adjusting their Life value. The longer they live, the further they move, the larger that object gets, and Motion has to render the whole thing.
On the CPU side:
Particles are a simulation and their locations have to be calculated on the CPU. The more particles there are, the more work that has to be done. Other factors like simulation behaviors can add a lot to those calculations.
Also, the nature of simulations is that conditions are set up and the simulation runs from the beginning. So if you have a project with an emitter that starts at frame 1, when you make any changes at frame 300 Motion has to recalculate the simulation from frame 1. Only if those changes affect the particles, of course. But if you combine multiple emitters with many particles and behaviors, it can take a bit for Motion to re-figure it all.
Hope this helps

Long page edits are in slow motion

I am creating a long page with text and imbedded pictures. All my edits, placement of pictures, typing in general are in slow motion like the page is getting too large. I have 9 pictures and 3 short videos inserted and lots of text. Any idea why everything is so sluggish?

Too much stuff on the page. Nobody likes scrolling down long pages and 9 images and 3 videos is way too much.
If its sluggish in iWeb, how long will it take to download in the browser? One video with a good text description is enough per page.

Sluggish performance- hardware test?

How can I run a Hardware/performance test on my Mac pro 2008(early).
2X3 GHz Quad-Core Xeon.
I am getting very sluggish performance from Motion and Avid programs.
Honestly I saw very little performance increase compared to my old Quad PPC.
I installed 16 gigs RAM from OWC.
ATI Radeon HD 4870 and a eSATA video RAID.
By all accounts this machine should be cooking- but it doesn't.
I ran DW on the Boot drive- but I still have issues.
I have read so much praise for the 2008's as great machines- so I just don't understand why I get so many hang ups.

Clone your drive (SuperDuper) so you have an exact backup image.
Question: did you migrate your apps from G5? It sounds like you did.
The nice thing about SuperDuper is it skips all the clutter (cache, temp, logs etc) and optimizes folder and free space.
Are you using drives from G5 that have not been reformatted?
I'm sure there are other things to look for under the hood.

Motion 5 seriously needs updating.

Just completed a new project (had to abandon my previous project as some layers were not getting rendered) and discovered that a layer is also *not* rendering even though it appears in the Canvas on playback!
Maybe I'm doing something wrong here - anyone have an idea what migth be the cause?

It's a real shame though - Am wondering that Motion 5 got rushed to release in order to accompany Final Cut Pro X and the new Compressor.
The UI gets sluggish even by just having a ten minutes audio track imported and *no* motion graphics going on! This is hardly what you could call a Pro App. Just hope the update is well in progress

Slow Motion songs

I have a 3rd Generation Nano and for some reason my songs on the ipod have slowed down. I mean they sound like they are in slow motion, like they are being played on "Tape" and someone is holding the tape making the song sound funny.
Has anyone run in to this problem and if so is there a fix?
Thanks

One of two options: iTunes 7.x is a bit sluggish to say the leat. So, either turn OFF the option in Advanced > Importing to "Play songs while importing" or don't play the CD whiles its importaning.
Whats happening is that it imports the music off the CD faster than real time - many times faster. SO whiles its reading the data in for importing you are listening to the music in real time, which means the laser of the CD player has to jump back and forth on the CD to both IMPORT the music and PLAY the music.
Easy suggestion: Start importing the music, wait til it mananges to get at least one song fully imported, then goto your iTunes Library, find that newly imported song, then play the imported copy. Then let the import do its thing. WIth todays machines, the import takes only a few minutes. THis is more the fault of how a CD player works than iTunes.

Livetype 2 or Motion 2 projects, better to render & import o

Which gives best finished quality when working with a Motion 2 or Livetype 2 project into Final Cut Pro 5, should I prerender or just render in Final Cut Pro 5, or does it just not matter?
As always thanks for your time in reading and replying to my post,
Sebastian

should I prerender or just render in Final Cut Pro 5, or does it just not matter? < </div>
If you just import the project you can do a round-trip if you need to make changes. If you render and import you can't.< </div>
Personal preferences, mostly, I'd say. The benefits in performing the render are increased performance at the expense of possibly requiring additional rendering if you change your mind about something. But I rarely get stuff right the first few times and today's rendering capabilities/speed do not impede my editing. (Now, if Apple could just give us realtime alpha processing like any other respectable NLE...)
I love the ability to whiz back and forth between the apps and have the unrendered file immediately update back downstream. However, most of my projects contain dozens of LT and Motion clips these days. Not rendering the files creates terrible sluggishness on my system (allowing for possibly idiotic user error, of course).
What I would like to see is an automatic relinking to the newly rendered files instead of merely being able to auto-update the link to the project file. Umm, is that possible now and I've just missed it? AE can autolink to proxies, tremendously cool timesaver.
bogiesan

Motion 3 Sluggish

Similar Messages

Maybe you are looking for