DeepDesertPhoto

I do have Brave, but I only use it with sites that Safari has a problem with. You would think that an expensive Apple product would not have these issues requiring the use of a 3rd party browser.

Thanks. No point in keeping a program I don't use anymore, especially since AP1 is consuming 2.63 GB of space on the drive. By the way, sometimes I have to reply twice to get my reply to show up on the thread. Is that a problem with the forum or could it be related to my browser. I am using Safari.

I don't know if this has been answered yet in other threads, but I was wondering if removing AP-1 from my MacBook would cause problems for AP-2. Since I have upgraded to AP-2 I have not used AP-1 for several months. AP-1 is showing as a separate program in my applications list but I want to make sure it is not interconnected with AP-2 in some way before I remove it.

On another note, I viewed the photo I first uploaded at the beginning of this thread in the two different Apple display settings and I can see a difference between the factory default and the P3-D65 photography setting. The banding does appear to be reduced in intensity when viewed with the P3-D65 setting.

Unfortunately all of the development settings I used in AP1 got erased when I used Time Machine to migrate it to my new Mac, and I cannot remember all of the settings I used for the Development Persona. However, I can tell you that when I exported to JPEG I used Lanczos (Separable) compression to preserve the original details with sRGB embedded in the JPEG profile so that it would be compatible with the websites I display them on. I used this JPEG export setting for both AP1 and AP2. I have been thinking of removing AP1 since I am now using AP2 with new custom settings. The only reason I haven't done it yet is because I was not sure it AP2 would be impacted. However, while I was waiting for a response to my last reply to your first suggestion, I watched a couple of video tutorials on the new Apple Liquid Retina XDR display, and it appears that this new display does have an effect on how color dependent images are displayed. According to the tutorial the default setting can cause problems with white balance and contrasts. The tutorial said that if you are working on color intensive workflows, such as camera raw photos or illustrations, it is best to turn off the "True Tone" feature of the display. That feature actually adjusts the white balance based on the ambient light in the room. That can be a problem when trying to determine the true white balance of photos. The tutorial also showed what display presets might be useful for certain workflows. For example, while I am working on photo editing with AP2 I set the display for a preset labeled "Photography (P3-D65)". I also customized this preset by going into its settings and activated the HDR processing. It did seem to have an effect on the way the images displayed. The banding is still present, but with the P3-D65 display setting it is reduced to more acceptable levels, and is only visible in certain darker shades of blue instead of all blue color like before. There is one drawback to this setting, however. It locks the display so that you cannot change the brightness of the screen. So when I am done editing my photos I have to go back into the presets menu and reset it back to the default so that I can turn down the brightness when just surfing the web or checking email.

I tried your suggestion but it had no effect. I have been using AP since 2017. However, in the past I was using it on a 2012 MacBook Pro running High Sierra. AP2 was not compatible with High Sierra, but when my older Mac developed a drive problem I went ahead and upgraded to a 2021 MacBook Pro 16 inch running Ventura. This was when I decided to try out AP2. When your suggestion had no effect I decided to take a look at some of my older photos that had been processed with AP1 on the older Mac. I immediately saw the same banding in blue skies that was not visible on my older Mac. I checked the specs of my newer Mac and it uses something called a Liquid Retina XDR (Extreme Dynamic Range) display. This is a higher resolution screen when compared to my older Mac and I am wondering if it could be causing the problem by revealing banding that was simply not visible on the older screens. Could this be a possibility, and if so is there a way to fix it?

