F_Kal

I have reached similar conclusions from the trial of v2 - at least when it comes to the issues (both annoyances and bugs) that I was encountering in V1, they are still present (most of them 4-5 years and counting). I too am on the fence whether I should buy it while it's discounted, only to futureproof myself in case the issues get finally addressed in the ...next 4-5 years.

I've been a long time user of AP/AD v1 on macOS, and while the software in terms of features matured quite quickly, a few bugs and quirks were there for a few years and never really went away: eg. spinning beach balls when resizing the handles of a layer that start after some time of playing - you need to restart the app to get it back to working (AP), random crashes, bugs with symbols (AD), not being able to cancel/exit raw development with a keyboard shortcut etc. I haven't seen any feature in V2 that I need but I wouldn't say no to upgrading if V2 had some or all of these issues resolved. what is your opinion? do you feel that V2 is less buggy than V1?

thank you John! Interesting; I've found auto-alignment to be most of the time producing inaccurate alignments - even with images from a tripod (let alone handheld) I also wonder whether this technique only yields results with extremely sharp lenses, where the sensor doesn't resolve all the detail procured by the lens. The kit and adapted lenses from the 80s that I use don't ever reach pixel-level sharpness

interesting finds @John Rostron! Could you elaborate a bit on the alignment method you used? was it auto-align or was it manually micro-tuning the individual images' perspective? Also, how do the results compare to the original images? Any chance you could share the crop of one of the original 13 images for us to see? Thank you for helping out!

I haven't had any luck with the technique; other than noise reduction which is awesome! I also can't understand the rational behind upscaling the images to 200% before importing them into the stack. What's the problem with upscaling them after the stack it created? It's dynamic anyways - isn't it? Unless this is for the auto-alignment algorithm to have more precision in alignment (though to be honest I find the alignment very ineffective) - Any thoughts on that?

Might be the case, even though if I recall correctly the previous time I had the issue I wasn't using global colors at all, but I'm no longer 100% sure. Anyway, I'm glad these are a known issue, I hope there is a fix soon, since global color and symbols are really useful! Best regards, - Fotis

This has been happening a lot with symbols - I've found an old thread that might be related (here). 1. I create a symbol so that I can place it on multiple artboards and test different compositions. I never turn symbol syncing off or detaching any instances. 2. Then I start changing the colors of certain elements inside the symbol. 3. At some point, a few of the symbol instances will stop syncing the color for some of their elements.All other properties of the very shapes sync just fine however. For other instances everything syncs, even the color! In the following video sample I use the 1st instance to rotate an element (everything is one symbol) and change it's color. The 2nd instance updates fine on both properties. For the 3rd (buggy) instance only the rotation updates (and not the color). Things started going awry after I duplicated the 3 colored elements inside the symbol, hid the originals and assigned global colors to them. I'd be happy to email a sample corrupt file for debugging purposes. cheers! bug.mov

Thank you callum!

Is there a way to export global document colors to the SVG in a centralized way? eg. style/linearGradient or solidColor So as to be able to change one line of code and have all affected elements change their color at once! Thanks!

I've been having an issue where I export a paragraph of text into SVG (without converting it to curves but relying on the system fonts) and some characters render differently in the browser (tested on both on the latest desktop firefox and the latest android samsung browser) as seen in the image below: On closer inspection it seems that the SVG adds certain tags to certain characters, isolating them - without an apparent reason however. it is easy to reproduce: create a new document use the type text tool type "Other All" as text (using Arial font) (for some reason the issue appears if there is another word before the word All! Other tested strings that produce the fluff are "A All B" and the "Unlock All Features" string) export to SVG The SVG should have isolated the Al characters into an unnecessary <tspan> element: <g id="Artboard11" serif:id="Artboard1"> <text x="209.036px" y="520.05px" style="font-family:'ArialMT', 'Arial', sans-serif;font-size:36px;">Other <tspan x="307.087px 331.099px " y="520.05px 520.05px ">Al</tspan>l</text> </g>

I accidentally started 2 batch jobs with the exact same file list - I was trying to find a way to cancel one of the two - is there still no cancel button? would be very useful!

hey I had the same question a few minutes ago! to achieve this: - select all the objects that you wish to prevent - at the Stroke studio (the button on the right where you can edit the stroke width etc) click on advanced - from there deselect Scale with Object option. Now the stroke won't scale with the object! (Do the opposite if you wish to make sure that the stroke retains its ratio to the object/document size after successive transformation)

