Jump to content


  • Content Count

  • Joined

  • Last visited

About 4Lakes

  • Rank

Recent Profile Visitors

480 profile views
  1. I have not tried every tool with every setting, but the following occurs in both Affinity Photo Windows and the beta Some tools that re-set to default values include: Color Picker Radius if changed from 1x1 will reset to 1x1 if the same file is saved & then re-opened or if a new file is opened. Similarly, Flood Select Tool Tolerance if changed from 20% will re-set to 20% if the same file is saved & then re-opened or if a new file is opened. Patch Tool Rotation and Scale if changed from rotation 0 degrees and scale 100% will reset if the same file is saved & then re-opened or if a new file is opened. Conversely, some tools that hold their values after closing & reopening the same or a different file include: Selection Brush Width if changed from default retains the changed value if the same file is saved & then re-opened or if a new file is opened. Burn Brush Tool: Width, Opacity , Flow, Hardness, Length retain changed values if the same file saved & then re-opened or if a new file is opened. I did not test if Stabilizer, Mirror, Lock, Tonal Range, Protect hue retain their status or not. Non-systematic testing of other tools indicates that some re-set to a default value while others retain a changed value. If desired, I can send the rather tedious step-by-step testing that shows the above behavior. I am no expert in Affinity Photo or interface design, but some consistency would be helpful. The ability to set tool behavior (retain vs reset to default when a file opens) either for all tools, by tool groups, or by individual tools would be helpful. An atomistic tool-setting-by-tool setting would be excessive (e.g. a user could set Burn Brush Width and Flow to reset to defaults but Burn Brush Hardness and Length would not reset). It might be desirable for the user to be able set the default values. For example, if you routinely worked with high resolution images, possibly higher default values for some tools would be more convenient. For comparison, in Adobe Photoshop CC the Color Picker radius or Magic Wand radius (which are always in agreement, changing one changes the other to the same value) will stay at the value when changed, they do not reset to a default when the file is closed or a new file is opened. This is different from Affinity Photo's re-setting the Color Picker Tool to 1x1. Similarly, the Ps Patch Tool retains the Structure and Color setting when these are changed.
  2. Mark, Thanks for your prompt response. I was seconding what previous posters had suggested, so best contact some of the earlier posters requesting this tool item.
  3. 1. Double-click on a slider to reset that slider to default/zero. 2. Store history or snapshots of raw development settings in sidecar file. Ironically, the history can be saved for Affinity Photo Persona (unlike Photoshop's inability to do so) but unfortunately Affinity Photo Develop is unable to save the history or at least snapshots (both of which Lightroom can do; even Adobe Camera Raw can at least save snapshots). With Affinity Photo, you have to start over from the beginning even if you just want to change one adjustment. 3. Save settings for tools.
  4. I also tried randomly selected slider settings in the General (including Wet Edges On) and Dynamics panels. The brushes continued to work:
  5. I do not have or use Designer, but in Affinity Photo Beta 1.7.209 the Dirk Wustenhagen Fine Art Texture Collection brushes seem to work as texture. Machine: Windows 7 Professional 64-bit up-to-date per Windows Update, Service Pack 1, Processor: Intel Core i7-3770 CPU @ 3.40GHz, 32.0 GB RAM, Windows Experience Index 7.7 (on a scale of 1.0 to 7.9), Graphics card: GeForce GTX 970 version 385.69 Since there are numerous options for the Brush settings, I am including screen captures of the General, Dynamics, Texture, and Sub-Brush panels as well. I presently rarely use brushes, so these are almost always the default settings in the panels. Perhaps different settings of these panels causes a problem?
  6. I too think the user should be able to choose if lens corrections on an image should be automatic, based on EXIF data, or instead be specified by the user. Mirrorless cameras such as the Sony a7 series cameras are a case in point. There are several electronic adapters that allow non-Sony lenses to use many of the camera's electronic functions. One way this is done (e.g. Metabones adapter) is the adapter identifies the lens in use as an equivalent Sony lens. For example, when a Canon EF 24-70mm f/2.8L II USM is attached via the Metabones adapter, the RAW file EXIF data records the lens as Sony's "24-70mm F2.8 G SSM II". Rather than go through the process of changing data in the proprietary RAW file with the risks of corrupting the file, the user should be able to select the correct lens profile. The short flange to sensor distance in mirrorless cameras also allows use of numerous purely mechanical lenses, some "vintage", some new. For such lenses there is no EXIF data recorded. Once again, the user should be empowered to be able to select the correct lens profile and not be forced to undertake the risk of editing a proprietary RAW file format. Finally, competing RAW processing software allows users to select the correct lens profile. Adobe Carmera RAW allows this. Adobe Lightroom allows this. Capture One allows it (if a profile is available). ON1 Photo RAW 2018 allows it. Affinity Photo needs to keep up with the competition. I made a similar request feature request here some time ago LINK.
  7. Alternatively, at the top click "Document", on flyout menu choose Resize Document (or just use keyboard Ctrl+Alt+I). You will now have choices of exact size to resize to (lock or unlock the aspect ratio), units of the enlargement (pixels, inches etc.), DPI, and Resampling method. The last is important to best preserve quality if enlarging the image. If doing many images, Rick G's suggestion of a batch file is a good one.
  8. Please allow the user to manually choose the manufacturer and lens model as Adobe does in Adobe Camera Raw. This lets the photographer select the correct lens in the lens correction database when the photographer uses a completely manual lens for which the RAW file will not have the data for manufacturer, lens model, f/stop etc. Similarly, when using electronic lens adapters such as the Metabones adapter for Canon EOS lenses on Sony alpha series mirrorless cameras bodies (e.g. a7r2), the Raw file EXIF data has the wrong manufacture and lens model because the electronic adapter must make the Canon lens appear to be a Sony lens model of the same focal length and f/stop. For example, if the widely used Canon 24-70mm f/2.8 L II USM is attached via a Metabones adapter to a Sony a7r2 body, the EXIF data records the lens as a Sony "24-70mm F2.8 G SSM II". The other EXIF data for focal length the zoom was at and exposure f/stop are correct. In Adobe Camera Raw's lens corrections, I can simply select the Lens Profile Correction for the "Canon EOS 24-70mm f/2.8 L II USM" and have the proper lens corrections applied. Similarly, if I use a Rokinon 14mm f/2.8 completely manual, no electronics, lens on a Sony a7r2 body, I can select that Lens Profile Correction in Adobe Camera Raw despite the lack of any EXIF lens data in the Raw file. At present, the only way to have Affinity Photo Develop apply the correct LensFun database corrections is to use ExifTool and change the data in the Raw file before Affinity opens the file. This is both time-consuming and I would rather not tamper with a proprietary Raw file format. Thank you.
  9. I second getting the equivalent of Photoshop's Adaptive Wide Angle. This can be very helpful in retaining nearly all of the image despite doing the corrections of verticals, horizontals, or straight lines by adding horizontal and vertical correction lines around the edges of an image. Thiese "correction" lines around the edges of an image will retain almost all of the image when other corrections are made elsewhere in the image. This can avoid either cropping out edges that are curved or having to fill in the vacant areas with cloning, content aware fill, or inpainting.
  10. Not only that, but the fly-out menu for "Document" has a choice labeled "Color Format". But my version cleverly and correctly defaulted to Preferences, General, Language as English (United States)! :^)
  11. Mark, Progress! First trial of Windows Safe Mode was loaded with network drivers because the file in question is on a network drive (or rather, drives since it is a RAID). Document, Color Format, 32-bit RGB to 16-bit RGB had the same multi-minute 100% CPU utilization until I ended the task with Windows Task Manager. Thorough person that I am, I then copied the problem file to a local disk and re-booted but in Windows Safe Mode without network drivers. The 32-bit to 16-bit conversion completed in several seconds. Closing the file without saving it in 16-bit and then re-opening the 32-bit file worked a second, third, etc. time consistently! Next I rebooted Windows 7 Professional 64-bit in its standard mode. In short, Affinity did the 32-bit to 16-bit RGB color format conversion in 1-2 seconds consistently and repeatedly as long as the image file was opened from either of my two local hard drives (I did not try the local SSD drive C:). Every time the image file was opened from the network drive, it was 100% CPU utilization for minutes. When you successfully converted the file from 32-bit to 16-bit without problems, was it on a local drive or a network drive? I will send you details on the network and RAID as soon as I contact my son, the IT professional, who set up and maintains the network and drives. Is there anything in particular you would like to know about the network architecture and the RAID drive? I know the drive sends a text message to him if any problems are detected and has been up and running at least 2 years without problems. It is used by multiple programs including Photoshop CS6, Lightroom 6, Bridge, Adobe Acrobat, LibreOffice, Capture One 9 and now 10, Luminar 2018 (as limited as the current Windows version is), VueScan x64, Firefox, Internet Explorer, NikonScan 4 (modified driver to get that to work under Win 7 64-bit), and Zerene Stacker 64-bit (focus stacking program). Essentially all non-program files are stored on the network RAID including Lightroom's backup catalog (my son got that to work on a network drive despite Adobe stating it can not be done). Regards, Jim P.S. This accounts for why, in my previous post, the 32-bit to 16-bit conversion worked on a file that was not yet saved. When I saved the file on the network and then re-opened it, conversion took about 8 minutes.
  12. Mark, Well this is frustrating. I opened the file and tried the 32-bit to 16-bit conversion and it again took minutes (I used End Task in Task Manager after a minute or two). Since Affinity can not have every possible combination of operating system, CPU, graphics card, etc. I went to Edit, Preferences, Performance, Renderer and changed from the NVIDIA GeForce GTX 970 to WARP and restarted Affinity Photo. Opened the file and again 32-bit to 16-bit took minutes before I again used End Task in Task Manager. Could you check on your end if changing the Renderer to WARP should take the graphics card out of the conversion and thus rule out the GTX 970 as a possible source for the problem? I also updated the graphic's card driver but problem remains. I deleted all the layers from the file, problem remains. Is there anything I can do on my end or send to you that would be helpful in troubleshooting this? Task Manager offers the option of creating a Dump File (1.47 GB) which I could send to you or I can take screen shots of any of Task Manager's tabs (Processes, Services, Performance; I doubt the Networking or Users tabs would help). Regards, Jim
  13. Mark, A problematic file #2 is being uploaded to the dropbox link you provided as I type this. This file #2 is a new one I made using another 5-shot bracket from the same photography session using the same camera. I did the complete process from opening the 5 RAW files for HDR through adding the masked curve adjustment layers and a B&W layer in one session today. Interestingly, after I had done all the processing on file #2, I tried the Document, Color Format, RGB 16 conversion and Affinity Photo did this in a few seconds. Puzzled, I closed file #2, opened the previous problem file #1, did Document, Color Format, RGB 16 conversion and, as before, this took several minutes with the CPU at near 100%. I thought to send you both this original file #1 and the file #2 I created today but then I thought to close file #1, re-open file #2, and try Document, Color Format, RGB 16 conversion a second time. This time the conversion took several minutes, just as file #1 had taken. Thinking over what might have some bearing on this different behavior, I think I used the History panel to go back to the 32-bit version after the initial rapid conversion to 16-bits. I am certain I did NOT use the Document, Color Format menu to convert the 16-bit back to 32-bit. I also had one crash while working on file #2. This crash has occured several times before and is associated with deleting points on a curve adjustment layer. As before, I sent the automatically generated crash report to Affinity with my email address. Unfortunately, I am not certain if the crash was before or after the initial rapid 32-bit to 16-bit Color Format conversion of file #2. If needed, I can go through another 5 bracket RAW to 32-bit HDR, add some curves and a B&W adjustment layers, and then try Document, Color Format, RGB 16 conversion. This time I will save the document with the File, Save History With Document option that I just noticed today. Perhaps having the history of the process will help you find the problem The uploaded file #2 is named _1120304-308, 32bitHDR.afphoto. Regards, Jim
  14. Can do but the .afphoto file is about 225 MB and I do not want to upload it to a public forum. I recall Affinity can set up a DropBox or something similar which would be OK. Please advise, but I need to get some sleep first. Thanks for the very prompt response.
  15. Summary: The image is 4988 x 2814px, 14.04 MB, 7 layers: 1 background pixel layer, 5 masked curve adjustment layers, 1 B&W layer in RGBA/32 (HDR), ProPhoto RGB (Linear). Using Document, Color Format to convert this image in 32-bits to 16-bits RGBA/16 - ProPhotoRGB takes over 8 minutes of processing time on a relatively well-spec'ed machine. Adobe Photoshop CS6 using the same image in 32-bits, similar number of layers and same color space to 16-bits in same color space takes about 5 seconds. Affinity Photo takes an inordinately long time that is not acceptable for the workflow. Details: The machine: Windows 7 Professional 64-bit up-to-date per Windows Update Service Pack 1 Processor: Intel Core i7-3770 CPU @ 3.40GHz 32.0 GB RAM Windows Experience Index 7.7 (on a scale of 1.0 to 7.9) Graphics card: GeForce GTX 970 version 385.69 NVIDIA Control Panel reports (see attached PNG) More details on machine in attached PNG. Disk C: is a SSD and has both Affinity Photo and Adobe Photoshop CS6. The software: Affinity Photo RAM Usage limit 25,599 MB Renderer: Default (NVIDIA GeForce GTX 970) Adobe Photoshop CS6 64-bit, using the NVIDIA GeForce GTX 970) Using Photo Affinity's Document, Color Format, RGB 16 bit it takes slightly over 8 minutes to have hourglass disappear and the RGBA/16 - ProPhotoRGB to appear. During this time Windows Task Manager reports (see attached PNG's). CPU utilization by Affinity Photo is essentially 100% during this time. Trying 32-bit to 16-bit conversion on the same image in the beta version (Beta) does not result in Task Manager reporting "Affinity Photo (not responding)" but if anything the conversion takes even longer at about 8 minutes 55 seconds. Doing this 32-bit to 16-bit conversion of same image and same color spaces in Photoshop CS6 takes about 5 seconds of processing time. Machine Info 1.pdf
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.