Catalina issues?

[Eric Santiago]

So far my experiences is with my Graphics/Motion designer at dayjob.
Took a 2013 D700 and reformatted system.
With a fresh Catalina (not great experience with a prev upgrade) and Adobe CC 2020 its all been a decent ride.
We are waiting for our 2019s and will be converting all 2013s to the same setup.

[Jeremy Garchow]

We have a couple of machines that were new and cane with Catalina.

We also got new shared storage, and did a general infrastructure upgrade from 8Gb fiber to 10Gb Ethernet.

I’ve posted about this before, but Catalina has a wicked bug that ejects 10Gig shares under heavy load. This is new machines with factory fresh installs.

The good news is it’s fixable, the bad news is is that who knows if Apple will fix it permanently so we have to “monitor” the situation on any install and it requires disabling SIP and running a utility. It’s not hard, just annoying. Our other machines are still on Mojave as the upgrade doesn’t seem worth it at this time.

Other than the constant OS warnings and security settings Catalina requires, it’s been fine after that. The new hardware is impressively fast and fcpx is still a lot of fun.

[David Mathis]

My main beef is the available hard drive space changes often. I suspect this has to do with the APFS “feature” unless there is something else going on. I just installed Adobe CC and Premiere Pro gave some warning about an issue upon first launch. I quick reboot fixed that. Resolve seems to be more stable than Catalina is at the moment. ????‍♂️

[Robert Withers]

What’s the deal with “vintage” media files?
Thanks,
R.

Robert Withers

Independent/personal/avant-garde cinema, New York City

[Oliver Peters]

[Robert Withers] “What’s the deal with “vintage” media files?”

What do you mean?

– Oliver

Oliver Peters – oliverpeters.com

[Eric Santiago]

[Oliver Peters] “What do you mean?
“

I wonder if he’s referring to the older QT codecs.
I have a ton of those that don’t seem to be having any major issues with the fresh install of Catalina on a 2013 Mac Pro.
It was an issue prior to the same 2013 upgraded from High Sierra to Catalina.
That install was a few days in hell at work.
So far so good with a fresh install.

[Oliver Peters]

[Eric Santiago] “I wonder if he’s referring to the older QT codecs.”

I think anything that’s on Apple’s supported list will work.

https://support.apple.com/en-us/HT209000

Some, like DNxHR, don’t work yet within QT or FCPX, but do work within an app that supplies its own 64-bit library files (Avid, BMD, Adobe, etc). Of course, ProRes Raw or BMD Raw support is still evolving.

– Oliver

Oliver Peters – oliverpeters.com

[Robert Withers]

Larry Jordan and an archivists’ thread made a lot of posts about how Catalina (or FCPX–was never clear) would deprecate 32-bit media files, we imagined such as ProRes and DNxHD.
Thanks,
Robert

Robert Withers

Independent/personal/avant-garde cinema, New York City

[Robert Withers]

Sorry, DNxHR I guess. Don’t use it myself.
R

Robert Withers

Independent/personal/avant-garde cinema, New York City

[Oliver Peters]

ProRes is absolutely supported. Nothing deprecated about that. DNxHR will be, but isn’t yet.

It’s an OS-level issue, not specifically FCPX or any other app. Apple’s ProApps and Quicktime Player depend on video libraries supplied in the OS. Beyond the standard codecs installed, additional “pro” codecs can be installed through a Pro Formats Update, generally associated with FCPX.

A codec that is deprecated because it uses 32-bit libraries will still work in the future, if:

a) Apple supplies new 64-bit library components for it. In that case, all apps that use these libraries can read/write those codecs, including FCPX. Or,

b) The third-party company that uses these codecs creates their own internal libraries and doesn’t on OS-level components, in order to read/write those files. In that case, those third-party apps can read/write the files, but Apple apps won’t necessarily be able to.

– Oliver

Oliver Peters – oliverpeters.com