M5 with OS 27 Golden Gate | incompatibility with Local rendering for Wonder

Topaz Photo Bugs and Issues
1

Ich habe ein reproduzierbares Problem mit der lokalen Verarbeitung von Wonder 3.0 und Wonder 3.5 in Topaz Photo.

System:

  • MacBook Pro
  • Apple M5 Pro
  • macOS Golden Gate
  • aktuelle Topaz-Photo-Installation

Fehlerbild:

Sowohl Wonder 3.0 als auch Wonder 3.5 schlagen beim Local Rendering mit „Error Running Model“ fehl.

Folgende Tests habe ich bereits durchgeführt:

  • Wonder 3.0 → Local Rendering: Fehler
  • Wonder 3.5 → Local Rendering: Fehler
  • Wonder 3.5 → Cloud Rendering: funktioniert
  • Recover Faces → Local Rendering: funktioniert
  • Super Focus → Local Rendering: funktioniert
  • Test mit einem JPG direkt vom lokalen Schreibtisch statt aus iCloud Drive: gleicher Fehler
  • Topaz Photo wurde vollständig deinstalliert und anschließend neu installiert.
  • Der coreMLCache wurde gelöscht und anschließend neu erzeugt.
  • Auch danach bleibt das Verhalten unverändert.

Damit scheint die lokale AI-/NeuroServer-Verarbeitung grundsätzlich zu funktionieren; das Problem tritt spezifisch bei Wonder 3.0/3.5 Local auf.

In den beigefügten Logs treten beim lokalen Laden/Ausführen von Wonder unter anderem Fehler im CoreML-/Metal-Performance-Shaders-Pfad (MPS/MPSGraph) auf. Auffällig sind insbesondere Meldungen im Zusammenhang mit:

MPSGraphExecutable

MPSXSymbolicShapeFoldingPass

mps.concat

sowie ein unerwartetes Beenden des Workers beim Laden/Ausführen des CoreML-VAE-Pakets. Nach dem Fehlschlag über CPU/GPU scheint auch der alternative Ausführungsweg nicht erfolgreich geladen werden zu können; anschließend wird gemeldet, dass die Worker das betreffende ML-Package nicht laden konnten.

Zusätzlich enthalten die Logs einen Hinweis, dass die verwendete PyTorch-Version 2.10.0 von der eingesetzten coremltools-Version nicht als getestet erkannt wird und PyTorch 2.7.0 als zuletzt getestete Version genannt wird.

Da Recover Faces und Super Focus lokal funktionieren und Wonder 3.5 über Cloud Rendering ebenfalls problemlos läuft, vermute ich ein spezifisches Kompatibilitätsproblem der lokalen Wonder-Modelle bzw. des CoreML/MPS-Ausführungspfads auf M5 Pro / macOS Golden Gate.

Die entsprechenden .tzlog-Dateien füge ich dieser Anfrage bei.

Könnten Sie bitte prüfen,

  1. ob Wonder 3.0/3.5 Local auf M5 Pro unter macOS Golden Gate derzeit vollständig unterstützt bzw. getestet ist,
  2. ob dieses CoreML/MPS-Problem bereits bekannt ist,
  3. ob es einen Workaround oder eine aktualisierte Wonder-/NeuroServer-Komponente gibt und
  4. ob ich Ihnen weitere Diagnoseinformationen zur Verfügung stellen soll?

Vielen Dank für Ihre Unterstützung.

2

I’m seeing a very similar issue on a MacBook Pro M5 Max running OS 27.0.. Wonder 3.5 fails during local rendering with “Error Running Model,” while cloud rendering works.

I checked my .tzlog file from September 15. Wonder starts processing, but the Core ML/MPS path fails during VAE processing at MPSXSymbolicShapeFoldingPass. The CPU/GPU worker then exits, and the Neural Engine worker also fails to load the Core ML VAE package. Topaz ultimately reports MODEL_INFERENCE_ERROR.

The log also warns that its PyTorch 2.10.0 version is newer than the last version tested with its coremltools build (2.7.0). I can’t tell whether that warning contributes to the failure.

The local Core ML/MPS error looks especially similar to yours. I haven’t found a confirmed cause or working fix yet.

3

I’m experiencing the same thing and getting the same error. It’s strange, though: I have two Macs, and the “Wonder” and “Face Recovery” error only occurs on the Macbook Pro M5 Pro with 24GB RAM, 15 CPU, 16 GPU. Everything works perfectly—without errors—on the Mac Studio with the M2 Ultra 64GB RAM.

Ange.topazlabs (ange.topazlabs@gmail.com) 4

Hi all,

Our development team is currently looking into the OS 27 Golden Gate compatibility issue affecting local rendering with Wonder.

If you’re running into this, please send us your logs so we can add your case and system information to the development ticket to help facilitate compatibility:

  1. Open Topaz Photo.
  2. Go to Help > Open Log Folder.
  3. Send us all of the logs currently in that folder at support@topazlabs.com.
  4. Please mention that you’re experiencing the Wonder local rendering issue on OS 27, and include your Mac model/chip.

Please send the logs directly to Support rather than posting them in this forum thread. We’ll review them and relay the relevant information to the development team working on this incompatibility.

In the meantime, Wonder Cloud Rendering is free and unlimited, so you can use Cloud Rendering as a workaround while the team investigates the local rendering issue or use Wonder Local on any machines that is on OS 26, our last current supported OS.

