Jump to content
You must now use your email address to sign in [click for more info] ×

Fixx

Members
  • Posts

    3,329
  • Joined

Everything posted by Fixx

  1. So you say merge operations rasterizes to upper layer dpi, not to document dpi? I generally do not merge layers until in export which I think produces acceptable output (but I am not sure does it really uses selected resample algorithm as base document is not resized).
  2. I just (ok, 3 weeks ago) wrote a spec for setting text size for CAD documents... and CAD specifies text size as height of cap size, while office and typographic apps use typographic size which is the ascender - descender measure plus some leading space --- that means typographic size can be anything that font designer specifies for his/her font.
  3. I do not think variable path thickness is available in PDF, SVG or EPS format so it is always converted to a filled path.
  4. Filesize of afpub file or exported PDF? What kind of images you have imported to layout?
  5. If you have image layer instead of pixel layer in your document you have placed images to your document, as layers. If you have selected document resolution wisely it will work OK. In rasterizing image layer the resolution converted to that of document resolution (as I have understood), which may mean that detail are lost if document resolution is lower. If lower resolution layer is then manipulated it is possible to get a lower quality image compared to that if manipulations had been done to original image layer. Anyway, if document resolution is right there should be no problems.
  6. If you do it once a week it is ok. If you do it daily, automated footnotes would save so much time that rental might make sense.
  7. Generally there is no gain in resampling up if images are initially low res. Some exotic tools can invent detail to images but that is still more like art than science.
  8. I would think free transform/warp/envelope tool would help here. It is also not available but it has been asked quite insistently.
  9. I would thing "page colour" IS for coloured paper. If you just want to print colour background for the layout you better use a coloured element at the bottom of layer stack, to remind you the colour is printed. I can think simple "page colour" feature would create a lot of printing problems for inexperienced designers.
  10. AP Curves tool is OK but it is missing some features, like "Auto". I would still prefer to do setting black, gray, and white points in develop module, there setting has to be done with exposure and brightness and blackpoint which are not so easy as exposure and brightness are messing each other.
  11. I would not do professional work with 8 GB RAM, even if it were M1.
  12. Grouping is what I do to keep layers palette tidy. I guess there are more sophisticated solutions for more complicated workflows but for my basic needs grouping is the thing.
  13. Layer > Transform > Flip Horizontal (in AD) Individual letters or selection within text, not as far as I know. I would convert text to curves and select individual path and flip it.
  14. DPI is metadata but anyway pixel images can have physical size defined, in metadata, and thus DPI would have meaning. Affinity chooses to offer pixel resolution resample in AP pixel format export, and DPI resample in PDF export. There is no deep reason why this limitation. Probably most users feel that is useful choice.
  15. It is generally a nuisance when app does not allow copying text. I use little app called Picatext to screen grab & ocr at one go. Very handy, OSX Mojave.
  16. It will not show hires version of original affinity file, only lores preview. There is no sw that can display affinity format except affinity's own apps. Serif is not going to open affinity formats to other developers. I wish though that they would do that by agreement with select DAM developers so that there would be better support for affinity in DAM sector. I suppose option to have larger previews would help also..
  17. This is a funny gem of UI design. Necessary buttons are in Context toolbar, which is not necessary visible/available..
  18. Try New Stack... command in AP. It has perspective correction features (though I am not convinced it is as good as PS).
  19. OP said: Thus, image was rotated to get horizon level. Tilted image borders are revealed when canvas is expanded. Either rasterize after straightening, or cover edges with white (if you really need the white border), or cut the extra area.
  20. The memory warning includes virtual memory. System is jammed because startup disk is full (of Affinity memory leak).
  21. I have too occasionally had memory leaks in Affinity apps. Affinity SHOULD not use more than system freely allocates so RAM preference SHOULD not affect that, but the setting may be connected to problem. Quitting/restarting Affinity resets memory usage which corrects situation. If it is repeated behaviour something is wrong. Maybe setting the preference lower may help.
  22. No, loos like single image layer is rotated. Rotate canvas would rotate everything. I think adding border area just revealed that image layer has tilted edges (=is rotated). As AP is nondestructive cropping canvas and after that adding area to canvas just reveals what was cropped earlier.
×
×
  • Create New...

Important Information

Terms of Use | 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.