Jump to content

LenC

Members
  • Content count

    111
  • Joined

  • Last visited

Everything posted by LenC

  1. 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.
  2. This is a change in behavior within the last few days. (The period might have included an upgrade from OS 10.14.5 to .6.) I export iPhone files from Apple Photos to a working directory from which, to choose a sequence to stitch, I usually display files sorted by Name ("Group Items by" in the window's icon's terminology). Ordinarily I can then scroll to the IMG_nnnn.jpg files sorted numerically. Today they did not sort correctly by name; the recently exported were grouped roughly together but not in numerical order. Initially they were increasing but scrambled. After switching to different sort choices they ended up in the decreasing order shown in the screen shot, with the recently exported ones at the top. After choosing different sort/group by options, Name now always returns to this screen. Sorting is correct if I choose Show items as List rather than Show items as Columns, so I can still operate the program, but does anyone have an idea why something so basic does not seem to work? I did a full reboot, but the behavior does not change.
  3. Yes, those are the settings I can contribute some more observations, but not solutions. Years ago I observed Apple Photos copying files from iPhone to computer out of order taken, so I thought perhaps the window here is sorting based on file creation date (to high precision). But apparently not. In Finder, under the cog one can choose View Options and get a window, labeled in the title bar by sidebar folder, that lets you choose Group and Sort separately. Apparently a 2-level sort. Perhaps there's a fix in there if one can understand what is meant. A side issue, but I think some Finder style windows (in Finder or an app) allow one to reverse sort. Why not all? Not even sure this is true, but I once had the impression that the behavior of an app Finder-style directory window was changing based on changing settings in Finder. Happy to try any experiments you suggest if time permits.
  4. I'll digest this tomorrow, but will just note that the motivation for needing this rapid search is that since the introduction of AP I have been exporting quite a few files from Photos to a working directory, and it would be nice to know if I had already done that rather than searching the working directory, since the sorting function (Group) does not always seem to work the way I think it should . If the file is not there, I could copy from the master, do my thing, export to Working and reimport to the library under a different file name. I know that it has been made easier to go directly from Photos to AP since I established that practice, but I just don't have time to master all the intricacies. I will manage fine, and thanks for writing at length.
  5. I love it that searching for an image string is so fast and brings up possible image stuff from everywhere and shows the whole path below BUT why does it show my iPhoto library originals and not my Photos library ones? The latter is what I use now. Is there a way to set it not to show my backup drive files unless I want it to, and not show PDFs if I want? Because of repetition of autoassigned image numbers (IMG_nnnn.jpg) and the issues above,, it takes considerable looking to identify the particular image I want.
  6. Deleted the iPhoto library, which naturally no longer is searched. But to my surprise, the Photos library is not searched. I guess I don't need that ability much, but would appreciate if someone has an idea to restore that. I had thought that this library search was a new feature of 1.7. Thanks to all for the suggestions; problems were solved, and something learned.
  7. I'll work on this and get back later. FWIW, this is not Spotlight Search but the bottom of the window I get in AP 1.7 when I do File .. Open ..type in '0533' in the search window (with current settings) and highlight that particular file to show the path. The Share folder was set up so long ago that I can't recall the motivation. Nothing has been done with the iPhoto library since I moved everything over to Photos back in - what - 2010? So deleting it should be no problem.
  8. The more one looks, the more odd corners turn up. If you press '+' in the window you get dozens of search criteria of possible and unlikely usefulness (e.g., Garage Band). And while we are chatting, is there a programmer's name for this window that is akin to a Finder window inside an app but may have different properties depending on various settings or even the app itself?
  9. It's buried in an iPhoto library (screen grab), which is the only one my search sees, not the 'system library.' I don't know why this is in 'Shared'; that was created ages ago. Any suggestion for a quick fix?
  10. Wow, Apple's buried preferences! Thanks for that, which worked on one try. I didn't know Spotlight was so involved in Finder. So, wise one, is there any way to tell it not to look at the many-sub-sub Thumbnails folder in the library since I don't usually want to open them? And, on your previous suggestion, the Photos Preferences General tab shows the correct Photos library after Library Location, but the button Use as System Photo Library is grayed out.
  11. It's a Time Machine backup. That I have never backed up from. Maybe there's another setting somewhere.
  12. I'll do some experimenting and report back on what I find. But why should Search This Mac also search the backup drive?
  13. 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.
  14. 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.)
  15. That works, though I had to force quit and relaunch a locked-up AP 1.6.7.
  16. 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.
  17. 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.
  18. 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.
  19. Yes, I just checked it: Library panel. Here is error message:
  20. @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.
  21. I have an (untested) idea from somewhere that the Add blend mode on your three layers may give you what you are after.
  22. 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.
  23. 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.
  24. 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?
  25. 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.
×

Important Information

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.