Jump to content

Greyfox

Members
  • Content Count

    166
  • Joined

  • Last visited

About Greyfox

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

444 profile views
  1. When I open an image in Affinity Photo, it opens by default "Zoomed" to fit (and I'm not aware of any setting to change that default) For a 4032px x 3024px image, that is zoomed to around 25%. DPI doesn't come into it, that value is for print purposes. (Yes, changing the DPI will affect the width/height as displayed on the rulers, but doesn't affect the way the image is displayed on the screen. "Zoomed to fit" will give exactly the same displayed size for any given image regardless of what you set the DPI to.) A computer monitor has a fixed number of pixels. On my 21.5" monitors that is 1920px x 1080px. The monitors have a pixel spacing of 99 pixels per inch, so at 25% zoom, my 4032px wide image will display physically about 10.18 inches wide. At 25% zoom effectively one out of every 4 pixels in the image is being displayed. I can of course zoom the picture to say 100%,, which will then display all of the pixels, but then only a portion of the image can be seen at any stage without panning.
  2. David, Your image is opening OK here in Affinity Photo 1.8.5.703, on Windows 10 Pro 2004 build 19041.572 and as you can see from the Task Manager insert, with a number of other apps open. The PC here has 32GB RAM, and the graphics card is a 6GB GTX1660. What are the specs of your PC.
  3. @Martin Palecek Windows 10 Pro, 2004 build 19041.508, 10Gen i7-10700 CPU with H470M chipset, GTX1660 OC, Affinity 1.8.5.703 For what it is worth, I'm using the latest Nvidia 456.38 game ready drivers, with Affinity Photo renderer set to GTX1660, and not having any issues with Sony .ARW raw images, including your DSC02455.ARW image.
  4. @Mike Webb In retrospect, my post missed the point. My problem or lack of understanding stems from the way I used the histograms in the old Serif PhotoPlus series. For an RGB Image in photo persona, my understanding is that the histogram in the curves pane simply shows a static mono display representing the combined RGB spread from shadows through mid tones to highlights, rather than it showing lightness. In the old Serif PhotoPlus series the static histogram in the curves pane closely matched the main histogram when that was set to display combined RGB, so to me the main histogram was able to provide the same starting point information as the static histogram in the curves pane, but also showed live the result of changes to the curves. So for me, the static histogram in the curves pane was sort of superfluous. In Affinity Photo, the main histogram isn't able to be set to show a single display of the combined RGB spread, or to show lightness as was possible in PhotoPlus. As I understand it the lighter blue only shows the overlap between R, G and B) and so I can't see the result of changes to the curves in the main histogram in the same way as I could in PhotoPlus.
  5. @Gabe Hi Gabe, OK, with no selections, can you tell me what the purpose is of having the histogram in the curves pane, when it doesn't respond to changes made to the tone curves?.
  6. I think it is a bug, but I actually don't see much if any benefit of the present histogram in the tone curve display. I refer to the main histogram when using curves.. The histogram in the curves pane doesn't change to reflect any changes made to the tone curve itself. (I seem to remember something about that being by design, but I really don't understand why that should be) and it doesn't appear to represent the condition within a selection like the one in PhotoPlusX8 did. I think there have also been issues raised in the past as to why it isn't in color in the Windows version, and why it can be really slow to appear (when it does appear). Maybe someone could explain to me exactly what it's purpose is meant to be.
  7. @Mike Webb With selections seems to be a bit hit and miss as to whether the curves histogram is shown here too, as can be seen from the two screen shots. Edit: Also just noticed, the curves mask icon in the second screen shot doesn't appear to be showing the selection.
  8. @Mike Webb Mike, for the image in your first post, what Nik plugin was involved. I have Nik Collection 3 here I can try.
  9. @Mike Webb Doesn't seem right that the two histograms are so different. That is not happening here in v1.8.5.703, see example. Windows 10 Pro, 1909 build 18363.1082
  10. @OhGee, The normal procedure for borderless printing is to size the image in the editor to exactly the size of the photo paper. When the "Borderless" box is selected in the printer driver, the printer itself actually prints the image slightly larger than the paper size, which results in some cropping, but edge to edge printing. So for example, if your paper size is 8.5" x 11" then I would expect you should be sizing your image to 8.5" x 11" in your editor. What confuses me a little is that when I look up the specifications for an Epson FX-8500 photo printer, it says "True BorderFreeâ„¢ printing is only available for media sizes: 4" x 6", 5" x 7" and A4,. Perhaps an FX-8500 is different to an 8500.
  11. Hi @Dan C Well this is rather embarrassing. The second part of the above statement is correct (in so far as the editor mentioned in the example is concerned), however despite my feeling that the plugins were taking longer to open in the latest version of Affinity Photo, my tests today showed there was actually no significant difference in the opening times of the various plugins between 3 earlier versions of Affinity Photo and that in the current 1.8.5.703 version. Each time in the table below was the best of three opening times of each plugin from the particular version of the software, and taken from the time the plugin was selected to when the image appeared in the plugin.
  12. Hi @Dan C The only plugin I have other than Topaz is Luminar 4 and the difference in opening time for that between Affinity Photo and ACDSee Photo Studio Ultimate 2020 is not quite so pronounced (14 seconds versus 9) as for the Topaz ones. The Topaz AI plugins at the moment seem to be being updated every second day, which introduces another variable, however the older Topaz plugiins (Denoise 6, Remask 5, Adjust 5) which have not changed for a long time are also taking up to 5 times longer to open in the current version of Affinity Photo than they do in Photo studio Ultimate. I'm hoping to get some time later today, and I intend to install some of the older versions of Affinity Photo and to do some comparisons.
  13. Whilst they are working, It seems to me that Topaz plugins are much slower to open in Affinity Photo 1.8.5.703 than they were in previous Affinity Photo versions and they are certainly much slower to open from Affinity Photo than when used as plugins from other host editors. As an example: On my PC, it takes 16 to 17 secs from the selection of the plugins (Denoise AI v2.2.9, or Sharpen AI v2.1.5) to when the image is open in their screen, where as it takes only 4 to 5 seconds when they are used as plugins from ACDsee Photo Studio Ultimate 2020. Test image 4034 x 3026px JPG. PC details are Intel i7-2600 CPU @ 3.4GHz, 16GB RAM, GTX1050ti 4GB Graphics adapter. Windows 10 Pro, 64 bit, v1909 build 18363.1049 I've tried resetting the links to the plugins in Affinity. Is this a known issue, and/or does anyone have any suggestions that might reduce the opening times.
  14. Chris, can the 1.1 folder then be deleted?
  15. Chris, I did say in the opening post that getting to that size was the result of an error on my part. I certainly can't think of any circumstances where I would normally want to export a JPG of that size. I see the issue firstly as whether Affinity Photo's JPG export process should be using the amount of memory it is, and then secondly whether a future version could provide a more graceful termination, even if that means applying some limits (maybe based on available memory).
×
×
  • 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.