Thanks to everyone who has reported this and provided details so far!

I will update this thread if any other issues are found as well as when a version update is available that fully supports OS 27.

1 Like
6

Subject: Topaz Photo 1.7.0 — Wonder 3.5 “Error Running Model” Locally on Apple M5 Max; Cloud Processing Works

I am experiencing a reproducible “Error Running Model” error when using Wonder 3.5 with Local Processing in Topaz Photo.

System and software

  • Computer: Mac Studio

  • Processor: Apple M5 Max

  • Memory: 64 GB

  • Operating system: macOS [please insert version]

  • Topaz Photo: Version 1.7.0

  • Wonder model: Wonder 3.5

  • Processing: Local Processing

Problem

When I select Wonder 3.5 and use Local Processing, Topaz Photo returns:

Error Running Model

The error occurs consistently.

Testing performed

I initially encountered the problem while processing photographs from my Sony A1 II. These are approximately 50 MP Sony files.

To determine whether the problem was related to the size or format of the Sony files, I also tested Wonder using a small JPEG file.

The same “Error Running Model” error occurs with the small JPEG.

I then tested the same Wonder processing using Cloud Processing.

Cloud Processing works successfully.

Thus, the problem appears to be specific to local execution of Wonder 3.5, rather than the image files themselves.

Diagnostic summary

Test Result
Sony A1 II file + Wonder 3.5 + Local Fails — Error Running Model
Small JPEG + Wonder 3.5 + Local Fails — Error Running Model
Wonder 3.5 + Cloud Processing Works
Apple M5 Max / 64 GB System meets/exceeds stated hardware requirements

Because Wonder fails even with a small JPEG but works through Cloud Processing, I believe the problem may involve the local Wonder 3.5 model, CoreML runtime, or local model installation/cache, rather than the source image.

Request

Please advise whether this is a known issue with Wonder 3.5 / Topaz Photo 1.7.0 on Apple Silicon, particularly with the M5 Max.

Please also advise:

  1. Whether there is a known fix for “Error Running Model” specifically with local Wonder 3.5 processing when Cloud Processing works.

  2. Whether I should clear or reinstall the Wonder/CoreML model.

  3. Whether there is a recommended procedure to reinstall only the Wonder model without disturbing my other Topaz models.

  4. Whether Topaz recommends upgrading to a newer version or temporarily reverting to an earlier version of Topaz Photo.

  5. If this is a known 1.7.0/Wonder 3.5 issue, whether there is a beta or subsequent release that addresses it.

Attachments

I will provide the following diagnostic information with this report:

1. Screenshot of the error

A screenshot showing the “Error Running Model” message while Wonder 3.5 is selected and Local Processing is being used.

2. Screenshot of the Wonder settings

A screenshot showing:

  • Wonder 3.5 selected

  • Local Processing selected

  • The image being processed

3. Screenshot of Cloud Processing

A screenshot showing the same image successfully processed using Cloud Processing, if useful.

4. Topaz Photo log files

I will attach the Topaz Photo logs generated immediately after reproducing the error.

5. System information

I will provide the relevant Mac system information, including:

  • Mac Studio

  • Apple M5 Max

  • 64 GB unified memory

  • macOS version

6. Test image

If useful, I can provide the small JPEG that reproduces the problem.

Reproduction steps

The problem can be reproduced as follows:

  1. Launch Topaz Photo 1.7.0.

  2. Open a Sony A1 II image.

  3. Select Wonder 3.5.

  4. Select Local Processing.

  5. Run the model.

  6. Topaz Photo returns “Error Running Model.”

The same error occurs when repeating the procedure with a small JPEG.

Changing to Cloud Processing allows Wonder 3.5 to process successfully.

Thank you. I would appreciate guidance on whether this is a known local Wonder 3.5 issue and, if so, the recommended version or model installation to use while it is being resolved.

7

I also removed the Cache, emptied the trash and restarted resulting in the same error

Ange.topazlabs (ange.topazlabs@gmail.com) 8

@richard.lipow - moved your post here as this is an incompatibility with M5 machines on the new OS 27, and Wonder local will not work on this new OS at the moment.

While the development team works on OS 27 compatibility with this model, you can use Wonder Cloud Rendering, it is free and unlimited, or use Wonder Local on any machines that is on OS 26, our last current supported OS.

I will update this thread if any other issues are found as well as when a version update is available that fully supports OS 27.

1 Like
9

Just to share my own investigation…

I have been using Topaz Photo v1.6.0 on Macbook M3 MAX on Golden Gate without any issue with using Wonder locally. I updated it to v1.6.0 when it came out and didn’t bother updating it.

I got a new Macbook M5 Max also on Golden Gate. I tried fresh installation of 1.7.0, 1.6.1, and 1.6.0. All failed to render Wonder locally.

What worked for me was copying the application, Topaz Photo.app, file from the old Macbook to the new Macbook.

I noticed when I install through the installer and download all models during the installation, the wonder files downloaded are different than what’s in my 1.6.0. Mine is using wonder-all-20260512.zip and wonder-2-20260508.zip but new installations always download later versions. I wonder if this is the difference…

11

Well, I’m facing the same issue with the hardware and software configuration mentioned. In addition, `Face Recovery 3` also doesn’t work with a local render.