anon1

you can change the date of your Mac in your settings and the beta will continue to work cheers

https://forum.affinity.serif.com/index.php?/topic/5336-file-system/?p=34539 "We'll hand it to the Giraffe team... they can almost reach that fruit. ;)" -Ben maybe someday :D :ph34r: :wub: cheers

please see here https://forum.affinity.serif.com/index.php?/topic/14571-support-10-bit-color-display/?p=180149 cheers

-

the iPad versions are also due thought AP on iPad was already running in the office and the video demos and now it's still not here :blink: :ph34r: :P Pub won't happen soon, I'd bet! cheers

-

to put RAM vs SSD or HDD into perspective http://www.directionsmag.com/entry/ram-is-100-thousand-times-faster-than-disk-for-database-access/123964 if you render a huge panorama for whatever reason and your computers has to write to the hard-drive, even if it is the fastest M.2 SSD with a good connector your CPU can no longer work at 100% load because the data can not be served quickly enough. (happened to me once) an Apple reseller once told a friend of mine that you would not need 8GB RAM because the new SSDs were so fast, which is obviously totally wrong. cheers

-

ah you used a pixel layer well that is kind of bad practise in this case (because vector is resolution independent and seems like affinity can thus optimise it in a better way) @gdenby, does my file not look good on your side? did you choose a very high export compression? cheers

so where did these pixel layers originate from? Ultimately it does not matter though, so anyway use a vector shape and fill it with a gradient and then export and all looks perfectly fine (at least when I tried it, so please try on your side) I attached the file cheers

I see what you mean I don´t have a solution but I admire the problem :D do you have the affinity file (probably a simple file but anyhow :P )?

-

-

sound like the performance test thread was also mine, anyway this is a helpful piece of information I can provide to you and shows that the devs are aware of the issue and working on something https://forum.affinity.serif.com/index.php?/topic/32447-exiftool-test/?p=158161 don´t know if it is already implemented or not if you want to experiment on your own risk and also disable exiftool for the time being your startup speed may improve significantly cheers

I see at first I thought the updates were synchronised but obviously they are not

YES PLEASE and please consider a new one the last two were great! cheers

Maybe try the speed --force option while starting affinity, but he sure to not have firewall active because it will need to download 4 additional cores from the affinity cloud. Cheers

@Petar " I don't always Test my code, but when I do, I do it in production" :D Actually the recent betas are...: "As this is a stability beta, it is suitable for production work and should be used in preference to the App Store version if you need any of the fixes it contains." Cheers

There is no adjustment to cure it, if there was one it would be activated by default. In fact this takes work by the developers to enhance performance and there is not much you can reasonably do. Cheers

Cheers I think they look good, definitely not overprocessed! (If one likes HDR or not depends ...)

Just use the "speed" adjustment layer and drag it all the way to

Or maybe use the source layer Filter > detect edges Layer > Rasterise to mask Cheers

just so you know Affinity will be making such (sort of) a software themselves as well https://forum.affinity.serif.com/index.php?/topic/13792-dam-affinity-lightroom-killer-request/?p=61067 cheers

you can still do it as a one click macro (just tried it) using the first technique macros are buggy concerning different document sizes at times and unfinished regarding layer selection and movement though but that is expected to improve (soon?) I guess like some more things :ph34r: cheers

-