@Ange.topazlabs is very good about responding to issues here and expediting dev attention if needed. I can’t speak to her schedule, but this is Thanksgiving holiday weekend in the US.
Did you also send an email with your issue (and system specs) to Topaz Support at: Support@topazlabs.com to cover your bases?
thanks for the reply. John Sloan and I are eMailing directly on it … I sent him some screenshots and logs a little earlier this morning. And, oh yes, happy thanksgiving weekend from Canada.
I am still getting this thing at the bottom with the fizzy and none viewable thumbnail photo.
I want to narrow it down for you guys, I am getting this on Canon R8 and it was in CR3, I edit it and save as 16 bit TIFF. I have DJI drone photos in DNG, edit and save to 16 bit TIFF,but the strip of the thumbnail photos is good.
I think that did it. Topaz Photo loaded two new models upon start. It was too fast to see any details, but I think that should be those missing earlier. Thank you.
yup, thanks…..that’s exactly where it should be - but the plugin is not installing on (my) MacOs properly. All I am seeing is “Export" and that means it is not returning it to LrC properly. I’ve sent a ton of stuff off to the team to diagnose.
@Tostanica-fezanamu - can you DM me before/afters of this pixel shift you mention? Is it on specific models? I want to make sure it’s tracked correctly and relay to the development team.
@jim.camelford - I see you are troubleshooting with Alexandre by Support Emails. If you that you clarify here that you are only missing Edit in and not File > Plug in Extras. We have sent new steps on our email chain just now - for you to test.
@mrtoyota03 - We have a open development team ticket for this. I added your contact information to it and we can tag you once its resolved. Until it is, some TIFF files (not all) will have this issue. Workaround is to either use the DNG files directly or use Photo AI v4.0.1, that you own.
ange…I can confirm the problem is only with the Edit In workflow - just sent a series of screenshots back to Alexandre to show this.
I do see where you have asked if I have Store presets with this catalog checked - and I can confirm that I do and have run this way forever…and cannot easily change this
So, if there is a PlugIn file I can manually copy to the presets folder within my catalog structure, let me know what it’s called / likely where you have put it and I can copy it there and that might do it.
@jim.camelford - Unchecking it would fix this! And also, the File path would give better results than Edit in, especially if you shoot RAW. Seeing you replied to Alexandre that you fixed it in your Presets as well. Glad to hear.
@TPX can you confirm what the link is in the Ideas Forum for this feature request? Votes will direct what is being implemented and considered by the development team. If you send me the link to the Forums Thread I can forward to the development team.
For me - I do have to keep the presets local to the catalogs because of my ADOBE Beta testing.
Once you tipped me to this, I checked out the global system location where your installer was placing the .lrtemplate file and copied it to the External Editor presets folder within my catalog and it picked it up. It’s cycling properly now.
Yes I’m afraid so, this is always the case with new Cameras the only workaround until support is added is either convert your RAW Files to DNG within Lightroom or use the Adobe DNG converter app
Until it is supported you can covert the CR3 file to DNG (still RAW format) and it will work. We can tag you here as well once it’s supported, to let you know you can use the CR3, once supported.