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

IanSG

Members
  • Posts

    1,450
  • Joined

  • Last visited

Posts posted by IanSG

  1. 2 hours ago, firstdefence said:

    You need to talk to the printers you use

    Agreed - in spades!  I designed a poster for one of my choirs a few years back.  Everyone thought it was great, but I was told by various printers that they either couldn't handle the gradients or the predominance of one colour (blue) made it uneconomical for them.  No harm done, and I ended up finding a printer we're all very happy with, but if I was designing posters for a living....

  2. 2 minutes ago, v_kyr said:

    See for the actual 1.6.x relesase versions:

    And for the 1.7.x beta versions so far ...

    Further note that under MacOS you can also make use of Apples RAW engine instead of the Affinity/Serif one in Affinity Photo, which means you can there switch the RAW engine to use. Therefor see the Apple OS releated reference links and their RAW support included in the above shown links postings.

     

     

     

    That list doesn't include the A7 III - "not supported" isn't  the same as "doesn't work"! 

  3. 2 hours ago, Jaffa said:

    Hi Ian, I hope that my suggestion is too basic, nevertheless, I recall that when I first started the selection brush happened to be in the "subtract" option.  Simply switching on the toolbar above to "add" solved the problem. This happened many times before I "cottoned on".

    I'm ashamed to admit that it wasn't too basic - that's exactly what I'd done wrong (this time)!!  Many thanks!!

  4. 11 minutes ago, carl123 said:

    It is my understanding that the released (1.6) versions will now never be patched. (Unless something like a major OS upgrade breaks them)

    Any bugs found in 1.6 that are fixed will be fixed in the 1.7 versions (beta and release)

    The 1.6 versions will always have those bugs for now and forever.

    So, if it has been fixed, your only choice is to use the 1.7 beta or wait for the official release of 1.7

    Reporting known bugs in 1.6 that are already fixed in 1.7 seems pretty redundant now but new bugs found in 1.6 should still be reported as the fixes can be added to the 1.7 versions (beta then release)

    All true - especially since we're looking at a new point release.  But the same argument could have been made 6 months ago, and maybe 6 months hence.  There's nothing in the beta release notes to suggest  that the problem's been fixed.

  5. 2 minutes ago, carl123 said:

    Is this on the released version or the beta?

    Unless it's reproducible on the beta it's possible it's already fixed. 

    The 1.7 beta has had numerous fixes/improvements since it started and cant be that far away from being released officially

     

    It's the release version - it works with the beta.  This has happened to me maybe half a dozen times over the last couple of years (but count how many times it's cropped up in this forum).  Each time it's happened I've gone to the  beta to make sure I'm not doing something wrong, and then cleared the problem by resetting AP.  It's possible that it's been fixed in the latest release, but I've got a solid example of an intermittent problem that's survived for a couple of years.  

  6. 16 hours ago, bwana4swahili said:

    I really like Affinity Photo (AP) most of the time; HOWEVER, the super slow loading/processing of RAW files is a real bummer.  Maybe this doesn't apply to Canon and Nikon RAW format BUT loading Sony RX10 III/IV and A7R II RAW files is a show-stopper.  In fact it is so slow I've gone back to preprocessing RAW files to TIF format in Lightroom then loading the TIF files to AP.  The result is a saving of 15-30 minutes for 10+/- RAW files!!

    Lightroom, Photoshop and OnOne load RAW files almost instantaneously.  What is Affinity Photo doing that causes it to essentially stall!?

    Crashes:  The above process (RAW processing) is also one of most common causes of crashes in Affinity Photo, i.e.: no error messages, AP simply goes away!

    Environment:

    • Lenovo YOGA 910
    • Windows 10 Pro
    • i7 CPU
    • 16GB RAM
    • 1TB SSD

    I've just tried a few RAW files from the RX10 IV and the A7R II - using v1.6.5, the former loaded in 4 seconds, the latter in 9 seconds.  Even loading multiple files, the increase in time was linear.  I'm using a desktop PC rather than a laptop, but the only significant difference that I can see is that I've got 24GByte RAM. 

  7. 1 minute ago, smadell said:

    Yes, for me, FastRawViewer is a one trick pony. But it’s fast, and it’s cheap, and the idea that I can see the Raw histogram instead of a JPG histogram makes it well worth the $20 price.

    Pretty much the same for me, though I've set it up to display "enhanced" RAW files rather than using the histogram.  As well as selecting the keepers, I've also used it to sift through 6 weeks of holiday shots, moving those that featured people to a specific folder - that's what my wife wanted, and if I can keep her happy for only $20....  

  8. On 4/2/2019 at 9:01 PM, R C-R said:

    They should also know that almost all apps will perform much, much better on systems that significantly exceed those minimum requirements, even when that is not explicitly stated anywhere in the software's promotional info.

    Back in the day, my answer to "what computer should I buy" was "what will you use it for" -  for the last umpteen years it's been "what can you afford?".  Someone less charitable than me might blame programmers' increased dependence on Moor's Law to make up for their inefficient design/coding :).  

  9. 7 hours ago, R C-R said:

    Nevertheless, it is a commercial font that should not be available from any web site without the permission of its owner. The version included with Macs includes this notice:

    Apple licenses many commercial fonts so they can be distributed with the Mac OS, but that license does not extend to copying or installing the font onto anything other than a computer made by Apple.

    It's worth noting that that copyright notice goes up to 2002 - couple it with this from Wikipedia (my emphasis) "In 2003, Hermann Zapf completely reworked the Zapfino design, creating Zapfino Extra, a large expansion of the Zapfino family designed in close collaboration with Akira Kobayashi.".  There are lots of sites providing free downloads of Zapfino, and many of them specify that it's the Linotype One or that it's the "official" free version - it looks like the owner gave permission.

  10. 1 hour ago, Alfred said:

    They apparently have two legs, one of which is much shorter than the other, so they tend to have great difficulty doing anything other than walk around in tight circles.

    Not that easy!   The asymetric legs are a genetic response to running round the steep mountain slopes - you still have to find the little buggers in the heather!  And then there's the issue of whether your hunting the dextro or levo versions....

×
×
  • 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.