Jump to content
You must now use your email address to sign in [click for more info] ×

Bungle

Members
  • Posts

    57
  • Joined

  • Last visited

Posts posted by Bungle

  1. As you can see in the following gif

    1 I have force pixel alignment ticked

    2 I create a completely empty layer (Cant be off grid, its empty

    3 I merge and flatten

    The image is blurred every single time, I have been working on images for the last few days and this happens every single time no matter what, it is actually so bad that after years of using Affinity and owning it on all platforms, I am going to start to look for another editor if this doesn't get fixed, I have seen complaints about it before and non ever get resolved, this is a bug, not a feature as some claim, blurring an image willy nilly is not acceptable.

     

     

    affinity.gif

  2. Oh sorry, i thought posting (AP) in the title would show i mean't Affinity Photo, my mistake, this is a painted line, not a vector line

     

    EDIT* Hmm i did put Affinity photo in the original post too, maybe i should have said painted line too, again i apologise, but this behaviour is still very poor, a 1 pixel line shouldnt blur when being rotated, vector or painted ;)

  3. To be fair, the entire color picker system in general is terrible in affinity, drag the color picker, then have to click the color you just selected so it can be used by tools WTF ?

    There should at least be a prefs tick box to make it instantly available, you know to people who have used every other piece of software that ever existed.

    Affinity is great, but sometimes they just reinvent the wheel and make it white noise shaped !

  4. So its just me then who finds creating palletes to be completely obtuse ?

    Click on the lines, click add color, panel shows, drag the color picker to the wanted color, then click on the color so that it is in the color box, then click add.

    But wait, just to run it in, the damn add color box now disappears, so you have to click on the lines, click add color.........on and on and on and on and on.

    Surely this is either the wrong way to do it or some cruel joke ?

  5. 1.42 = previous beta

     

    1.5x = current beta

     

    Going back to the 1.42 beta, which is what you brought up, would be unforgivable. Which is what I said.

     

    Removing a feature from a current beta, thanks to revision software, to then output a new beta is different and is common practice. But that is way different than reverting to a former beta and beginning all over again with bug fixes is unheard of with any company, be it the one I owned or one that I have tested for.

     

    I think I'm done with this silly conversation.

    1.4.2 is the current release version and i never mentioned previous beta, not surprised you are done ;)

  6. I didn't say previous beta, although that happens all the time too, i said starting a new branch from the previous release, not only does it happen all the time, it is actually recommended form when creating new experimental features, maybe the audio world is different to whatever you do, but it happens all the time and it is a great way to work.

    Dunno maybe the code we use in audio software is a lot more modular, but you are more than welcome to cme and tell all the audio software developers i test for that they should be sacked, in fact pop over and tell Justin Frankel https://en.wikipedia.org/wiki/Justin_Frankel, probably one of the most famous (Infamous ?) developers of the last twenty years, because he does it on a weekly basis as part of his teams development process, notably known for being the fastest developers in the audio world too, you can catch him at the Reaper forum or at the nullsoft IRC ;)

×
×
  • Create New...

Important Information

Terms of Use | 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.