Time to move AJA & CC installs to Mavericks?

[Shane Ross]

Well, the big question I have is…why upgrade the OS? What will it gain for you? Do your machines work fine on the OS they are running? All the apps work? Then why upgrade?

Personally, I don’t upgrade unless I have to. If one of my software apps requires it, for example. Otherwise I leave well enough alone. Just because Apple releases a new OS, doesn’t mean you need to update to it. I have an older 2008 MacPro…I’m keeping it on Mountain Lion on one partition, and Lion on another…keeping it on the OS versions that my software that I use to make a living works best with.

So my recommendation is to stick with what works.

Shane
Little Frog Post
Read my blog, Little Frog in High Def

[Andy Edwards]

[Shane Ross] “What will it gain for you? Do your machines work fine on the OS they are running? All the apps work? Then why upgrade?
“

Better interaction with our big iron SAN. Adobe changed the way file permissions are treated under the hood of the last 2 OS upgrades. So hopefully it would solve some of the issues editors in the building are seeing with file permissions and how Premiere interacts with the OS. Do the Aps currently work, yes with some daily headaches that need work arounds. There are some inconsistent issues when exporting to the SAN from AFX or PPro, so an upgrade might be worth the change if it solves the permissions issues. Of course I’ll need a week or two of testing various department work flows to see if anything else crops up with the upgrades OS. This is why I’m asking to see what other editors are seeing with making the move to Mavericks, so I’ll be able to check on those issues. I’m not making this jump to keep up with the Jones’s…. some of our bays are still running FCP 6.06 because it just works for that departments workflow. So I definitely get the mantra if it works why change.

With the latest OS being out for four months, I figure we would be hearing a giant stay away till it’s fixed or tons of feed back that it works great. I’m not seeing or hearing either and just wanted to toss this out to get a better feel of what is or isn’t working.

Are you running Adobe CC on your Mountain Lion install? Or still running CS6? Are you using AJA hardware on your Mountain Lion install?

Andy Edwards

[Chris Borjis]

[Shane Ross] “Personally, I don’t upgrade unless I have to. If one of my software apps requires it, for example. Otherwise I leave well enough alone.”

I’ve been doing it this way for years, keeps me out of trouble for sure.

I never understood the need to upgrade for the sake of it. As it usually causes
unnecessarily problems I don’t need.

There have been posts of various issues once someone installed Mavericks
that was fine just before they did. Do a search here and at adobe forums
to get specifics.

I didn’t even upgrade to Mountain Lion until CC mac required it for pro res.

Safe to assume I won’t be using Mavericks until we get the Dysan Canister macs.

[Shane Ross]

[Andy Edwards] ”
Are you running Adobe CC on your Mountain Lion install? Or still running CS6? Are you using AJA hardware on your Mountain Lion install?”

I’m running Avid Symphony 7.0.3, FCP 7, and I used the trial of Adobe CC pretty hard for a month…all under Mountain Lion, and all with the AJA IoXT connected. I’m sticking with CS6 because the subscription model of Adobe CC bothers the crap out of me.

Shane
Little Frog Post
Read my blog, Little Frog in High Def

[Peter Garaway]

To my knowledge there are no 10.9 specific bugs AJA/Premiere Pro bugs.

If you encounter any change in behavior please reach out to AJA support and/or file a bug report here

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&product=12

Best,

Peter Garaway
Adobe
Premiere Pro

[Andy Edwards]

Thanks for the official reply Peter. I’m setting up a test system before a full deployment to all our bays.

Andy Edwards