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

Stuart444

Members
  • Posts

    63
  • Joined

  • Last visited

Everything posted by Stuart444

  1. Thanks for your reply, Walt. You were right. I had installed Affinity 2 from the file affinity-photo-2.1.1.msix, so I uninstalled it. I found affinity-photo-msi-2.1.1.exe on https://store.serif.com/en-gb/update/universal-licence/and installed that. The shortcuts in both programs set up normally and now work. Many thanks! Without being too technical, can you tell me why there are two installers, and why the downloads page pointed me first to the msix one?
  2. I used file browsers XnViewMP and Olympus workspace. When using Affinity1, I was able to set up a shortcut in those programs to open the file being viewed. This no longer appears to be possible. The Photo 2 exe file is in an odd location "C:\Users\stuar\AppData\Local\Microsoft\WindowsApps\SerifEuropeLtd.AffinityPhoto2_3cqzy0nppv2rt\AffinityPhoto2.exe". Neither of these programs will allow me to access AffinityPhoto2.exe. Please can you advise me how to get round this? Thanks
  3. Thanks for your comment and link. I don't necessarily agree with the views expressed there, but that's based on my experience, not any deep technical understanding of how RAW files are developed, either in the camera, in Affinity, or in any other RAW converter. I'm an amateur photographer who has many hobbies, so I don't spend lots of time looking for "better" when what I have is satisfactory. I found shooting in RAW and developing them in Affinity 1 gave me good results, and none of my camera club friends disagreed. Others might think my photos could be improved due to my use of Affinity develop were they asked to comment. I've heard a lot about DxO, indeed I have a friend who was an ambassador for them, but I don't really want to spend time and money if what I have isn't broken. So, apart from a quick skurmish with their free trial, I haven't used it. Raw Therapee is a bit impenetrable in my view, again time is needed to learn it well enough to use with confidence.
  4. Bought, downloaded, installed and it works! Great stuff, I'm looking forwards to finding the time to try the new features. Thanks again, James. Stuart
  5. Hi James, I must admit I didn't read all the cameras supported by V2 which I guess will be on the Affinity web site, and the statement I saw on the forum might have been wrong. It's a shame V1 won't receive any support for new cameras, but none of us can complain about the value for money which V1 was. A friend of mine upgraded as soon as V2 came out and I think at the time it was only as a bundle, and I've received several offers for the bundle since. So if that's the solution, I'll buy it. Thanks for the link. Stuart PS thanks for all your tutorials too - they make such a big difference for oldies who don't use it intensely, like me.
  6. I'm aware that the problem of Affinity 1 not opening these files was first discussed here over a year ago. For Windows users, it was said that compatibility depended on a program called LibRAW, and its update was expected within 6-9 months. I recently upgraded my M1ii to an OM-1, and found the problems that others described. I'm using Affinity Photo 1.10.6.1665, and have deferred upgrading to Affinity version 2 as I didn't want to buy their bundle with Designer etc which I would never use. Perhaps it's just as well I didn't! I'm aware that Fast Raw Viewer can view the new orf files, and I've read that Raw Therapee can process them for use in Affinity. I have versions 2.0.6 1971, and 5.9 respectively of these programs. I've not bothered much with those, as Affinity's RAW converted satisfied my needs well. I find that FastRawViewer does display my new orf files OK, but RawTherapee doesn't - I just get black squares for the thumbnails. RawTherapee does display my previous M1ii's orf files correctly. I've tried to convert the new orf files using DNG converter 15.4.0.1508 and that has converted the new orf files. So I have a work-around, but it's an extra step I don't really want to have to do. It seems to me that we are still awaiting LibRAW to support Affinity, both versions 1 and 2. What a weakness in the pretender to the throne! I'm as disappointed as I was years ago when Photoshop Elements only supported orf files if I paid for an upgrade, which led me to Affinity in the first place. Please can you tell me if and when we are going to get both Affinity versions to support my new camera? I'd hate to go back to Photoshop, but without this fix, I might have to. Thanks.
  7. Hi Walt, Oh no, I can't believe I missed that! Yes, I'd forgotten to select the move tool. Doh....... Many thanks, Stuart
  8. Hi Carl, Thanks for your reply. OK, I've made a new file using the same method (I was already using Save with History) and also a screenshot of the file before I closed it. In the screenshot you can see that the second image is still editable, but if you open the AfPhoto file you'll find neither image can be adjusted. Or at least, I find that. Test_file.afphoto
  9. I'm creating an overview image for a portfolio of photos. I'm making it by creating a new empty file, then placing the portfolio of 10 images onto it using File / Place. Each one appears on a new layer. Whilst the Overview file remains open, I can resize my Placed files, replace them, move them around over the new file, etc. It remains that way after I've saved the new file. However if I close it and open it again, the layers are then no longer editable, although I can switch them on and off, and delete them. If I delete one and then create it again, that layer's Placed file is again editable, but none of the others are. Why does this happen? Can I make it so that my placed images can be adjusted after closing the Overview file?
  10. OK. I'm ready now, but I don't suppose that counts I'm sure it will be worth the wait.
  11. Great, thanks. My computer has started bringing up the beta by default since I installed it, so rather than change that I'll keep using the beta. Do you know roughly when the retail version will be released?
  12. I see now that when files created in 1.6 are opened in the beta, it gives a warning that if modified they might no longer be able to be opened in 1.6. Does this mean there's a risk that they also possibly won't be able to be opened in the production version of 1.7 when it is released?
  13. I'm using Photo, and following @DanC's advice soved the problem. Thanks!
  14. Recently my Windows Affinity has been refusing to close, I need to use Task Manager to make it quit. When I try to close it, even if I haven't loaded any file in that session, it says "Quitting: At least one file is currently being opened. Please wait for files to load before quitting the application". Can anyone please tell me how to stop it doing this? Thanks.
  15. Is there any progress on this issue? It's not difficult to work around, but it is a bit tedious given the excellence of the rest of Affinity.
  16. Hi Dan, I apologise, I must have only looked at RAW images in Affinity but had looked at a partner JPG in the viewer programs (I had my M1 set to only record in RAW but the M5 to record in both). I've opened the M5's JPG in Affinity now and the histogram is correct. Stuart
  17. Hi Dan C, That's a relief (to me!) I'd noticed that the images performed normally in that Exposure or Levels can restore a "normal" histogram and the results appear OK after usual processing, but I figured something was wrong and assumed it was me. Great, I can live with it and look forwards to the fix. Thanks, Stuart
  18. I'm using an Olympus OM-D EM-1 mk2. Recently I've noticed that all RAW and JPG images straight from the camera that I open in Affinity have a histogram which is mainly on the left, little above 100 and nothing above 150. I've taken some test shots and made sure the histogram on the camera spans the full range. These show in Olympus Viewer 3 and in XNViewMP as having a histogram from 0 to 255. I've done this as well on my OM-D EM-5 mk 2 and got exactly the same sort of result. Is there some setting in Affinity that I've changed, as I've not seen this behaviour before in 2 years of using it. Thanks.
×
×
  • 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.