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

GracieAllen

Members
  • Posts

    28
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. There's nothing in the setup log. Just a few lines and "Setup Failed". The Microsoft Uninstaller troubleshooter got rid of enough junk I could put 1.10.6 on. Thanks for the reply.
  2. It appears all the V1 forums are blocked - at least I wasn't able to put a topic in any. I've got 1.10.4 and 1.10.5. It APPEARS 1.10.5 got installed at some point. It doesn't work. It doesn't exist. There's NOTHING there. EXCEPT, if I try to re-install 1.10.5 it says "Setup Failed" - one of the less informational errors. So, I cannot REPAIR 1.10.5 OR uninstall it. And I CAN'T install 1.10.4 because it SAYS 1.10.5 is already there. Is there SOMEPLACE I can get information to GET THIS unusable software OFF the system so I can put it BACK ON for what little use I need it for?
  3. I bought Affinity quite a while ago, and I very occasionally still use it - mostly to compare HDR output against Aurora HDR to see which I prefer. Certainly not enough use to make it worth buying V2. I can't get it to start, so I attempted to re-install 1.10.5, and just got a "Setup Failed" error. Tried to Uninstall it and got the same error. Tried to install 1.10.4 and it failed saying there's a newer version on the system. I can't uninstall anything, repair anything, or install anything, and even from the Control Panel I can't get it to uninstall. What do I need to do to make this go away so I can re-install either 10.4 or 10.5 - or, if there's a newer version for V1 (which I presume is what I'm licensed for), how do I download that and force THAT to install?
  4. Bummer... I found some discussions in here from about 6 digital generations ago - back in 2017-2018, talking about command line parameters and being able to use Affinity from Lightroom. I thought for SURE that after 4 years this would be available in some form. Fortunately, I've got other 3rd party tools the integrate cleanly with Lightroom. They may not generate an HDR that's quite as good as Affinity, but they're a WHOLE lot faster than having to go outside Lightroom and find images manually for dozens of stacks. Thanks for the reply.
  5. I have a copy of Affinity Photo. It says it's 1.10.4.1198. Unfortunately, I can't find any information on much of anything on the Affinity site, including exactly WHAT the current version of V1 is. And when I asked about updating, it sent me to the Microsoft Store to update for Windows... BUT, what I would like to do is export a set of images to Affinity from Lightroom, and have Affinity USE those images to do a "New HDR Merge". I can get the files there, but can't see HOW to tell Affinity to USE them to do an HDR. How do I do this? I have it set up as an external editor, but that's extremely limited - if I send three images, it creates .tif files. Instead I'm exporting directly, but either way, I need to know HOW to make Affinity USE the files. I figure this is something simple and stupid that I just don't know. Is there a command line parameter when calling photo.exe to tell it to do an HDR with the images it gets? Or there's got to be some other way...
  6. Yeah, I found that. What I haven't found is HOW to have "Batch Jobs" or anything else in Affinity do what I said in the original post - Select (Open) multiple HDR sets of images and have Affinity process each set and send them back to the source folder. Even better would be to be able to send them directly from Lightroom, but if I have to Open Affinity standalone and select them, that would be OK... Is Affinity capable of this or do I need to stay with Aurora, which can.
  7. I found a few topics on creating macros, but nothing on what I CAN'T do... I want to send a set (preferably multiple sets) of Nikon RAW HDR images to Affinity, have it generate the TIF output (I'd prefer a .dng output, but that doesn't seem to be an option), and put it back into the source folder. If necessary, I can start Affinity stand alone and load in a bunch of HDR sets, but is Affinity going to be capable of generating outputs from several HDR sets and sending them back to the source folder?
  8. PC, Windows 10 Pro, 32 GB memory, AMD5700 XT, LOTS of SSD storage I occasionally try using Affinity Photo for a focus stack or HDR. It rarely works. Typically, even for the simplest HDR - 3 images from a Nikon D850, I can add the images, tell it to deghost, and process. It churns for a while, then disappears. Nothing. No error, no popup, nothing. It very occasionally succeeds - maybe 1 time in 10 for HDR. I don't think it's ever worked for a focus stack, even a small one of 15 or 20 D850 images. Is there somewhere Affinity logs all it's processing so I have some clue why it consistently terminates? I've NEVER been able to turn on the hardware acceleration - not with the old GTX 970 OR with the new 5700 XT. The error popup doesn't make much sense: Windows 10 Pro matches, and it's had 21H1 installed... and the 5700XT should fit the "modern" GPU. Is there a reasonably simple way to find out what's going on?
  9. I'm hoping I missed an update or something, but there still don't appear to be plugins so I can use Lightroom to feed the Focus Merge in Affinity Photo. Are they out there, or if not, hopefully someone from Serif can at least indicate they're being worked on and will be available SOON, 'cause it's very inefficient to have to find the image filenames in Lightroom, then go outside of Lightroom to open Affinity, find the files, then run Affinity to OPEN the files, and finally run the Focus Merge.
  10. Thanks John... Yes, the source of THIS set is jpeg, because Helicon Remote on the tablet CREATES jpegs. I have other sets captured in RAW, both from a Nikond D810 and a Nikon D850, and they work fine in Helicon Focus and even Photoshop. Admittedly Photoshop is crude, but it doesn't produce halos. And yes, John, I know I can clone from one of the images, but that's not a practical thing to do in the real world. Cloning a half inch of stem may work, but on any normal focus stack it's not going to be reasonable to clone all thing things Affinity is handling poorly... In this case I rendered the stack with Method C in Helicon Focus. And yes, I paid for it a few years ago. I keep HOPING there will be a significant improvement in Affinity so I can STOP using Helicon, but from what I'm understanding here, there isn't... And having to spend time trying to clone out the problem areas from Affinity, that don't occur in other products, isn't a practical answer. Is there any practical way to "encourage" the people making Affinity Photo to improve their Focus Merge 'cause having to do extra work just to use Affinity isn't reasonable.
  11. As the original entry said, I ran a set of 4 images through Affinity Photo and Helicon focus. "a" and "f" are the outputs of those two processes. The images below them are close-up views of the images above. The halos in the image on the left do not appear in the image on the right. " Certainy halos such as you show can be an artefact of focus merging, but I think we need more information. Could you post a link to the four original images? " Yes, in some cases they can, but since they only appear in "a", I believe they're not the result of a problem with the input images. The only variable is which software did the processing. I was processing a bunch of series of images, and don't know which one I used for the original post. I ran a new set, which may have been the same ones from the original post and placed them on my website. I have no idea whether or not you'll be able to download them, but they're on my website at www.dperezphoto.com The files are 799.jpg, 800.jpg, 801.jpg, 802.jpg and affinity.tiff "It would also help if you could explain what you mean by "crop and resize." Are you talking about resampling the images or something else? " Crop and resize means I took the full-sized output of the 7360x4912 px inputs and cropped it to show the relevant area, then resized it so it wouldn't be overly large when I stuck it in the forum entry. "I would assume that both images have been produced by processing the set of 4 images through Helicon focus and then repeating the same process through Affinity Photo's Focus Merge to make a comparison but which image belongs to which processing?" "a" is from Affinity. Which is why I asked the question in this forum... "Image 'a' looks duller and more blurred than image 'f' which is clearer and brighter colour rendition." Duller, flatter. Which I presume is the difference in the two software program's default processing. With enough additional processing I can get the Affinity output to look the way I want, it'll just take a little more clarity, sharpening, and HSL than it will using the other image. That's not a big deal. The halos are. "Also what were the camera settings?" I don't know why it would be relevant, but it was a Nikon D810, using a Tamron SP 90mm macro, on a very sturdy Gitzo 3540XLS. Subject was in a windbox. Nothing was moving. I shot all the series at 1/200 @f/16 @ISO 400. The camera does minimal processing on the jpegs. As I asked originally - I don't see any settings, parameters or adjustments I can change for Affinity to optimize the quality of the output of the Focus Merge, but if there IS something, what SHOULD I be setting to optimize the output? I don't know if Affinity does this on every series 'cause I don't have the time to process them all through multiple programs and I need usable output from the image stack processing. But it's happened more than once. It does seem that the output from Affinity is duller and sometimes appears less sharp than the output of the other focus stacking software. As I said, I can work around that. But, coupled with the halos it makes Affinity difficult to use to get the best possible output to use as input for additional processing. The images and the tif output are on the website. Let me know. If the answer is "there's a whole bunch of people at Serif, busting their humps to make the Focus Merge work perceptibly better than Helicon or any other image stacking software, and the improved version will be out in xxx days/weeks" great. If it's "TS, it's not going to get better any time in the appreciable future", I wasted $40, which certainly isn't the first time.
  12. Hello? No response after a week? Is there some other channel for getting support on this product?
  13. Windows PC, Windows 10 Pro, GTX 970, 5820 running at 4.5GHz, 32GB of DDR4 memory. Current version (as of last Friday) of Affinity Photo... I bought Affinity Photo when it went on sale. To some extent because I'm hoping for a better tool than Helicon Focus for doing stack processing. I took a simple, 4-shot series of full-sized jpegs, captured with a Nikon D810 using Helicon Remote so the intervals are consistent, and processed it through Helicon and Affinity Photo. These were taken outside on a "windless" morning, so there may be very small differences in position between shots. Nothing visible, but... No processing was done on any of the images before, or after, the image stack processing, so these are as close to un-messed-with as possible. Only thing done was to crop and resize down to a reasonable size. Image "a" is on the left and "f" on the right The next images are a close-up of an area with "a" on the left and "f" on the right I'm using the Focus Merge (or image stacking) to create the raw material for further optimization in Lightroom and Photoshop, so I want the sharpest, cleanest output from the stack processing to start with. From my examination "a" isn't as sharp and has more "haloing" (or whatever you'd call that smear on the edges in the close-up images). Is there some setting or set of settings I can/should be using to improve the output quality of the Focus Merge?
  14. Rendering using the GTX 970 on six D810 images (not the same ones, but same number). Also changed the Disk warning to 20K the other night and Disk usage to 25K. Total time using WARP approximately 2:50. Total using the 970 approximately 2:35. Time using Helicon method C approximately 45 seconds. WARP slightly slower but nothing massive.
×
×
  • 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.