I am using a MacBook Pro 16inch 2021 running Ventura. I used to have the output color profile for AP1 set to Wide Gamut RGB Linear and Wide Gamut RGB Calibrated for 32 Bit HDR. When I applied those same settings to AP2 I noticed that some colors did not seem quite right and I was getting highlight blowouts when exporting to JPG with sRGB embedded profile. I switched to ProPhoto RGB Linear for 32 bit HDR and that eliminated the highlight blowouts, but now I am getting a faint banding effect in blue skies when I export to JPG sRGB. I do not see this banding while developing the camera raw file or when I export to a 16 bit LAB Tiff file. It only occurs when exporting to JPG sRGB. I have tried various methods of smoothing this banding out but nothing has worked, and since I did not encounter this problem in AP1 I am suspecting another bug in the software related to how it compresses JPGs. I have noticed that the file sizes for my JPG exports in AP2 are smaller than AP1 by as much as 10 megabytes even though I have the JPG compression set to 100%. Could this be a problem with the way AP2 is creating JPGs from the camera raw images? I have attached an image to illustrate the banding in the blue sky.

Since I live in Arizona I have my camera time set to Mountain Standard time, so I'm not worried about other timezones. But as long as the fix will allow the original timestamp created by the camera to be displayed in the EXIF data, that is all I need.

Hopefully the problem will be fixed in the next update for AP2 because it was displaying normally with AP1.

My first attempt to upload this file failed so here is a 2nd attempt. Please let me know if it has uploaded correctly. _DSC4083.NEF

Sorry I missed your reply. I never got an email notification that I got more replies to this subject even though I have the "Follow Topic" turned on. Maybe a glitch in the system. Anyway, was this problem fixed? I currently have AP 2.0.4 and my latest Nikon pictures still show a 7 hour difference between the time it was taken by the camera and the time displayed by AP. I am using a Nikon D810 camera body. Do you still need one of my raw files to study?

I went to the assistant preferences and it was set to 16 bit. I changed it to 32 bit and that did fix that problem. I forgot about that function since it has been a few years since I needed to open it. Anyway, thanks for the assistance on that color bit depth issue. Now I only need to wait until the timestamp problem is fixed with an update.

I just upgraded to AP2 earlier this week and just started using it today. I am running it on a new 2023 MacBook Pro with Ventura OSX. I am very impressed with the quality of the image processing, but it might have a couple of bugs. The first thing I discovered that might be a bug is the timestamp of my raw photo in the metadata window is 7 hours off the actual data. The date of the shot is correct, but the time of day it was taken is 7 hours off what is displayed. I have uploaded a screenshot with the metadata window circled in red. The time displayed is 3:45:43 AM. The actual time the shot was taken was 10:45:43 AM. A 7 hour difference. The time in the camera is set correctly for where I live, and I double checked it by opening the same raw file with AP version 1, and the time stamp displays correctly with version 1. So if AP2 is displaying a timestamp that is 7 hours behind the actual time taken that must be a bug in the way it is reading the metadata. I am using a Nikon D810 camera. The 2nd issue I discovered is that when I click the develop button for developing a raw photo the color bit depth drops from 32 to 16. That did not happen in AP1. Since I need it to remain in 32bit color after clicking the develop button I have to manually convert the color depth back to 32 by going into the Document properties. I did not have to do that with AP1. So is that also a bug, or is this drop in color bit depth normal for AP2?

I'm still using High Sierra. The problems I reported back in 2019 were fixed with the latest update. Since you're using Catalina you may have to wait until an AF tech can help you because I am not having any problems right now.

A while back I asked if the 96 PPI resolution for panoramas, stacks, focus merge, and HDR merging would be fixed so that the final rendering would reflect the original 300 PPI of the source images. I noticed that it has been fixed when rendering panoramas using the TIFF format for the source images. However, I just tried to render a panorama with the source images being in the Radiance (HDR) format and the finished resolution of the pano was 96 PPI even though the source images were 300 PPI. Is this just an oversight by the development department or is it a bug? Just wonder, because even though I don't use Radiance or EXR formats often it is annoying to have to manually reset the final resolution to 300 PPI before doing my final editing. I mostly use Radiance and EXR for stacks and focus merging. I did a test and found that when using Stack or Focus merge I get the same 96 PPI resolution on the final rendering. Although this is not a priority fix I was wondering if this would be remedied in the next release so that when I use EXR or Radiance formats the final rendering will be the same as the source images.

