"CaptureOne" folders since V10?
Since V10 I often see folders named "CaptureOne" between my RAF files after importing into my catalog. Support tells me this happens when you use sessions but I have never used a session. Do you have these folders too?
0
-
In sessions: always.
In catalogs: never.
I use both, but with cr2.
You are importing referenced into catalogs, right?
Are you sure that you weren't accidentally using a session at creation time/date of these folders and their content?
What are the subfolders in the 'CaptureOne' folders? Only 'Settings100', or are there earlier versions, too?
Regards,
Hans0 -
I imported directly into a catalog. Never used a session. The "CaptureOne" folders have two subfolders : "Cache" with subfolder "Proxies" (with files of extension "cop") and "Settings100" (this folder is not always there.). "CaptureOne" folders are pretty much in all folder where RAW files have been imported to. 0 -
[quote="NN635781531552263255UL" wrote:
I imported directly into a catalog. Never used a session. The "CaptureOne" folders have two subfolders : "Cache" with subfolder "Proxies" (with files of extension "cop") and "Settings100" (this folder is not always there.). "CaptureOne" folders are pretty much in all folder where RAW files have been imported to.
It looks very much like if you were using sessions.....0 -
[quote="tenmangu81" wrote:
[quote="NN635781531552263255UL" wrote:
I imported directly into a catalog. Never used a session. The "CaptureOne" folders have two subfolders : "Cache" with subfolder "Proxies" (with files of extension "cop") and "Settings100" (this folder is not always there.). "CaptureOne" folders are pretty much in all folder where RAW files have been imported to.
It looks very much like if you were using sessions.....
That's what their tech support tries to tell me but I don't use sessions. I import into a catalog. My import process is this:
- Open C1, my only catalog is open.
- Insert Sd card
- Wait for import dialog.
- Press "OK"0 -
I'll get me some raf files and give it a try when I'm back at home.
In the meantime:[quote="HansB" wrote:
...
You are importing referenced into catalogs, right?
...
What's the location and folder structure you are importing to?
What does the 1st box in 'Library' tab - 'Library' tool state as active session/catalog?
You are using 10.0.1?
Regards,
Hans0 -
The Library shows my catalog as active. And yes, I am on the latest version. 0 -
Out of interest, go to Window on the menu and click.
In the section at the bottom of the drop down list what can you see?
Then go to File > Open Recent.
What do you see on the list?
Finally perform a system search for a files with "cosession" in the name.
See what you get.
Maybe you have already done these things with Support?0 -
[quote="SFA" wrote:
Out of interest, go to Window on the menu and click.
In the section at the bottom of the drop down list what can you see?
Then go to File > Open Recent.
What do you see on the list?
Finally perform a system search for a files with "cosession" in the name.
See what you get.
Maybe you have already done these things with Support?
I have done quite a bit with support but I got the impression that they don't to deal with this. They just keep claiming that I am using a session.
Under "recent" I can find only the catalog I have been using. Nothing else. No 'cosession" file on disk.0 -
I had the same folders in my referenced catalog files. I have never used a Session. I did move my files from a managed catalog to a referenced. I used Capture One to create the folders and move the files.
I was experiencing a slow down if clicking "all files" for any reason. I replaced my main disk with an SSD and move the Capture One catalog to the SSD but the referenced files were on a separate spinning disk. You could hear the HDD being accessed when opening Capture One and when clicking "all files". I regenerated all previews, which took hours by the way, and it still was slow and you could hear the hard drive working.
What I finally did was trash all the Folders inside my referenced folders named "CaptureOne". After doing this my software sped up and only stalls for 15 seconds or so when first clicking All Files. Once it gets past this it works great.
People here and Capture One support insist I was using Sessions. I have never done it and am not wanting to use them.
Hope this helps.0 -
[quote="Edgephoto" wrote:
I had the same folders in my referenced catalog files. I have never used a Session. I did move my files from a managed catalog to a referenced. I used Capture One to create the folders and move the files.
I was experiencing a slow down if clicking "all files" for any reason. I replaced my main disk with an SSD and move the Capture One catalog to the SSD but the referenced files were on a separate spinning disk. You could hear the HDD being accessed when opening Capture One and when clicking "all files". I regenerated all previews, which took hours by the way, and it still was slow and you could hear the hard drive working.
What I finally did was trash all the Folders inside my referenced folders named "CaptureOne". After doing this my software sped up and only stalls for 15 seconds or so when first clicking All Files. Once it gets past this it works great.
People here and Capture One support insist I was using Sessions. I have never done it and am not wanting to use them.
Hope this helps.
Thanks! At least I am not alone with this.
I got really annoyed with C1 support insisting that I am using sessions. I tell them repeatedly I have a catalog and never used sessions and they respond with "This happens when someone uses sessions and is the expected behavior".0 -
[quote="NN635781531552263255UL" wrote:
[quote="Edgephoto" wrote:
I had the same folders in my referenced catalog files. I have never used a Session. I did move my files from a managed catalog to a referenced. I used Capture One to create the folders and move the files.
I was experiencing a slow down if clicking "all files" for any reason. I replaced my main disk with an SSD and move the Capture One catalog to the SSD but the referenced files were on a separate spinning disk. You could hear the HDD being accessed when opening Capture One and when clicking "all files". I regenerated all previews, which took hours by the way, and it still was slow and you could hear the hard drive working.
What I finally did was trash all the Folders inside my referenced folders named "CaptureOne". After doing this my software sped up and only stalls for 15 seconds or so when first clicking All Files. Once it gets past this it works great.
People here and Capture One support insist I was using Sessions. I have never done it and am not wanting to use them.
Hope this helps.
Thanks! At least I am not alone with this.
I got really annoyed with C1 support insisting that I am using sessions. I tell them repeatedly I have a catalog and never used sessions and they respond with "This happens when someone uses sessions and is the expected behavior".
Same BS I got. Even here I was told I must have used sessions. I know I never did because up until a week or two ago I had a managed catalog. I moved everything out of the catalog to referenced folders when I got the SSD. Could not swing a big enough SSD for all my RAWS.
Did you go from managed to referenced by chance?0 -
So what was your process to move the files from Managed to Referenced?
Did you advise the Supporter about that activity? What did they indicate to be the expected results of such an activity?
Grant0 -
This might be related, although there was no resolution.
viewtopic.php?f=68&t=250920 -
[quote="SFA" wrote:
So what was your process to move the files from Managed to Referenced?
Did you advise the Supporter about that activity? What did they indicate to be the expected results of such an activity?
Grant
I have never used a managed catalog either and I have the same problem.0 -
A wild guess.
If you move from Managed to Referenced C1 may use the functionality available for exporting to a new session or simply exporting with adjustments. Using the same code could make a lot of sense in development terms.
The second part of the process would be to then "re-import" "with adjustments" and that might require an intermediate cos (etc) file in order to simulate, say, a Session Import which would do the same thing.
However I rather suspect that if Renaming is involved for everyone who sees this problem, that may be the source of the files and they are simply not being tidied up afterwards - for which there may be a reason.
If so I would very much doubt that a Supporter - or indeed anyone else come to that - might be expecting to find the sub-folders in any situations except the use of a session at some point even if people had not realised that they had kicked into one for a moment.
Grant
ETA: On the basis of a post that came in whilst I was typing ... the rename process seems to be the strong candidate!0 -
[quote="SFA" wrote:
A wild guess.
If you move from Managed to Referenced C1 may use the functionality available for exporting to a new session or simply exporting with adjustments. Using the same code could make a lot of sense in development terms.
The second part of the process would be to then "re-import" "with adjustments" and that might require an intermediate cos (etc) file in order to simulate, say, a Session Import which would do the same thing.
However I rather suspect that if Renaming is involved for everyone who sees this problem, that may be the source of the files and they are simply not being tidied up afterwards - for which there may be a reason.
If so I would very much doubt that a Supporter - or indeed anyone else come to that - might be expecting to find the sub-folders in any situations except the use of a session at some point even if people had not realised that they had kicked into one for a moment.
Grant
ETA: On the basis of a post that came in whilst I was typing ... the rename process seems to be the strong candidate!
As users we should stop trying to come up with theories. It's up to C1 to listen and then to look at their code to see how this can happen.0 -
[quote="NN635781531552263255UL" wrote:
[quote="SFA" wrote:
A wild guess.
If you move from Managed to Referenced C1 may use the functionality available for exporting to a new session or simply exporting with adjustments. Using the same code could make a lot of sense in development terms.
The second part of the process would be to then "re-import" "with adjustments" and that might require an intermediate cos (etc) file in order to simulate, say, a Session Import which would do the same thing.
However I rather suspect that if Renaming is involved for everyone who sees this problem, that may be the source of the files and they are simply not being tidied up afterwards - for which there may be a reason.
If so I would very much doubt that a Supporter - or indeed anyone else come to that - might be expecting to find the sub-folders in any situations except the use of a session at some point even if people had not realised that they had kicked into one for a moment.
Grant
ETA: On the basis of a post that came in whilst I was typing ... the rename process seems to be the strong candidate!
As users we should stop trying to come up with theories. It's up to C1 to listen and then to look at their code to see how this can happen.
You are getting a complementary, open ended technical support service.
The problem that you perceive exists due to something about the process you are using. It's not really a show stopping effect is it?
If it is in fact correct that the unrequired folders and files are due to something to do with renaming of files in some part of a process no one has mentioned that up to now as far as I recall.
Are the supporters aware of that part of the sequence of events?
Why have no users previous pointed a finger at the operation and suggested it might be the source of the problem?
Had anyone tested for the effect.
At the very least it is reasonable to try to emulate the potential problem - what people see, or think they see, is not always correct.
You might set any number of people poring through many lines of code attempting to imagine what it might be doing not sure what they are looking for or where it is. It could be some other routine entirely outside the developer's control that just happens not to work on certain configurations in certain situations.
If that is the level of service you require then fair enough. Add at least one 0 to the price and think in terms of paying 30% per annum for a support contract.
Is the problem that important?
Grant0 -
When I reported the issue I asked Capture what the deal is with this folder and if I can delete or need to back it up. They didn't not answer this very simple question but instead told me that I am using sessions. I told them several items that I don't use sessions but they kept repeating it. I don't even care about that folder I just want to know if it's important. Instead Capture One basically denies its existence since it can supposedly happen only when you are using sessions.
I have been doing professional software development for 25 years now. At some point you have to sit down and look at your code and you will probably find some edge case that will cause this behavior. This is not difficult. You can't just say "This is impossible". It's not up to the customer to do the debugging. We have at least two people in this thread who have seen this and probably a lot more who haven't noticed. This behavior is new in V10 so that's another hint to find the code that's causing this.0 -
[quote="NN635781531552263255UL" wrote:
When I reported the issue I asked Capture what the deal is with this folder and if I can delete or need to back it up. They didn't not answer this very simple question but instead told me that I am using sessions. I told them several items that I don't use sessions but they kept repeating it. I don't even care about that folder I just want to know if it's important. Instead Capture One basically denies its existence since it can supposedly happen only when you are using sessions.
I have been doing professional software development for 25 years now. At some point you have to sit down and look at your code and you will probably find some edge case that will cause this behavior. This is not difficult. You can't just say "This is impossible". It's not up to the customer to do the debugging. We have at least two people in this thread who have seen this and probably a lot more who haven't noticed. This behavior is new in V10 so that's another hint to find the code that's causing this.
25 years and you and your team have never had a truly puzzling and unexpected occurrence or result that was so far out of anyone's expectation range that it took a while to spot it?0 -
[quote="SFA" wrote:
[quote="NN635781531552263255UL" wrote:
When I reported the issue I asked Capture what the deal is with this folder and if I can delete or need to back it up. They didn't not answer this very simple question but instead told me that I am using sessions. I told them several items that I don't use sessions but they kept repeating it. I don't even care about that folder I just want to know if it's important. Instead Capture One basically denies its existence since it can supposedly happen only when you are using sessions.
I have been doing professional software development for 25 years now. At some point you have to sit down and look at your code and you will probably find some edge case that will cause this behavior. This is not difficult. You can't just say "This is impossible". It's not up to the customer to do the debugging. We have at least two people in this thread who have seen this and probably a lot more who haven't noticed. This behavior is new in V10 so that's another hint to find the code that's causing this.
25 years and you and your team have never had a truly puzzling and unexpected occurrence or result that was so far out of anyone's expectation range that it took a while to spot it?
At least you have to try spotting the issue and not deny the existence of a problem. My point is that they deny the issue and try to blame it on the user. I have told them repeatedly that I am not using sessions and that this is new since V10. Why are we still talking about sessions?
The while thing is not very important to me but it's starting to bug me that people here are trying to excuse C1's behavior.0 -
[quote="NN635781531552263255UL" wrote:
[quote="SFA" wrote:
[quote="NN635781531552263255UL" wrote:
When I reported the issue I asked Capture what the deal is with this folder and if I can delete or need to back it up. They didn't not answer this very simple question but instead told me that I am using sessions. I told them several items that I don't use sessions but they kept repeating it. I don't even care about that folder I just want to know if it's important. Instead Capture One basically denies its existence since it can supposedly happen only when you are using sessions.
I have been doing professional software development for 25 years now. At some point you have to sit down and look at your code and you will probably find some edge case that will cause this behavior. This is not difficult. You can't just say "This is impossible". It's not up to the customer to do the debugging. We have at least two people in this thread who have seen this and probably a lot more who haven't noticed. This behavior is new in V10 so that's another hint to find the code that's causing this.
25 years and you and your team have never had a truly puzzling and unexpected occurrence or result that was so far out of anyone's expectation range that it took a while to spot it?
At least you have to try spotting the issue and not deny the existence of a problem. My point is that they deny the issue and try to blame it on the user. I have told them repeatedly that I am not using sessions and that this is new since V10. Why are we still talking about sessions?
The while thing is not very important to me but it's starting to bug me that people here are trying to excuse C1's behavior.
Well, I don't use catalogs and I'm on Windows ... so I thought I would use a test catalog I have been experimenting with that just happened to have a couple of Managed files in it and see what I could create.
Exporting the images did not seem to cause a problem with extra folders.
Importing them was not a problem.
Renaming them (both before export and again after import) was not a problem.
I may have followed a different procedural order to those experiencing the challenge but as far as I could tell there were not that many alternative possibilities.
So, at this point I would conclude that it is not a generic problem of design but might be a specific problem for Macs. Perhaps certain combinations of Mac configurations? Who knows .... and that's one of the challenges posed by Agile development in fairly open development environments. How do you manage to test all possibilities in so far as you can conceive where challenges might arise?
The answer is probably that you don't, at least not for everything, because you cannot do it. There are too many variables. So you have to expect to react as and when problems are raised and, as in this case, it starts to become clear that the usual expectation for a cause and effect are not what is playing out here - or so it seems.
And of course if you cannot clearly and easily reproduce the problem as reported, as a developer you are rather reliant on the people reporting the problem to continue to try to help you identify the origin.
Or not.0 -
Usually when I know there is a problem in a certain area I can review that section of the code even if there is no clear path to reproduce. I only wish C1 would tell me at least if the folders are needed or not. 0 -
[quote="NN635781531552263255UL" wrote:
Usually when I know there is a problem in a certain area I can review that section of the code even if there is no clear path to reproduce. I only wish C1 would tell me at least if the folders are needed or not.
If they are not aware of any way to make it happen it might be difficult to answer that question.
Copy them out go the way outside of C1 and see if anything is adversely affected.
I would have thought not but if it is an unrecognised situation other than for people using sessions then any answer offered may be suspect.
Anything in Cache folder is disporable since it can be re-created if needed.
The .cos files are edit instruction files in a session environment. Whether there are any important edit instructions in them is difficult to tell. Depends how and when they were created - dates and times on the files? - and what activities you had undertaken up to that point. They may be trivial to recreate or they may represent hours of work.
If the result in the catalogue look ok the chances are they are not required but you can check that by removing them (temporarily if necessary).
If you use Adjustment Masks they are held separately if they exist. Also in a sub-folder.
HTH.
Grant0 -
I did not nor do I ever rename my files. So that theory is out.
Like I said I started with a managed library and moved the files to a referenced library.
How I moved the files was to create folders in the folders section. My photos are organized in the user section so I just dragged the files out from the user section to the folders I added. They did not move out of the albums I have them in the just moved where they are stored. As I did this the catalog got smaller.
I did a test and found that deleting the Capture one folder inside the referenced files folders did not change my adjustments. It did stop Capture One from accessing the hard drive constantly even though the catalog was on an SSD. After trashing all those folders the program sped up significantly. I had move the much smaller referenced catalog to my SSD.0 -
I use C1 with a catalog (!) on the internal Mac Pro SSD drive and referenced (mostly) RAW pictures on a direct attached pegasus promise2 RAID.
I import my pictures into the catalog from my SD card reader directly into the C1 catalog. The RAW pictures are copied with that operation directly into my referenced picture structure on the attached RAID. No additional 'capture one' folders are created in my referenced RAW picture structure by doing so.
But, when I rename those pictures in the very same C1 cataloq (and the renaming gets written to the physical pictures) then there is this (silly) 'Capture One' folder with it's subfolders 'Cache'/'Proxies' and the *.cop files inside created.
I delete that 'Capture One' folder afterwards because I really don't want to spoil my clean picture structure with something that definitely does not belong to be there. In my opinion system files should be placed in the system folders and not into my personal data structure.
The above happens every time I rename pictures within C1 (and I often do) and is clearly reproducible. And no, you don't have to ask me about sessions, I use a catalog.
As far as I can remember this behaviour already took place with C1 Version 9 (but not from the start but rather with a later release). But don't take me on that.
Therefore PhaseOne team please fix this and put that cache folder inside the catalog or wherever you want but not into my picture or user data structure.0 -
[quote="AndyE" wrote:
I use C1 with a catalog (!) on the internal Mac Pro SSD drive and referenced (mostly) RAW pictures on a direct attached pegasus promise2 RAID.
I import my pictures into the catalog from my SD card reader directly into the C1 catalog. The RAW pictures are copied with that operation directly into my referenced picture structure on the attached RAID. No additional 'capture one' folders are created in my referenced RAW picture structure by doing so.
But, when I rename those pictures in the very same C1 cataloq (and the renaming gets written to the physical pictures) then there is this (silly) 'Capture One' folder with it's subfolders 'Cache'/'Proxies' and the *.cop files inside created.
I delete that 'Capture One' folder afterwards because I really don't want to spoil my clean picture structure with something that definitely does not belong to be there. In my opinion system files should be placed in the system folders and not into my personal data structure.
The above happens every time I rename pictures within C1 (and I often do) and is clearly reproducible. And no, you don't have to ask me about sessions, I use a catalog.
As far as I can remember this behaviour already took place with C1 Version 9 (but not from the start but rather with a later release). But don't take me on that.
Therefore PhaseOne team please fix this and put that cache folder inside the catalog or wherever you want but not into my picture or user data structure.
Seems like possibly a Mac thing then as I don't see it in Windows.
Andy, this is a user to user forum.
Your "Please fix this..." point may or may not be picked up by someone but you can be sure it is by taking a couple of minutes to create a Support Case. That will give everyone on the Tech Support team a focus point for working out why you see what you see.
HTH.
Grant0 -
[quote="SFA" wrote:
Andy, this is a user to user forum.
Your "Please fix this..." point may or may not be picked up by someone but you can be sure it is by taking a couple of minutes to create a Support Case. That will give everyone on the Tech Support team a focus point for working out why you see what you see.
HTH.
Grant
I know Grant that this is a user forum and I definitely should better have written 'PhaseOne should fix this' and yes, I already issued a support ticket to PhaseOne on that.
Cheers0 -
[quote="AndyE" wrote:
[quote="SFA" wrote:
Andy, this is a user to user forum.
Your "Please fix this..." point may or may not be picked up by someone but you can be sure it is by taking a couple of minutes to create a Support Case. That will give everyone on the Tech Support team a focus point for working out why you see what you see.
HTH.
Grant
I know Grant that this is a user forum and I definitely should better have written 'PhaseOne should fix this' and yes, I already issued a support ticket to PhaseOne on that.
Cheers
Ah, had you mentioned that Andy we could have saved a couple of posts .... well, 3 now!
😉
Grant0 -
[quote="AndyE" wrote:
As far as I can remember this behaviour already took place with C1 Version 9 (but not from the start but rather with a later release). But don't take me on that.
Therefore PhaseOne team please fix this and put that cache folder inside the catalog or wherever you want but not into my picture or user data structure.
The oldest folders I can find are from 12/4/2016. I think that's when V10 came out. I had never noticed this before.0 -
[quote="NN635781531552263255UL" wrote:
[quote="AndyE" wrote:
As far as I can remember this behaviour already took place with C1 Version 9 (but not from the start but rather with a later release). But don't take me on that.
Therefore PhaseOne team please fix this and put that cache folder inside the catalog or wherever you want but not into my picture or user data structure.
The oldest folders I can find are from 12/4/2016. I think that's when V10 came out. I had never noticed this before.
I assume your date format is MM/DD/YYYY?
Just for checking to be certain.
Grant0
投稿コメントは受け付けていません。
コメント
32件のコメント