Jump to content

pb2016

Members
  • Content count

    21
  • Joined

  • Last visited

About pb2016

  • Rank
    Newbie

Profile Information

  • Gender
    Not Telling
  • Location
    New Jersey, USA
  1. Jon, I see something different. Behavior varies depending whether I exit brush adjustment mode by (1) releasing Mouse keys and then ALT key, or (2) releasing ALT key and then Mouse keys. With sequence (2) it works fine - the brush never disappears. With sequence (1) the brush disappears after releasing ALT; the brush reappears when I left click anywhere in the image. One further variation: Do sequence (2). Then do sequence (1) and it will work fine (brush does not disappear) the first time. Do sequence (1) again and the brush disappears each time sequence (1) is used. I had to upload the video clip as a Zip file since your uploader does not permit me to upload an MP4 file. There is a brief video clip inside the attached Zip file. The video illustrates sequence (1) and then sequence (2). It does not illustrate the further variation since that would have made the video clip too big to upload. Pete Brush Disappearing Video Clip.zip
  2. AP 1.5.0.45. After resizing a selection brush using mouse right + ALT + mouse left then drag the brush circle disappears. It then reappears looking normal after using the invisible brush once. While disappeared what I see is a cursor like a "+". This is on a Windows 7 Ultimate 64-bit computer. I'm assuming the brush circle is supposed to still be visible immediately after resizing and before again using the brush. Note: If I resize the selection brush using the left and right bracket keys the brush circle remains visible through the resizing. Pete
  3. Chris, Thanks for following up on this. A related suggestion: If Photo could also pre-build previews in a way similar to Lightroom that would greatly speed subsequent load times. This can help a lot when editing a large group of images and moving back and forth amongst them. The previews could automatically be removed after a time, say 30 days, also in a manner similar to Lightroom. I also realize this may be impractical since Photo does not maintain a library of image files. Pete
  4. pb2016

    AP 1.5.0.45 Help Not Working

    Hi Sean, Sorry - can't believe I forgot to add the screen shots. Yes - I was referring to the image files that I edit - they are on my F: drive. Pete
  5. I'm unsure whether to post this as a bug or a feature request. If it's in the wrong place, moderators please move as needed. I mostly process Nikon D7200 RAW images. The image files mostly are between 27MB and 34MB. I notice that in AP 1.5.0.45, as in the betas before, a saved .afphoto project file is about 154MB, or about five times the original .nef raw image file. On the plus side I notice that adding snapshots and using 32-bit RGB color do not increase the size of the afphoto file. On the negative side, that's a big file. By comparison, Adobe Lightroom (which I am trying to get away from) just creates the very small .xmp file along with the original raw image file. (With Lightroom I do not routinely convert to DNG.) So the overhead added storage per image is frequently less than 10KB and almost always less than 100KB. I understand that AP stores a bitmap in the afphoto project file and assume this causes a lot of the large file size. Nonetheless, that is a large pill to swallow. If I have, say, 250 images to edit from a trip this creates a lot of extra hard drive space. And at the moment I have about 11,000 images total in my Lightroom catalog. Adding 154MB per image is a lot. Is the file size as expected from a design perspective? If not, can it be fixed? If it is as designed, is there any hope of somehow using the original raw file rather than a bitmap, not incorporating a bitmap in the project file, and reducing the added storage per image to, say, 10MB? Thanks, Pete
  6. pb2016

    AP 1.5.0.45 Help Not Working

    Hi Sean, This makes sense, assuming the CSS failure also causes the links to not work properly. Attached are two screenshots. One is a cut-down copy of the F1 Help screen showing what Help item I right clicked to display in Chrome. The other is of my entire Chrome window showing the top of the AP help screen with the bookmarks toolbar blurred out for privacy. I did not vertically scroll the screen capture to show the full height of the help and I reduced the screen capture image by half to reduce attachment size. If you need either a larger size or the full height let me know and I'll upload a new version. The full path to the AP executable is: C:\Program Files\Affinity\Affinity Photo\Photo.exe It probably does not matter although I will also mention that all my image files are on a different drive. Pete
  7. Hi Chris, Sorry - I do not have a DropBox or other file sharing account. If you could find space and send me a link I will be happy to send some sample Nikon D7200 RAW images. Each of the images I would send takes just under 30MB. Pete
  8. Sankos - I think you are referring to the start-up time for Affinity Photo. This is different than the topic of this thread, which is about the time Photo takes to load a raw image file. If your concern is about start-up time for the application (Affinity Photo) then you may get more attention by opening a new topic. Pete
  9. Chris, Thanks for your response. I picked a Nikon RAW file at random and found these load times: Affinity Photo: 19 seconds Fast Raw Viewer: 3 seconds Lightroom 6.6: * 9 seconds when no 1:1 preview exists * about 2.5 seconds when a 1:1 preview exists In my Lightroom workflow if I import a set of images I'll be processing I routinely have Lightroom create 1:1 previews of all images so I can move between them more rapidly. I will be happy to provide sample images but the Attach Files limit on size of any one file is 20MB. All these files are in the range of 27MB to 35MB. Is there some alternate way I can get these to you? Pete
  10. pb2016

    AP 1.5.0.45 Help Not Working

    Hi Sean, It is simpler looking - attached is a screen shot of the Help window that opens when I press F1 or click Help. I use a Dell workstation running Windows 7 Ultimate 64-bit. IE version 11.0.9600.18499 is installed on the computer. Pete
  11. I'm running AP 1.5.0.45. When I click Help or press F1 the Help menu appears normally. If I scroll down to an entry and click it, the display scrolls back to the top of the help menu and nothing opens. The only way I can look at the help is to right click and open it in a new window. Then it opens in my Chrome browser. This is similar to what I experienced with the beta. A bug, or are we supposed to view help in a web browser? Thanks, Pete
  12. I'm seeing very slow file opening with Nikon D7200 raw files, which are about 29 MB. It takes 13 seconds from selecting the file to it opening in AP 1.5.0.45. This is only slightly faster than the 15 seconds I experienced with the beta. This is a real problem if editing a large number of images. Is it what I should expect, or is it a bug that will get fixed? Win 7, 24GB RAM, solid state drives. Pete
  13. Several requests focused on ease of use: Brush size: Rather than having to go to the toolbar, let me press, say, ALT and drag my mouse to change size. Show the changing size as I drag my mouse so I can quickly and easily get the size brush needed. The request is similar to how one can change brush size in Lightroom. Changing zoom factor: There are some screens where it seems I cannot change zoom factor without leaving the tool in use. Let the zoom change work at any time in the midst of any tool without having to leave the tool. Pete
  14. Hi James, Your explanations do help, thanks. They also generate more questions! Please pardon my questions. I hope to clarify these aspects and determine practicality for my post-processing work before investing a lot of time working with the beta. And I really want to find an alternative to Adobe products! My starting premise is a strong desire for non-destructive (perhaps better called impermanent or reversible?) editing. It seems I could create a mostly or perhaps entirely non-destructive editing environment by minimizing use of the Develop persona and frequently creating snapshots. I am open to your thoughts and rationale about why I should "get over it" and be OK with destructive editing. Perhaps there is a white paper on this? The D7200 I presently use is a 24 MP camera so I assume the .afphoto file would typically be about 1.5 * 120 MB = 180 MB. Ouch. Hard drives are inexpensive, but... Lightroom, for example, just adds the one small sidecar file and leaves the NEF file size alone. This could be a significant factor preventing my adopting Affinity Photo - I'll have to give it more thought. You mentioned using 32-bit output in Develop instead of 16-bit. Would this double the size of a .afphoto document file? Does saving snapshots add about 120 MB (for the "base case" with 16 MP image files) for each snapshot? Or is only editing information stored to allow recreating the snapshot? If the former then this limits the practicality of using many snapshots to achieve virtually non-destructive editing. It also seems, though, that I may need only one or two snapshots to achieve virtually non-destructive editing. Namely, before and at the end of the Develop persona work. I'm saying this assuming in the Photo persona I do almost all work using layers that may be left in the history for later changes. Is this reasonably accurate? Thanks, Pete
  15. Thanks for making the Photo Windows beta available. I look forward to testing it. I even forced myself to switch to an Aero UI to allow using the Beta. I am presently a Lightroom user and thus accustomed to fully non-destructive editing. In case it is relevant I edit Nikon RAW images, and usually export to JPG or TIFF. So I would normally start in the Develop persona. I'd like to clarify what editing is and is not non-destructive within Affinity Photo. Is this accurate: Anything done with an adjustment layer is non-destructive. Are filter layers also non-destructive? Is everything else destructive in the sense of getting baked into the image when done so it cannot later be undone? If the above is accurate then I gather the entire Develop module is destructive? If I save to an Affinity Photo document is it accurate that everything is effectively non-destructive in that the document can be re-opened, previous edits adjusted or deleted, and a new versioin of an image exported? Is the Affinity Photo document large - i.e. does it contain a copy of the image or is it only the editing instructions similar to a Lightroom .XMP sidecar file? Thanks, Pete
×