Yes, MEB, I already know about the Beta version. I have been using it to work with my LAB color files. But it is an extra step in my development process since all of my custom presets are on the main program. Hopefully you will have the new update out soon.

LAB does have some advantages over RGB. LAB was originally invented to mimic the colors perceived by the human eye. Although I am not creating vectors like you I like to archive my finished images in LAB color for printing purposes. When I print with my LAB images I find that the colors of the print are visually identical to what I see on the screen. When I used to print in RGB mode certain shades of red and blue would never look come out right in the print. As MEB said in his reply there is a Beta version that can handle LAB color. I don't have Design or Publisher, but if you are getting the same crash when it tries to export or open a LAB color file then the problem is in the base coding of the program, so make sure to keep sending in those crash reports. They can't fix it if they don't know about it.

I have been exporting my finished images as TIFF 32 Bit HDR files to preserve all the color and details of the Camera RAW image after development. I then use the Beta version to create 16 Bit LAB for final archiving. The reason I don't use the Beta version to do everything is because all of my custom presets are on the main program. Using the Beta version to export a Lab TIFF from the 32 bit HDR TIFF is an extra step, but at least the Beta version enables me to complete the work. Hopefully they will have an update soon that corrects these problems in the main program so that I don't have to keep using the Beta for the final export step.

I don't have Design, but if it uses the same base coding as AP for its export functions then it might be the same problem. I downloaded the Beta version of 1.9.1 which is able to open 16 bit LAB TIFF. You'll have to contact a moderator to see if there is a Beta version for Design that has this problem fixed.

I don't have Publisher or Design. All of my work is in photography and photo-manipulation. I also do some digital painting. So Affinity Photo is all I am using right now. I know it takes time to fix the multitude of bugs but any idea as to when the next update for the main install will be ready? Just wondering.

Since the new update to fix all the bugs in AP 1.9.0 is not out yet I have been using the beta version for specific tasks that I cannot do with the main program due to the bugs making it crash. But I have noticed that I cannot create any export presets with the beta version. For example, when exporting TIFF 16 bit Lab the default preset uses ZIP for the compression, Bilinear for the resampler, and "whole document" for the ICC profile. I normally change the resampler to Lancsos 3. I normally change the compression to "None". And I normally change the ICC Profile to CIELAB D50. In the original program I had these settings saved as a preset so that I would not have to manually make these changes every time I wanted to export to this TIFF format. When the 1.9 update was installed that was when the bugs caused the program to crash when using the preset I created or trying to open images created using that preset. When I downloaded the Beta version I thought I could create the same preset so that I could continue my work while waiting for the official update with the fixes. However, when I tried to create the preset with the alternate settings the "Add Preset" would not highlight when I clicked "Manage Presets". Is this due to it being a Beta version, or is this a bug in the Beta version. If it is a bug I hope it is fixed when the new update is ready because not all the default export presets work for me and I need the ability to save the settings I create.

I don't know if this has been asked yet, but I downloaded the AP 1.9.2 beta and when I opened it the program asked me to register it. I bypassed that message since I wanted to see if the problems I reported in 1.9.0 were truly fixed. But I was wondering, if I do decided to register the Beta version will it interfere with the main program already on my Mac? I was also wondering if I can keep the Beta version on my Mac to use as a backup in case I have further problems with the original program I bought?

I don't normally use beta programs because there might be other bugs. I'll wait for the next update release.

I had to run your comment through a translator, but if I understand you correctly AP 1.9 is pretty buggy. I just sent tech support a file that causes the program to crash. Hopefully they will find the problems and send out another update with corrections as soon as possible.

Just in case you might need the info I have included 2 screenshots of the LAB presets. One screenshot is of the original builtin TIFF LAB 16-bit preset. The other screenshot is a custom preset I made in which is changed the resampler, the ICC Profile, and the compression. Since the program crashes when trying to open a file made from the custom LAB preset this info might by relevant. Any questions or if you need another file for comparison let me know. I do need this problem fixed as soon as possible because if I cannot open the files with AP I cannot print them for my work.