Attempting to process Photos using Topaz Photo AI.

[ThadInUT]

Max OS 13.2.1 .

Lrc (most recently updated 2/23/2023.

When I attempt to use Topaz Photo AI via Lrc, I can launch fine using File / Plug in Extras / Process Using Topaz Photo AI.  When I attemp to save the image back to LRC as a DNG file, I get "Internal Error has occurred: assertion failure".  

I have enabled full disk access to Topaz and Lrc.  

If I launch Topaz using Photo / Edit In / Topaz Photo AI, it launches fine, and I can save the image, but it saves as a tiff image.

Any help to get the first option to work is appreciated.

Lightroom Classic version: 12.2 [ 202302032259-eb84d255 ]
License: Creative Cloud
Language setting: en-US
Operating system: Mac OS 13
Version: 13.2.1 [22D68]
Application architecture: arm64
Logical processor count: 8
Processor speed: NA
SqLite Version: 3.36.0
Built-in memory: 16,384.0 MB
Real memory available to Lightroom: 16,384.0 MB
Real memory used by Lightroom: 2,106.2 MB (12.8%)
Virtual memory used by Lightroom: 406,056.3 MB
Memory cache size: 45.0MB
Internal Camera Raw version: 15.2 [ 1381 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2
Camera Raw virtual memory: 909MB / 8191MB (11%)
Camera Raw real memory: 988MB / 16384MB (6%)
Standard Preview Size: 3024 pixels
Displays: 1) 3024x1964, 2) 2560x1440

Graphics Processor Info:
Metal: Apple M1 Pro
Init State: GPU for Export supported by default
User Preference: Off

Application folder: /Applications/Adobe Lightroom Classic
Library Path: /Users/btapplegate/Creative Cloud Files/firstTimeUser/firstTimeUser-v12.lrcat
Settings Folder: /Users/btapplegate/Library/Application Support/Adobe/Lightroom

Installed Plugins:
1) AdobeStock
2) Aperture/iPhoto Importer Plug-in
3) Flickr
4) Nikon Tether Plugin
5) Topaz Photo AI

Config.lua flags: None

[Jim Wilde]

What version of Topaz Photo AI are you using? I just tried that process (I'm also on MacOS 13.2.1) initially using Photo AI v1.2, which worked correctly. Then I updated to the latest v1.2.2, which also worked correctly.

Does that issue happen with all files, or one file or file-type in particular?

[ThadInUT]

All files I have tried so far.

[ThadInUT]

Topaz Photo AI 1.2.3

[ThadInUT]

I am using Nikon NEF files into Topaz.

[ThadInUT]

Also just tried a JPG file.  Same error.

[GoldingD]

Does this occure if you login to the MAC as a different user?

[ThadInUT]

Topaz advised deleting their software and reinstalling.  After that, I did reboot my MAC and still have the same problem.

[ThadInUT]

OK All,

I think I'm narrowing the scope of the problem.  If I launch the plug in (File / Plug-in Extras / Process with Topaz Photo AI) from the Hard drive (I'll try and include a screenshot), then I can also save back to Lrc.  If I launch using a photo that is in a Collection, that is when I get the assertion error.  

[ThadInUT]

And still more information.  I'm still green on my learning curve of Lrc.  If a photo is part of a collection SET, then I get the error.  But if the photo is in a Collection, with no sub-collections (for lack of a better word), No error and the DNG is saved.

[ThadInUT]

Thanks for the patience, all,

I accidentally discovered that the DNG files were being saved to my hard drive even if I received an assertion error.   It's just that the altered image was not being displayed within a collection.  How can those altered images be displayed in a collection automatically? I'll include a screen shot.  The original image name is PRD_0206.nef.  In the screen shot, Lrc is in the background and Finder is in the foreground with copies of the saved files highlighted in blue.  

[Jim Wilde]

It's quite odd. I've tested some more and can confirm that if operating from either a collection or a collection set, when using the Plug-in Extras route the returned DNG is NOT added to the collection (which is a little bit surprising). However, and helpfully, on return LrC automatically switches the source from the collection/collection set to the actual folder in the Folders Panel so the the returning DNG is automatically stacked with the original file.

So in all cases the DNG is created in Photo AI, and when it is added to LrC I am able to see the returned file stacked with the original, although the initial source is changed if I started from a collection or collection set.

No error messages are produced, however.

That's with Photo AI v1.2.2. I'll try updating to 1.2.3 to see if that makes any difference.

[ThadInUT]

I'm beginning to think there is an issue between Lightroom Web and Lightroom classic.  You see, when I first started using the Adobe product, I was importing photos to LrcWeb.  I think the interface is better than Lightroom Classic.  

So, my troubleshooting steps have been : In Lrc, I found a photo that returned an assertion error when being saved back from Topaz.  I then deleted it from a collection, then from the folder within Lrc.   I also made sure the file could not be found on my hard drive using Finder.  I also went into LrcWeb and removed the photo from there.  I exported that file again from Apple Photo and reimported to Lrc, then added it to a collection.  With the phote selected in that collection, I launched Topaz through Plug-in Extras.  After saving in Topaz, the assertion error did not occur.  I seem to be experiencing some inconsistencies on having the saved DNG stacked to the original in the collection, but that could be user fog 

I don't know if this rises to the need for development attention or not, but I think I have a work around.  

[ThadInUT · Accepted solution]

This will be the last thing I have to say on this thread.  I heard back from Topaz, and they said the plugin is designed to place the image back in the original folder.  In order for that to work, the file needs to be located directly on the computer, or in a connected drive.  Images stored in the cloud will not work.

This is a hobby of mine, and I've been using Lightroom and Topaz for just a little while.  

I'll just adjust my workflow.

Thank you for all the replies.