Problem with UNDO/REDO
After few normal operation of UNDO/REDU (cmd+z/cmd+shift+z) pressing cmd+z start show me particular image or undelete some of deleted, but can't redo (cmd+shift+z stop working at all) adjustment just made. However after restarting C20 things go ok for couple of minutes. (2018 MBP 16gb lot of free space, session with >1000 images from z6 nothing super heavy I believe)
0
-
Are you using the direct color editor by any chance? That’s a known culprit for this behavior. Look around on the forum, there are a few threads about undo/redo problems. 0 -
Emile thank you for reply, i can't imagine so many wierd things happened at same time and so is how lucky am i dealing with this silly UNDO/REDO behaviour ))) btw yeah, color edit want you go straight to win and never look back ))))
I believe I need some manual to read:
1) surely you can update your Mac and tethering is overhyped
2) you can easy edit colors, yes, you know what you do and doubt never
3)
4)0 -
lococroco wrote:
After few normal operation of UNDO/REDU (cmd+z/cmd+shift+z) pressing cmd+z start show me particular image or undelete some of deleted, but can't redo (cmd+shift+z stop working at all) adjustment just made. However after restarting C20 things go ok for couple of minutes. (2018 MBP 16gb lot of free space, session with >1000 images from z6 nothing super heavy I believe)
Having the same problem...
When I UNDO, it's undoing adjustment I've done way back (about 1h ago or 200-300 adjustments ago. Very rough estimate), and it keeps undoing at that place, undoing work I've finished. I'm not able to REDO, so I do not even dare to touch the UNDO command, it will just continue to undo work I've completed.
iMac Pro (2017)
Canon 1DX Mark II0 -
Johan121 wrote:
lococroco wrote:
After few normal operation of UNDO/REDU (cmd+z/cmd+shift+z) pressing cmd+z start show me particular image or undelete some of deleted, but can't redo (cmd+shift+z stop working at all) adjustment just made. However after restarting C20 things go ok for couple of minutes. (2018 MBP 16gb lot of free space, session with >1000 images from z6 nothing super heavy I believe)
Having the same problem...
When I UNDO, it's undoing adjustment I've done way back (about 1h ago or 200-300 adjustments ago. Very rough estimate), and it keeps undoing at that place, undoing work I've finished. I'm not able to REDO, so I do not even dare to touch the UNDO command, it will just continue to undo work I've completed.
iMac Pro (2017)
Canon 1DX Mark II
similar problem, just lost all the layers of one shot and I wasn't even on the shot where the layers disappeared when I pressed undo. What is it with undo/redo?0 -
If I change workspaces form dual monitor (large viewer), to any other workspace and then reselect the dual monitor, the Undo/Redo arrows and the zoom slider tool are grayed out. Undo/Redo still works from the small browser monitor as do the shortcut keys for these functions. If I close the catalog and reopen it, Undo/Redo and the zoom slider tool are still grayed out on the viewer monitor. This has been going on since version 11. I filed a support ticket, sent the log files, reinstalled C1P after a complete uninstall. It still does the same thing. I can get the zoom slider (but not the fit feature) to work by selecting the zoom tool and zooming, but I can only get the Undo/Redo function back in the dual monitor mode, by selecting the default, exiting my catalog, quitting C1P, restarting C1P and selecting the dual monitor workspace. As long as I do not select another workspace and quit C1P rather than closing the catalog, everything is fine when I restart C1P and it automatically loads the last catalog opened.
My point is, there are many bugs that only manifest themselves on specific configurations. Many are almost impossible to track down because they result from interactions of the software with other software and hardware. Problems with camera tethering and Undo/Redo functions being lost when using the Direct color Editor cursor are reproducible and will be likely to be fixed in the next point release. Problems like Johan's are serious and deserve attention because they are basic to function, but those like mine that are annoying, but have workarounds, will likely never get fixed or explained.
A company without the resources of Apple, Microsoft, or IBM simply cannot test for all possible bugs from all possible configurations in advance (not that the big guys do such a splendid job). Those like C1 rely on beta testing and those of us willing to go on a shakedown cruise with the new X.0. version. If it were not for the extremely high quality of the processing, few of us would ever buy anything before version X.3. My approach is to keep the previous version as my work version until at least the common bugs are addressed in the 1st or second point version.
At some point, code needs to be rewritten from the ground up, as Apple did when it went to a Unix-based OS. Otherwise, bugs resulting from conflicts of legacy code with modern hardware and operating systems becomes intolerable. I would be happy to pay for a new version of C1 that did nothing but clean out the bugs and rewrite the DAM.
Jerry C0
Post is closed for comments.
Comments
5 comments