Jump to content

LenC

Members
  • Content count

    100
  • Joined

  • Last visited

Everything posted by LenC

  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. 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.
  4. 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.
  5. That works, though I had to force quit and relaunch a locked-up AP 1.6.7.
  6. 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.
  7. 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.
  8. 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.
  9. Yes, I just checked it: Library panel. Here is error message:
  10. @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.
  11. I have an (untested) idea from somewhere that the Add blend mode on your three layers may give you what you are after.
  12. 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.
  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. I'm trying to learn about using channels for blending or masking to darken a sky. I selected my background layer and executed Background Blue channel: Create mask layer. The new mask layer appears as in the attached file, with a checkerboard all over the image. The blue channel is supposed to be 256 shades of gray, not an alpha channel. (My document menu has Transparent Background checked, presumably a default, as I don't know what this means.) In any case, if I nest the mask in the background layer it appears as the blue channel and does what it is supposed to do, permitting me to blend-Multiply-darken the sky without darkening the foreground. Can someone clarify what is going on or where I can read more about this? Also after importing a JPEG, the Channels panel always shows a Background alpha channel, which can't be there (I think). Bug, or feature of which I am ignorant?
  15. 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.
  16. Or point me to some text or video. I understand and can make use of the Channels to Mask Layers macro, and I would think the Colour Ranges to Masks would do the same thing, which it doesn’t. Can someone explain the steps used in the macro and what the resulting mask is useful for? For that matter, is it possible to display the steps of a macro other than when creating one?
  17. Thanks, I should have thought to try that. Perhaps the busy @James Ritson could say a little about my first question.
  18. Thanks to both. Just a little more: how do you create that link to a particular member like @GabrielM?
  19. Thanks, I guess my puzzlement is just because I never saw this before, and it does begin to make sense. I have created masks as part of adjustment layers for a couple of years and never (IIRC) saw this checkerboard before. I get it that a mask and an alpha channel are two aspects of one type of algorithm, but not sure when the different names apply. The mask above the layer shows the checkerboard plus what's visible in the layer below, but nested with the layer it shows no checkerboard, or just the blue layer if I click the thumbnail. But the Channels panel has added a Mask Alpha channel. I will have to check if other masks have a Mask Alpha channel. The bug question was separate. I thought that all JPEGs do not have an alpha channel by their 3-byte design ; is this right? But the Channels Panel has a layer (empty) labeled Background Alpha. This would make sense to me if importing a file with an alpha layer, but not if it does not exist. I will be exploring the issues with channel behavior and UI in AP that others have pointed out in these forums.
  20. That's right. Also checked it in the Terminal since there was another Applications folder, but it is empty. (Will not be responding tonight if you have other thoughts, must sign off.)
  21. I have had the same problem since the beginning, unable to launch the beta, even though both apps are in Applications off root as far as I can tell. But I guess this is too rare to inspire a search for a solution.
  22. I am a beginner in LAB attempting to apply the writings of Dan Margulis, who uses only Photoshop, to Affinity Photo. The LAB underlying functionality is mostly OK, but I have found that the AP user interface could be improved in several places. More experienced users, please comment. 1) In the Curves adjustment layer with LAB selected, the A channel curve is colored green and the B curve magenta. The appropriate colors are green left and magenta right for A; blue left and yellow right for B (with light or high luminosity on the right). 2) Creating a check box on the A and B curve windows for Intersect Midpoint would make it easier to construct color-intensifying curves. This is probably the most important basic move in LAB, and even Photoshop does not have this feature. 3) The Input Minimum and Maximum default to 0 and 1. Though I have not found a use for these, shouldn’t they be -1 to 1 or -100 to 100 or -127 to 127? 4) The Curves/LAB window’s second drop-down menu offers Master, L, A, B, and alpha. Is there a known use for ‘Master’ as in RGB? Nothing I have read about LAB indicates that there is. For that matter, is there any use for Master in CMYK? And how about ‘All’ as an alternative to Master in RGB? Furthermore, the histogram curves displayed for the LAB components here are not positioned the same as when one transforms the document to LAB and displays its histograms. May relate to previous point (3). 5) Photoshop can display the graphs of the various color space curves with the light (high-luminosity) side on the right or left (one-click toggle). This option would be useful to people learning from Margulis’s books, which show dark on the right. 6) Other Affinity users have called for improvements in the Curves window in general, not just for LAB: more precision and ways of placing nodes, a larger or scalable window, saving curves. Because of the sensitivity of the A and B curves to small movements, a fine control on node dragging would be handy, e.g., option-drag would reduce the motion by 1/5 or 1/10. Perhaps it already exists. 7) A LAB curves user on this forum called for a keyboard shortcut to move among the channels. Why not? He needs efficiency in a much-used workflow application. In the same vein, having selected the color space, instead of a second drop-down, radio buttons for the three or four channels would slightly simplify choosing one. 8) In the Channel Mixer adjustment layer, the LAB window A and B sliders need appropriate coloring like the RGB and CMYK. Just for consistency. 9) The Levels adjustment layer makes sense in RGB, but I am not so sure about LAB and CMYK. Does this lead to a useful correction? (Please help me, advanced users.) If you push the existing RGB colors to the AB limits of +/-127 won’t you just create out-of-gamut colors that will have to be distorted back in RGB space? And is gamma defined for this color space? Also, in the LAB window, shouldn’t the correct labels for the sliders be, for the A channel, green and magenta, and for the B, blue and yellow. Similar questions for CMYK. 10) The Apply Image filter and Channel Mixer adjustment layer seem as if they should have similar functionality, but their capabilities and interfaces are rather different. My understanding of Apply Image in Photoshop from Margulis is to blend or replace channels one at a time, sometimes across color spaces, but to do that in AP one has to create a gray scale image of a channel in a layer and make that the source. The destination seems to be all channels of a selected layer, or does one have to separate out those channels as well? The Channel Mixer is designed to specify a single channel as destination, but it appears the source must be in the same color space. Shouldn’t these two processes allow individual choice of source and destination channels in all color spaces? Are equations (Apply Image) and sliders (Channel Mixer) of equal value in practical applications? I don’t think this exhausts these issues, but this post has already exhausted me. My compliments if you have read this far. If you want to know more about Margulis, use a search engine or post here and I will try to summarize what I have earned from a large corpus of writing.
  23. Could we get a post pinned to the top of this thread or otherwise visible that tells where the latest version of the roadmap is to be found, or even contains it?
  24. The "master" histogram shown in the current version is the intersection of all the channels. The current beta has improved this, though IMO there's more to do. Why don't you look at it and offer comments in the beta forum.
  25. I was interested in the claim in the 101 release note that the Curves histograms had been fixed in a version prior to 101. Something changed, but there are a number of old histogram issues, including the "master" that is not a sum of RGB or CMYK channels but apparently the common area; the "master" in LAB that is nonsense; the fact that the histograms did not change when the colour format changed using the drop-down in the Curves window; the poor legibility of the multiple-channel display, and perhaps some more (I have some notes but I didn't think they were neat enough to publish yet). So what is fixed, and is it fixed if we are able to change the colour format?
×