FCPX.guru wrote: If you don't want to wait, move FCPX, Motion and Compressor from your Applications folder into the Trash. Then launch the app store, and it'll show a download icon for each. Reinstall, you get the latest version right away.
Did so and then emptied the trash. Launched FCP icon from Dock: my latest project opened. Does FCP perhaps use the Timemachine version from the bundle? Somewhat puzzled.
ddixon wrote: Actually, what I finally did was open App Store (Mojave) and in the Store Menu chose Reload Page and they appeared. I had no idea that was an option.
Some observations looking things over now. I see Motion has the addition of this.
Create motion graphics that accurately display and animate foreign language text, symbols, and emoji."
Plus, Windows > Window Layout, there's Classic and Cinema. Was that there before?
FYI, 2013 rMBP maxed out, Noise Reduction grinds it to a halt, zero playback.
Other things in the release notes.
Volume control is adjustable for a selected, connected clip
Audio playback continues when resetting the peak indicators
Audio playback continues when changing pan mode on an audio component
Changing audio configuration of a clip properly clears any soloed audio components
Double clicking to add an effect adds it to the top clip at the playhead position
Core Text engine ensures accurate display of Arabic letters, Indic vowel signs in Devanagari and Thai diacritics
Shape and Effect Mask values properly transfer via XML
When dragging in the timeline to select a secondary storyline, you can now select individual clips or the entire secondary storyline
Typing the first few letters of a font name jumps directly to the font in the list
Straight away I am seeing an alert about legacy media. Something to watch out for:
"About legacy media in Final Cut Pro X
To prepare for future macOS releases, complete Final Cut Pro projects that contain legacy media.
In Final Cut Pro, you might see an alert that legacy media files won't be compatible with future macOS releases.
Legacy media files are compatible with macOS Mojave, but they won't be with future macOS releases. Legacy media can include footage recorded with cameras like Sony HDCAM-SR cameras, footage from GoPro cameras recorded in the CineForm format, video files in the Avid DNxHD/DNxHR format created with software, footage shot with many other older cameras, or files modified with older software.
To make sure media you create now will be compatible with future macOS releases, use cameras and media formats supported by Final Cut Pro."
just read about that. I'm glad I don't work with any of those types of files, but still angry and confused why they're dropping support for them when it seems like it would be a very negative things for lots of professionals
Don't worry, not the next macOS but the one after it will likely make sure that good ol' h.264 is a legacy media. **poof** goodbye pretty much everything. Apple likes forcing people to move forward. Well except when it comes to their hardware which is weaker and more expensive to what you can get by building your own. My dream is for Apple to allow macOS to be self-installed on self-built PCs... no more Apple hardware.
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.
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.
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.