Jump to content


  • Content Count

  • Joined

  • Last visited

About wolfnowl

  • Rank

Recent Profile Visitors

174 profile views
  1. Hi There, and thanks for your response. Capture One 21 was released today; I downloaded and installed it, and so far Affinity seems to be working fine!! Mike.
  2. Hi There: I use Capture One 20 for my raw editing and image processing, and Affinity Photo for pixel editing, etc. This is all under Windows 10 (Intel(R) Core(TM) i7-8705G CPU @ 3.10GHz, 16GB RAM, Windows 10 Pro 20H2, OS Build 19042.662, Experience Pack 120.2212.551.0). I recently signed up to be a beta tester for C1 21 and have played with it a bit. This thread won't violate the beta NDA. This morning I started Affinity Photo (1.85.703) and when I went to open a .jpg file, it crashed. I tried other jpg files, a tiff file, and even creating a new document. It crashed every time. I went to the Affinity site, re-downloaded the install file and ran a repair installation. Hard booted the computer. Still crashed. I tried opening a file in Affinity Designer. It crashed. Downloaded the install file... The only other installation I've done recently is the C1 21 Beta program, so I used Revo Uninstaller Pro to uninstall the C1 21 Beta (I still have C1 20). Restarted the computer and Affinity works fine. I haven't yet tried reinstalling the C1 21 Beta program, but thought someone might like to know. Mike.
  3. Here’s another example: This is an overlay with two of three raw files in C1 on the left, and the panorama made from them in Affinity Photo on the right. Again, I exported the three raw files as .tif files and made a panorama out of them: Again, quite a difference. It seems that while Affinity can make panoramas, I need to create .tif files first rather than simply using the raw files. Mike.
  4. Here’s the comparison: The top three images are the raw files in C1. Bottom left is the panorama made from the C1 .tif exports. The other two images are the panoramas made from the raw files, using an sRGB Document profile and a PhotoPhoto RGB Document profile. The last two are almost indistinguishable, but there’s a small difference with the other four.
  5. I’ll be the first to admit there’s a lot about colour I don’t know, so feel free to correct me if I mis-step. I have a Sony A7RIII, Capture One Pro for Sony 20.1 and Affinity Photo 1.8.3. NB: I can’t see what you’re seeing because your monitor is different. Also, these are sRGB .jpg screen captures of what I’m seeing. Still, there’s value in comparing them to each other. 1) In Affinity/Preferences/Colour I have the default set to ProPhoto RGB: 2) If I select some raw files and make a panorama out of them, Affinity stacks them and renders them as a panorama. At that point I click on the Develop module, go down to Profiles and set the profile to ProPhoto RGB and click Apply. Once you click Apply it sets the rendered file as a pixel layer. Now, if you go to Document/ Convert Format / ICC Profile you’ll see that Affinity has set it to ProPhoto. It appears to default to sRGB but I haven’t tested it extensively. 3) Now, Lightroom works with Melissa RGB as a default colour space. Capture One doesn’t say, but I presume it’s similar. No matter. When I imported these raw files into C1 I used the Sony A7RIII generic profile, and the standard curve. No other adjustments have been made. 4) I exported the three raw files from C1 as .tif files using the ProPhoto RGB colour space, imported them into Affinity Photo and made another panorama. I exported the panoramas made with the raw files using an sRGB Document profile and a ProPhoto RGB document profile (both exported using a ProPhoto RGB profile), and I exported the panorama made using the .tif files, again using a ProPhoto RGB profile. I imported those three panorama files into C1.
  6. Hi There: Making HDR panoramas is a part of my photography workflow, and there are a few things in AP that would make this better. As it currently stands (1.83), one CAN combine all of the images into one panorama directly but this yields results that are distinctly lacking. The better way is to make the HDRs of each sequence first and then merge them into the panorama. There are two issues here. One is that while one can save the merged HDR files as .aphoto files, those files cannot be used to make panoramas. They're invisible in the selection window for the panorama. The next best way is to export each HDR merge into something like a 32-bit .tif file, and then gather those .tif files into the panorama. The second thing is that it's vital to do some tonemapping for each of the HDR merges before exporting them. Since (if one does this properly and used manual exposure control during capture) the exposures are all the same, the tonemapping choices for each set of merged images should also be the same. The simplest thing to do would be to create a macro before tonemapping the first HDR merge, and then run the same macro for each of the following sets. That's not possible. The best option I can come up with right now is to use Notepad to record the slider values I set for the first HDR merge, and then manually apply those values to each subsequent set before exporting them to .tif. Thanks! Mike.
  7. Thanks, Walt. The teaching assistant and I couldn't figure out why we were getting different results when doing the same thing. It turned out she was working on a rectangle (vector) layer and I was working on a pixel (raster) layer. The gradient tool does indeed perform differently on the different layer types. Mike
  8. Hi There: This may not be a bug as I'm still new to Affinity and taking a course on learning it, so feel free to correct me. 1) I created a new document, added a pixel layer, and dragged a gradient across. I set the left point to red, and the right point to blue: Now, without leaving the gradient tool, I added a third point at 50%: Here you can see there are three colours, with yellow in the middle. If I switch tools or even click on the canvas outside the document, I still have the colours showing but I've lost the gradient. This is where I decide I want to move the yellow more to the left. I click on the Gradient tool, but I still don't have my existing gradient (only the colours, not the control points). I draw a new gradient, but it looks like this: Clearly this is not what I want. I click back on the white->gray colour in the context bar and click on Swatches. Here my previous gradient is stored under Recent. I click on that colour bar and it replaces the white to gray gradient with the previous colours. From there I can click back on the Gradient option in the context bar, select the middle point (yellow) again, and move it to 25% for example. The biggest challenge as I see it with this method is where the gradient doesn't go straight from left to right across the document, but starts somewhere in the middle, or is angled like this: Duplicating that is going to be a challenge. The swatch maintains the colours, but not the gradient parameters, or if it does, I don't know how to find them. Mike.
  9. Walt: Thanks for the response. I understood that I could create specific pixel or size dimensions and create a custom aspect ratio from that, but I wanted to be able to draw something out from the screen and create a preset from that. Madpeaz: Thanks also for your response. For some reason I tried that yesterday and it didn't work, but it did today. Must have been a 1 or 0 in the wrong place. Mike.
  10. Okay, but the (perhaps unasked) question is then, how do you save a custom ratio? Mike.
  11. Hi There: Just downloaded/installed Affinity 1.8.3. In Photo, if I go to the Crop tool, choose unconstrained and set a custom crop, then go to the Presets Manager, Create Preset is grayed out. Mike.
  12. Hi Laurentia: What I attempted did work... even though I'm not sure about the .comask extension that was added. So if you want to link Affinity Photo to Capture One, set it - even temporarily - as the default for a file type you work with in Capture One. Mike.
  13. I take that back. I went back into Capture One, went to Edit/Preferences/Open With and Affinity Photo is now part of the list. No idea what's happening with the .comask extension, however. Mike.
  14. Hi There: I'm not sure if this is a challenge with Affinity Photo (1.7.2) or Windows 10 (latest updates installed) but I'll throw it out there. While I'm still using Lightroom 6.14 for my photography, I'm also using Capture One 12.1 in a hybrid workflow for my Sony A7R III (.arw) files. I use Affinity Photo rather than Ps for pixel editing. Now, in Capture One, I can right-click on an image and select Edit with or Open with and it brings up a list of software I can use for additional editing. C1 first creates a .tif file, then sends the rendered image to the program of choice. On that list are Affinity Designer and Affinity Publisher, but not Affinity Photo. I can go to browse, go to the correct folder and select photo.exe, but I have to do that every time. I asked this question on the C1 forums and someone suggested I get Windows to associate Affinity Photo with my .arw files. So, I did a quick search, right-clicked on an image file, selected Open With, chose Affinity Photo and set it to use as default for this file type. What happened is that Windows added a .comask extension to the file name - i.e. filename.arw.comask and then Affinity Photo told me (of course) that it couldn't open a .comask file. Any suggestions appreciated!
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.