Jump to content

MikeFromMesa

Members
  • Content Count

    1,182
  • Joined

  • Last visited

Everything posted by MikeFromMesa

  1. OK. Thanks. That was what I expected, but it is always good to get confirmation.
  2. My basic question was whether or not there was any way out of having a plugin not run. That is, AP is in a state where no commands can be called because of the plugin that is not running. Is there any way out of that situation other than terminating AP?
  3. I tried to run the new Luminar Flex plugin from AP today and it failed. I got the Plugin Started dialog but Flex never actually opened. This post is not about not being able to run the plugin - who knows what that issue might be - but rather is to ask if there is any way out of this situation. That is, if a plugin is called, the Plugin Started dialog opens and nothing happens, is there any way to get back to the edit state without closing AP and starting all over again? Starting the "Force Quit" on my MacBook Pro does not help since the plugin runs in the program space of AP and so I can not close it without also closing AP. I would rather not lose all of my work but don't see any way out of this condition. Of course in the future the best policy would be to save the intermediate state before calling a new plugin but once there is there any way out of that situation? This question is about the Mac platform but I also wonder if the same situation exists on Windows.
  4. Exactly how does someone determine what the current Persona is? I can find no visible indication of the current Persona state. The only thing I have been able to find is that clicking on the Affinity Photo command usually displays 4 Persona links and that the one that is missing is the one I am in, but that does not always work since sometimes there are no change links displayed. What is the easiest way to determine what the current Persona is? And yes, I generally remember what I changed to, but that does not help if I got called away from editing and return 30 minutes later, and it does not help when an image is originally opened. UPDATE: Never mind. Got it figured out.
  5. When Topaz's Studio is called as a plugin from Affinity Photo Mac it does not show any "Plug-in" command. I originally thought that this was an issue with the Topaz plugin itself, and reported it on the Topaz forum, but got a response that said that the same plugin, when called by the AP beta, showed the proper commands. Here is the relevant part of the UI when Studio is called from AP: Here is the relevant part of the UI when the exact same version of Studio is called from APB. You can see the Plug-ins command, which is missing when called by AP, is shown when called by APB.
  6. OK. That worked. So there were multiple problems. I needed to duplicate the layer and I needed to Merge the B&W image. Thank you for clearing that up.
  7. Did that. It did not do what I expected, and I did not get a mask. I am sure your instructions are correct, and that it works properly, but perhaps there is some intermediate step or setting that is wrong on my machine because it does not create a mask for me, but only creates a grouped image. The icon, which should show a mask, instead shows a B&W adjustment layer.
  8. @MEB I have sent you a video of the steps that I took to try to create a mask from the B&W image via a PM.
  9. When I did the Google search for an answer to this question I found your response to the same question from 2015, and I tried it. It did not give me a mask. It only gave me a b&w image grouped with the original image, and nothing I could do actually gave me a mask. I will do a screen video to show you what is happening and send it to you via a PM. I am sure I am doing something wrong, but I could not get your response to the old question to work.
  10. I have been playing around with some luminosity masking tools and the way they worked made me a bit curious as to why much of this could not be done easily with B&W images. That is, I assume I should be able to take a color image, create a black and white image from it using the B&W layer adjustment, refine that to include what I want and convert that directly to a mask for the original image. That process works with Photoshop but I can not get it to work with Affinity Photo. I did some searching looking for phrases like "Affinity Photo convert B&W to mask" and other similar phrases, and found several links, but none of the instructions actually seemed to do what I wanted. One, on this forum, said I should create the B&W image, rasterize it to a mask and drag the layer to the original image layer until a vertical blue line appeared, but I could never get the vertical blue line and always ended up with the B&W image grouped with the original image, and never got a mask. I am completely sure I am just doing this wrong. The tutorials talked about creating masks from selections, but I wanted to create the mask directly from a B&W image. Can anyone tell me how to do that? Thanks.
  11. I have been processing a series of HDR landscape sequences that I shot during a recent trip. I have done this before using AP without any issue but these photos were taken with a fisheye lens and so that distortion needed to be corrected. That can not be done within AP so, after adjusting the resulting HDR image, I tried to call a plugin (PTLensEdit) to fix the distortion, but it did not show as being enabled. In fact none of the plugin links were enabled. I had to save the image to disk and then reload it before I could get the plugins to enable, so I wanted to know if this was a bug or if it was by design. I understand that there is no name for the resulting HDR until it is saved, but even doing that (saving it) did not enable the plugins and the saved image had to be reloaded before I was able to call a plugin.
  12. Well, of course. I do not understand why I did not think about that before posting the question. Easy as pie. Thank you for reminding me.
  13. I recently purchased an inexpensive fisheye lens to use for panorama photos. When the images are "de-fished" they give a decent panorama, better than most stitched panoramas that I have processed, but the image tends to be a bit compressed vertically due to the "de-fishing" distortion. I loaded some of these images into AP to "stretch" them vertically, but could find no such native functionality. I ended up using the Perspective Tool and stretching both the top left and top right handles, but I thought there might actually be a "compression" tool that I could use to stretch an image either horizontally or vertically. Is there such a tool in AP?
  14. Yes. I restarted the app. As I wrote in the previous response: Try 2 involved removing all of the entries from the Plugins Search Folder and then restarting AP. However it does not matter at this point as the reset fixed the issue.
  15. > I was referring to the screenshot you attached No. That was not clear to me. However the screen shot I attached was taken after several tries at fixing the issue. Try 1 involved verifying that there were no entries in the default folder and then restarting AP. Try 2 involved removing all of the entries from the Plugins Search Folder and then restarting AP. Try 3 involved putting some of those Plugins Search Folder entries back in and restarting AP. It was after the 3rd try that I took the screen shot so it looked as though they might have had an effect. However the Plugin Search Folder only had entries for Topaz and MacPhun (now Skylum) plugins and nothing involving Luminar or Aurora, both of which were showing up in the defaults list. > Removing all those entries from that section should have cleared the list on the left without the need to resort to the reset. As I indicated, it did not. However the reset did.
  16. > do you have any entry in the Plugins Search Folder section The folder was completely empty. There were no entries, including aliases or other links. > remove them all from the Plugins Search Folder section and check if they still appear for you. There was nothing to remove. > This will clean the Affinity list. That seems to have solved the problem.
  17. > Hopefully an un sandboxed veriosn will be more available in the future which may solve some of these issue I am sure an un-sandboxed version would solve all of these problems. So would the ability to call an external editor app and pass along a temp copy of the current image, since most of these plugins have an associated app that could be called instead (and that is how I use them from PhotoLab and/or CaptureOne). But that does not address my concern as to why plugins are showing up even though they are not in the default folder.
  18. I know that improvements have been made to the AP plugin functionality so yesterday I decided to try to add some plugins to AP. The results puzzled me. 1. I first added some plugin modules to the default plugin folder. When the plugins did not work I removed the modules from the default folder, but they continue to show up in the plugin dialog box. There are NO modules in the default folder, but here is a screen shot of the dialog box. As you can see there are a great number of modules that show up as being in the default folder, but the folder itself is complete empty. 2. I then added some folders to the plugin search location, and you can see those, but none of the MacPhun Creative Kit plugins actually even start. If I load an image and call one of the plugins I get the dialog box saying that the plugin has started, but nothing ever actually runs and, because focus has been given to the non-running plugin I can do nothing with AP except kill the process. If there is some way to address these issues I would appreciate it.
  19. I have seen a similar problem, although on my system when I drag the bottom handle for the perspective tool and release it the top snaps out to where the bottom is. The effect is the same as R C-R reported. In Dual mode it works as described by R C-R.
  20. I uploaded 3 images from a high-res sequence from my Olympus E-M1 Mk II camera. The ORF is the high-res raw (80MP), the ORI is the normal raw (20MP) and the jpg is the 50MP jpg, OOC.
  21. How complete is the scripting for Affinity Photo? Is it limited to recording actions taken within the app? Or is it a complete scripting language, including the ability to control internal and external actions? Is there a scripting guide? If so, where could I download it?
  22. +1. This issue has bothered me in Affinity Photo for so long that I just gave up expecting it to be resolved.
  23. Yes, of course. Sorry. I should have named it in the original post. The app that this came from is the new ACDSee's new Mac workflow tool which they are calling Photo Studio. It is the successor to the ACDSee Pro 3 application and can be found here. What I have noticed is that many, but not all, tiffs from this app work this way, but all of the other 3rd party tools can load it properly.
  24. I have been testing a new workflow tool and noticed that some (but not all) of the tiffs it produces are treated by AP and APB as raw images. That is, when I create a tiff from that workflow tool and load it into AP and APB to do some additional processing, it opens in Develop Mode, specifies that the image is a raw (although the name shows it is a tiff) and then it can not properly display the image. I assume that it can not display the image properly because it is not a raw, but why is it loading a tiff as a raw? I assumed that the problem was with the image itself, but when I loaded the same image into my other software (PhotoLine, Elements, Luminar, ON1 and some others) the image loaded properly. It seems that AP and APB are both having problems with this image while my other non-OEM software is not. Perhaps the problem is the image itself, but then why can my other software open it properly? The image can be found here.
×
×
  • 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.