Colour Editor Tool returning to the top of the tool stack
Another small glitch identified, just checking if anybody else experiences it before contacting support. Basically my Colour Editor tool keeps returning to the top of the tool list in the scrollable list (NB - not the pinned list) no matter where I put it.
My workflow involves colours after exposure and crop so the colour balance and colour editor tools are about 2/3rds of the way down my list (I use a single custom list now to take advantage of the scrolling function rather than clicking between tabs). If I close a session or catalogue down and reopen it the colour editor is back at the top of the scrolling area.
Anybody else seen this?
2014 iMac running latest MacOS.
My workflow involves colours after exposure and crop so the colour balance and colour editor tools are about 2/3rds of the way down my list (I use a single custom list now to take advantage of the scrolling function rather than clicking between tabs). If I close a session or catalogue down and reopen it the colour editor is back at the top of the scrolling area.
Anybody else seen this?
2014 iMac running latest MacOS.
0
-
Try saving the modified Workspace (preferably with a unique name rather than, say, "Default") and then see what happens when you close and re-open.
Grant0 -
Thanks yes I’ve saved the workspace but didn’t make any difference. Colour editor keeps placing itself at the top of the stack. I’ll put a ticket in...... cheers. 0 -
I have the same issue. I submitted a ticket last Friday. 0 -
Saeed Rahbaran wrote:
Mine does the same, but moves to the bottom. I have to click my saved custom workspace every time I open C1.
Try saving your "fixed" workspace as a new one. It might be that 20 isn't reading the old workspace correctly, in which case saving the correct one under a new name may fix it. It's worked for me with similar issues in both 12 and 20.0 -
for several releases now, each new version is beta software, full of bugs like this. What a shame, that we should have to put up with such shoddy software over and over again. 0 -
Saeed Rahbaran wrote:
Nature Isme wrote:
Saeed Rahbaran wrote:
Mine does the same, but moves to the bottom. I have to click my saved custom workspace every time I open C1.
Try saving your "fixed" workspace as a new one. It might be that 20 isn't reading the old workspace correctly, in which case saving the correct one under a new name may fix it. It's worked for me with similar issues in both 12 and 20.
Did this a few times starting from scratch with new modified workspaces, nothing changed. I also used unique names every time. Problem doesn't go away
Me too, didn’t fix it. Thanks though.0 -
Pavel wrote:
for several releases now, each new version is beta software, full of bugs like this. What a shame, that we should have to put up with such shoddy software over and over again.
If that is your long time opinion why have you not identified a better replacement product?
What keeps you working with Capture One?0 -
Saeed Rahbaran wrote:
Mine does the same, but moves to the bottom. I have to click my saved custom workspace every time I open C1.
Same here, it moves to the bottom. When I am in my workspace I have to choose it again to move the color editor to the right spot. So, the workaround is to double choose the workspace with color editor tool.0 -
Same issue here, even after 20.0.1 update. 0 -
The issue seems to be related to which workspace is loaded at startup. At least that is what I am seeing. If I open CaptureOne and click on the Color tab I see the Color Editor at the bottom of the scrolling area. I then go to Window -> Workspace -> My workspace (the one I saved after getting the menus the way I wanted) and all is back the way I want it.
I'd expected my workspace to be loaded when CaptureOne is started as that was the workspace in use when I last closed the program.
That is not the entire story as other workspace changes I've made take effect upon program launch. Confusing.0 -
Did you give your workspace a unique name when you saved it?
Note that in previous times User created workspaces were always saved in the same place (not with the C1 provided workspaces).
With V20 the user workspaces have been copied into a new folder ready for redeployment and adaptation to V20 functionality.
Whether this might be a factor in what you are seeing I don't know but it occurs to me that there is some potential for unexpected behaviour to develop.
I'm not seeing what you describe - but I'm using Windows so probably don't count for this one. However if it was a consistent problem for all I think more people would have been raising questions by now.
I would suggest running a test. Select the Default C1 Workspace (not any workspace with that name that might be in the User workspaces section) make some obvious changes and then save it with a completely new name that makes it easily identifiable.
Close C1 and re-open.
What do you get for the workspace?
Grant0 -
SFA wrote:
Did you give your workspace a unique name when you saved it?
Yes. Well, every time I save it I give it the same name. When I start Capture One I see most of the changes I made, but the color editor position is wrong. I select Window -> Workspace -> <name> and the color editor is where I placed it. That implies that the workspace at startup is not the <name> workspace, but something different. Or I'm wrong 😉SFA wrote:
I would suggest running a test. Select the Default C1 Workspace (not any workspace with that name that might be in the User workspaces section) make some obvious changes and then save it with a completely new name that makes it easily identifiable.
Close C1 and re-open.
What do you get for the workspace?
Grant
OH... I selected Window -> Workspace -> Default and did NOT get the out-of-the-box Capture One workspace. I can tell because I've added tool tabs and they exist. It looks like what I get at startup is the "Default" workspace. Knowing that...
I saved my preferred workspace with the name "Default". Quit and restart. I see that I've a user workspace named Default. That is NOT the workspace that is loaded.
More conjecture: My modified workspace that existed when I transitioned from 12 to 20 is being used as the workspace that is loaded whenever I start Capture One. I don't know where that data is stored on my machine. It is not in the Capture One application support folder. I simply must remember to change to my current saved workspace.0 -
I think it is smarter to name your custom workspace to something other than 'Default', just to prevent confusion.
Your custom workspaces are stored in the so-called Application Support folder. They can be found in the hidden user's library folder. Full path:
HD/Users/<user name/Library/Application Support/Capture One/Workspaces
I suggest that when you create a custom workspace, add -CO20 or something as a suffix to identify the version it was created with.
I also suggest to create new workspaces with CO20 for CO20 and not use older version's workspaces to prevent issues with workspaces.
Note that on Windows there is a dedicated workspaces folder for Capture One 20 - named Workspaces130 - but on Mac there is currently not made that distinction.0 -
Paul_Steunebrink wrote:
I think it is smarter to name your custom workspace to something other than 'Default', just to prevent confusion.
Of course! Using the name "default" was only a test to see if there was something magic about that name. There isn't.Paul_Steunebrink wrote:
Your custom workspaces are stored in the so-called Application Support folder.
Not hidden on my machine -- I'm into the Library folder often enough that I added it as an item to the Finder sidebar.
I've saved my desired workspace enough times under different names in Capture One 20 that I know it is not a version issue. I also checked Capture One defaults -- it knows the name of the workspace I want to use. The issue seems to be a Capture One startup issue. It loads my workspace, but gets the Color Editor in the wrong place. If I reload the workspace Capture One gets it right.
So I will reload the workspace until the issue is found and fixed.0
Post is closed for comments.
Comments
14 comments