C23 Moving Crop during shooting tethered
We recently upgraded to C23 in the Studio and we discovered that if you use an (upgraded) old session and shoot tethered with a crop variant applied, the position and size of the crop slowly move inwards and up. This only happens if you have upgraded an old session and continue shooting into that session.
Next Capture Adjustments is set to copy from last. We use Fujifilm GFX 50R and GFX 100S and MacOS 13.0
In C22 everything works just fine.
-
Same here. If I copy and apply adjustments from the previous version, I get a matching crop. Nikon Z7 II here with MacOS 13 and Capture One Pro 23. I made a new catalog and it's just the same.
0 -
yes ... same here as well. It's a bit of a pain when you have to re apply every time you take a shot. Also you have to delete the extra layer that duplicates when you re apply. ;0(
0 -
Just to add to the above, it's a clean install and not a shoot folder carried over from Capture 22
0 -
Working on the same catalog today and (weirdly) the crop sits still. I didn't change anything since Friday, when the crop shifted. I think the bug has a bug.
0 -
We are having the same issue but we didn't upgrade an old session we started a new one. We had this same issue several versions back.
0 -
We also discovered that it happens to new sessions as well so we have completely reverted to C22.
0 -
same issue with a new session shooting tethered Nikon Z7.
with every new capture the crop from the previous image moves around.0 -
Fixed mine ... Delete Capture 22 & reboot ....Worked for me. ;0)
0 -
Bah its broke again ... seems like the glitch is connected to adding keystone for me. ;0(
1 -
Please report this bug by opening a support ticket here: https://support.captureone.com/hc/en-us/requests/new
0 -
Just did that. Included screen recordings.
0 -
reboot and deleting C22, didn’t do anything here. Still bug with keystone, Crop and rotation .. hope for a fix soon. Back to C22 for now!!
0 -
This moving crop issue was quite a pain today for us while under the gun with a client on set. We spent quite a bit of time troubleshooting before finding this thread. Going back to C22 now. I hope there is a C23 patch soon!
0 -
Still no fix?
0 -
Have not received any feedback in any form from my registered case :-(
0 -
Same problem here with the crop moving, very annoying. Especially when shooting multiple images that are then comped through in photoshop.
0 -
Same issue here. Architectural photographer here, this is unusable currently.
0 -
Have everyone submitted a bug report? 25 days and counting… total silence from C1
0 -
This is super frustrating. This bug that keeps moving the crop when tethered is wasting plenty of time. Even more so during a commercial shoot. Capture one, act on it!
0 -
I reported this bug on November 10th. It’s pretty annoying
0 -
Hello folks,
same problem in our productions....
Is there no solution...?
Joern
1 -
Hi Joern, Phase one has not replied to me in weeks regarding this issue. I'm using a Sony A7RV, so moving back to an earlier version of C1 Pro is not an option.
There is no solution I can find.
0 -
I received an answer from Capture One support.
Hi Radu,
Thanks for contacting us. This issue you are describing is a known bug that our R&D teams are working to fix.
Your case will be added to the bug report, and I will place your ticket on-hold while we work on this. I will get back to you in case we need any more information regarding this report.
We will do our very best to provide a fix for this as soon as possible, but unfortunately I can't guarantee that it will be ready for the the next service release.
I can however promise that I will keep you updated on the progress of the fix.
There is however a workaround to this, we could reproduce: The problem is that the Crop tool and Keystone tool are playing tricks with each other. So please reset the Crop even if you haven't done a crop at all.
Kind Regards,
Nick - Capture One Support
I haven't been able to get a stable crop with keystone applied, but if there isn't any keystone correction applied, it works.
0 -
Sept 13 2023, despite clean installs, updating capture and the mac Os on all my machines, this is still an issue
0 -
Do you have the latest version? For me at least, it’s been fixed for quite some time.
0 -
Can confirm that it's still moving on the latest version.
0 -
Can confirm issue still exists even to this day for CP1 22. Any solutions yet??
0
Post is closed for comments.
Comments
27 comments