Did 1.0.4 Kill Magic Bullet?

[Michael Hadley]

I’m in the middle of two project so I’m going to wait until they are out the door but I would really appreciate hearing how the update with Looks goes for you.

Good luck. Fingers crossed.

[Jim Giberti]

[Oliver Peters] “IS it performing better? I haven’t noticed. No version of FCP X has performed any differently on my Mac Pro running 10.7.3. Ignoring plug-in performance, the general app performance has always been fine, though I find the UI itself is inherently slow, because of all the built-in UI animation.”

How would I know, I’m the guy that hasn’t updated .

I’m just going by a.) Apple’s “performance” update and b.) The consensus here that it’s a lot faster.

Now I’m disappointed and I haven’t even tried it.

[John Godwin]

Well, response is much faster here, on a Mac pro, iMac and MacBook Pro. 3rd party playback unrendered is much more stuttery. But the tradeoff is worth it, in overall response.

Best,
John

[Jim Giberti]

Are you seeing any faster render times John?
It would help if all 3rd party FX need rendering to view now.

[John Godwin]

Render times seem longer, at least with Magic Bullet Looks and ToneGrade. I haven’t done any timed tests so everything is pretty subjective. Playback of either of those unrendered is rough. I think the native filters may be a little faster than before. I do find that leaving background render on with a 3 second delay works out well, for me. By the time I reach a stopping point the rendering has usually caught up, or nearly, so that isn’t too big a deal.

And this is mostly on my Mac Pro that has never been the stable system others seem to have. FCP 7 usually crashed several times a day on it. FCPX has only crashed a very few times, period.

I do find that after a couple of hours editing it helps to exit and restart FCPX and everything zips along more smoothly. Since that whole process takes less than a minute it’s worth it.

Best,
John

[Jim Giberti]

Yeah, you’ve got to quit the program in order to clear RAM as well as continually delete renders in order to keep it working well.

I always keep Activity Monitor open to monitor RAM usage when I’m doing a lot of intensive work that chokes it fast.

[Jorgen Gustafson]

For me it works all fine now – latest FCPX and the brand new MB update. I’m sure Looks now render faster than before – nice surprice. Mojo is still a slow muddy hog though…but maybe it was no update for Mojo in this package from MB. Looks is my main tool for style fixing, so I’m plesed. Red Giant is obviosly a very fast and dedikated company – I wish other (for example Apogee) had this serious speed with updates :-D.

[Jim Giberti]

[Jorgen Gustafson] ” I’m sure Looks now render faster than before – nice surprice. “

So Jorgen says the new MB fix actually renders faster with 1.0.4.

OIt would be great to have some kind of confirmation of this as I’m staying clear of the update for the very reason that I’m hearing it makes MB sluggish.

Obviously it would be great to have improved performance of both programs but I’m OK with 1.0.3 right now if it keeps MB from becoming a dog.

[Michael Hadley]

keep the updates on the updates coming. Seems like some see better performance with MB Looks and .0.4 and some seeing worse.

Thanks.