Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Luma range is killing my new Macbook pro M1 pro

Comments

10 comments

  • SFA

    How does the resolution of your screen compare to the resolution of the Preview files you are using?

    Do you have any power management settings that might be constraining processing in some situations?

    0
  • Henry Deletra

    I'm going to look at that, thank you. But I haven't change it, I have kept the default settings.

    0
  • Ric Cohn

    I'm interested in the answer to this. I have a new M1 16" MacBook Pro on order and I'm hoping to speed up several programs. Luma Range is one area where C1 really drags with my current MacBook Pro. For the record, I have "Preview Image Size" set to the width of my main monitor, a 17" Eizo = 2560 px.

    0
  • SFA

    Henry,

    It has occurred to me that your phrase "Using a single Luma range layer mask" might mean several different things as far as what you see in your processing is concerned. So it may be useful for the purpose of this thread to be sure about the effects you are seeing.

    I originally read the description to mean that some aspect of working to create a luma range was slow or that using that particular range was a problem. But since then it has occurred to me that you might be telling us that the Layer using that range causes a problem when it is active but does not if you make it inactive? That is a somewhat different problem.

    The other issue might be related to what the luma range selection is doing. Is it selecting a single block of information or does it perhaps identify a lot of small areas of a particular Luma value - possible even down to or near the pixel level across the entire image? Such differences could have a significant effect on processing power requirements and therefore the impression of speed.

    In the other hand if you do something using that layer and the response can be measured in units closer to minutes than to 2 or 3 seconds (3 or 4  seconds as a worst-case for most users I would guess) then maybe something else is affecting the results. You may need to ask the Support Team to take a look at the log files etc., before discovering any source to the apparent problem.

    0
  • Henry Deletra

    Hello,

    To answer your question, I said a single luma range layer mask, referring that is the only edit i'm doing to the picture. The problem is when the luma rage edit box opens. Everything slows down, even just clicking on display mask take a lot of time, when I click on the apply button sometimes the radius cursor goes by itself all the way to 300. So random behaviour.

    Thanks again for your insight, I will ask the support team to look at it.

    0
  • SFA

    Hi Henry,

    As a Windows user, not a Mac, user all I can say is that I have never seen anything like you have described - which is a very extreme reaction to a simple click. It is certainly not normal behaviour. I do not recall any previous similar reports from a Mac user - but I may have missed some.

    I cannot even think of anything that might produce such strange results - especially the radius slider.

    Have you already tried the reinstallation of C1? My guess would be that Technical Support might suggest that early in an investigation so one may as well try it sooner rather than later.

    0
  • Henry Deletra

    Ok I just reinstalled C1, and I have the same issue...

    I recorded the screen so I can send it to the support team.

    0
  • FirstName LastName

    I have the same problem, after i apply luma range it takes forever

    0
  • Wayne Smith

    I just tried the luma range on a filled adjustment layer as the only edit on a 50 MP image using an M1 Max MacBook.   Adjusting the range is very responsive - the displayed masking updates almost instantly when adjusting the range points or moving either slider.   Applying the mask is also very quick.   The Display Mask and the Invert Mask check boxes do appear to have a bug.   If you check or uncheck either it can take a long time (if ever) for the display to update.  However if you then immediately touch the range adjustment or a slider the display updates instantly with the slightest range/slider movement.

    0
  • Ric Cohn

    I am experiencing the same problem with my new 16" M1 MacBook Pro with 32 GB of RAM and a 2 TB hard drive. It seems to be only for a first Adjustment Layer-- which makes it seem like a bug. Is this what others are seeing?

    This was always the slowest part of C1 on my old MacBook Pro but this seems worse. I was hoping to speed things up and not slow things down. It is just adjusting the Luma Range that causes C1 21 to spin. Not all the time but it seems to be the initial adjustment that spins for a long time. There is no spinning when I add more Adjustment Layers.

    I haven't installed v22 yet, but is there any reason to thing that is better?

    0

Post is closed for comments.