Jump to content


  • Content Count

  • Joined

  • Last visited

  1. This is a problem I've experienced occasionally over various versions of AP. It's random, but today it happened three times. Not sure what's causing it, and I can't seem to pinpoint — let alone solve — the issue. My workflow is to use TIFF files saved from my RAW developer of choice, DxO Photolab 4. I open those TIFFs in AP, add a number of layers, then re-save it as a TIFF by pressing "Cmd-S"; on the first save, it presents me with the option of "save with Affinity Layers", which I always choose. After that initial save, as I'm working I save periodically by pressing Cmd-S. Here's the problem: on occasion, AP will save that file and collapse the layers into the background pixel layer. When this happens, the file size shrinks from, say, 250mb (or more) down to 80mb (or less). The problem is that it doesn't necessarily include all the layers, leaving me with a file that often doesn't reflect some of the time-consuming edits I've done. I've been trying to diagnose the problem by deliberately triggering the behavior, but as yet haven't been able to. I'm not opening the TIFF in any other application other than AP, at least until I'm finished with it. The collapse always happens when I've used AP exclusively to open and save the file. Running 10.14.6 on an iMac; AP version is 1.8.4, but this has been happening over all versions in the last year. (I'd rather not save as a native AP file, because my DAM solution (digikam), along with some other apps, doesn't recognize Affinity files. It would also require a convoluted save process and increase the amount of space to keep both the TIFF and the AP file. This is an internal AP problem, not one of an interface with any other app.)
  2. Thank you for this! From your test protocol I noticed a discrepancy between your workflow and mine, which allowed me to isolate the problem a bit further. When I open the TIFF in AP for the first time, I do not Export it — I simply save it (CMD-S on a Mac), because it's already an open TIFF file and I'm simply re-saving it. When I do that, the metadata is stripped. Editing the metadata, re-opening, and re-saving it again strips the data. If, however, I Export it as a TIFF (which is a PITA because it doesn't default to the source directory the way Save does), it retains all the metadata. If I then re-open that same TIFF file in AP, make another change, and then Save it as I'm accustomed to doing, the metadata is, again, retained. It seems, then, that in order to retain the metadata the first save with Affinity layers must be done via Export, and once done the file can be opened and saved at will. This appears to be a bug rather than a feature issue as I first surmised. It would be interesting to see if you can replicate this behavior in your Windows environment to determine if it's a Mac-only issue.
  3. Spotlight indexes (which are built from the data in the document/file) are a different matter. EXIF/IPTC data most certainly is stored in the image file and goes with the image wherever it is moved.
  4. I've searched the support forums and found a variation of this problem going back to 2016. I make extensive use of the metadata fields (both native Mac and the standard EXIF/IPTC fields) in cataloging photos. My workflow is to shoot RAW and develop those raws in a separate application (DXO), generating a TIFF file. I then catalog those TIFFS, add metadata (using NeoFile) and keep them until such time as I need to work on them in AP. When I open the TIFF in AP and edit it, I always choose to save it as a TIFF with AP layers. This gives me compatibility with other apps that I may use later. When I save that edited TIFF, however, all of the metadata I've added is stripped from the file. (Yes, I've tried "embed metadata" both on and off.) After much experimenting I have failed to find a combination which allows me to save as a layered TIFF and retain the data. Problem persists even in the 1.70 Beta. This seems like a basic functionality issue, so I can't believe it would be unresolved for several years. Am I missing something in my workflow?
  5. Further information: it appears to be Live Filter layers that are the culprit. Without any live filters, save times are fast — 10-15 seconds. Add one live filter, and the time jumps to a minute to a minute-and-a-half. With two live filters, it's a minimum of 2 minutes, and 4 minutes is common. Both also have horrendously high CPU use. Again, this was never an issue with the last v1.5.x
  6. Recently updated to v1.6.6 from the last 1.5.x version. Using a 27-inch Late 2013 iMac with 16gb memory, running 10.12.6 With this version, routine operations like file save/export have become EXTREMELY slow. I save the files I work on in layered TIFFs, with a typical file size of ~350mb. In the last 1.5.x build, these files would save (or export to TIFF) in about 30 seconds; with v1.6.6, file save times have jumped to an average of almost 2 *minutes*, with occasional save times of more than 4 minutes! What's more, the save times are very inconsistent; on the same files, successive saves can double with no apparent reason. During these long saves, Monitor reports Photo running up processor use to 700%! In addition, live filter updates have become slow as well — sometimes taking nearly a full minute to completely finish application. In the old version the same operations, on the same files, took perhaps 5 seconds. (These times are on files which I use regularly and am familiar with their performance.) I was excited about the 1.6 update because of the claimed improvement in performance, especially with large files, but it's actually become unusably slow. Is it possible to download the last 1.5.x version and use that until issues with v1.6.x get worked out (if they ever do)?
  7. Thank you - rasterisation was the step I was missing. Here is the resulting workflow: 1) Crop image as desired 2) Merge visible layers 3) Uncheck all except the merged pixel layer 4) Rasterise that layer 5) Change the document size to the desired dimensions 6) Change the canvas size to the size of the paper I'm using 7) Move the merged pixel layer around the paper until I have the placement I need (Just to be clear: Affinity Photo's printing functions need some serious work; they're woefully behind what the competition offers.)
  8. I'm having a bit of trouble figuring out how to print a section of an image to specific dimensions. Let's say I have a picture which I'm cropping to a specific ratio; the cropped area is significantly smaller than the full document, is of a different ratio, and is off center. I want to then print that cropped section to a specific size on paper (to fit within the window of a matte.) How can I achieve this? Setting absolute dimensions (say, 7.6x9.6 inches, which is the matte's opening) makes a crop that is much tighter than what I want. Resizing the canvas to the specific dimensions produces the same result. Resizing the document is hit-or-miss, because I have to guess at the resulting size to get the cropped area to the dimensions I want. I can print the cropped area and specify sizing in percentages, but again I have to guess as to what percentage gives me the size I want. All I want to do is make a crop, then tell AP to print that crop to a specific size. This is easy to do in Aperture or LR, but seems devilishly difficult to do in AP. What am I doing wrong?
  9. Here's one I grabbed at random which illustrates the problem. _1040060.tiff
  10. I have an extensive background in conventional film processing and printing, but I'm still relatively new at using Affinity Photo. I'm digitizing a large number of color negatives using a macro lens on my camera. My procedure has been to white balance on a blank piece of the film to zero out the base color layer of the negative stock; this is conceptually identical to the old days, when we "balanced" roll and package printers for each type of negative being printed. This method works extremely well, giving me a negative that with just a little massaging in Affinity Photo (channel levels and whatever individual color balance adjustments the individual frame may need) produces a print that is at least as good as what I used to be able to get in the darkroom (or on my various roll printers) -- sometimes better. However, I have encountered a problem: I'm digitizing a bunch of negatives from a very different color stock, but none of them have a big enough piece of the base layer for the camera to white balance; all I have is the blank area between frames. I've tried manipulation without neutralization, and although I can get an acceptable print it's never as good as what I've gotten with my regular method — and it takes far more time. What I think I need to do is sample the base layer color, invert it, and use that as a filter to neutralize the base color so that I can do my other manipulations. How can I do this in AP? Thanks!
  • 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.