Jump to content


  • Content count

  • Joined

  • Last visited

About dasigna

  • Rank

Profile Information

  • Gender
    Not Telling
  • Location
  1. just wondering what might be the benefit of more than 2 decimals (regarding mm) in a graphics app??? (set it to 2 and just works fine btw. ...) a watchmaker might use more - but not in affinity or similars ...
  2. dasigna

    PNG Export size (for web)

    honestly, referring to such filesizes they wont bother me at all! getting much more interesting with bigger sizes, lets say 50 or 100kb up. more interesting what AD would do here (havent really tested yet, awaiting the promised preview-update with 1.6). so as long as the qualitys just fine some more kb are o.k. (to me). that spoken, the far more interesting part would be the files compared regarding quality (again, to me). concerning "making google speed insights happy": i dont give a damn about it as long as speaking of several tiny 5 or 10kb! :) speed insights anyway has to be treated as not very helpful more often than less. the results are regulary kind of... yes what? ... strange? as long as any website runs smooth without hassle under every condition, google might tell me whatever they want. so as long as its about 3 or 4kb for a file - forget about it. if its 10 for a 100kb file - ditto. (unless there aren't hundreds of them...) if theres a remarkable difference in quality - thats another thing. may it be possible to see what you've tested?
  3. dasigna

    PNG Export size (for web)

    just as remark from my side... fireworks always supplied the smallest files so far - even unmatched by ps or illustrator. (insnt used by myself anyway, as 3.5 or 3.2 kb doesnt matter to me...) but as meb said - it may not be appropriate to compare in this way as you dont handle the files directly made by AD. seems it cant handle ps-files very well due to the mentioned reasons. would be interesting whats happening to quality and size if you would build them from scratch in AD (know this is not intended and extra work, but would be interesting anyway...) :)
  4. dasigna

    16bit cymk support

    ... reading, reading again etc. maybe that might help. seems you can follow my demands as well as you dont? so it may be pointless to you - not for me. but thats o.k. in every way. thanks for being here. :huh:
  5. ... yes thats the fun side of it at the end ;) (forgot to mention).
  6. dasigna

    16bit cymk support

    ... thought i have done that some way up from here ... no?
  7. sometimes its kinda strange in here ... battle of words and such where no one is eighter completely wrong or right. and sometimes i have a strange kind of feeling that too many seem to be forced to defend affinity or serif wheres no need to. and the discussions over stability towards mac or windows are quite useless anyway. the thing is (just my two cents): if serif would claim to be only for the 'average' users or just for the fun stuff side and not charging anyone for anything, alright. but they dont. and even more as the software is claimed to be for professional use also - what would be any better for serif than those who uses this every day (if not for work), reporting issues and such? its kinda development stage for free and even getting paid themselves... ;) so yes - there are chrashes. and yes there are demands for new features. development has to be towards more reliability and enhancement of existing features as well as new features. hard job. but i hope they will manage it - last update already lead to much faster startup times e.g. - great. so dont damn those who want more features, nor those who are reporting issues or want more stability. btw. i want both :lol: so hopefully serif listens to all, sort things out and go for wise decisons. at the end (supposing) we all want the same: a good reason to ditch off the old bulls with confidence!
  8. some words in english for all to read: really dont know whats the problem here :) the complete url is listed at the beginning of every chapter - what you are referring to in your photo is only the notice for the single file you need at that stage of the chapter, as theres no link to every single file. and you get all those files as .zip from the url mentioned before. complicated, huh? the actions are: reading - understanding - acting. vica versa is not that good ;) the only thing you are right to is the circumstance regarding the lack of 'https' in german edition as somewhere stated. in fact theres only 'http'. so hopefully at least i was able to bring you some light into the dark.
  9. dasigna

    16bit cymk support

    yeah - read that. so someone of the marketing people have to talk to those others finally and tell them what they have promised!! :blink:
  10. dasigna

    16bit cymk support

    ... hmmm. always regarding the print file factor. but thats not what i'm after... its the way in between ...and yes, i know (has been mentioned) dealing with 16bit cmyks is obviously an pre 2000 behaviour :wacko: so this seems to be an argument anyway. but eighter way - it would be really poor if i would have to tick that point off. not even being able to handle lots of existing content aggravates the real change to affinity unnecessarily. cant imagine it would be this complicated or heavy labour to implement it.
  11. dasigna

    16bit cymk support

    any statement from dev side possible?
  12. ... or at least resize them to max screen when viewing. :) +1
  13. dasigna

    16bit cymk support

    just to be clear: "... I do not know any printing processes that take CMYK16." - nor do i . "... most people use RGB in the production and convert to CMYK8 at last stage." - obvious. but thats not the point. 1. you can go along with (pro-photo) 16bit rgb most of the way. right. best way. but at some point you have to change to cmyk - and that leads to the important thing: (at least me) never let any software handle this completly in an automated way! the results quite often are more or less not whats to be expected. no matter if generating the print files yourself with automated conversion from rgb to cmyk or even sending rgb within your files to the printers and let them do it. (btw: for the second one i do not know any printer who is giving any warranty in this case for perfect results...) 2. so you have to have control over this when going for cymk at the end, and occasionally (and possibly) have to tweak some things within your required colorspace (cymk) ... you cant do that in 8bit seriously due to the high risk of the limited colorspace and loosing information and other damages. you have the smaller cmyk colorspace anyway with 16bit, right, but you take advantage out of the much bigger headroom (just watch the histogram when editing photos in 8bit... regardless of colorspace). so going for 8bit is the very last step when compiling the final files for print. everything above that has to be 16bit - even in cymk. mandatory. maybe most of the people who are using cmyk for print havent noticed any issues so far (i had), or arent even aware of the limitations within 8bit cmyk (i am). so theres no way dismissing 16bit cmyk in a serious workflow for print at least for me - have to have this both in AP and AD. its simply all about control over the final result.
  14. ... they cant be 'saved' normally (at least here on windows) obviously due to copyright reasons (absolutely clear and o.k. with this) so you have to perform 'save as' anyway when tweaking with them. but 'wasting diskspace' shouldnt be any argument really with terrabyte-disks nowadays for a several MBs 'big' file B)
  15. ... why not simply take advantage of the 'save as' option and store them to a destination of your choice? as long as you remember this you'll find them again with no hassle :)

Important Information

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.