跳到主内容

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

Undo Not Functioning

评论

36 条评论

  • svorenberg

    I worked for 3 hours on something and didn't realize that the undo button had become unavailable and greyed out. I accidentally pressed delete and took the photo back to its original state. I found no way to recover all that work. Words have no way of expressing the frustration I feel. I think I'm going to go back to Adobe Lightroom. Unless, anyone has a solution.

    1
  • Anthony Kurtz

    I'm in the same boat. Undo randomly stops working. I'm on the latest update 13.04.10

    CAPTURE ONE, YALL HERE?

     

    1
  • FRANCK

    Same problem here, with last update ... 

    So much bug with capture one, became crazy

    1
  • Peter Valli

    Yes.  It's the" batch rename" that triggers it.  I upgraded to 20 earlier this week. I was on a two day shoot and everything was going swimmingly. Love the addition of "blacks" to HDR...I digress.  Yesterday afternoon, while shooting tethered I inadvertently opened a different job and the images I was shooting ended up in that job's Capture folder, named with under it's convention.  Consequently, I "batched renamed" several images and the rest apparently is history. 

    Capture/Phase,

    If you could please correct this issue as soon as possible, it would be greatly appreciated.  I rely heavily on "command Z".  

    Thanks!!!!!

     

    1
  • Anthony Kurtz

    I find this issue (and many other bugs) unacceptable as a tool supposedly made for professionals. 

    Now it's at a point where i hit "Cmd Z" and nothing happens, so I do it AGAIN

    "CMD Z" !!!!!!

    suddenly the image i'm working on disappears and I'm set back in time to an old project that I worked on hours ago!

    This must be addressed or I'm moving back to Lightroom! I don't want to but I'd much rather have an undo/redo function that works, have a HISTORY STATE (hello C1, we need that) as well as being able to open images in RAW vs C1 who not only doesn't address these bugs but can't do the basics correctly.

    We don't need C1 to do everything but what it does it should it do it well.

    I'm really refraining from using foul language here.

    ps: I just updated to 13.1.2.37 but now IT'S JUST WORSE

     

    HELP

     

    1
  • SFA

    Which update are you using?

    0
  • Dan DeVries

    20.02.13

    0
  • Dan DeVries

    13.02.13

    0
  • Ian Leslie

    There was a bug reported about a particular edit or action that broke the undo chain. I have no idea how to find it in this new "forum". I searched and came up empty but I am sure I read a discussion about this in the forum recently. If you report your problem to support they might be able to let you know if the issue is being looked at or if this is something different you are hitting.

    0
  • BeO
    Top Commenter

    I have the same issue, UNDO button disabled and CTRL Z not working. I mainly do adjustments, masking, luma range, maybe switch to another image, use undo on occasion, and things like that. No direct color editor. 

    Noticed this with 20.0.2 and with the betas.

    Do we have something in common? e.g. a Wacom tablet and Windows ink disabled, and a whole lot of  'received negative coordinates' messages in the application log?

    0
  • Dan DeVries

    I upgraded to the latest version.  Plus I deleted all older version of Capture One  - per the advice of tech support.

    I have not had any additional incidents in a while.  I just use a mouse - I have a WACOM -  but have not bonded with it after many tries.   

    Hope that helps.  

    0
  • Jonathan Nesteruk Nesteruk

    I had this same problem. I resolved it by deleting the Capture One .plist files.  On Mac its located in "Macintosh HD--> Users---> "Your User" --> Library --> Preferences

    com.captureone.captureone13.plist.

     

    good luck

     

    0
  • Michael

    This did work for me. If you do this know that at least on a Mac, Capture One will startup as if it has not been run before. You'll get the welcome screen, workspace setup screen etc. Once you are past that everything works as before including, thankfully, undo.

    Thanks Jonathan.

    0
  • Tom Thrasher

    I've had this same problem. Restarting Capture One sometimes fixes it.  A lot of glitches happen when I do batch renames on a tethered shoot--it resets white balance and exposure settings for future captures.

    0
  • BeO
    Top Commenter

    I upgraded to v13.1 last week and had to restart after editing every second image or so. I mainly did some "create mask from color editor" work for a layer I copied before, and some copy mask from another (the newly created) layer, and some mask finetuning, for abaout 20 images altogether. Not only did the undo button not work after a while but also feather mask got stuck. Meanwhile I edit with C1 as if no undo function would have ever existed.

    0
  • SFA

    Tom Thrasher,

    I have no idea about about how the logic works in such a scenario nor what you have actually renamed but lets assume for a moment that have a series of images named in sequence with various adjustment applied.

     

    You deliver an instruction to "Copy from last" in the sequence.

    Now you rename a chunk of the sequence to be a different sequence.

    Your "Copy from last" setting now goes back to the last image that was NOT renamed in order to continue the sequence.

    Might that be what is happening? Or something along those lines?

     

    If so I think the issue might be some sort of balance between complexity and system overheads. (And costs. Always costs.)

    0
  • Tom Thrasher

    SFA, 

    No, that's not the situation.  And I'm afraid this is going to lead this thread astray.  I've been tech-ing on an e-commerce shoot, where we shoot outfits on a white background, with the same User-Style applied to all of the images, uniformly.  Once in a while, I'll get an incorrect SKU number for an outfit, and have to do a batch rename after the images have been imported to CO.  For some reason, after that batch rename, the next batch of images to be shot will not have that Style applied on import. Like the batch rename severs the "Copy from last" altogether.  Keep in mind all of the images in the shoot have the exact same adjustments.

    This may have nothing to do with the "undo not working" issue.  But I'm also having occasional issues with the Undo/Command+Z function not working, and was just throwing it out there that things go wacky after batch renames for me.  

    0
  • DanM

    Just noticed this too. Build 13.1.1.31. Had to close and restart to get back the undo function.

    Also, when shut down normally, the program does not remember the most recent image you were working with.

    0
  • Dan DeVries

    I was told by C1 to make sure I uninstalled all old versions of the software.  I have done so and have not had an issue since.  I am on C1 20 - latest version.  

    Might want to check with customer support on the best way to uninstall old versions.  I think there were a few things to delete that were not obvious.  But I would start with deleting the old versions first.

    0
  • Jose Garzaro

    It's not working for me either. I started using the Capture One about a month ago and installed the latest version, I just started getting this issue but don't know what to do to fix it. It really affects my workflow.

    0
  • DanM

    Oddly enough, I have not had that problem again since I posted. Maybe it just affects certain controls / sliders?

     

    0
  • Jonathan Nesteruk Nesteruk

    This is still happening on my Mac. Brand new install on a brand new Mac, Guess Im going back to version 12.

    Batch Rename definitely is triggering it. Help us out C1. 

    0
  • Bobby

    Just happened to me. I was working on an image, try to undo and next thing the image is in my trash. So I copied it back to the Capture folder and now all my changes on it are gone. Had to start again. 

    0
  • Jonas Ingman

    The same is happening to me as well. Very frustrating... 

    0
  • Victor Affaro

    Same Problem Here. Undo only does undo Selction, it doesn't record the last tool used

    0
  • FirstName LastName

    Same with version 21. This is not what I want to experience using my trial period. Undo function randomly stops working when using brush on mask usually. After restart it works for awhile. Wow.

    0
  • Dan DeVries

    I had the issue occur last week with Capture One 21.  It always seems to happen when I use Auto Levels.  So I don't use it any more.

    0
  • FirstName LastName

    Sadly I don't use auto levels 😊

    0
  • Johannes Pistorius

    Keeps happening to me as well. Not sure how many bugs I have reported. Migrating from LR really was a big win for me in terms of pure image quality, but the dozens of acknowledged (!) bugs that get no fixes is ridiculous and becoming a burden to work with. I am by no means a fan of Adobe, but I have been using LR since version 2 and I never had any major bugs or stability issues or had to rely on flimsy workarounds like deleting plist-files.

    0
  • Ahmad Sazali Mohamad Noh

    Wow!! I'm not alone.
    Start with upgrading from Capture One 12 to Capture One 20..
    Can't quit catalog. Can't quit the Capture One app and a lot more problem. This is why I not going to upgrade to Capture One 21. Start using session per project. Still the same problem. Cant undo is one of them...

    0

请先登录再写评论。