10.4.4 Released

Well I found what I consider to be a rather giant bug. Creating Compound Clips does not work correctly any more for me. The newly created compound clip will slide to a new place earlier in the timeline instead of staying put, like it should. Does not seem to matter if created with Alt + G or via right-click/contextual menu.

Video evidence: - www.gamesack.net/crap/CC.mp4

It should absolutely not do that.

H264 is considered legacy?
Do the Apple guys like to be bashed? What about the older hardware that doesn't play well with HEVC? Do they obsolete it?

ektoras.papageorgiou wrote: H264 is considered legacy?
Do the Apple guys like to be bashed? What about the older hardware that doesn't play well with HEVC? Do they obsolete it?

There's no evidence for that. They talk about HDCAM-SR, CineForm format, Avid DNxHD/DNxHR "and other media from older cameras", probably HDV and the like. Anyway, they give early notice. Next MacOS, they won't be supported, so better transcode old codecs and consolidate longtime projects *now*. So that in a year, when Mojaves successor comes, nobody can complain.

I use absolutely zero of those codecs and I still get the warning. They need to let us know EXACTLY what clips or files are affected instead of being vague.

… for our German board members:
Robin Kurz hat in kurzweiligen 35min alle Neuerungen zusammengefasst

There’s a new and insightful opinion no one has ever heard.before...

Redifer wrote: I use absolutely zero of those codecs and I still get the warning. They need to let us know EXACTLY what clips or files are affected instead of being vague.

Yes, same here. Week old library, footage shot with FS7 and some stills and video from smartphones and got a warning when I updated the library.
I hope these legacy codecs will still be supported in other NLE when years come buy. I can't afford to lose DNxHD, there is no other way to get something equivalent to Prores from a PC.

Redifer wrote: Well I found what I consider to be a rather giant bug. Creating Compound Clips does not work correctly any more for me. The newly created compound clip will slide to a new place earlier in the timeline instead of staying put, like it should. Does not seem to matter if created with Alt + G or via right-click/contextual menu.

Video evidence: - www.gamesack.net/crap/CC.mp4

It should absolutely not do that.

Oh man, that IS a big problem! Thanks for reporting it here, please send Apple a bug report if you haven't already. I use compound clips heavily in my workflow. I think I'll wait for the bug fix, as exciting as the new features seem to be.

Doug wrote: Is it weird that I'm potentially most excited for this?

"- Typing the first few letters of a font name jumps directly to the font in the list"

This is a longtime annoyance, and it's a relief they finally fixed it! Looking forward to testing it out, once they fix the apparent Compound Clip bug.

Anyone try and find the extensions in the App Store? When I type in Final Cut Extensions I get nothing within the app store. Maybe this needs to be done while in FCP???

ektoras.papageorgiou wrote:

Redifer wrote: I use absolutely zero of those codecs and I still get the warning. They need to let us know EXACTLY what clips or files are affected instead of being vague.

Yes, same here. Week old library, footage shot with FS7 and some stills and video from smartphones and got a warning when I updated the library.
I hope these legacy codecs will still be supported in other NLE when years come buy. I can't afford to lose DNxHD, there is no other way to get something equivalent to Prores from a PC.

JPEG is out of time too.

Pro Video formats 2.0.7 in my App Store update section 11/16/2018

Jonathan Levin wrote: Anyone try and find the extensions in the App Store? When I type in Final Cut Extensions I get nothing within the app store. Maybe this needs to be done while in FCP???

Extensions won't be in the App Store, they'll be given as plugin installs directly from the developer. And the only three available at the moment are inlaced with the update install.

What's this mean?

Shutterstock's extension is in the App Store as is Frame.io's.

To load the Pro codecs:
> open FCP
> go to Top Menu > Final Cut Pro > Download additional content

You'll get the Pro Video Formats, 1300 Sound FX and some stuff for Motion, all in all 1,77 GB

Made a clean install & tried some things with the help of Robin Kurz' tutorial. With the new comparison viewer, it's a breeze to match shots. I made workspaces in the fashion of Apple Color's "rooms".
"Primary" - scopes, a 100% viewer, wheels, effects (i.e. for noise reduction) and a mini timeline
"Secondary" - as above, but with HS-curves and without effects tab
"Match" - comparison viewer with scopes, viewer with scopes, color tab

Assigned F1, F2 and F3 to it in >System Preferences >Keyboard >Shortcuts >App Shortcuts>Final Cut Pro (custom workspaces are not listed in FCP's command editor). Never worked before (used to "hack" the default workspaces), but now it works.

I have tried to find the extensions as mentioned by Steve in his video, and I can find the frame io and it works I think, not sure, but the other 2 mentioned, shutterstock and the ripple training extension, nope nowhere, I tried the shutterstock website, no mention of a plug in or an extension for fcpx...

Nothing on the high sierra version, and nothing on the mojave version..strange.

UPDATE: I was able to find the shutterstock extension, and the frame io extension and yes it creates a puzzle piece, come on Apple really this is poor, the app store is a pigsty, it is so out of date, barely functional hunk of junk.

The 10.4.4 update should have included the 3 "apps" as a automatic pre download or pre-install or install at first launch, this hunt and seek idea is just stupid at every level!

Just tested out the font search function and it's really going to save me a lot of irritation. That's a nice little tweak. The colour comparison windows - while limited are a welcome addition too. Interested to see what happens with the extensions as that's going to be very interesting with third party apps. Being a bit fanciful but I wonder if motion would work as an extension at some point in the future...

The HDCam SR Codec is one of the codec choices on the Sony F5 and F55 where its called SSTP. Its a real shame FCP X doesn't support it because its a great HD 444 codec especially for Chromakey work.

And annoyingly it works fine in Resolve 15.2