Motion3 Chronic Dysfunction

[Nigel Beaumont]

Sorry to be late to the party….I can’t offer a solution, but just wanted to say there’s nothing unusual about still working with FCS2.(I managed to edit 25 Broadcast TV programs on it last year) Many people prefer to give any new upgrade a bit of time to settle, to be sure any bugs are sorted before they commit and the jury seemed to be out for a while with Snow Leopard and FCS3. Two colleagues who have upgraded have had no issues at all but that wasn’t everyone’s experience.
Although I could upgrade, I do a lot of work for my church and they run a G5 Mac that can’t use FCS3, so I’ve stayed with FCS2 for easy project exchange.
I was an infrequent user of Motion last year, but never had it hang like that. Advice on the Cow seems to be make sure any re-install is clean though – get EVERYTHING off before putting anything back on. Not fun(!) but the pain will be worth it if Motion returns properly.

Nigel Beaumont

MBP 2.53 FCS 2 FCP 6.0.6, Aja IO, some black cables, shiny firewire drives

“Ofcourse it’ll be finished in time for tx”

[Taliesn Jones]

Thank you , Nigel , for that seasoned advise. Best response yet. Certainly more informative than the * Just upgrade and then ask me again* one size fits all response I initially received from Kadner.
And , yes , doing a clean & full reinstall of the entire FCStudio 2 Suite is a solid recommendation that I will take in good faith. I may yet wait until the next FCStudio incarnation or when the next paying job involving video editing justifies the expense.
Short of that I still make far more money using *Motion* in concert with AE CS4 which is more pressing for next in line for an upgrade to CS5.