diff --git a/404.html b/404.html index df919822f7..37cf4e4978 100644 --- a/404.html +++ b/404.html @@ -3,7 +3,7 @@
- + @@ -28,11 +28,11 @@ - + - + - + diff --git a/accessibility/index.html b/accessibility/index.html index fef859afa0..6717bc661a 100644 --- a/accessibility/index.html +++ b/accessibility/index.html @@ -3,7 +3,7 @@ - + @@ -33,11 +33,11 @@ - + - + - + diff --git a/bugtracker/index.html b/bugtracker/index.html index 0529715ae9..f77838ac07 100644 --- a/bugtracker/index.html +++ b/bugtracker/index.html @@ -3,7 +3,7 @@ - + @@ -33,11 +33,11 @@ - + - + - + @@ -372,6 +372,7 @@Here's a list of the 30 most recently added Final Cut Pro bug reports:
The above list is pulled from our GitHub issues site.
Here's a list of the 30 most popular Final Cut Pro bug reports:
The above list is pulled from our GitHub issues site.
Here's a list of the 30 most recently added Final Cut Pro 11 bug reports:
Last Updated: 16th November 2024
For most users, on modern Apple Silicon Mac's Final Cut Pro 10.8.1 is rock solid.
-Final Cut Pro 11.0.0 is brand new - but from early reports, aside from some weirdness with Magnetic Mask and collaboration - everything else seems fairly solid.
+Final Cut Pro 11.0.0 is brand new - but from early reports, aside from some weirdness with Magnetic Mask, Custom Overlays and collaboration - everything else seems fairly solid. See below for more information.
Final Cut Pro 10.8 is very similar to Final Cut Pro 10.7.1, so if you're still on 10.7.1 on a major project, there's no rush to update.
If you're still on Final Cut Pro 10.6.5 or earlier on Intel machines - just stay there until you buy an Apple Silicon Mac.
If you're currently on Final Cut Pro 10.6.10, you can safely upgrade to Final Cut Pro 10.7.
@@ -367,20 +367,33 @@Final Cut Pro 11 was released at the Final Cut Pro Creative Summit on 13th November 2024.
+Final Cut Pro 11 was released at the Final Cut Pro Creative Summit on 13th November 2024.
One interesting thing about the new Magnetic Mask in Final Cut Pro is that it saves all the analyse data in a folder called VideoSegmentationFiles
within the Final Cut Pro Library bundle.
You can't move it outside the bundle - it needs to live inside the Library bundle (unlike other cache files). This is super interesting, and may present some challenges with collaborative workflows (i.e. with Postlab).
Magnetic Mask data is also not transferred with FCPXML - so if you export a project/timeline containing a clip with a Magnetic Mask, then re-import the FCPXML, the mask won't correctly come across - in fact, you'll just get an empty effect.
Unfortunately in Final Cut Pro 11, Magnetic Masks don't work with Send to Compressor.
-This has been reported to Apple.
-You can follow along via our FCP Cafe bug report.
+This has been reported to Apple. You can follow along via our FCP Cafe bug report.
-
There are some early reports of issues with Custom Overlays and exporting PNGs - but these are not yet confirmed.
+Custom Overlays are currently not working. You can follow along via our FCP Cafe bug report.
+There are some early reports of issues with exporting PNGs - but these are not yet confirmed.
We've updated to Final Cut Pro 11 and haven't had any major issues yet - but tread with care, as this is a major update, as Final Cut Pro is now sandboxed.
+The amazing Joe Marler reports on Facebook:
++There are two significant FCP 11 problems I'm working on:
+
++
+- A serious performance regression if combining certain built-in or third-party effects. E.g, if using a simple color wheels shape mask and built-in FCP video noise reduction on a clip, even if fully rendered to cache, playback will be sluggish.
+
+- If a
+v10.8.1
library containing certain high-frame-rate clips is upgraded to 11.0, they will display as black. Reported and reproduced on a GH6 UHD 4k 100.0 fps 10-bit 4:2:0 HEVC clip. Reported on a Nikon Z9 clip (specifics yet unknown) but we don't have the clip to test. Does not happen with Sony 100.0 fps or 120 fps XAVC-I 10-bit 4:2:2 (H.264) or XAVC-HS 10-bit 4:2:2 (HEVC) clips.
+
+The affected clips can be imported from scratch to FCP 11 and they work. The problem happens during the library upgrade. It also happens if loading a ver. 1.12 library or project XML from FCP 10.8.1 to FCP 11.0.
+The reverse XML direction is possible. If high-frame-rate black clips are in the FCP 11 library, a ver. 1.12 library or project XML can be exported and imported OK to FCP 10.8.1 and they will all work.