How is C1 on the new 2021 MacBook Pro and on MacOS Monterey?
I have not seen any posts yet about if C1 (latest version) works with MacOS Monterey?
I ordered a custom configured 2021 MacBook Pro arriving in two weeks or less, so I will have no choice but to deal with the just released Monterey. Has anyone else already updated to Monterey on any Mac? If so, how does C1 work on it? If someone already got their new 2021 MBP with Monterey (and M1 Pro or Max chip) is C1 working on it? And if so, much faster performance?
Thanks!
-
Would love to know if C1 works fine in Monterey too.
0 -
I think you have choice, because you can always install a different version of macOS - e.g. the previous one is still supported. When I got the MBP 16" the past February I installed Mojave (two versions behind Big Sur, that was already available) because it was an unforeseen switch (the previous laptop experienced a problem all of a sudden). I installed Mojave because I knew I had a few software applications that wouldn't work with Mojave. I took the time to update the needed parts, then upgraded to Catalina, then to Mojave.
I'd advice to stay with a o.s. version officially supported by your applications to avoid surprises.
On another perspective, I always avoid using version "x.0" of anything. It's likely it comes with (bad) surprises.0 -
I run C1 on two macs, and I just upgraded the '18 MBP to Monterey this morning to test. So far C1 looks fine, did some edits and an export. I may have time to try things later in the day if you want anything in particular, just reply to this.
To me , Monterey looks like a bug-fix release in a lot of ways, except maybe the cool features in Facetime to take on Zoom and Google Meet perhaps, and the email privacy features. Overall the changes appear to be communications related and perhaps not likely to affect C1. But we'll see.
https://techunwrapped.com/macos-monterey-now-available-whats-new/
1 -
C1 21 seems to run mostly ok on my new 16" MBP M1max with Monterey 12.01. There was a plug in failure on first start up however, but it doesn't seem to have occurred again.
Just to note I had to update my Canon 5d4 to the latest 1.33 firmware for tethering to work. Before that tethering failed.
1 -
@Peter -- good to know that basic stuff on C1 seems to be working on Monterey. Any update on using C1 with Monterey in the past couple of days?
@Adrian -- sorry to hear some of your plugins are not working. What plugins are you using? I guess I did not even know there were plugins for C1. I do not use tethering (I should!).
Also, it seems you will NOT be able to put Big Sur on the new 2021 MBPs due to their hardware spec needing Monterey from another forum post I read yesterday.
0 -
@Jason
I don't use anything other than a standard installation so it was a component of C1 that came up with the error. As I mentioned it hasn't happened again and unfortunately I was a bit hasty and didn't note the what the error was so I can't offer any further insights.
Incidentally, I've just run a test on processing a batch of 113 5D4 raws to jpegs with keystone, lens corrections and multiple adjustment layers which I had output last week for a client on my old MBP (a venerable SSD equipped 2013 model) and where that had taken about 22 minutes, which had felt a little slower than normal, the new MBP achieved the same task in about 1 minute and not even a hint of the fans coming on!! It's also run half of yesterday and all day today, including charging my phone, on the battery and has 20% still remaining.
Quite a revelation.
0 -
Also, it seems you will NOT be able to put Big Sur on the new 2021 MBPs due to their hardware spec needing Monterey from another forum post I read yesterday.
Actually 2021 MBP is not listed in the compatibility list of Big Sur: https://support.apple.com/en-gb/HT211238
Fortunately I'm not going to buy a new laptop, but it's really annoying to see this behaviour from Apple.
0 -
@jason, so far so good. Unfortunately a hot water tank failure dominated my last couple days! (aargh, the trials and tribulations of home ownership) ... but I did manage to tether and initiate photos from my macbook triggering my Sony A7r3 and it worked as it has the last couple years. I was able to change ISO from the laptop and a few other controls.
Editing wise, I didn't do a ton, but played with layers and masks and all worked. So nothing noticeable for me so far to worry about, but I don't pretend this to be a thorough test.
0 -
@Peter -- thanks for the encouraging update. I shoot with a Sony a7R IV and have more and more shoots where I can see shooting tethered would be beneficial. I will give it a try. Sounds like you have done a pretty good job of testing out C1 to me.
Good luck with the hot water tank!
0 -
Adrian, do you have the 24c or 32c GPU? The M1 Max comes in two configurations.
0 -
@Wesley mine is the standard configuration M1 Max with 32 core GPU, 32GB RAM and 1TB SSD
I did consider the 24 Core Max version but, in the end, for the small amount extra bearing in mind the considerable overall cost of these things it didn't seem worth comprising. Plus, anything non standard was looking 3-4 weeks delivery minimum.
0 -
I have new macbook 16" m1pro.... Can no longer tether my gfx100 to capture one pro. Ideas anyone?
0 -
I have a gfx100s, never tethered it before, but my Sony tethers fine.
Is there any setting on the GFX you need to tweak before plugging it into the Mac? (I'm on an intel mac BTW). I'll try to find info on it. If I cannot get it working on mine, then it's not an "intel" vs "apple silicon" issue, it's a C1-on-Monterey issue.
0 -
Correct my last post. I got tethering to work with intel macbook and gfx100s on Monterey.
I had to go the camera menus and change one thing:
- enter settings (wrench)
- connection settings
- connection mode
- and set to "usb tethering auto"
I was able to trigger a photo from C1, the camera took the shot, shot showed up in the Session browser. (I only use sessions for tethering).
0 -
I'm on C1 version 20, and currently running Catalina. Has anyone tried v20 on Monterey? I would love to upgrade my OS, but I don't plan on paying C1 money every year, Adobe-style ;).
0 -
With further use I've uncovered an odd and potential issue with C1 14.4.1.16 on Monterey 12.01 on the new M1Max 16" Macbook Pro, has anyone else had a similar problem or is it something I'm doing, I've not come across this behaviour before? I will make a support case if there's no obvious flaw in my method.
With a Canon 5D4 raw file using the healing tool (in a layer) the effects look perfect in C1 but when output as a 16 bit PSD and viewed in PS the results are anything but good. I've tried it a couple of times after restarting the software with the same results. Same thing happens as a 16 bit Tiff also.
C1 screen shot
The output viewed in PS
0 -
Hi Adrian,
There may be an issue with the OpenCL pipeline in Capture One, so try disabling Hardware Acceleration:
- go to Preferences - General tab;
- scroll down to Hardware Acceleration;
- set Display/Processing to Never;
- restart Capture One;
- after restarting, see if you face the same issue.
This will force Capture One not to use OpenCL when processing, generating previews and interacting with the UI.
If you face the same issues, try to rebuild OpenCL kernels as described in this article, enable Hardware Acceleration in preferences and restart Capture One.
For Windows users who may have recently installed driver updates, we recommend reverting to the version prior to this update to avoid driver compatibility issues.
You can find the driver versions for AMD here and NVIDIA's drivers can be found here.0 -
There may be an issue with the OpenCL pipeline in Capture One, so try disabling Hardware Acceleration:
Many thanks April, turning off hardware acceleration does indeed result in a clean output without the processing errors in the image.
I followed the rebuild process as indicated but the same processing errors in the image returned. I guess this indicates there's a potential issue in the C1 hardware acceleration on 2021 Macbook Pros/Monterey?
0 -
what happend to metal ?
0
Post is closed for comments.
Comments
19 comments