Jump to content

mattspace

Members
  • Content count

    13
  • Joined

  • Last visited

  1. Just bumping this topic, this issue is still present in 1.7.1. Any feedback on whether it's likely to be addressed? Thanks.
  2. Hi Gabe, There's no .afphoto file, but the pdf is attached here. cheers. text_042.pdf
  3. Hi, A hiccup in trying to use Affinity Photo in my pdf-to-EPUB processing workflow, in which all my text is being exported from my layout app as transparent background pdfs, to be converted in AP to png and resized. Every text box that has a feathered edge, is getting a hard outline at the outermost extent of the feather - ie where the feather is transparent. This same effect doesn't appear to occur in Photoshop. It occurs in AP with either a batch processor, or opening a single file. Attached is a comparison of the same file opened in both Photoshop and AP, with the same dpi and size settings for rendering. (the photoshop file has a layer of white added behind, to show up the lack of artefact. A white feathered box gets a white bounding outline. Any thoughts? (edit - genuine textbox from the book, not a statement towards the any reader of this ) thanks.
  4. Woot! Much appreciated. Absolutely fixed it - that's an interesting solution, given all the input files canvasses were the same proportions, my gut feeling would be aspect ratio wouldn't have an effect. Anyway, you've just saved my production process literally hours of work every day. The options I had for processing 260 pages of a document were: an older version of Photoshop, which did each file one at a time, and never used more than 150% (out of 1200%) CPU, or using a macOS Automator action - except the native Mac pdf renderer puts left / right, red / blue fringing on all the text which doesn't rotate with the file, ie it stays on the screen left and right, when you rotate the document (and it doesn't show up in Safari), and more importantly, it bakes that colour into the page when you use the system libraries to convert to png. Affinity Photo drives all 12 (physical) Xeon cores to ~100% to do the batch in about 10 seconds, but I couldn't get the consistent dimensions - now solved. Cheers for the fix
  5. Hi, I'm seeing an odd issue trying to use AP to batch process a whole bunch of .pdf files. All the pdfs are the same dimensions and resolution, but when i run through a batch job to open and save them out to a different target pixel dimensions, some pages will end up several pixels out. If I look at the pages in Preview, there doesn't seem to be anything different about them, or if I open / rasterise them in Photoshop, there's no difference. If I open the files on their own in AP, choose their native 300 dpi, then go to resize canvas, all of them show a native size of width: 2007px, height 3070px. BUT if I use batch to process the files, with a target output size of 2007x3070px, some of them will be sized differently by a few pixels in either width or height. If I turn off all the content layers in InDesign before outputting (so that it's just the background colour of the master pages), then AP batch seems to output a consistent size, so I think the batch process is using a content box of what's on the page, rather than the crop box for the page itself (to use Photoshop's description of rasterising options). Attached is the file to try it with. It ends up as 2003x3070 when batched to png or any other format, but when opened, it's 2007x3070. Any ideas for how to get this consistent? page.P006.pdf
  6. Hi, Feel Free to merge this if anyone else has asked, but is proper 10 bit display output to get non-banded gradients currently possible with the colourspace options, or is it on the roadmap? I know Affinity Photo (Mac) doesn't seem to support it yet (hoping it arrives there soon).
  7. Likewise, I produce Fixed Layout EPUB graphic novel / photo books content for Apple's (i)Bookstore, and while Apple's Pages appears to have added a FXL EPUB option, it doesn't have the layout capabilities of a full-fledged DTP app. At the moment, my workflow is DTP in InDesign (CS5), output to uncompressed jpeg, process in photoshop to correct size and format, then handcode pages. An ability to output to EPUB, with user defined templates for how the app places content (eg images as background textures for DIVs defined in CSS), how elements are named etc, would be pretty special.
  8. i... i'll be over there, looking sheepish *facepalm* cheers.
  9. Hi, A simple request, I'd like to be able to tear off the main tools palette, so that it's not part of the document window. I'm super impressed at how much of the UI can be undocked - it makes life with a triple display system (main document display, with portrait displays on each side for palettes) much more productive, but if I could get that tool palette out in its own window, that'd be really sweet. Looking good from the POV of an old Quark & InDesign operator.
  10. Add a +1 for me on this - user looking for new solutions to CS-era Photoshop, InDesign, and Aperture. Serif's products look VERY nice. Aperture's strengths of quickly triaging large numbers of files, batch adjusting, batch keywording and organising, don't really seem to have been bettered. What really does it for me is all of the adjustments / retouching being applied as metadata & versioning - every solution I've looked at seems to want me to flatten my adjustments out into extra TIFF files (which are about 120mb each, as opposed to 30-50mb RAWs). Apple has even dropped the ball on Photos.app with 3rd party plugins still being destructive edits on flattened files. The one thing about Aperture I don't like is it being over-protective of the original files - even for things like rotating - sometimes the camera gets the orientation of an image wrong when shooting up or down, and Aperture can't rotate the original. It needs an "unlock to edit original" function.
×