Problem when renaming or moving folders
I am wondering if i am the only person that has problems when renaming or moving a folder from within C1 when using a catalog? I could reproduce the problem on every Computer i had access to (independent installations).
Here is a video i created for opening a Case within PhaseOne some months ago showing the problems https://www.screencast.com/t/pK1hKYnK
(please ignore the long loading-times of the folders in that video - this happened only during the screencast-recording).
Scenario:
I have a Folder with pictures in the Library. Lets say c:\2019-05-26
then i move this Folder via drag and drop to the drive e:
After a few seconds that folder will show up as expected as e:\2019-05-26 and i can see the pictures in it.
BUT: when i close and reopen capture one then, everything is messed up.
The Library shows only the old folder c:\2019-05-26 with no pictures in it.
I have to reimport or re-add the folder e:\2019-05-26 to get my pictures back into the Catalog.
The same happens when i rename a folder from within Capture One (I am not doing any work of this in the windows filemanager, everything in capture one).
Even in the actual version of C1 this behavior still exists. đ
Here is a video i created for opening a Case within PhaseOne some months ago showing the problems https://www.screencast.com/t/pK1hKYnK
(please ignore the long loading-times of the folders in that video - this happened only during the screencast-recording).
Scenario:
I have a Folder with pictures in the Library. Lets say c:\2019-05-26
then i move this Folder via drag and drop to the drive e:
After a few seconds that folder will show up as expected as e:\2019-05-26 and i can see the pictures in it.
BUT: when i close and reopen capture one then, everything is messed up.
The Library shows only the old folder c:\2019-05-26 with no pictures in it.
I have to reimport or re-add the folder e:\2019-05-26 to get my pictures back into the Catalog.
The same happens when i rename a folder from within Capture One (I am not doing any work of this in the windows filemanager, everything in capture one).
Even in the actual version of C1 this behavior still exists. đ
0
-
I have had this problem (and many others) recently, refer to my post about the lost edits.
You will habe to add the folders manually and then sync them.
If you are lucky you'll still keep the edits.
G,0 -
[quote="NNN636404120592017559" wrote:
I have had this problem (and many others) recently, refer to my post about the lost edits.
You will habe to add the folders manually and then sync them.
If you are lucky you'll still keep the edits.
Currently i stuck in a lot of unnamed folders because i do not dare to touch them for renaming. Slowly i am loosing control and overview over my work. âšī¸0 -
I understand your frustration.
For me is unacceptable, I have lost a lot of time for these things.
In the end, not happily, I am back to Lightroom.
G.0 -
Sounds like a bug - thanks for the warning. What did support say? 0 -
[quote="IanL" wrote:
Sounds like a bug - thanks for the warning. What did support say?
I reported this three months ago to the support. From my last inquiry about the status three days ago they replied that the bug is still on their todo-list.
What really disappoints me is that for me this is a major bug that was not fixed during the last four updates from C1 12.0 to now 12.3. Maybe not enough people did open a case so the pressure to the development is low?0 -
This is one of the reasons that I use Lightroom as my main DAM, and only process my "best" photos in CO. 0 -
It looks now as C1 20 is on its way. I'll bet a crate of beer that the bug is not fixed in the new version (as it had not been fixed in 4 months after i reported it in C1 12). We'll see... 0 -
I wish i was confident enough to bet against you ... but I'm not. 0 -
12.1.4 is out now. Still not fixed. đ
The problem is now there for at least one year - Seems that only a few people on the world are using catalogs on windows (or they do not do any type of work on their folder structure)??0 -
[quote="Schopi68" wrote:
12.1.4 is out now. Still not fixed. đ
Disappointing[quote="Schopi68" wrote:
(or they do not do any type of work on their folder structure)??
That would be me. I have a long standing directory structure and established work flow so the only scenario that would expose me to this bug would be if I made a mistake and had to fix it. So, right now I'm not going to that - thanks for the warning.
I hope Phase One gets this sorted soon. It sure seems like a "fix this next patch" type of bug.0 -
[quote="Schopi68" wrote:
After a few seconds that folder will show up as expected as e:\2019-05-26 and i can see the pictures in it.
I've investigated this issue and the catch seems to lie in the last few words of your phrase.
I mean, I've noticed that when you rename or move a folder, Capture One does not open it by itself and that's exactly what you must not do. As long as you do not open any renamed or moved folder, you can rename and move everything you want to. You just have to remember to close and reopen Capture One before accessing any of these folders or you will screw things up for these particular ones.
Also, should you screw things up, you don't need to import images again (I've seen in your video you ended up with double images). Just right click the parent folder and choose "Add folder... " to add the missing one. It will appear in the list displaying 0 photos inside but, if you select it, all pictures will be loaded back with their adjustments.
Very annoying, but at least we can workaround it.0 -
[quote="ClauS" wrote:
..
I've investigated this issue and the catch seems to lie in the last few words of your phrase.
I mean, I've noticed that when you rename or move a folder, Capture One does not open it by itself and that's exactly what you must not do. As long as you do not open any renamed or moved folder, you can rename and move everything you want to. You just have to remember to close and reopen Capture One before accessing any of these folders or you will screw things up for these particular ones.
Also, should you screw things up, you don't need to import images again (I've seen in your video you ended up with double images). Just right click the parent folder and choose "Add folder... " to add the missing one. It will appear in the list displaying 0 photos inside but, if you select it, all pictures will be loaded back with their adjustments.
Very annoying, but at least we can workaround it.
I share in all the frustrations.I have been trying to work out a good workflow where I use LR as my DAM, where I cull, rate, and keyword everything, and later process the "average" shots. LR is pretty good at this. I then process my good shots in CO; only the good shots are imported into CO.
My issue comes when I later move a folder via LR from my SSD where I keep a upper level folder called "Work in Process" to a secondary folder on a spinner HD. I am not always finding that moved folder and subset of photos with CO so I can maintain my edits. I don't rename the photo folder, but I haven't figured out the best way yet to have CO relocate a moved folder. Frustrating.0 -
[quote="Jim MSP" wrote:
I share in all the frustrations.I have been trying to work out a good workflow where I use LR as my DAM, where I cull, rate, and keyword everything, and later process the "average" shots. LR is pretty good at this. I then process my good shots in CO; only the good shots are imported into CO.
My issue comes when I later move a folder via LR from my SSD where I keep a upper level folder called "Work in Process" to a secondary folder on a spinner HD. I am not always finding that moved folder and subset of photos with CO so I can maintain my edits. I don't rename the photo folder, but I haven't figured out the best way yet to have CO relocate a moved folder. Frustrating.
I cannot grasp why you're not able to find your folder with Capture One or I'm missing something but, with this kind of mixed workflow, why don't you use sessions instead of catalog? Depending on how you are used to organize your working folder, you could create a session in the parent folder of your set and it will move along with the folder itself when you'll move it via LR. When you use a catalog you'd better do everything inside the catalog. With my workaround you can. It's just annoying to be compelled to close and run the program again.0 -
[quote="ClauS"....
.., with this kind of mixed workflow, why don't you use sessions instead of catalog? Depending on how you are used to organize your working folder, you could create a session in the parent folder of your set and it will move along with the folder itself when you'll move it via LR. ....[/quote]
I have just started to try Sessions. CO 12 doesn't read the RAW files from my Canon 90D yet (it was shipped in mid Sept) so I have to create a DNG file of each RAW I want to process. A session seems to work ok, I have created a separate parent for my CO sessions, but hadn't thought of creating them inside the parent of a shoot -- it should have been obvious, but I got stuck on a different train of thought.
Thanks, I'l try that.0 -
[quote="Schopi68" wrote:
It looks now as C1 20 is on its way. I'll bet a crate of beer that the bug is not fixed in the new version (as it had not been fixed in 4 months after i reported it in C1 12). We'll see...
It seems as i have to pay a crate of beer. They've fixed the bug in C1 20.0 -
Okay, today my girlfriend wanted to move some folders to a year 2019-folder. The first folder movement were fine. The second folder was moved on the hdd but not in C1 - so it failed, no chance to move that folder from within C1.
Seems as i spent the crate of beer too early. The code in C1 for file management is still broken. đ đ0 -
Still borken, just encountered it and found this thread.Â
A little update here for the record.Â
0 -
Brian Ho, which version are you using?
The bug had been fixed with 20. I've tried to reproduce it now, thinking it was back with the latest version, but I could rename and move a folder with no apparent issues except that the count of pictures inside that folder was wrong after the move/rename (but OK after restart).
Also I had to run CO as an administrator to allow renaming, but this could be a problem with my system authorizations due to my pc and drive change. I don't know.
0 -
Hi Clau_S, I am using v20 Pro, Build 13.1.2.35. I believe it is the latest version.Â
Â
0 -
You'd better contact support then. Maybe there's a peculiar reason why you're still affected by the issue in this version.
0
Post is closed for comments.
Comments
20 comments