Welcome to our community

Be a part of something great, join today!

Register Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

FCPX 10.4.4 and Legacy media not compatible in future Mac os

J

Joachim Hoge

Well-known member
Joined
Jul 18, 2011
Messages
786
Reaction score
0
Points
16
Location
Norway
After updating this morning I got a warning saying something like: "Legacy media not compatible in future Mac os". The project was shot on my Epic-W
Heading over to Apple gave mi this info
https://support.apple.com/en-us/HT209000

And in the list of supported Red cameras (for the future) I found only Raven , Scarlet-W and Weapon cameras.
Wonder if this means Epic-w will not be supported in future MacOS upgrades. Seems strange though.
 
That's odd. R3D is R3D surely? Could it be referring to some old proxy or optimised media that was created for the project?

I'm not a huge FCPX user but i can't see how one flavour of R3D wouldn't work and others would. Makes no sense.

cheers
Paul
 
Thats what I'm thinking as well. R3D is R3D. Could be optimized media it was referring to, I didn't use proxy.
 
I am getting the same thing. I don't se why MX cameras would be excluded. They shoot .r3d....
 
No worries you also have to update MacOS to use this new version of FCPX, which comes with more restriction to use the beloved NVidia GPU's.
Another good thing is that it also doesn't support many other (legacy)codecs.
 
Clearly it’s about optimizations but I do think there is some danger in this strategy of forcing users to update the OS in order to use a dot rev update. I’m still stuck at 10.4.0 because 10.4.1 required update to High Sierra which I’m not ready to do yet. I’m sure those dot revs are taking advantage of things in the new OS but I still think this is a slippery slope for Apple. Of course, if you don’t need any of the new feature or bug fixes then you can just stay where you are.
 
Hard to argue with Misha's sarcasm on this one. In the bigger picture, one has to wonder how this plays out if Apple is determined to stonewall nVidia GPUs. Could there be a mMP next year that leverages AMD GPUs (or Apple's own chips) to run circles around CUDA/Turing? It's theoretically possible, but in reality...

I prefer OSX over Windows, and it's propensity to take over one's computer for endless "updates" that mostly seem to add annoying crap. That said, if Apple is seriously courting folks like us, and won't support nVidia/CUDA, they better leverage Metal/AMD/A-series/whatever very well.

Cheers - #19
 
Blair S. Paulsen said:
Hard to argue with Misha's sarcasm on this one. In the bigger picture, one has to wonder how this plays out if Apple is determined to stonewall nVidia GPUs. Could there be a mMP next year that leverages AMD GPUs (or Apple's own chips) to run circles around CUDA/Turing? It's theoretically possible, but in reality...

I prefer OSX over Windows, and it's propensity to take over one's computer for endless "updates" that mostly seem to add annoying crap. That said, if Apple is seriously courting folks like us, and won't support nVidia/CUDA, they better leverage Metal/AMD/A-series/whatever very well.

Cheers - #19
Click to expand...
it's so easy to bypass the auto-update, takes maybe 15 brain cells fireing for 15 seconds....
 
Blair S. Paulsen said:
In the bigger picture, one has to wonder how this plays out if Apple is determined to stonewall nVidia GPUs. Could there be a mMP next year that leverages AMD GPUs (or Apple's own chips) to run circles around CUDA/Turing? It's theoretically possible, but in reality...

I prefer OSX over Windows, and it's propensity to take over one's computer for endless "updates" that mostly seem to add annoying crap. That said, if Apple is seriously courting folks like us, and won't support nVidia/CUDA, they better leverage Metal/AMD/A-series/whatever very well.

Cheers - #19
Click to expand...

This.
 
Joachim Hoge said:
After updating this morning I got a warning saying something like: "Legacy media not compatible in future Mac os". The project was shot on my Epic-W
Heading over to Apple gave mi this info
https://support.apple.com/en-us/HT209000

And in the list of supported Red cameras (for the future) I found only Raven , Scarlet-W and Weapon cameras.
Wonder if this means Epic-w will not be supported in future MacOS upgrades. Seems strange though.
Click to expand...

Apple's support doc is vague and could be a bit more informative regarding what's going on.

There is speculation that Apple's phasing out of 32bit apps also affects older 32bit codecs (the encoder/decoder).

https://www.digitalrebellion.com/blog/posts/thoughts_on_32_bit_codecs_being_phased_out_in_macos
https://discussions.apple.com/article/HT209000
https://twitter.com/Hildron101010/status/1063602772715687936
https://twitter.com/Adamski/status/1063146640368758784
https://twitter.com/fcpxpert1/status/1063503107055747072

The warning might potentially be a generic prompt or perhaps mis-flagging media that is otherwise fine.
I've read of a few people getting that message on projects that were formats clearly stated
to be compatible and not legacy media.

http://www.fcp.co/fcp-forum/4-final-cut-pro-x-fcpx/29230-10-4-4-released?start=20#97715

Apple might consider issuing a statement clarifying the codec situation a bit clearer (i.e why do otherwise codec compliant projects get the warning).

ADDENDUM:
This might be a way of getting Mac OS to list "Legacy Video Codecs".
https://twitter.com/Apple_Trainer/status/1064775976419241984

The only problem is this might only list legacy codecs within QT and not necessarily those installed through plug-ins and 3rd parties.


Brian Timmons
BRITIM/MEDIA
 
Blair S. Paulsen said:
Hard to argue with Misha's sarcasm on this one. In the bigger picture, one has to wonder how this plays out if Apple is determined to stonewall nVidia GPUs. Could there be a mMP next year that leverages AMD GPUs (or Apple's own chips) to run circles around CUDA/Turing? It's theoretically possible, but in reality...

