Jump to content

MikeFromMesa

Members
  • Content count

    1,182
  • Joined

  • Last visited

About MikeFromMesa

  • Rank
    Dedicated User

Profile Information

  • Gender
    Not Telling
  • Location
    Arizona, United States

Recent Profile Visitors

1,224 profile views
  1. MikeFromMesa

    Rolling Selection bug

    It seems fixed. At least I was not able to reproduce it when I tried. I will do some additional testing and post if I run into this issue again. And yes, I have Metal set.
  2. MikeFromMesa

    Validating the beta

    Interesting to know, and it does explain why this is happening, but it does not fix my problem. I would have thought that the developers would have considered this condition when releasing the Beta.
  3. MikeFromMesa

    Validating the beta

    There is a significant difference between how the regular release works with my Topaz Studio plugin and how the Beta works with it. The Beta version, at least the last one, allows me to call Topaz Studio and then call the Topaz plugins. The regular release (1.7) does not. I do not know why there is such a basic difference between how the two operate, but I use the Beta rather than the regular release because of that.
  4. MikeFromMesa

    Validating the beta

    Yes. I realized that after I posted.My mistake. I updated the regular AP from the App Store and updated the beta from the link sent to me via email. The fact remains that I can not use the beta because it asks me to validate it using my email, but when I enter the email there is no button to press to validate using that email. The Validate button seems to validate the serial number and, having bought in the App Store, I do not have one of those.
  5. MikeFromMesa

    Validating the beta

    This is puzzling to me. I updated the beta from the App Store and now it is asking me to validate it using either my email address or a SN. Since I bought it from the App Store I entered my current email address but the dialog box does nothing. When I press the Validate button it tells me that the information is invalid, presumably because there is no SN. How can I get it to accept my email address?
  6. MikeFromMesa

    Luminar plug-ins not working in beta version

    I tried using Luminar Flex (which is their plugin) and it never launched. Flex did not crash. It just did not run. Once AP/APB goes into plugin mode you are stuck if the plugin does not run.
  7. MikeFromMesa

    Topaz JPG To RAW image

    Sent via PM.
  8. MikeFromMesa

    Topaz JPG To RAW image

    I am not sure that this post belongs in the beta or regular AP forum, or even sure if it should be in either, but I think it may be an AP issue and I did want to raise visibility in case it is a real issue. Topaz is marketing an app called JPG to RAW that users can use to create dng files from jpg images. While I don't know exactly what it does to the jpg to produce a dng, and I do not know if the resulting image is any different or better than what the free Adobe DNG converter produces, I did want to give it a try. I generally shoot in raw so ignored this app when it was first released, but tried it yesterday out of curiosity. I do shoot my backup photos in jpg so there is that, and my Olympus E-M1.2 does automatic de-fishing of images I take with my 8mm fisheye, but those images are (of course) jpgs so I might have some use for it. In any case I loaded the resulting dng file into Photoshop ACR opened it and the auto-adjust looked just fine. I did not have to do anything. I then loaded it into Affinity Photo (both the regular and the Beta) and got a terribly over-exposed image. When I tried to compensate by lowering the exposure (2+ stops) the result was badly tinted as well. You can see both screen shots here (PS) and here (APB). As I said I do not know that this is an AP/APB bug but thought the developers at Serif might want to know. I would be happy to send the actual dng image if desired.
  9. MikeFromMesa

    Rolling Selection bug

    I have been able to reliably repeat this problem on the latest Beta (1.7.0.130), but not on the regular release (1.6.7). On the Beta I get it with both raws and jpgs and with every photo I have used. Here is a screen shot of what I see: https://www.dropbox.com/s/30t9r0azu9yrudi/RollingSelection.jpg?dl=0 although it is only a snapshot of the rolling selection. Here is what I did to create a luminosity mask: 1) Load an image, 2) If the image is raw, press the Develop button, 3) Unlock the background layer and duplicate it, 4) Make sure the new layer is selected, 5) Add an HSL adjustment, make sure the Master is set and turn down the saturation all the way, 6) I also then selected the Blue setting and raised the Luminosity to include more of the sky, but I do not believe this has any bearing, 7) Merge the HSL adjustment with the top selection, 8) Make sure the top merge layer is selected, right click on the Red Composite entry in the Channels panel and select Create Spare Channel, 9) When the channel has been created delete the top merged layer so that only the background layer remains. Make sure it is selected, 10) Press the Reset on the RGBA Channel entry to restore color to the image, 11) Right click on the newly created Spare Channel and select Load To Pixel Selection Here is a screen recording of the whole process.
  10. MikeFromMesa

    Rolling selection

    This issue is apparently repeatable. I have followed the same sequence twice and gotten the "rolling selection" each time. I guess I should file an official support request.
  11. MikeFromMesa

    Rolling selection

    I was experimenting with creating Luminosity Masks with the Beta. I was using the tutorial at this link and although it worked reasonably well I also so what I can only describe as a "rolling selection" when I loaded the LM to pixels. Here is a video of what I saw. I will go through this again to see if I can reliably repeat this issue. This reminds me of an issue that I reported some years ago, so something may have re-surfaced.
  12. OK. Thanks. That was what I expected, but it is always good to get confirmation.
  13. 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?
  14. 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.
  15. Yes. I am not seeing this anymore with the latest release.
×