Jump to content

c_moon

Members
  • Content count

    16
  • Joined

  • Last visited

About c_moon

  • Rank
    Newbie

Recent Profile Visitors

393 profile views
  1. c_moon

    Script Error in Help on 1.7.2.434 Beta

    Mmm. I must be doing something odd! If I make this change to line 855, I get the same script message. However, if I just change the file name (added "1"after "functions", I get the help file without the script error - whether or not I make the line 855 change.
  2. Hi. If I select a tool and then use the space bar to get the hand cursor icon to move the photo about, when I release the space bar the hand stays showing instead of immediately reverting back to the original tool icon. That feels odd. Often, the hand will change to the tool if I move the mouse, which isn't ideal - or click which I may not want to do as that activates the tool. However, in some cases the hand remains there (again unless I click or) unless I move it to the tool bar and back again (without clicking, doesn't need to be the same tool). This has happened with the floodfill tool, selection brush and colour picker - I haven't tried many other tools. Thanks. Nigel
  3. Hi. If I make a section using the marquee tools or selection brush and then resize (using grow/shrink) I get the following oddities: 1. For a circle, when shrinking it, the shape soon becomes square-like even with the circle box ticked. 2. If I move the cursor out of the grow/shrink box and move it up/down or left/right whilst moving the mouse (left click) in one direction the selection will shrink then grow (or vice versa) instead of continuing to shrink (or grow). A while ago I asked about the possibility of being able to centre a square or circle selection about the mouse position so that it would grow equally outward from the mouse point, which I found useful in Elements (sorry for mentioning "them"!) for precise positioning. Is there any chance this might be implemented in Photo? Many thanks. Nigel
  4. Thanks, both. Just to be clear, the numbers on the settings sliders won't therefore be comparable? And you won't be able to get the same intensity (if that's the right word) of smoothness out of the live filter at maximum (which seems to be the case)? Cheers. Nigel.
  5. Hi. Trying out the two methods of denoise filter with the same settings, I get a very different look from each method - much smoother using the destructive filter. Is this supposed to happen this way? Same result on 1.7.0.367 and beta 1.404. Thanks, Nigel.
  6. I'm surprised that if a circle shape can be done centre outwards that a selection can't - but perhaps it's too techie (though lowly Elements had it). Anyway, thanks guys for the workaround. However, I'm being thick or click happy, but I can't seem to work this (new) option correctly. Is there some instruction you could point me to? Many thanks.
  7. Hi. Could I add my voice to those requesting the ability to draw a circle (or other regular shape) selection from the centre i.e. outwards from the cursor which is positioned at the centre? Many thanks.
  8. c_moon

    Black and white

    Hi Paul Fellow newbie here. Unless I'm misunderstanding what you are doing, if you shoot in B&W but in raw then when you load to the processing program the raw file shows in colour (as with Lightroom) and you then process the file to make it B&W. If you shoot in jpeg then I think you do get B&W from the outset. So this sounds normal, I think. I haven't tried the Canon software (which perhaps you've been using?), but I have a vague recollection that does give B&W from the outset. Cheers Nigel
  9. c_moon

    Oversaturated raw pictures

    Hi It's nothing to do with the Exposure Bias setting in Develop Assistant not being on "no action" is it? Cheers I'm a great fan of James' video tutorials (thanks, James!) but the video on exposure bias and the develop assistant settings has me flummoxed - either I am totally missing what these settings are for, or they are not working as they should. James explains that AP does not apply EB (based on the setting in exif) by default - which is where I started to get lost. After all, the exposure compensation setting causes a "physical" change in the camera settings to achieve the desired result - so how can AP not apply these, I wondered - after all, that would mean AP ignoring what I told the camera to do. To test, I took two RAW images based on -1/3 and plus 2 EVs, with aperture and ISO fixed so the variable was shutter speed. The develop assistant setting was "do nothing" and on loading into AP, the images looked about what I was expecting - and compared near enough to Lightroom. "So far, so good" as someone one said... I then tried the "initial state" and "default" options and in both cases the exposure bias was applied yet again, so doubled up - so effectively -2/3 and +4 based on what the camera "wanted" to do and -1/3 and +2 on what I had told it to do. In summary, the results were: No action - images as expected/wanted - slider setting 0 Initial state - image effects "applied again" up so darker or lighter than expected/wanted - slider setting being the EB/EV value Default - image effects "applied again" so darker or lighter than expected/wanted - slider setting 0 I'm getting the results I want using "do nothing" so I'm leaving develop assistant on that - but why would I want to apply the EB/EV already applied to an image again so it doubles up? If, as in James' video, I know that my camera consistently over/under exposes then I guess that might warrant a standard user setting to apply to all images from that camera, but even that must be inconsistent depending in the scene, I would have thought, and wouldn't be based on the exif data as this adjustment would aim to effectively override camera settings. What am I missing? Cheers
×