Proteus Natural simply won't start. Getting "Error - error"

Topaz Video Bugs and Issues
1

Just downloaded the latest release, (1.4.0 on Apple Silicon), and selected “Proteus Natural” mode for a video. I then started a 5 second preview. After meditating for a few seconds, I get the helpful message “Error - error”. I’ve tried deleting and re-installing the app, as well as deleting the Topaz Video directory under Application Support.

The log shows a lot of errors indicating messed up data structures, starting with

2026-04-30 15-27-12.523 Thread: 0x1f1c1d8c0 Warning qrc:/models/TOutputModel.qml:62: TypeError: Cannot call method ‘map’ of undefined

and continuing with hundreds of entries along the lines of

2026-04-30 15-27-13.058 Thread: 0x1f1c1d8c0 Warning qrc:/videoplayer/TPreviewPane.qml:398:9: TypeError: Cannot read property ‘height’ of undefined

and so forth. Is this model supported on this platform? Is there a workaround, or is this model simply unavailable to me until there’s a fix?

Let me know if I should send the logs zip file to someone…

2

Also tried deleting the Topaz Video directory under ~/Library/Caches. No help.

3

Yes, Proteus Natural is supported on Mac OS 15 and it should be working with 26 systems. Can you grab the full logs and send to the support team for review into the matter? help@topazlabs.com

To gather logs, please select Help > Logging > Get Logs for Support and attach the zip file to your reply.

Here is a video to help with the steps of how to collect the logs.

4

got the same problem on my Macbook with M1 Max 32GB, on my Mac mini with M1 8GB its working

5

This sounds very much like the previous Proteus Natural bug on Apple Silicon. In that case, I found a work-around by setting the max memory to 10% in the app’s settings. Maybe worth trying that, just in case.

6

thanks this works :+1:

7

played a bit arround with my script and it looks like more then 8GB of memory is the problem here:

  • 10% = 3,2GB works
  • 25% = 8GB works
  • 50% = 16GB did not work
8

For some reason I thought that Topaz had fixed this for all but now it appears not.

However, when I tried it on my M3 Ultra Studio (Tahoe 26.4.1) , I no longer get the error with any memory settings. So not sure what’s going on.

Thanks.

Andy

9

The reduced RAM trick worked for me, too. Topaz support supplied an updated model file that also solves the problem without having to reduce RAM usage. I think we can reasonably expect this to be fixed in the next release.

Thanks to the Topaz team for a quick fix!

10

I’m glad that worked. But the thing is, Topaz have known about this since before February. They sent me an updated pnat-1.json file on 3 Feb which I then confirmed back to them that solved the issue.

So I can’t see any good reason why they haven’t issued a permanent fix since then. They’ve had plenty of opportunity. Perhaps they’ve made other changes since then which has undone the fix.

Andy