CS 6.02 on 10.6.8 anyone?

[Vince Becquiot]

Hi Chris,

No problems here, issues are most likely a third party cards if you have one installed (drivers).

Of course, there are still different hardware combinations. MacPros 2010 here.

Vince Becquiot

Indigo Live
San Francisco – Bay Area

[Phil Balsdon]

Problems since updating to CS 6.02. Initially problems with playing or stopping a sequence in the timeline at all.
Deleted preferences, cache, checked NVidia and Blackmagic drivers (which were all up to date) etc. etc.

Now there is a few frames delay stopping the timeline playing, (very annoying) and occasionally hen opening a project sequences in the timeline won’t respond to play (keyboard or play arrow). Solution is to close the all the sequences and re-open them.

I had none of these problems prior to the upgrade.

I’m not the only one with this problem; https://forums.creativecow.net/thread/3/930228

Cinematographer, Steadicam Operator, Final Cut Pro Post Production.
https://philming.com.au
https://www.steadi-onfilms.com.au/

[Vince Becquiot]

Hi Phil,

Was this a clean install? If not, that could be an issue. We always do a clean install using Carbon Copy Cloner and a USB drive, now that install DVDs are hard to find.

Also, BlackMagic… Editing became fun again once we got rid of our Decklinks.

Vince Becquiot

Indigo Live
San Francisco – Bay Area

[Chris Borjis]

[Vince Becquiot] “Also, BlackMagic… Editing became fun again once we got rid of our Decklinks.”

I’ve had really great luck with an old multibridge-extreme and premiere 6.01
with a quadro 4k.

My other machine had random lockups and output issues, ended up being
hardware issues on a Decklink studio and quadro 4k.

[Phil Balsdon]

I really don’t think a clean install should be necessary for a CS6 update only. With the number of updates that come out I’d never get time to do any work between clean re-installs, especially without discs or dmg.s on another drive.

I do have a Carbon Copy Clone of the system drive from just prior to the update though.

The problem seems to be erratic though, for Walter Bascardi it fixed problems. Over on the Adobe support forum it seems to have created problems for Windows users, especially those with more RAM on their machines.

Cinematographer, Steadicam Operator, Final Cut Pro Post Production.
https://philming.com.au
https://www.steadi-onfilms.com.au/

[Vince Becquiot]

Hi Phil,

Sorry, understood your post as a Mountain Lion update. No need for a clean install of an Adobe update.

Have you tried tried to just run your external display through DVI on a new sequence instead of BM, to see if problems go away? Are you running SDI, HDMI out?

Vince Becquiot

Indigo Live
San Francisco – Bay Area

[Phil Balsdon]

I’ve tried without the BMD out, same probs. Spent a few hours yesterday trying all sorts of options to isolate the issue.

Three possible solutions for me.
1) Put up with it and wait for the next update.
2) Go back to FCP7 which is working fine.
3) Re-instal the old system and CS6.01 (which was also working fine) from the back up drive.

Could also try doing a clean system install upgrade to Mountain Lion, but this going to create hassles with a whole load of archived material .mov files from a Firestore drive when Apple broke them with Quicktime and iTunes upgrades. (7 system re-installs last year due to this).

If I took my car in for a scheduled service and they broke it in Australia I’d be able to appeal to the Motor Traders Authority. I’m trying to run business here.

Cinematographer, Steadicam Operator, Final Cut Pro Post Production.
https://philming.com.au
https://www.steadi-onfilms.com.au/

[Phil Balsdon]

I didn’t realise that uninstalling Premiere Pro CS6.02 and then re-installing from Creative Cloud would start me off with v CS6 again.

Having done this and then manually downloading and installing the CS6.01 update I now have a properly functioning Premiere Pro again.

Cinematographer, Steadicam Operator, Final Cut Pro Post Production.
https://philming.com.au
https://www.steadi-onfilms.com.au/

[Chris Borjis]

thanks for the headsup.

I’ll not be updating to 6.02