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

Sharkey

Members
  • Posts

    353
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Sharkey reacted to LCamachoDesign in No more new features, dam, filters, or other requests.   
    I can expand a bit more on the central theme of this topic, I think there's nothing wrong in asking for features, just ask for reasonable stuff. Requesting reasonable features keeps development in focus and increases the chances of it actually being implemented. Below are two examples.
     
    Reasonable request: Artboards in Affinity Photo, we can already trick the software into having artboards in a number of ways, so the feature already exists. I'd therefor ask Serif to simply add a button saying "Insert Artboard", just so it's simpler to do it.
     
    Unreasonable request: Asking for the immediate release of a full featured, Lightroom killer, DAM software out of thin air...
     
    So, nothing wrong with asking, just keep it real please. Thanks!
  2. Like
    Sharkey got a reaction from Fixx in Batch Processing of Open files?   
    Thank you for that. Oddly, I would have thought that selecting open files would have been the first option on the list. Hey Ho!
  3. Like
    Sharkey got a reaction from ostonica in PPI, not DPI , and numerical entries   
    As I remember the USA made a slight error with unit names that were thought interchangeable. Made a bit of a difference to their space program.
     
    Still, if programme can become program then there is confusion for us all for years to come.
     
    One man's foot, in the past, was all that was needed until some men grew taller.
     
    Subsequently we realized standardizing units was quite important for almost anything we tried to do as a group. Although pedanticism is contagious it has a use and in this case clarity of unit is the goal.
     
    As of now I shall think DPI for printing and PPI for digital image work on my computer.
     
    There you go. Problem solved. I will use your software my way. (hope you don't mind if I ask the occasional question). Simples!
     
    Regards.   Sharkey
  4. Like
    Sharkey reacted to NobleValerian in PPI is not DPI   
    NobleValerian, on 23 Dec 2016 - 6:26 PM, said:

    I respect that everyone has a perspective, but if Affinity is unwilling to change it, I think they should just state that, and state why.  "We believe DPI is less confusing to our users than PPI, even though it's not very accurate.  We understand many of our users would like it to be changed, but everyone who understands the difference is only affected by our lack of accuracy and professionalism, and it makes no difference to their workflow whatsoever, so it will never be a priority for us."  (Obviously you don't have to say you lack accuracy and professionalism, that's just the view some of your users have when they see DPI instead of PPI.)

    I don't have to agree with that choice to respect it, but I can't tell from staff responses over the last 2 years whether this is truly the case, and I'm being patronized, or if there is a legitimate chance your company will consider correcting this in a future update.  I respect that your various staff have thoughts on this, but I have no idea where "Affinity" stands on this.  It's just not clear what the decision is.  One staff member says they agree that it should be changed, one says it's too much of a hassle to change because users are more likely to understand the wrong term, one says it's a perfectly acceptable term, and another says all suggestions are considered.

    Which is why I reached out to Affinity, and not to the Affinity community.  Your users can't decide to change it, so I don't really have a case to make for them.  We can just "debate" among ourselves for 2 years without ever getting a real decision on it.
  5. Like
    Sharkey reacted to NobleValerian in PPI is not DPI   
    I explain this in my post, and later posts.  The digital file resolution may only be relevant for *when* you print, but it's also still only relevant to your digital file.  You can print a 300 PPI document at 300 DPI and 1200DPI and get drastically different results, but printing a document 300 PPI and 1200 PPI at the same DPI is an almost indistinguishable result.  If you didn't label them, you wouldn't know which one came from which file.  And then if you don't understand the difference, then hearing that you can print a 300 DPI image at 1200 DPI to make it a better quality image than 300 DPI, is inherently confusing.  Because if that's true, why can't you just print my 50 DPI image at 1200 DPI to make *that* a better image.  The "DPI" settings in Affinity have almost nothing to do with the final print quality of the file.  That comes down to print DPI, paper quality, finish, etc.  So, it's an important distinction to say your document is measured in pixels, and your print isn't, and describing them both the same way is confusing.  And between professional printer reviews and feedback, print on demand feedback, and other online discussions, there's just no legitimate way to say that calling them both DPI makes it easier for anyone, because people all over the place are still getting crappy results and they have to reach out to the printer to find out why.  Which is also why so many great printers have so many terrible reviews.  My prints will always be sized correctly.  Everyone who understands it is always going to have their work sized correctly (well, all other things being equal, I guess).  I'm guessing the vast majority of people jumping into a $50 art program are not working professionals who understand this stuff, and either way, it's still not an accurate way to describe your document.
  6. Like
    Sharkey reacted to Marj in PPI is not DPI   
    This has been an informative thread, I have enjoyed it! My “4 pence” would be if its inaccurate fix it now not later. Its important for a professional level product to be accurate, even if its seen by some as being a bit pedantic. Anything less depletes the product. So bite the bullet Affinity.
  7. Like
    Sharkey reacted to NobleValerian in PPI is not DPI   
    That is utterly absurd.  I have lost count of how many forums and threads I have been through, and it's quite obvious to me that many professional artists and designers working with digital files understand the difference between PPI and DPI.  The notion that any designer of the last 2 decades is thinking of dot matrix technology, on screens or with printing, when creating their digital files is one of the worst arguments I've ever heard.  It's not like this was a dominant, long lasting technology, or that the majority of the professional market is made of people old enough for that to be a significant memory in their professional careers (I'm not exactly young, so I don't buy it).  Though, still not as absurd as saying there is no point trying to "change" it from DPI to PPI when the industry digital photo editing tool in the world, now a verb, correctly uses PPI.
     
    If that's why their program costs more than 10 times as much, I'm completely underestimating the issue  ;)
     
    It seems to me the reason not to change it is that the experienced professionals who understand the issue make up too small a portion of the user base.  It's just too difficult, or expensive, to educate people with a brief forum post, help section, FAQ, or short video.  And possibly an issue because so many printers, who usually work in DPI, can't grasp the concept that digital files aren't measured that way.  As if it isn't confusing to say your 350 DPI image is going to print great at 2400 DPI, but your 50 DPI image is too low res to look good at any DPI.  I mean come on, if my 50 DPI image doesn't look good, just keep increasing the print DPI until it does, isn't that how it works?  Aren't those things inextricably linked?!  Why strive for progress or excellence when it's so much easier to keep doing everything the same stupid, incorrect way?!
     
    And now I'm upset.  So, let me just say, I love the software.  These are excellent programs and I'm proud to be a user.  I, apparently along with several other vocal users, would obviously very much appreciate if this issue was corrected.
  8. Like
    Sharkey got a reaction from NobleValerian in PPI is not DPI   
    A little knowledge is a dangerous thing but too much knowledge can also be so.
     
    Up until now my knowledge was based on the image manipulation software having PPI in the file title and my printer (and printing companies) I have used, having a DPI which I am asked to select.
     
    Having read this and other contradictory postings I now know I know just enough to edit and print my photographs in a manner that is comprehensible to me - the rest is from my perspective mostly irrelevant.
     
    Rasters/Vectors/effective resolutions etc. I know not what they are and in my ignorance, I will no doubt remain.
     
    My original contribution (if it was a contribution) was to simply state the I found the AP usage of DPI confusing and would like it changed. Easy really. Why do I need a 'Doctorate' in digital imaging etc. to back my contribution up? I do not.
     
    My initial confusion no longer exists because I have decided that although I think the usage is wrong I can adapt to its existence faster than the software writers.
     
    Regards    Sharkey
  9. Like
    Sharkey got a reaction from NobleValerian in PPI is not DPI   
    Is this continuous 'Nit Picking' really necessary?
     
    OK. Not in the file title - in the file description is probably more accurate.
     
    Lucky I do not write software for general public use :lol:
     
    I used to use Adobe Raw Reader and a file description was always at the bottom of an image opened. You could change the parameters of the image to what you wanted in preferences as I recall. I think my default choice was RGB 1998,600PPI,16BIT or there abouts.
     
    I will try in future to be more accurate but I cannot guarantee it. I would try harder if I was being paid to be that accurate but luckily I have not had to be that committed to earn crust for some time. Retired early. 
     
    Regards.   Sharkey
  10. Like
    Sharkey got a reaction from anon1 in PPI is not DPI   
    Is this continuous 'Nit Picking' really necessary?
     
    OK. Not in the file title - in the file description is probably more accurate.
     
    Lucky I do not write software for general public use :lol:
     
    I used to use Adobe Raw Reader and a file description was always at the bottom of an image opened. You could change the parameters of the image to what you wanted in preferences as I recall. I think my default choice was RGB 1998,600PPI,16BIT or there abouts.
     
    I will try in future to be more accurate but I cannot guarantee it. I would try harder if I was being paid to be that accurate but luckily I have not had to be that committed to earn crust for some time. Retired early. 
     
    Regards.   Sharkey
  11. Like
    Sharkey got a reaction from NobleValerian in PPI is not DPI   
    I am in complete agreement.
     
    Much as I am committed to this software the obtuse nature of some of the terms and methodology does grate on occasions. Almost an obtuse language used to avoid the obvious..
  12. Like
    Sharkey got a reaction from NobleValerian in PPI is not DPI   
    Sometimes getting it right is enough - no matter what software/hardware named.
     
    Practical, real world benefit is in the eye/mind of the beholder/user. 
     
    A deeper respect for the tool is usually achieved by producing a tool that demands respect!
  13. Like
    Sharkey got a reaction from NobleValerian in PPI is not DPI   
    It is time some common sense was used here.
     
    PPI is and always has been self-explanatory. Pixels Per Inch.
     
    DPI similarly also is self-explanatory. Dots Per Inch.
     
    PPI relates to digital file size/quality/density.
     
    DPI relates to the conversion of an image file into a print affected by an inkjet printer which produces hard copy images by squirting ink onto paper at so many Dots of Ink per Inch.
     
    The two units are not interchangeable or confusable.
     
    I do not claim multiple years of knowledge or a technical vocabulary large enough to confuse a physicist; but.
     
    If your software is designed to work with digital files, I ask you. Why can you not see/comprehend that to use these terms as if they are the same 'thing' is just foolish.. and an indication of fundamental disregard for the subject you purport to be expert in.
     
    With all due respect to people who produce a product that is as far beyond my capability as a 9second 100m run. This must be the most simple of fixes for you, so why make such pathetic arguments when acceptance of fact and fixes would gain you so much more credos and respect.
     
    I do not think it will affect sales but you never know!
     
    Regards    Sharkey
     
    ps.. please do not launch into another tirade about what is or is not an industry wide acceptance because as a part of that industry for thirty years or so it is not accepted here!
  14. Like
    Sharkey got a reaction from SrPx in Last decent(lucky)photo   
    Set up for landscape and this happens :o
     
    Regards.   Sharkey
  15. Like
    Sharkey got a reaction from affinitypete in Last decent(lucky)photo   
    Set up for landscape and this happens :o
     
    Regards.   Sharkey
  16. Like
    Sharkey reacted to Alfred in Last decent(lucky)photo   
    For those wondering, it's near Pitlochry. ("A popular destination since Victorian times, it is often thought that the location was named after Queen Victoria who did, in fact, visit in 1866 . However, it is more widely believed to have been named after Queen Isabella the 14th century wife of Robert the Bruce who used the spot as a resting place on her travels") 
  17. Like
    Sharkey reacted to Andy Somerfield in Partial Update&Fixes   
    Hi Sharkey,
     
    I agree that the term "Beta" is sometimes not really accurate - it really means "Unreleased" - although sometimes, it means "Beta" :)
     
    We have 3 types of unreleased product:
     
    1.) A public beta (this only happens before a product is initially released).
    2.) A customer beta (this is a long-lived beta of potentially unstable features, for the next major release of the product).
    3.) A customer "live" beta (like 1.5.2). This is where we push fixes before we ship them out to users of the stable version.
     
    Photo is currently in "live beta" - this means that we believe the code is more stable than the shipping product - so why would we not immediately push those fixes out?
     
    Well, two reasons to be honest - firstly, as in this case, we will deliver beta builds at any time to fix regressions which stop an existing user from doing what they do with the previous shipping version - these are the worst possible bugs for us, and we will move heaven and earth to get a build to that user so he/she can get back to work. That said, hasty fixes can often have bad side-effects - we will never go straight to MAS with an emergency fix..
     
    The second reason is commercial - weekly releases on the MAS would probably make users concerned / frustrated - and our ratings / reviews reset each time we update the app - which is frustrating for us. We accumulate fixes for specific, niche problems until we have enough for a plausible update - or encounter an issue which we consider worthy of losing all our ratings - then we release..
     
    I guess what I'm trying to say is that it's all quite dynamic - we do the best we can for everyone and that can never be perfect..
     
    Thanks,
     
    Andy.
  18. Like
    Sharkey reacted to R C-R in Newbie here, I have some questiens!   
    Because I do want to see as clearly as possible the actual pixels the image contains. That is particularly important for doing things like manually applying anti-aliasing with brush tools or deciding which (if any) resampling method will give me reasonably good results if I want to enlarge it.
    On the contrary, for most of the editing I do on small images it is much easier to see the results at high magnifications. When I am concerned about the accuracy of the screen representation I use the keyboard shortcuts to zoom to 200%, 400%, or 800%, depending on how many pixels the image contains & how finely I am editing at the pixel level.
     
    When I zoom in, I can see things I would not notice otherwise, like fringing artifacts in compressed JPEG files or 'spill over' when using the inpainting brush at small sizes on small areas of the image.
  19. Like
    Sharkey got a reaction from CekariYH in Export Persona   
    This is ALL COMPLETE RUBBISH - Please Ignore!!
  20. Like
    Sharkey got a reaction from ronnyb in It's PPI not DPI   
    I know it is of no interest or affect  BUT  when I first decided to move to Affinity Photo one of the first confusions was its use of DPI!
     
    Just Saying.
     
    (oh, only thirty years plus as a photographer and printer with a fair few years in digital art)
     
    Worked it out for myself----
  21. Like
    Sharkey got a reaction from Patrick Connor in It's PPI not DPI   
    I know it is of no interest or affect  BUT  when I first decided to move to Affinity Photo one of the first confusions was its use of DPI!
     
    Just Saying.
     
    (oh, only thirty years plus as a photographer and printer with a fair few years in digital art)
     
    Worked it out for myself----
  22. Like
    Sharkey got a reaction from Mt. in Performance?   
    Understood.
     
     
     
    It is not unusual for me to be wordy and I have been criticised for it before. Suppose I try to be accurate and in doing so become more confusing to the reader.  My apologies.
     
    Will try harder next time :D
     
    Regards    Sharkey
  23. Like
    Sharkey got a reaction from Petar Petrenko in Performance?   
    Understood.
     
     
     
    It is not unusual for me to be wordy and I have been criticised for it before. Suppose I try to be accurate and in doing so become more confusing to the reader.  My apologies.
     
    Will try harder next time :D
     
    Regards    Sharkey
  24. Like
    Sharkey reacted to Petar Petrenko in Performance?   
    Clarity and simplicity are always appreciated, expecialiy when asking for help. You must understend that there are lots of people who would like to help and their mother tongue is not English so they can't understand complicated questions and explanations.  :)
  25. Like
    Sharkey reacted to R C-R in Performance?   
    Generally speaking, "Use hardware OpenGL" should be ticked on a Mac with GPU's as powerful as yours, but you can try it both ways to see if that makes any difference. It probably will perform more poorly without it ticked, but testing while editing one of your typical, very large files open is the only way to be certain.
×
×
  • 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.