Serious issue for me in 6.4.3
I have filed this as a support ticket (108099).
But this is a warning in case someone else experiences this...
It may just be me, but 6.4.1 did not have this problem.
If I am working in 6.4.3, eventually, I will come to a point where I hit Undo (CTRL-Z) on a step (say a Crop or an adjustment) to step backward, and Capture One will lose ALL of my changes for ALL pictures during my editing session.
My Image Selection will revert back to where my editing session started, and every adjustment will be gone.
It could be a number of things wrong and not specifically this version I suppose, but the only way around this is to edit your images, and CLOSE Capture One often (to force it to flush out its session).
It has happened on new sessions I've created in 6.4.3 and old sessions I've opened to continue working in.
So be careful. I lost a few hours of work yesterday because I thought I just had a single corrupt session... but it turns out I have it in new sessions too.
But this is a warning in case someone else experiences this...
It may just be me, but 6.4.1 did not have this problem.
If I am working in 6.4.3, eventually, I will come to a point where I hit Undo (CTRL-Z) on a step (say a Crop or an adjustment) to step backward, and Capture One will lose ALL of my changes for ALL pictures during my editing session.
My Image Selection will revert back to where my editing session started, and every adjustment will be gone.
It could be a number of things wrong and not specifically this version I suppose, but the only way around this is to edit your images, and CLOSE Capture One often (to force it to flush out its session).
It has happened on new sessions I've created in 6.4.3 and old sessions I've opened to continue working in.
So be careful. I lost a few hours of work yesterday because I thought I just had a single corrupt session... but it turns out I have it in new sessions too.
0
-
Gregger,
I can't say that these results are reproducible on my Windows 7 System so perhaps something just local to your system. As the actions are logged on a specific file, perhaps that specific file on your specific machine is not properly logging the changes you are making in each incremental step?
I'd suggest you uninstall and reinstall the software for a clean starting point.
http://www.phaseone.com/Search/Article. ... nguageid=10 -
Is it possible there is a permissions issue going on here?
Where C1 is trying to write someplace that has been "taken ownership" by another machine's User ID?
This particular session was created and used without what I describe below happening... (I was not on that network and new folders were created under my Windows 7 ID).
I'm working in a folder that Windows 8 can see, but does not own.
Capture One is only used in Windows 7, but Windows 8's Picture Viewer can see some of the folders.
It appears that Windows 8 sometimes take control of the folders that the Metro Picture Viewer can see, but in theory, Windows 7 still owns the folder where the Capture One work is being done.
6.4.1 never had this problem though...
I'll try what you say though. I'm also getting a "Spinning wheel of Loading Metadata" for certain sessions now.
So if it fixes that, I'm happier.0 -
[quote="gregger" wrote:
I'm working in a folder that Windows 8 can see, but does not own.
Capture One is only used in Windows 7, but Windows 8's Picture Viewer can see some of the folders.
I imagine that has something to do with it but as Capture One is not tested with, supported on or built with Windows 8 in mind I can't say for sure.0 -
Like I said, it isn't used IN Windows 8. But Windows 8 may be affecting the folder permissions.
But 6.4.1 didn't have this issue, and Windows 8 was there before doing the same folder thing.
So I think that's spurious.
The Metro Pictures behavior with folder permissions is something you should be aware of on a dual boot system though.0 -
[quote="gregger" wrote:
Like I said, it isn't used IN Windows 8. But Windows 8 may be affecting the folder permissions.
Like I said, I can't say for sure 😄 ... did the suggested uninstall yield any results?0 -
This sounds similar to something that happened to me a couple of weeks back. I'm running Win 7 32bit and C1 6.4.3.
I wondered at first if C1 had stepped back on CTRL-Z but picked up an alternative COL file from a second disk on the system - a backup copy of the same session taken just after it was created and with few edits applied. (I was looking at an old project form last year.)
So I closed everything down and initiated a new instance of C1 from the COL file I had assumed I had been editing and everything came back as it should.
It has only happened once. I don't have Win 8 installed. I'm not familiar with 'Metro' (or whatever MS will call it in the future now that another company has laid claim to the name ...)
It could, of course, be a totally unconnected event and I certainly cannot be sure of what happened and why. My assumption was some sort of internal windows memory cache glitch but who knows.
Grant Perkins0 -
Sorry Drew!
I wasn't trying to be snarky. I just wanted to be clear that I wasn't using Capture One in an unsupported OS.
Although, Win8 is RTM now, so soon it will be in my workflow and I really want C1 running on a Surface Pro as a Tethered C1 device!
I will do the big uninstall today. I had to box up my camera and send it back to Canon yesterday - they "repaired" a focusing issue (i.e. focus? maybe... or maybe not...) but it only focuses in the center. Sometimes.
So one major photo support activity per day 🤓
Thanks!0 -
I did the BIG uninstall yesterday and then reinstalled.
I re-opened the session that had problems and started working (after realizing how much workspace customization I had done!)...
I was unable to make the UNDO behavior happen after about 25 minutes of doing some edits (I was re-doing all the work that was lost)... but I have to admit I was really being cautious. Losing another few hours of work wasn't going to be high on my list.
I will try a few more editing sessions and see if the "fresh install" of 6.4.3 keeps working along.
The other alternate bug that showed up during this UNDO behavior was the inability to "ALT-Click REVERT" on a tool to temporarily see what the impact of that tool's changes are to an image... it would actually REVERT ALL the image's changes back to "0" (all tools, all settings for the selected image).
And another behavior that crept in was that "ALT-Click COPY" for things like Metadata or White Balance and "SHIFT-Click Paste" on tools didn't always work. Sometimes they did, and sometimes they didn't.
That became more prevalent in 6.4.3.
If that sounds all related to a corrupt installation, then maybe this is the root cause.
Thanks!0
Post is closed for comments.
Comments
8 comments