Jump to content


  • Content count

  • Joined

  • Last visited

Everything posted by Lagarto

  1. Export as PDF/X-4. It keeps K100, or create the PDF (print) file without including the color profile (since it is the color profile that converts your K100 to rich black).
  2. Lagarto

    PANTONE Guide

    This is a bit late post to this thread, but as I have just exported up-to-date Pantone colors from Pantone Color Manager created Illustrator and Photoshop .acb files, first exported as .ASE files from these apps, and noticed that there are slight differences compared to equivalence color values in Adobe apps (in the same environment, and using identical color profiles), I wonder if Lab values are supported at all in .CVS files. As I went throught them it seemed they all contained just RGB definitions (and CMYK, when relevant), while the .ASE files seem to have Lab definitions. Not a particular problem, though, as I just read that the Affinity apps will soon have up-to-date Pantone libraries, but just considering any other or future conversions. So the question is: if .csv files only take RGB and CMYK definitions, are they supposed to be in certain color profile (like sRGB for RGB and certain color profile for CMYK coated and uncoated paper), or "neutral" values (Pantone Color Manager states "No profile" values as defaults, and then changes them according to the selected color profile). I exported the up-to-date Pantone colors without a profile and they seem to work ok, but values shown in Affinity apps, Adobe apps and Pantone Color library deviate slightly from each other even if the same color profile is used. I guess this is to be expected, and deviations are so small that they are not meaningful (Adobe apps even show fractions, as a result of conversions while Affinity apps show whole numbers).
  3. You're welcome, happy to be able to help while learning to know the Affinity apps (and find out how they differ from what I already know -- not much, luckily)! I am not sure. I made first a blunder there, uniting all three letters without any overlapping outline, but it's a bit tricky part as the "white" needs to be a hole. For the same reason I also had to change the green outline of these letters as it was composed a bit oddly (probably a result of exporting it to EPS), and had to remove the internal masks of the letters so that instead of using a mask, the green outlines are aligned inside the curve and have a width of 2 mm (rather than being 4 mm wide middle aligned curves, half of which is masked). Masks can be tricky, especially when needing to clean something that comes from another app, but I suppose there are good tutorials. Basically it is done similarly in all vector based apps. Having the "Expand stroke" feature is especially useful since you often need to convert outlines to closed shapes in order to cut them precisely and become part of a workable mask.
  4. This one. Helvetica Neue appears here, too, and probably not the OpenType PS version at least from Adobe, as I have that, and Frutiger, and many other super families, and they list just fine in Affinity apps. I basically have Type 1 fonts only for the base 35 fonts, but do have the usual mix from diverse office apps, etc. so I' m no font purist, and I do not use font manager on my laptop where I use Affinity apps. But I do know that even a minor name conflict can cause strange problems so I avoid installing any fonts that are likely to share family names from different sources (and at least try to avoid having mixed Type 1s, TrueType and OpenType fonts even remotely sharing the family name). The topic of the beta forum involved hundreds of fonts, and probably a mixed bag of high-quality and less-so fonts. As OP of this new topic has less than 300 fonts installed, I hope this can be easily solved, and also helps you improve the enumeration routines (e.g., separate fonts using different font technologies in their own groups, if that could have any role in avoiding name conflicts).
  5. I compared the two (AI and AD) and could not find significant differences. AD seems to crop the artboard to selection adding a small margin at top and right but this can be easily edited by cropping the artboard. When exporting, unchecking "Set viewport" causes similar export as with AI, and the size is determined by the dpi setting. I get pretty similar results from the same art when using these apps. (See the attachments.) Here's how AI and AD export the artboard created based on selection defined by the two black bars above (the differences in the graphics itself result from the original being an AD graph with blur effects and exported as eps and not fully translated to AI): yes_ai.svg yes_ad.svg
  6. This seemed like a suitable task for me for learning to use Designer's basic drawing and node editing tools, so I tried to clean it for printing with just two colors (I defined the green as a spot color for that purpose). It had some tricky parts that required drawing a couple of extra lines and expanding the outlines. The pawn had to be created, as well, so the drawing has changed a bit. I noticed afterwards that I had created this with the latest beta so I attached a PDF file, as well. If you're struggling with this, you hopefully have some use of the cleaned version. This was pretty much my first real session with Designer, and while it does not seem to be as capable as Illustrator or CorelDRAW, it did feel like a good node editing tool, and quite intuitive to use. DCT mit Text ai _fixed.afdesign DCT mit Text ai _fixed.pdf
  7. That's mostly fine in batch-jobs anyway. And for individual images fully manual workflow from start to finish.
  8. Thanks, actually much more useful. B/W negatives photographed with a digital camera most probably come as RAW images, but I am not sure how useful it is to make adjustments there. Some things might be, but generally ability to save settings in the general UI, and record them as macros, works really well. I now noticed that batch jobs actually allow RAW image development and then postprocessing with macros so it seems this could work really well!
  9. I can see that a preset can be created in Develop Persona (as per setting, e.g., use reversed curve to invert the negative), but it seems not elsewhere? Recording macros, on the other hand, seem to crash Photo as soon as Develop is finished... So I think it is more or less manual job at this stage. EDIT: Macros do not seem to be availabe as panel in the Studio menu when Develop Persona is active so I guess macros are not supposed to be used with Personas (and for that reason crash the app if change of Persona and subsequent acceptance of operationds done there occurs at part of macro recording process).
  10. Ok, thanks! Time to read manual ;.)
  11. I am quite new with Affinity Photo and I am learning about its features and capabilities by reading these topics, and fiddled a bit with b/w negative processing, but just with a quickly googled low-res sample negative, which of course is not even nearly the same as working with a RAW file. But in search of trying to create different adjustments for certain typical workflows I could not find a way to save adjustments, not individual, nor a way to chain them to a saved batch process. Am I missing something? Anyway, perhaps you could shed some light on workflows you had when using Lightroom + Negative Lab. E.g., the example below shows manipulation which I think involves features like adding tones with duo/tritone channels and then flattening back to grayscale, which do not seem to be available in Affinity Photo, so I am not sure if it is possible to create such workflows there. But how straight forward are these kinds of negative conversion processes when using Lightroom + Negative Lab? Compare this with the basic conversion done in the following Affinity Photo document, which only has the inversion, level and shadow adjustments applied on the Layers palette: 3F_sample_workflow.afphoto ...and compare this with the basic conversion created with Tritone curves in Photoshop (without much consideration, but coloring different gray levels with Pantone Warm Grays), simply to try to simulate the example given in the first image which shows negative conversion of a Hasselblad FFF raw image: My point is that these kinds of conversion processes involving inversion, basic level adjustments and duotone based toning can be saved as an action in Photoshop, which could then be used as basic workflows in negative conversion. Is something like this possible in Affinity Photo at this stage?
  12. The blue component of the halo area was already at max (B55), so what was done to the sky part was just adding Cyan to it so that it became approximately identical with it and lost its redness. The color areas in this image were so clear (zone-like) that you could have achieved even more uniform results simply by area selecting with contiguous setting on, and with a tolerance of about 10% the sky and then fill it with the color of the aura, and then use selective color adjustment to change the sky the color you wish. Selective color tool also works with selected part of the image, so first flood selecting the whole sky part (including parts where sky mixes the leaves) would have avoided changing blues in other parts of the image. But this image did have clear "blues" only in the upper part so that was not a problem. It often helps to keep the Info palette visible so that you clearly see how much of each color component exists in different areas of the image. There are cases, like when needing to cut out a person from the background and there is clear colored background shining through the hair, where you have to manipulate the difficult part (hairs, or in this case, the "leaves" part). It is always difficult to make this kind of cut neutral, so it helps if the original and new background can have even a hint of certain color (not necessarily the original of either of the images to be merged) so that the cut can be blended in by applying not only selective coloring but even recoloring (and perhaps some transparency) to the "leaves" part, but just strictly in the bordering area. But often it is possible to manipulate the "easy" part of the image and make it blend into the "problem part" and then apply an adjustment that applies to both.
  13. Note that you can also use the Transform palette to adjust the heights and widths of cells and rows (by way of changing the total height or width of the table). It seems that if the table has certain height or width, you cannot make the measures lower within the table itself. (See edited table below) tables.afpub
  14. If your purpose is the make the row of the cells A B C lower, try increasing the height of the cell "Ṥrednica rury Ø" especially if you have forced line break within it, or Wymiary {mm]. If the total of cell heights in merged rows is "impossible", this may prohibit you from making the ABC rows less high (the measures do not automatically get updated if they are "impossible", so you may need to make manual adjustments). So first increasing the merged header row's heights or top header row's height should help you make the second header row's height smaller. Attached an edited table where I increased the height of the Ṥrednica rury Ø cell, and after that I could make the row of A B C cells lower. Did that achieve what you were trying to do? tables.afpub
  15. If you depend on the fonts that cause conflicts, there might be point in getting a utlity like TransType 4 to resolve name conflicts. There are probably free tools available, too, but hardly ones that are as easy to use as TransType.
  16. My guess is that the cause for these problems is either of the superfamilies Helvetica Neue, or Frutiger (or some other where you have several substyles grouped under the same family), especially if you have mixed Adobe Type 1 (.PFB + .PFM pair) and TrueType/OpenType versions, since this is likely to cause name conflicts which may result in this kind of strange behavior. There is at least one post on Windows Publisher beta forum that is similar to this case. I would start by uninstalling all Type 1 fonts and seeing if that already helps. Then re-installing one-by-one other than fonts from superfamilies, and finally pinpoint the one that causes the error. Adobe apps arrange fonts more cleverly, and do not depend on Type 1 kind of meta data returned by system font enumeration that is often too generic (based on old 4-style family grouping), so that explains why you won't see this problem in InDesign etc.
  17. Exactly, I am just getting acquanited with Photo and I was looking for support for converting to indexed color modes (paletted images), which in Photoshop would allow this kind of effect simply by using local adaptive color reducton without dithering, like below, where the number of colors is reduced to 7: If more zone-like effect is wished, the number of colors could be still reduced, which would result in distorted and unbalanced effect, but then the palette colors could be manipulated directly to get the desired base colors.
  18. Just quick and dirty: you could try Selective Color > Blues > Set Cyan to 100 > Merge. Then reapply, select again Blues, and reduce Black to get the desired darkness. As demonstrated in the attached reduced Photoshop file that has the original and manipulation in layers. selectiveblues_original_fixed.psd
  19. The terminology can be confusing but I think it is understandable in the context of cross-editing capabilities, and common file format for all three apps. Affinity Publisher was, after all, the latest app in the trio. Photoshop also has layers that in a way behave like "objects" (e.g., you can align layers as if they were objects or a group of objects in a vector based app), and then it calls "objects" as "shapes". I am not sure if there can be any intrinsically correct terminology for graphic applications, especially as they are typically hybrid in these days. Perhaps Serif chooses to call InDesign kind of (global) "layers" in Affinity Publisher as "sheets" -- surely the term cannot be reserved to describe only objects in the physical world (like a sheet of paper), or objects in a spreadsheet app (which too, are kinds of "layers", as they can interact in a way similarly as graphic layers)? When PDFs are created in code, the term that is used for "layers" is often "creating or changing the content stream" as that describes accurately what is done when there is need to re-write/re-position on the same page data from a different stream that cannot be accessed meaningfully at the time the first stream was output. The decision to call them "layers" rather than "content streams" was no doubt more user-friendly, but it is not by any means accurate in terms of how they are created. EDIT. Oops, a very old topic. But still useful reading when learning to use these apps as they behave in many ways differently than Adobe apps.
  20. This way I realized that you can achieve a node editable container, no matter what its initial shape is. If this is tried the other way around, first placing text in standard rectangle shaped text frame, then converting it to curves, the contained text is contained to curves, as well!
  21. Thanks, very useful! This allows fully controllable and shapable containers.
  22. A very good question! I would have assumed that this is possible, similarly as InDesign, simply by editing the text frame nodes, but it does not appear to be so? It is however possible to use any shape (e.g. a triangle, or Trapezoid, to achieve the effect described in your post) as the container for the text, but I am not sure if it is possible to rehape this container by using node edit mode?
  23. Definitely by design! One often needs auxiliary objects to perform complex text wrapping and does not want these objects to be visible! InDesign applies text wrapping disregarding the visibility state of wrapping objects but allows an option where wrapping can be turned off layer-wise if the layer is hidden.
  24. Lagarto

    A random "glyph" problem?

    I do not think that there is anything wrong with Roboto. Not applying ligatures automatically is just fine. If you want to use them, you can enable them in apps that support OpenType features. The reason why you initially had the ff ligature in your text as a glyph, rather than as a feature that you had wished to use, was probably that the source application had replaced the mere attribute with a hard coded glyph. This does not work well if you need to transfer the text from one app to another. "Client" refers to leaving formatting decisions to the user and their preferred apps, rather than being dependable on a feature that the app, or individual font, is supposed to have. In this case this means that it is always better to just have "ff" (and other character pairs that can have ligature forms) as two single characters and use a software setting for applying ligatures, than trusting that a hard coded glyph will be correctly handled when any of the affecting parameters change (like changing of the font, or copying text via Clipboard to another app). Actually the source of the hard coded ligature could well be an Affinity created pdf, since ligatures are hard coded in them. Just compare the attached two pdf files and copy paste the text from them to a new Publisher document (or to any other document). You get two f characters from InDesign created pdf, also where discretionary ligature is used, but unrecognized glyph (a "box") from Affinity Publisher created pdf. roboto_ligatures_apub.pdf roboto_ligatures_id.pdf
  25. But isn't this a designed feature? If you want to move the text frame that is based on a master page, you are supposed to "detach edit" it (that is, right click on the master layer in the Layers tab and choose "Edit detached" from the context menu)? That is, the text frame is in that respect similar as any other object placed on the master page, but it just has that important exception that it accepts changing of the text content. EDIT: Dragging and dropping individual text elements like words etc. is possible also in a text frame based on a master page. But now that I re-read your description I am not sure if I understood what you actually meant. EDIT2: Ok, finally got it, just realized that drag and drop editing is only possibe when detach-editing is on while it probably should be possibe also without. Similar behavior applies also to inline graphics placed within the text, and I am not sure if graphics is supposed to be moveable, without detach editing. Possibly not, since even if the graphic object is floating, it cannot be moved, if it is an element in the master page layer. That might explain why drag-and-drop editing is disabled for text, as well. However the visual controls indicate that drag-and-drop would be available, while it is not.

Important Information

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.