Jump to content


  • Content count

  • Joined

  • Last visited

  1. That's fine R C-R. I'm just asking if Affinity Photo offers it now (i.e. command line options for stacks). I am not demanding the app to have that capability nor that the devs should provide it. I do fully understand the complexicity of these things as I write code for a living. I was just hoping for a yes or no answer from some one who's affiliated with Serif. However, that seems to be too much to ask, given the responses (or lack of) I received for my last post. Applications can be launched from command line the exact same way on both Windows and MacOS sanes the difference in executable name. But that's not really relevant here and not something AP needs to care about. The app launch stuff in my previous reply is merely an examply of what I would do in my own code (in Windows) to launch AP in a more streamlined manner from Lr. I can almost guarantee you that AP (or whatever frameworks/libraries it uses) is already doing checks for the things that you've mentioned whenever a file is read from/write to. Which is precisely why "In the GUI you could never add it to the list". But that's not what I was asking here. Since you've had spoken about how AP works in a matter of fact manner. Are you a developer working on it?
  2. It's been a pain in the ass everytime I try to do a HDR or focus stack from Lightroom into Affinity Photo as I would have to basically do Select photos in Lr --> Edit in Affinity Photo (external editor) --> Close all the tabs in AP --> open HDR Stack window in AP --> add photos --> click 'Run' every single time! As a software developer myself, I think it would be useful and quite easy if Affinity Photo could expose command line options such as a '-hdrstack' then some one like me could create custom launchers that can be added as Lightroom external editors that then launches AP with specific windows opened and prefilled. I've done some testing and basically Lr calls any external editor (e.g. Affinity Photo) as follow: photo.exe "photoPath1" "photoPath2" "photoPath3" If AP could support application launch parameters then I could write dummy 'editors' that will get added into Lr as external editors and call AP with the relevant command parameters. Here's an example, say if I want to do a HDR stack and AP could provide a '-hdrstack' command then a dummy Lr external editor can just call the following: photo.exe -hdrstack "photoPath1" "photoPath2" "photoPath3" New workflow would then just be Select photos in Lr --> Create HDR Stack (external editor) --> Click 'Run' in the AP HDR Stack window It should then open AP with the HDR stack window open and the photos added and ready to go. @R C-R without going in depth. You can basically launch any applications on any platform via command line. As far as AP goes, it receives the command line options and parameters the same way on both MacOS and Windows. It's just a matter of exposing a command line option and handling it internally which shouldn't require any platform specific code.
  3. Does Affinity Photo support command options and parameters? I.e. photo.exe -hdrstack "photo1.tif" "photo2.tif" "photo3.tff"
  4. Thanks @R C-R. You are right. I have included additional information on the spec and the environment the systems are running in.
  5. Hi, I have recently purchased Affinity Photo and have been quite happy with what I can achieve with it. I'm a photographer and I normally go through the workflow of Iridient X-Transformer --> Lightroom --> Affinity Photo on my PC. Affinity Photo is only used for stacking and tone mapping purposes using TIF files generated by Lightroom. More and more I am finding myself going through the same performance pain points where I am basically sitting there for minutes waiting for Affinity Photo to do something (which I will get into below). Last night I downloaded the trial version of Affinity Photo on my Macbook Pro and did a few tests. Turns out Affinity Photo consistently performs up to 3 times faster on the MBP using the same set of files. I am hoping someone with more experience here can give me some advice on how I could improve the performance of Affinity Photo on PC. Below are the specs for my PC and MBP: PC Intel i7-4790K OC'd @ 4.40 Ghz (with a large Noctua air cooler) 16GB DDR3 RAM @ 2400 MHz with XMP profile 1 enabled (G.Skill Trident-X 8Gx2 F3-2400C10D-16GTX) Nvidia 1080 GPU (a Gigabyte OC model) Macbook Pro (Mid 2015, 15'') Intel i7 @ 2.5 Ghz 16GB DDR3 @ 1600 MHz AMD Radeon R9 M370X + Intel Iris Pro 1536 MB As you can see the PC's spec is significantly higher than the macbook's. It is winter here at the moment (<0C outside) and the system is well ventilated (has no problem in 144hz gaming) so there is no thermal limitation. The photos that I edit generally sit on a NAS. The PC is connected to the NAS via ethernet and the MBP via wireless AC. I have uploaded a sample of 4 RAF files generated by a Fujifilm X-T2 onto Dropbox. Here's the link. To test the performance. I always repeated the following steps and timed each one on each machine: Create a new stack in Affinity Photo using the 4 RAF files Set Live Stack Group blending to minimum Rasterize the Live Stack Group Tone map the pixel layer Here are some observations I made from the tests: Affinity Photo loads up faster on the MBP than the PC. Creating a Live Stack Group is consistently quicker on the MBP. Live Stack group blend mode live preview is a lot faster on the MBP than the PC. Live Stack group rasterizing is significantly faster on the MBP than the PC (10sec vs minutes) PC tone mapping consistently takes 00:50 ~ 1:30 to process. MBP tone mapping consistently takes 00:20 ~ 00:22 to process. CPU heavy tasks will utilise 100% of the CPU on the MBP but only 60~80% on the PC in some cases. There is no CPU throttling on the PC at all (winter + large cooler) GPU utilisation never goes above 1% on the PC. There is very little disk/network bandwidth utilitsation during any of these tasks. All of the above are true regardless of which renderer I use on PC and whether I have hyper-threading enabled or not. Having the RAF files on SSD's instead of the NAS made no differences either. I have tried the latest 1.6 beta and it made no differences in performance on PC using the same steps above. I don't understand why a PC with much better hardware is being out performed by a Macbook by 3 times as much and generally have a much smoother experience... I am getting to the point where I am seriously considering using the MBP as a photo editing machine but that would mean some significant investment into repurchasing software licenses and some new hardware so I could actually dock the MBP to my PC monitors and input peripherals and I would rather not have to do that. Any help is much appreciated! EDIT: more info on the spec's and additional notes on the observations.
  6. I have the same issue on Windows as well. It is very distracting and annoying!