Repository navigation
Open
Description
Apple Feedback Assistant ID: FB25628258
DESCRIBE THE BUG:
Findings from the November 2026 investigation into two inspector bugs affecting every KOLOR plugin with custom UI. Both bugs are still open.
Overview
- Environment: Final Cut Pro 12.4, macOS 27.0.1 (26A434), FxPlug 4 (out-of-process XPC plugins), Apple silicon.
- Bug 1, cold-open height: on the first inspector build after launching FCP, a plugin with collapsed groups or hidden tabs draws with wrong heights and the inspector can disappear. Clicking away from the clip and back fixes it.
- Bug 2, cut-off: an effect stacked above one of our plugins gets its controls cut off on the right. Value fields, buttons and keyframe diamonds are missing.
- Conclusion: both are triggered by documented FxPlug features (
kFxParameterFlag_HIDDENandkFxParameterFlag_USE_FULL_VIEW_WIDTH). Both happen inside FCP's inspector layout, which a plugin can't see or control. No workaround on our side has been found that fixes them without side effects.
How we investigated
- Logging: a diagnostics module (
Shared/FxSharedControls/KOLORFxDiagnostics, Debug builds only) logs every view's lifecycle, its frames, draw and layout passes, every call to FCP, and every flag write. It flags faults such as "flag write inside a draw pass" and "zero width". - Recordings:
Scripts/capture-inspector-log.shrecords our log together with FCP's own messages, with BAD/GOOD markers typed by the tester.Scripts/summarize-inspector-log.pycounts the signals in each segment and compares a broken build against a working one. - Experiment switches: behaviour changes can be switched on one at a time:
KOLORFxExperiments.h,BASIS_EXP_NO_FULL_WIDTHinBasisPlugIn.m, andTEMPLATE_CUSTOM_UI_MODEin the Template plugin. All are currently off. - Minimal reproducer: the
Template FxPlugtarget, with one plain custom-UI view that uses none of our code. - Log signal: FCP logs
Invalid view geometry: height is negativewhenever its inspector layout is broken. It was the most reliable signal for bug 1.
Bug 1: wrong heights on the first build after launch
What we know, and how we know it
- Trigger: custom-UI rows that are HIDDEN when FCP first builds the inspector after launch.
- BASIS with nothing hidden: 0 FCP errors, correct. BASIS with one group collapsed (7 hidden rows): 25 errors, broken. SPEKTRUM (38 hidden rows): 217 errors, broken.
- The errors scale with the number of hidden rows, about 4 per row.
- Only the first build is affected.
- Clicking away and back rebuilds the inspector with the same hidden rows, with 0 errors and a correct layout. This held in every recording.
- The errors start before our plugin does anything.
- The timestamps show FCP logging errors while it creates our views, before our plugin's first draw and before any call from our plugin to FCP.
- FCP saves the HIDDEN flags in the project and restores them at launch.
- Snapshots of the flags taken on the cold open and on the rebuild were identical.
- Once the inspector is broken, toggling flags makes it worse.
- Showing and re-hiding the rows after the build doubled the errors (BASIS 25 → 95, SPEKTRUM 217 → 445). Only a full rebuild recovers.
- Our redundant tab write adds a second burst of errors, but isn't the cause.
- Removing it took SPEKTRUM from 217 to 145 errors; still broken.
- Showing the rows before the first build does fix the layout: 0 errors, correct inspector. But it causes a visible flicker: all of SPEKTRUM's tab rows and BASIS's collapsed groups appear for about 0.5 s.
pluginInstanceAddedToDocumentis called off the main thread, andFxParameterSettingAPIis nil there, despite the documentation. The API is available inside an action pair on the main thread, about 0.4 s after the project loads.
- FCP doesn't follow height changes of our views after it has created them.
- Starting held-back rows as 1-point transparent placeholders broke heights and spacing after a rebuild.
- Ruled out: zero-width views, ambiguous Auto Layout in our views, refused flag reads, calls off the main thread, our width syncing.
What we don't know
- Why FCP's first build mis-lays out hidden custom-UI rows.
- Whether "first build" means the first in the FCP process or the first in each plugin's process.
- Whether FCP's native groups (
startParameterSubGroupwithkFxParameterFlag_COLLAPSED) avoid the bug. - Whether hidden rows without
USE_FULL_VIEW_WIDTHare affected as well. - Whether reading values on a timer instead of in
viewWillDraw(as CINEM8's plugin does) makes a difference.
Bug 2: the effect above ours is cut off
What we know, and how we know it
- Trigger: any row with
kFxParameterFlag_USE_FULL_VIEW_WIDTH. All our rows use it.- In the Template plugin, a plain 200×30 custom view that only draws (no shared code, no calls to FCP, no width sync) is fine without the flag (mode 1) and reproduces the bug with it (mode 2).
- Only effects above the full-width row are affected, in our case Comic Basic.
- Moving our plugin above Comic Basic fixes it; moving it back below brings the bug back. Removing our plugin fixes it.
- It happens on every rebuild, but not on a cold open in our tests.
- CINEM8 also saw it right after launch.
- The cut-off grows with our view's starting width, and doesn't go away at width 0.
- Measured in the Template plugin.
- FCP calculates the upper effect's layout once and keeps it.
- Resizing the inspector, collapsing Comic Basic or changing its values doesn't fix it. Only this works: move ours above, collapse both, move Comic Basic back above, expand both.
- Our views are identical in the working and the broken build: same views, sizes and windows, no errors. FCP gives every row the same width (702 points in a 715-point inspector).
- Not fixed by any of these:
- turning off our width syncing;
- starting every view at 150 points or less;
- CINEM8's view setup:
intrinsicContentSizereturningNSViewNoIntrinsicMetricfor the width,NSViewWidthSizableand a 100-point starting width (Template modes 3 and 4).
- It isn't specific to KOLOR.
- CINEM8's Better Round Corners (full-width rows) now shows the cut-off too, and CINEM8 reported BASIS cutting off their effect (1 November 2026).
What we don't know
- How FCP derives the upper effect's width from the full-width row below it.
- Why Better Round Corners seemed unaffected at first. The bug may depend on timing.
- Whether BASIS without
USE_FULL_VIEW_WIDTHon every row is fixed.BASIS_EXP_NO_FULL_WIDTHis built but hasn't been tested; it needs a freshly applied BASIS. - Whether any workaround exists other than dropping full-width rows.
Options for our plugins
- Bug 2: drop
USE_FULL_VIEW_WIDTHand redesign the rows for FCP's standard control column, where FCP draws the parameter name. This works in the Template plugin (mode 1), but costs the full-width design: group headers, tab bar, crosstalk and header logo. - Bug 1: show hidden rows before the first build and re-hide them afterwards. This fixes the layout, but flickers, and FCP could save the project while the rows are shown. The other option is FCP's native collapsible groups (untested).
- Both: report them to Apple (see below) and wait for a fix.
Reporting to Apple
Two separate reports in Feedback Assistant: area Final Cut Pro, type Incorrect/Unexpected Behavior.
Report 1: Effect above a full-width custom FxPlug parameter is laid out too narrow
- Summary: when an FxPlug 4 effect with a custom-UI parameter that uses
kFxParameterFlag_USE_FULL_VIEW_WIDTHsits below another effect in the inspector, the effect above it is laid out too narrow whenever the inspector is rebuilt. Its value fields, buttons and keyframe diamonds are cut off on the right. - Environment: Final Cut Pro 12.4, macOS 27.0.1 (26A434), FxPlug 4 XPC plugin, Apple silicon.
- Steps to reproduce:
- Install the attached sample plugin: one standard slider plus one custom-UI parameter whose view is a plain
NSView(fixed frame, draws a rectangle), added withkFxParameterFlag_CUSTOM_UI | kFxParameterFlag_USE_FULL_VIEW_WIDTH. - Apply Comic Basic, then the sample plugin, to the same clip, so the sample is below Comic Basic in the inspector.
- Select another clip, then select this clip again.
- Install the attached sample plugin: one standard slider plus one custom-UI parameter whose view is a plain
- Expected: Comic Basic's rows use the full inspector width.
- Actual: Comic Basic's sliders are shortened, and its value fields and keyframe buttons are cut off. Its header row is unaffected.
- Notes:
- Without
kFxParameterFlag_USE_FULL_VIEW_WIDTHthe problem doesn't occur. - The cut-off grows with the custom view's initial width. It persists at width 0.
- Putting the sample above Comic Basic avoids it.
- Resizing the inspector doesn't restore the layout. Only collapsing both effects and reordering them does.
- Seen with several third-party plugins, including KOLOR BASIS and SPEKTRUM and CINEM8 Better Round Corners.
- Overriding
intrinsicContentSize(no intrinsic width),NSViewWidthSizableand a small initial frame don't help.
- Without
- Attach: the Template FxPlug built with
TEMPLATE_CUSTOM_UI_MODE 2; screenshots of the correct and the cut-off state.
Report 2: Hidden custom FxPlug parameters break the first inspector layout after launch
- Summary: if an FxPlug 4 effect has custom-UI parameters with
kFxParameterFlag_HIDDENset when Final Cut Pro first shows it after launch, the inspector draws wrong row heights, and can disappear entirely. Final Cut Pro logsInvalid view geometry: height is negative(about 4 times per hidden row). Selecting another clip and back fixes it. - Environment: as Report 1.
- Steps to reproduce:
- Use an FxPlug 4 effect with several custom-UI parameters (
kFxParameterFlag_CUSTOM_UI | kFxParameterFlag_USE_FULL_VIEW_WIDTH). From its custom view, hide some of them withaddFlags:kFxParameterFlag_HIDDEN toParameter:insidestartAction:/endAction:, for example a collapsible group. - Save the project with the parameters hidden, then quit Final Cut Pro.
- Relaunch Final Cut Pro and select the clip.
- Use an FxPlug 4 effect with several custom-UI parameters (
- Expected: the inspector shows the visible rows with correct heights.
- Actual: wrong heights, with the inspector partly or completely blank. Console:
[com.apple.runtime-issues:AppKit] Invalid view geometry: height is negative, starting while Final Cut Pro creates the custom views and before the plugin makes any call. - Notes:
- Only the first inspector build after launch is affected. Rebuilds with the same hidden rows are correct.
- The error count scales with the number of hidden rows: 0 hidden → 0 errors, 7 → 25, 38 → 217.
- Toggling
kFxParameterFlag_HIDDENafter a broken build makes it worse. ClearingHIDDENbefore the first build avoids it. - In
pluginInstanceAddedToDocument(called off the main thread),FxParameterSettingAPIis nil, although the documentation says the APIs work there.
- Attach: a sample plugin with a collapsible group (BASIS, or a reduced version of the Template plugin), a console log of a cold open (
Scripts/capture-inspector-log.sh), and screenshots.
TO REPRODUCE:
Step one: Apply any effect to a clip
Step two: Apply our template plugin or any plugin with a full-width parameter
Get the template plugin: https://drive.proton.me/urls/YTK2XX1CMG#nQS4zx1hroSW
EXPECTED BEHAVIOUR:
The upper effect's view will be cut off.
SCREENSHOTS:
SPECS:
- 2025 Mac Studio (M4 Max, 64GB RAM, 2TB SSD)
- macOS Golden Gate 27.2.1
- Final Cut Pro 12.4
Reacted by Chris Hocking
Activity
latenitefilms commentedon Nov 18, 2026
Thanks for reporting! I've chased up Apple.
latenitefilms commentedon Nov 18, 2026
Apple says: