Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

anon1

Members
  • Posts

    3,209
  • Joined

  • Last visited

Everything posted by anon1

  1. What do you mean "different"? So postt a Video in which toggling on all layers in the sample document provided (all filter/ adjustment and the top merged layer), show that affinity still is fluid as it is with only one layer. (Again: with the top layer in the document activated, affinity should not do any calculation other than straight displaying this layer, no matter if the layers beneath are activated or not, but apprently affinity recalculates everything always no matter what are you telling me this is different on your maschine?)
  2. "Switching to the old OpenGL display renderer works much faster, so perhaps this is at least in part a bug in the beta?" form my last psot: "mind you, this is latest AP beta with Metal enabled on a MacBookPro which supports Metal but it was the same before, and is the same on other much more powerfull iMac" It is very hard to tell much from the movies // it is very easy to see how slow it is once the filter layers below are turned on, although the top layer is 100% opaque file is attached: slow.afphoto
  3. so once more: a video (actually two): the green layer is aligned now still one can clearly see, it is much faster to toggle on without any layers underneath - for no good reason - by which I mean, nothing is needed to be calculated/ no effects applied slow:fast.mov and as a proof of the live filter thing which again: using live filters slows AP down, obviously the result is that one has to merge visible the layers beneath this however does not yield any significant performance increase because they are still calculated as shown here: real slow.mov mind you, this is latest AP beta with Metal enabled on a MacBookPro which supports Metal but it was the same before, and is the same on other much more powerfull iMac which is clearly a flaw which hinders usage in e.g. compositions with many layers/ filters/ adjustments
  4. #affinity always shows dowsnized previews unless you are zoomed in more than 100% Alignment should not make any difference, this happens using same sized/ by which I mean canvas sized pixel layers just the same the usage is no edge case at all as a before/ after view you may put the original image at the top and see the difference but even more importantly using live filters slows AP down, obviously the result is that one has to merge visible the layers beneath this however does not yield any significant performance increase because they are still calculated so one has to turn all underlying live filters off additionally
  5. if there is only one background layer it IS instantly always so it IS possible the software needs to stop rendering the layers below which do not show up at all anyway cause they are 100% covered by the top image
  6. turns out you are actually the first one to ever ask this question, let me try to do some research in order to answer this... 1 2 3 4 5 6 7 8 9 ...there may be even more turns out you were not the first one after all bottomline ist get a quad core laptop
  7. I am not talking about toggling off the top layer i am only talking about toggling it back on that should always be instantly
  8. just for the sake of comparison: here is how a fast UI looks like fast.mov you really only notice once you know how a faster UI feels like https://danluu.com/term-latency/ https://www.youtube.com/watch?v=vOvQCPLkPt4
  9. again this should be instantly every time toggle.afphoto
  10. have you actually created a document that takes noticeable time to compute on itself and overlaid an opaque layer? happens every time on 4 Macs so it is definitely not a singularity the professional dev can figure out how to use metal api and non trivial math can probably figure out how to deal with keypresses
  11. here is another clip showing the slowdown of toggling on a 100% opaque layer slow2.mov 1. you klick correctly much more frequently than incorrectly thus, the snappy behavior is a benefit 99% of the time, and a false klick can be corrected with one cmd z keypress in the other 1% (it can not, if you enter HDR merge e.g. but that is another usability issue for affinity and could easily be corrected so that it accepts esc or cmd z) 2. affinity does not support much accessibility features anyhow so it would not be worse or better by any significant margin anyway 2.b this device you are describing sounds really special to say the least, on the other hand many use tablets to avoid the same issue and tablet would work even better as described in (3) 3. a further benefit of the "klick down = klick" behavior as seen in the adjustment panel is that you can actually klick+drag and get the adjustment instead of two klicks, this is especially very good on a graphic tablet 4. even if the layer panel would support something like PS where you klick and drag down to toggle a series of layers, this behavior could still very well be implemented and would not interfere so the distinction between keydown/ keydown+keyup is not necessary (maybe there are one or two buttons in the whole UI but the rest is not depending on it
  12. had that issue yesterday as well but could not reproduce on iOS 11 latest public beta and 1st gen iPadPro12 and latest photo beta though
  13. I think it is down to how clicks are handled just noticed in another application, klicks are accepted on the "push down of a klick" and thus it is more responsive in affinity this only happens on a few dialogs, most dialogs have the "slower" behavior some dialogs are very fast - always very fast slow.mov some can be infinitely slow (yes, I've exaggerated the effect a bit) hopefully you can produce this though : " On a related issue: if if you place a 100% opaque image/ pixel layer on the very top affinity still calculates all potentially expensive live filter layers below "
  14. yeah should have used an editor with auto correct I'm not completely sold on this table anyhow, but it is difficult to describe all file formats in a few lines so the rest is yet to be discovered by the user I think alpha is super weird for someone that is new to this...naming is not good at all
  15. just had a second thought think I know what goes wrong now change your document to LAB and monitor your info panel in LAB mode as well LAB is just a beautiful color space the issue is that affinity does not calculate in HSL such that the Luminance blend mode color model is not HSL and thus it does not match up if you setup everything in LAB everything is beautiful more info on LAB cheers
  16. On a related issue: if if you place a 100% opaque image/ pixel layer on the very top affinity still calculates all potentially expensive live filter layers below although they obviously have no effect this makes before and after comparisons more painful as well
  17. The conversion part was news to me sounds very reasonable though thanks for the insight
  18. If you have any objections let me know (things missing/ too complicated) if you like it you may let me know as well
  19. Looked at Wikipedia as well but still seems somehow weird to me
  20. https://forum.affinity.serif.com/index.php?/topic/44836-very-basic-things/ added a new PDF about the very very basics of image editing cheers
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.