+1

Hi, I wonder if there is some way to automatically crop/trim and downsample pixel layers to their visible portion and document dpi resolution so that the affinity designer file isn't bloated beyond necessary? I've found that Rasterize Layer does the downsampling, but when you have hundreds of such layers, it's hard to keep track which ones have been rasterized and which ones I've missed! Any function already in the software that I've missed? Thanks,-Fotis

+1 for @VIPStephan's answer Of course a more automated version would be welcome, but I'm quite sure we humans can still use some reasoning also +1 for @Lojza's suggestion that the Beta doesn't expire. It's a big inconvenience moving settings between MAS and Beta Versions; which makes it inevitable that at some point every single beta tester will eventually "retire". And not because of the rough edges, or that he/she wants to stop testing out the software and give feedback: But because there is unnecessary overhead in maintaining the beta-tester status!

hey, it looks good so far!!! no problems with some jpg and png tested on the 1.6.7 (beta 1) - everything worked I'll keep you posted if something comes up!

this happens not only on the beta version of AP, but also on the MAS versions of both products Affinity Designer 1.6 (MAS) and Affinity Photo 1.6.6 (MAS)

hehe, happens to me too! The dialog box that pops up is slightly intimidating and doesn't explain that your problem might be that the MAS version is newer than the beta - after all this time; whenever I read the "A purchased copy of Affinity X must be installed", I still get momentarily shocked ("oh no, what happened to my purchased copy? Did it expire?")

you are right! I tested png and it worked, but after your remark, I tested with jpgs, and trying to open more than 3 jpg files, won't work! Again, three is the magic number - three will work, four won't...

Hi @manu schwendener, Seems that there's been a new released version while I was away! well, I didn't get the chance to test Beta 8, but the new released 1.6.6 on the app store seems to be working fine! -Fotis

FWIW, I'm not a professional photographer so the price point is a concern of mine: For a few weeks now, I've been using DxO OpticsPro 11, since it is free if you download it by the the end of November. The speed and processing quality is rather good (imo much better than ACDSee, Aftershot, Darktable or Apple Photos). While it is not a fully fledged DAM/raw developer in the vains of lightroom, it's been very satisfying as a substitute for the Bridge+Adobe Camera Raw combo. I'm only missing gradient/brush masks, and perspective corrections (that can be found if you buy some plugins or upgrade to the Elite version) but for now I can finally live with that until something better comes out (Perhaps Luminar 2018?) hope this helps somebody!

hi @manu schwendener, so sorry for not getting back to you earlier: unfortunately (or fortunately perhaps) I'm away from my computer - I'll be back by the end of the week and come with some follow up! thank you, -Fotis

I think I have the same issue with beta 11 - and I didn't have this before! I noticed that up to 3 files, they can be opened simultaneously - make them 4+, and you get stuck for eternity!

Loading more than 3 files simultaneously cause the program to stop responding. I first noticed this when I tried opening 12 PGN files (1920x1080x24bit), each around 300kB by dragging them on the AP window. The message "Loading 12 documents" would stay on the title bar forever. Checking the activity monitor, the CPU cores are working intensively (350% CPU usage by AP) but 10minutes later nothing has opened yet. Eventually one has to force quit the program. Opening the files individually (one at a time) works fine; the same files open in milliseconds. Since then I've discovered that I can reproduce this problem with all PNG, and JPG files I've come across and the problem is present even through the File->Open command. The strangest thing is that as long as I select up to three files, there is no problem. Doesn't matter which files! The moment I add one more file to this selection, it doesn't work. There are some rare instances that I will be allowed to open more than 3 files at a time, but this is not something I can reproduce consistently. I got the impression that 4+ files might open if the splash/welcome screen of AP is still displayed(!), or if there are other documents open already in AP, but it doesn't seem to always work - this may be just coincidence. I never had such a problem in any other version of the beta (not sure about beta 5 though since I never really tested it). It seems to be similar to this issue by user @MikeFromMesa even though he was using an older version. I've included 4 PNG files that cause the program to lock on my computer (2011 21.5" iMac - macOS Sierra). I hope this helps! -Fotis

Thanks MBd, that's interesting! I must agree that probably Serif has it under control, there is time until the public release of iOS 11 and even then, it remains to be seen how this format affects our lives. Still, it will be interesting to see how (whether) Apple manages where google failed to convince everybody move away from jpeg!