Jump to content

LenC

Members
  • Content count

    100
  • Joined

  • Last visited

1 Follower

About LenC

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    : US
  • Interests
    photography

Recent Profile Visitors

581 profile views
  1. Making panoramas and keeping them in the Apple Photos space requires exporting the individual pictures, stitching, editing, and reimporting. The current software allows us to easily move all the pictures into AP, so it should not take much coding to simplify the process and eliminate/automate the exporting and reimporting.
  2. Apologies to Lance_G, this does not answer your question directly, but there is a recently posted series of videos on YouTube by D. Straker that covers frequency separation in Affinity Photo. The most technical one ("How It Works, In Detail!") shows, with excellent visuals, how the step-by-step process works for RGB images. The following link gets you to the series, or search for "InAffinity" and "Frequency Separation." (I have not viewed the more basic videos.)
  3. For the benefit of the Serif AP beta development team, I will try to describe the strange trip on the way to a successful launch of AP 1.7.110 on my desktop Mac. A couple of days ago I downloaded a macro offered by an advanced member that, it turned out, would not run in AP 1.6.7 because it had been created in a beta build. This .afmacros file when downloaded displayed the square beta logo rather than the triangular one before the file name. Shortly thereafter, practically all my existing .afphoto files (created in production versions) changed to display the beta logo in Finder or in other windows (e.g., Open). (Cause and effect presumed, not proven.) Attempting to address what I presumed was a faulty icon look-up, I removed the old beta app (1.7.106), using AppCleaner to remove auxiliary files. After that, most though not all of the square logos were replaced by the appropriate triangular ones. I then installed 1.7.110, but it would not launch, with error window exactly as before. I then decided to try to reinstall 1.6.7, though I did not remove it. At the Apple App Store, there was an icon suggesting to download from the cloud, but clicking it did not start a download. Then I clicked the square-in-circle icon that is usually a download progress indicator. This initiated an unfamiliar response from my Launchpad Dock icon that appeared to show downloading, though nothing appeared in my Downloads folder. When done, I clicked the beta icon in Launchpad, and the beta launched successfully. I still have something of a mix of production and beta icons in my directories, though it appears that the betas are gradually (mostly!) being replaced.
  4. I was unable to launch AP 1.7.106 beta last year and discussed the problem with a moderator on November 16, 2018, but no solution was posted. Yesterday I was encouraged by carl123 in an unrelated thread to raise the issue again in hope of aiding beta development. I have not tried again with a more recent build but will if it is thought possibly informative. Here is what happens, back then and now. My bought AP 1.6.7 and 1.7.106 beta sit side by side in my default Applications folder under my user directory (image). Clicking to launch the beta gives the hopping Dock icon and after a while the error message that appears when the apps are in the wrong place (image). I get out of there with cmd-Q or Force Quit. Hardware: My computer is a 2012 Mac Mini with memory increased to 8 GB. It works ok for my needs, though it has, especially with recent OS updates, taken to running very slowly, with the spinning beach ball often taking over for tens of seconds or even minutes. I use Force Quit a lot, though these delays usually resolve if left alone for a few minutes. Activity Monitor offers no useful clues. Sometimes AP fails to function, e.g., recently macros stopped working but worked on relaunch. Sometimes AP locks up completely, but not often. Software: please ask.
  5. That works, though I had to force quit and relaunch a locked-up AP 1.6.7.
  6. Well the icon change didn't happen on the first beta install and failure to run a month or more ago. It happened just now, with no further attempted beta install. The history is rather hard to recover, but I may still have an old installer in my trash. I will write this up again for the beta thread, but it did not get resolved the previous time. Looking through the trash, the original unrunnable beta was dated December 2018. As I scrolled through files in the trash, they all (of every type) came up with the square beta logo, which in a few seconds switched to a more appropriate one.Anyway, I will write up this tomorrow.
  7. I don't need the macro that seriously, though there are issues here to be resolved. Why have the Ritson macros stopped working? And, if any Serif experts take note and have an idea how I can run both the beta and the production versions on my desktop, it would be much appreciated. Maybe this leakage of beta icons into my Finder window display provides a clue. As noted above, the betas will not run on my desktop Mac Mini even though they are in the same standard app directory as AP 1.6.7.
  8. Yes, I just checked it: Library panel. Here is error message:
  9. @HVDB Photography FYI, when I tried to import your macros to my Mac I got an error "Unexpected Macros Format." Windows issue or something else? Do the macros work on either OS? Perhaps unrelated, but your macros file, my Ritson macros file, and all my production 1.6.7 afphotos files have recently acquired a square beta logo. An AP beta version is on my machine but will not run even though it is in the same standard apps directory as AP and all my other apps. The Ritson macros, including one for dodge and burn, appear to have stopped working. May not be your problem but my apparently peculiar though standard Mac. Also, >|<: thanks, that was it.
  10. I have an (untested) idea from somewhere that the Add blend mode on your three layers may give you what you are after.
  11. The burn tool works on a separate pixel layer as expected. It also sort of works if I select both the fill layer and the pixel layer underneath, with the burning happening visibly in the combined image -- but Ritson's video shows the gray layer changing lightness. Mine does not. This may or not be pertinent. I could not get Ritson's sequence 'create fill layer and then fill it with 50% gray' to work. Instead I chose 50% gray in the color panel and then created the fill layer from the menu, whereupon the new layer contained the desired gray. The color panel single circle was gray but could be adjusted to B/W without apparently affecting the burn brush behavior. Changing Tonal Range from Shadows to Midtones did not have any perceptible effect.
  12. I'm trying to follow Ritson's video below. Surely some trivial setting is wrong. When I paint on the 50% gray layer with the burn brush, nothing changes, even at 100% opacity. When he paints, you can see the gray layer getting lighter in places. I'm attaching a full screen shot. . Surely some trivial setting is wrong.
  13. Presumably you have created a basic white mask. Depending on what you want to do, you may want to make some black selections on it. If your question is more specific and contains some more details and is posted on the main forum page, you will get better help. I would go over the selecting and masking video tutorials Also look up masks in the online help https://affinity.help/photo/en-US.lproj/index.html If you are looking for a text introduction, there is a new inexpensive one by Robin Whalley that you can find through Google.
  14. Thank you for pointing out this video at Dave Straker's InAffinity YouTube channel, previously unknown to me, which has a large number of videos that I intend to explore. As he demonstrates, the menu Select .. Colour Range .. operation selects less than the full individual color channel. Thus selecting R, G, and B "ranges" individually and adding them does not give a full RGB image. The nature of the algorithm or result is not discussed in the online help topic Selecting Colours, which discusses app user choices more than app developer ones. The related Select .. Select Sampled Colour comes with tolerance and colour model options, showing that this operation is not as precisely defined as the channel masking one. In terms of practical image operations, I repeated the sky darkening operation I use with both a blue channel mask and with the select blues mask and found the results much more comparable than in my initial experiment that led me to the original post. No further help needed for now.
  15. Thanks, I should have thought to try that. Perhaps the busy @James Ritson could say a little about my first question.
×