Jump to content


  • Content count

  • Joined

  • Last visited

About LionelD

  • Rank

Recent Profile Visitors

384 profile views
  1. Can’t imagine an iPad dancing the Macarena, but you’re obviously one of those lucky people whose imagination works very well. It sounds like your problem might be connected to the size of the file, and that makes me wonder if your iPad and MBP are up to date. When Apple fixed the bug they diagnosed in my case, that problem went away. You’ll know everything is working when your iPad and MBP start doing an Argentine Tango; I hope you have appropriate music ready... Regards
  2. Well, I eventually resolved my Airdrop problems. I was dropping iPad to MBP, and had intermittent failures; Apple was very good, and persistent troubleshooting identified a size-related issue. MBP to iPad seems to require receiving app to be running. But then we got iPadOS, and it seems to offer another alternative. If you connect your iPad to MBP with USB cable, iPad shows up in Finder on MBP, and I’ve been able to move files that way. Take a look and see if that works for you. Regards
  3. Brad, these files are large stitched images or panoramas, some with as many as 60 source images. So there are lots of pixel layers, layer masks and so on, with the occasional vector path that I use for cropping. These are my master files; files for printing and other uses are JPG. I do use the PNG format, but only for files where I require transparency; size is not an issue for these files. For historical reasons that probably don’t apply any more I used a combination of TIFF and PSB files for the stitched images. When I last tested TIFF for images in the 8GB to 10GB range, TIFF failed, but I don’t recall precisely why. Regards
  4. Hi, I’m trying to find out which of Affinity Photo’s output file formats is suitable for very large files in the 10GB range. I checked the Serif web site, and I see it claims Photo can open very large PSB files, but I haven’t found a corresponding output format. I’m asking because I have hundreds of stitched images in this size range, as well as a small number of stacked images. I’d really prefer a file format that is widely supported. Can anyone direct me to the appropriate resource, please? Regards
  5. @Callum Any updates, please? Regards
  6. @Callum Thanks for the response. The attached file has all 3 brushes referenced above. I hope this is what you need. By the way, I’m using a “new” iPad Pro circa April this year, Apple Pencil with iOS 12.4.1 and the corresponding version of AD from the App Store. I also have AD for Mac, current version. Regards Test Textured Intensity.afbrushes
  7. Hi, I’m looking for help or documentation that will help me understand the behaviour of some Textured Intensity vector brushes I made, please. I’ve attached the 2 PNG images used to define the brushes; they are different slices of the same circle in a single file (Dots.afdesign). I’m trying to make a vector brush that I can color, and produces a string of evenly spaced round dots, size to vary with pen pressure. I’m very much a novice when it comes to making brushes, so any guidance will be very much appreciated. I defined 3 brushes from the two attached images: Dots V1, Dots V2 (100) and Dots V2(200), named for their source images. The difference between Dots V2(100) and Dots V2 (200) is the Width specified when defining the brush. My puzzles began with Dots V1. I expected round dots, but they appear to be both deformed and have rough edges. Some of the tutorials I’ve looked at have advised using a square image without providing any explanation or justification. I surmised that might be my problem, even though I really prefer to understand what I’m doing.... Dots V2 is the square version of the brush image. While defining the first brush with this image I noticed that the preview varies with the Width specification, so I defined two brushes with this image. Screen shots of brush definitions are attached. I made a new document (Dot Brush Tests, attached) to test my brushes (the vector curves are named for the brush that was applied). I made a single vector curve, duplicated it twice, and spaced them out. Best result seems to be Dots V1. The Dots V2 brushes both make severely deformed circles; I assume the difference in circle sizes reflects the different Width settings. Is there a way to make a Textured Intensity brush that emits evenly spaced circles? How would I make the size of the emitted circles sensitive to pen pressure? Is there a way to make the distance between circles vary with pen pressure? Is there any substance to the idea that nozzles should be square, especially when it’s clear that many of the standard-issue vector brushes are not based on square nozzles? Why are my circles deformed? Regards Lionel Dots.afdesign Dot Brush Tests.afdesign
  8. @GabrielM Thanks for the response, but I’m going to ask that Affinity consider the naming convention first proposed by @Aammppaa in one of the referenced threads. I use Symbols very extensively (DM for more info if you need it). I have some documents that have tens of instances of each of two Symbols, and it makes a lot of sense to link each instance to its source definition, but I think you also need to be able to name an instance for the role it plays in the overall design. @Aammppaa‘s proposal accomplishes that elegantly. Here’s some insight based on one group of documents. The basic building block in this case is an equilateral triangle; because I need to keep the content associated with a triangle synchronized, I define it to be a Symbol. I create 6 instances of that Symbol, and position them with their apexes at the same X,Y position, rotated 60 degrees with respect to each other. Take together, they form a regular hexagon; I think of this as my base hexagon. In the next step I make lots of copies of the base hexagon, and align them edge to edge and vertex to vertex so they tile a fairly large area. Now I start adding graphic content to one of the triangle Symbols; I’ll edit that content and add to it as necessary, working in the first hexagon I made. With the MacBook naming, the triangles that make up my base hexagon all have the same name. It’s sometimes more convenient or intuitive to add content to a particular triangle because it’s position and/or orientation make it easier or more natural. With the MacBook naming, I have to hunt and peck to find the most suitable triangle, or contrive another mechanism to facilitate my search. If they were named individually, I could choose by name. I’m going to be traveling for the next two weeks or so, so further responses from me are likely to be sporadic. Regards LionelD
  9. @Lee D Thanks for your response, that’s very helpful. Regards
  10. LionelD

    Naming instances of Symbols

    Cross-posted to for further action please. Regards
  11. This topic refers to another at That topic describes behaviour on both iPad and MacBook and, as a comparatively new user, I’m a little reluctant to describe it as a “bug” because I’m still learning. Please move this topic to the correct part of the forum, as appropriate. Just to be clear: I’m using an iPad Pro and Pencil purchased this past April running the latest iOS and Designer (from the App Store). The MacBook is running the latest Mac OS X, and the current release of Designer (from the App Store). The referenced topic has sample files that illustrate the behaviour described. I’ll try to provide any additional information you need, just let me know. Regards Lionel
  12. LionelD

    Naming instances of Symbols

    This issue continues to be a problem for me, so I’m really hoping for some help and/or feedback. I found a discussion at which appears to be related, in spite of the part of the forum where it’s posted (Windows, Designer Beta). I’ve attached sample files that illustrate the problem. Each file contains 6 instances of a single Symbol; the Symbol is private to its host file - I’m not trying to synchronize Symbols across files. This table summarizes the results. File iPad Macbook Symbol Naming - iPad - Instances Named Independently Symbol instances named independently in Layers Studio Symbol instances named independently in Layers Studio Symbol Naming - Mac - Rename Propogates Symbol instances named independently in Layers Studio Instance names in Layers Studio propagate on rename. The first file permits instances of a given Symbol to have different names in the Layers Studio on both iPad and Mac. This suggests the problem is not specific to iPad or Mac. The second file permits instances to have independent names on the iPad, but synchronizes instance names in the Layers Studio. To me, this suggests there’s a difference between the two files. Any thoughts, please? I appreciate the logic in @Aammppaa‘s suggestion in the referenced thread (Instance name should include a reference to the source Symbol) because that seems to deliver the best of both worlds. Regards Symbol Naming - iPad - Instances Named Independently.afdesign Symbol Naming - Mac - Rename Propogates.afdesign
  13. LionelD

    Naming instances of Symbols

    @DM1 Thanks for your feedback. My experience is the same as yours, except I have not been successful re-establishing synchronization - probably finger trouble or ignorance on my part. I’ve made major changes to the graphical content in a Symbol numerous times, and that has behaved flawlessly. I seldom disable synchronization, so have limited experience with it. At the moment I believe the strange behaviour is mostly the renaming I described. The documents in question generally define one Symbol, and, at a guess, from 20 to perhaps 100 instances of the Symbol. I’m not certain yet, but I think I may have files that behave inconsistently; if I confirm that, it might indicate that there’s a setting somewhere that explains things. Regards

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.