Ian Tompkins
-
Posts
20 -
Joined
-
Last visited
Everything posted by Ian Tompkins
-
The clarity is much appreciated, but were these commitments codified in the terms of the sale in a way that has any legal weight? If not, I’m sorry to say it won’t matter. Serif and Canva employees can truly believe in these ideals, but an investor owned corporation either private or public has no obligation to maintain them. As soon as they think they can get away with it, these commitments will be dropped to pursue more profitability for the shareholders. As I and many others have said already, we’ve seen it happen many times. This statement does very little to assuage those fears.
-
sad-trombone.mp3
-
We’ve all seen this type of acquisition before, and no amount of marketing copy will dissuade the well-founded fears of this community. Unless Serif has strong guarantees from Canva in writing, it’s pretty obvious that they will become a lemon for the parent company to squeeze until there’s nothing left. That’s almost always the outcome. Canva is awful software. If I’f known Serif would be owned by Canva eventually, I never would have purchased a V2 license. This is a pretty big betrayal of our trust.
-
I recently started using Affinity Designer 2 on my iPad Pro and was a bit baffled that common keyboard shortcuts are absent. When I place my cursor between two letters and press Option + Right Arrow, it jumps to the end of the line of text rather than increasing the kerning. Cmd + Right and Ctrl + Right do the exact same thing, so I don’t see a compelling reason why Option + Right Arrow wouldn’t be available for use as a kerning shortcut instead. I recognize that the iPad interface is (necessarily) optimized for touch, and I think it’s done quite well for that purpose. However, kerning is buried fairly deep in the menu, and the traditional Option + Arrow shortcuts would be a major convenience for those of us using keyboard and mouse on iOS. It doesn’t look like enabling them would interfere with any other functionality, so please consider doing so! I would add that there are a number of other shortcuts in the same boat which I think could be added without causing issues, such as Cmd + and Cmd - to zoom, or Esc to back out of editing a text object. -
I did end up trying TIFF/16 from the RAW files. That did not resolve the color cast issue, but definitely agree I should do this for merges in the future. It was an oversight when I batched out the TIFFs. Wow! I did not know you could delay the tone mapping for later, nor did I really understand how the Sources panel worked. After some experimentation, I finally understand: if I have a layer that was merged from sources and I pick the Clone Brush Tool, it shows all the sources and I can clone in from any of them. This is perfect, and probably the preferable method for subjects like this anyway. Thank you very much for mentioning this. Ultimately it would still be nice to know what's going on with the color cast issue and wether it's a bug that needs to be reported, as I can see the manual cloning approach being a non-starter for some subjects, such as dense trees in a landscape. The method you described provides a great solution, though.
-
Thanks for this, I couldn't find it earlier. My camera must be set for sRGB, this is the entry similar to your screenshot: <photoshop:ICCProfile>sRGB IEC61966-2.1</photoshop:ICCProfile> Sure, attached! P2030015-19_RAW.zip
-
That is an excellent suggestion—it did not occur to me to omit some of the exposures. You're right, using just 3 works well without ghosting. I've been considering going back to 3 exposures instead of 5 since I don't usually see much gain from 5; maybe this is a sign from the universe telling me to do that. The original images out of camera were Olympus RAW files (ORF). I don't see a clear way to check what color profile they have by default in AFP, but I do see that they are RGB/32, and the AFP file is RGB/16. Does that indicate 32-bit vs 16-bit? Could that be the cause?
-
I have 5 bracketed exposures that work great in HDR Merge, but only if I leave "Automatically remove ghosts" unchecked. I would like to correct ghosting, but when I select that option, the subject takes on a yellow hue from the surrounding environment, even though none of the source photos show that hue on the subject. I've attached one finished JPG that has correct color, but shows ghosting because the option was unchecked, as well as on JPG that has corrected ghosting but altered color. I've also attached a ZIP file with source images if you wish to experiment. Any thoughts? Anything I can try? I'm on macOS 12.6.3, Affinity Photo version 2.0.4 Here are the things I've tried but did not work: Using JPGs instead of TIFFs as source files Switching to OpenGL in Performance settings Unchecking the Tone Mapping option in HDR Merge P2030015-19.zip
-
Hmm. This didn't quite work for me. I tested the Stacking, and the alignment did not work so well with the paste method. The images did align well when I stacked them as a group with File > New Stack. And it unfortunately won't work for HDR merge either, as that tool does not create a live group. Once you commit the HDR merge settings, they are flattened. That said, thank you for exploring and sharing!
-
Confirmed, this worked very well for me on a set of 10 images on a Mac. In my case, I also used a different macro first to ensure that each RAW was linked, and I batched them into .afphoto files. I would still prefer to not have to make a special macro for each set of photos as this requires constant management (deleting old macros) and is a few extra clicks. However, I'm quite happy with this for now. Thanks for the tip!
-
I can confirm this solution does work well. The batch window has a lot of room for improvement (like setting options for .afphoto files without needing a macro), but it's very functional and easy to use.
-
Oh wow, this is great, thanks for sharing. I will add that if you want the layers to be linked (like I do) you have to set your placement policy before placing them in the document (see screenshot). This would actually be a really good solution for bracketed photos, if only I could Stack or HDR merge using layers from the current document instead of separate documents. As it is, I would have to export TIFs as you described, only to re-import them as a merge and delete the TIFs—an unnecessary extra step. What I'm finding is that Affinity Photo is very close to being an improvement on Camera RAW/Photoshop for RAW editing, but there are a few rough edges that slow down the workflow. A relatively short list of improvements, combined with genuine innovations like the one above, would really put AP over the top for me. Here's hoping some of these more subtle refinements will come with updates.
-
Just want to add that I agree with the need for a more complete preset implementation. The preset should be able to cover all the RAW editing sliders, not just the ones from a single panel. Also, there should really be some kind of auto-sync between files. The simplest implementation would be an option to "duplicate these changes to all open files" or something similar. When working with a set of bracketed photos, for example, I just want to get the color and lights/darks right on one image, then apply the same settings to all the others in the set. Currently that requires clicking on the same preset multiple times, but it could be just one button.
- 28 replies
-
- 2
-
-
- affinity photo v2
- v2
- (and 1 more)
-
Publisher/Photo feature request
Ian Tompkins replied to tinpeas's topic in Feedback for the Affinity V2 Suite of Products
I agree with this concern. I don't use Affinity professionally (yet), and the inability to create/place rasters with spot colors in them would prevent me from doing so. It happens a lot on direct printing to plastic, as @tinpeas says. -
Support for Blender
Ian Tompkins replied to Jack Underscore's topic in Feedback for the Affinity V2 Suite of Products
I'm curious, what is it about the PSD format that is required (or desired) for Blender textures? Would a PNG or TIF not work the same? I don't claim any real experience with 3D textures, but it seems odd to me that a proprietary Adobe file format would be the best choice for a highly established FOSS app like Blender. -
I've noticed this as well on a Mac. I found that I don't have to switch back to "Default"—I can just select the preset again even though it's already selected, and the settings are applied. It did strike me as being a bug, though.
-
Add a Built-In Font Creator
Ian Tompkins replied to rawii22's topic in Feedback for the Affinity V2 Suite of Products
To build on this list, there's also Glyphs and Glyphs Mini: https://glyphsapp.com- 19 replies
-
- 1
-
-
- font
- font creator
- (and 5 more)
-
Interesting, you're right. I copied a set of files and opened the copy—it still referenced the original RAW. I wonder if this would complicate things during a system recovery, if all of your images had to be copied to a new system from a backup. Would the links break? Not the biggest concern I suppose, since I rarely re-edit an image and it would be easy to re-link via the resource manager if I did. A good thing to be aware of, though, and maybe a reason to make the link truly relative to the .afphoto file instead.
-
You're right, this works—thanks! When I was not able to change an embedded RAW to linked using the interface at the top of the Develop persona, I assumed it was not possible. It's odd that you have to do this from the resource manager instead, but I'm glad to know it's possible and available in Macros. If you have any tips on importing .afphoto files as a stack, I'd love to hear them. I just moved my files around to test this, and I did not have the same issue. As long as the .afphoto file was next to the RAW file (in the same folder), it worked no matter where I placed them. I agree—absolute paths when linking would break the functionality for me. Perhaps this behavior is different given the operating system or RAW format? I don't know why that would be the case, just throwing out a guess. I'm on macOS 12.6 and working with Olympus .ORF files.
-
First order of business: I love the updates, big thanks to Affinity and Serif for the hard work! Onto the suggestion: Currently, I can batch RAW files to .afphoto files, but they are embedded with huge file sizes and no option to make them linked instead. To convert RAW to .afphoto as linked files, I have to individually save each one. This is a problem for my workflow. Also, when merging for HDR or Stacks, I cannot use .afphoto files as the source. This requires me to batch out intermediate TIFFs first, which eventually get deleted and seem like a wasteful extra step. For context: I shoot a lot of bracketed photography, mainly for HDR but increasingly for focus stacking. Currently, for a 5-bracket shot, I have to manually open and save each of the 5 exposures. With larger photosets following multi-day trips, this is going to be extremely cumbersome. Bonus points: I would love to be able to add text to the end of a filename (e.g. "_Edit") when batching, but that's a much lower priority than the requests above.
