[BUG]Gateway 1.01 triggers an Audio Unit stability warning in GarageBand on macOS Tahoe 26.6.1

Open
#675 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp, macos
Domain
audio-video-rtc, desktop

Research direction

Start by reproducing the warning with Gateway 1.01 loaded as an Audio Unit in GarageBand on macOS Tahoe 26.6.1, using the listed Apple M4 and audio settings. Investigate the Gateway Audio Unit before any model or IR is loaded; done means GarageBand loads it without displaying the Audio Unit stability warning.

Written by the indexing model from the issue text.

Description

bug priority:low unread

Description
Gateway 1.01 crashing on Garageband (AU)

To reproduce
Install macOS Tahoe 26.6.1.
Install Gateway 1.01.
Open GarageBand.
Load Gateway as an Audio Unit.
GarageBand displays the Audio Unit stability warning.

Expected behavior
Gateway should load normally as an Audio Unit in GarageBand without triggering an Audio Unit stability warning.

Screenshots

Image Image

Computer & other info
OS: macOS Tahoe 26.6.1
Onboard graphics & version: Apple M4
Plugin version: Gateway 1.01
Standalone, VST3, or AU: AU
DAW: GarageBand
Audio interface: Built-in Audio / Scarlett Solo 4th Gen
Sample rate: 44.1 kHz
Model: N/A — issue occurs without a model loaded
IR: N/A — issue occurs without an IR loaded

Does the bug not happen under some other conditions?:
The issue appeared after reinstalling/updating macOS to Tahoe 26.6.1 and reinstalling Gateway 1.01. The warning occurs when using Gateway as an AU in GarageBand, before loading a NAM model or IR.

Add any other context about the problem here.

Additional context

This issue appeared after updating to macOS Tahoe 26.6.1. I then reinstalled Gateway 1.01. Before the macOS update, I did not encounter this warning.

The issue appears to occur with the Gateway Audio Unit itself, without requiring a specific NAM model or IR to be loaded.

Dominant language
C++
Stars
3k
Forks
281
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sdatkinson/NeuralAmpModelerPlugin

All issues in sdatkinson/NeuralAmpModelerPlugin

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.