I prefer OSX over Windows, and it's propensity to take over one's computer for endless "updates" that mostly seem to add annoying crap. That said, if Apple is seriously courting folks like us, and won't support nVidia/CUDA, they better leverage Metal/AMD/A-series/whatever very well.

Cheers - #19
Click to expand...

This interview with Apple's Phil Schiller and Anand Shimpi seems to indicate Apple's direction pretty well.

https://arstechnica.com/gadgets/2018/11/apple-walks-ars-through-the-ipad-pros-a12x-system-on-a-chip/

I understand Apple wanting to control their own destiny in this fashion. It's similar to decisions RED has made in development and manufacturing their own tech.

Apple needs to still consider that the hardware they design may not satisfy the needs all users and should still keep things open for ALL 3rd parties to participate on the platform given they are compliant to the OS architecture and not hacking their way into it.

This is obviously a big deal for Pro users and it needs to be pushed front and center for Apple to do right by us.

Having said this, how many people signed the petition for Apple to publicly commit to work with Nvidia on drivers for Mac OS 10.14?
https://www.change.org/p/tim-cook-a...-work-with-nvidia-on-drivers-for-mac-os-10-14

Has anyone sent feedback to Apple - https://www.apple.com/feedback/macos.html or Tim Cook (tcook@apple.com) for that matter?

Brian Timmons
BRITIM/MEDIA
 
Steve Sherrick said:
Clearly it’s about optimizations but I do think there is some danger in this strategy of forcing users to update the OS in order to use a dot rev update. I’m still stuck at 10.4.0 because 10.4.1 required update to High Sierra which I’m not ready to do yet. I’m sure those dot revs are taking advantage of things in the new OS but I still think this is a slippery slope for Apple. Of course, if you don’t need any of the new feature or bug fixes then you can just stay where you are.
Click to expand...

I waited a bit to go to High Sierra too and am not in a rush to go to Mojave. I must say that High Sierra works fine and I think the majority of conflicts and plug in issues have been long dealt with. I even have a 2008 Mac Pro 3,1 running High Sierra and FCP 10.4.3 and it runs quite well. Not my main system anymore but still good enough to work on.

While I'm not in a rush to update to this latest 10.4.4 I must say the 3rd party Workflow extensions is a feature that may be bigger than
most people realize. I can't think of an NLE that has more extensive 3rd party support than FCP X.

Brian Timmons
BRITIM/MEDIA
 
Apple Final Cut Pro X 10.4.4 Presentation



By LumaForge




Watch Apple's Final Cut Pro X 10.4.4 presentation from the Los Angeles Creative Pro User Group meeting in January 2019. Learn about the new Workflow Extensions, Noise Reduction, Batch Export, Comparison Viewer, and VR tools built into FCPX 10.4.4.

Hear from Emery Wells from Frame.io about their new FCPX workflow extension. Also see how FCPX and ProRes RAW were used to create a recent episode of Lowerider Roll Models.

For super easy collaborative video storage, check out the LumaForge Jellyfish.
https://lumaforge.com/jellyfish/

Don't forget to Subscribe for more presentations from the Faster, Together Stage.

To learn more about us, go to our website, or follow us on social media.
Website: https://lumaforge.com
Twitter: @lumaforge
Facebook: LumaForgeInc
Instagram: @LumaForgeInc
 
You must log in or register to reply here.
Back
Top