CO v 7.1 also buggy?
I just tried CO v7.1 out and processed 12 DSC-RX100 RAW files and while it does not crash it's still buggy.
CO sees the files as cRAW? the RX100 only has RAW cRAW is not even an option.
Renaming worked like a dream, no crash and in the correct sequence, that's a first for me in a while now 😄
I selected all 12 images with (Edit All Selected Variants) enabled, made my adjustments and CO applied all of the adjustments I made except for contrast and saturation, should they not be applied as well?
After I developed the RAW files to jpg's I Permanently deleted the files in CO but not all working files are deleted! with v7.01 and 7.02 it always left a few settings files in the settings70 folder, in v7.1 it does not delete any of them!
I deleted them manually in finder and converted a few more RAW files which had a different name than the previous 12 RAW's, I again permanently deleted the RAW files in C1 and again they were not deleted in the settings70 directory, to make matters worse I then had half of the setting files left from this conversion and half the settings were back from the first conversion? even though I had deleted them manually.
This was a 30 minute play around doing pretty basic stuff so I'm wondering, what else is still not working properly?
Dave...
CO sees the files as cRAW? the RX100 only has RAW cRAW is not even an option.
Renaming worked like a dream, no crash and in the correct sequence, that's a first for me in a while now 😄
I selected all 12 images with (Edit All Selected Variants) enabled, made my adjustments and CO applied all of the adjustments I made except for contrast and saturation, should they not be applied as well?
After I developed the RAW files to jpg's I Permanently deleted the files in CO but not all working files are deleted! with v7.01 and 7.02 it always left a few settings files in the settings70 folder, in v7.1 it does not delete any of them!
I deleted them manually in finder and converted a few more RAW files which had a different name than the previous 12 RAW's, I again permanently deleted the RAW files in C1 and again they were not deleted in the settings70 directory, to make matters worse I then had half of the setting files left from this conversion and half the settings were back from the first conversion? even though I had deleted them manually.
This was a 30 minute play around doing pretty basic stuff so I'm wondering, what else is still not working properly?
Dave...
0
-
Hey Dave,
The bug I found is that if I drag a file from one folder to another, then go to that folder in CO, it doesn't appear. If I go into the folder via the finder, sure enough, the file is where I dragged it to. My work-around is to quit CO after I drag the files then relaunch it. The files appear!
Good luck to us all.....
Paul0 -
Hi Paul, I have noticed that as well!
Here is another one, sometimes after having made an adjustment the adjustment doesn't show, the workaround is to click another image and then go back again to the adjusted image it then shows.
To be honest the list of bugs and work-a round's in C1 just goes on and on, it's pathetic for a v7.x, or any version of software for that matter, except perhaps a beta version, I really don't know what PO is on.
I don't think there has been a fully bug free version of C1 since v3.7x, and the only reason I stick with C1 is that the end result when reached, is very good.
Dave...0 -
Ever thought about that your "workflow" is a little buggy or at strange?
Deleting the the files in COne does not meant that all met data is deleted, unless the regarding sessionDb and related folders are deleted.
Regarding file actions on OS level is something completely different than file actions in an application, that usually only applies "metadata" to the originals w/o touching them anyway. Changes in your file systems needs updating/synchonising COnes sources as well, before the changes are recognised and displayed. This action you initiate by newly reading in the data that are changed on fs level.
The reason why not all edit steps are displayed is not a bug in COne - it is a bug in Layer 8!
If the actual raw file specification is not supported by COne you can be lucky that most of the elements can be applied to the files by "downgrading" the file through renaming them to an older version of file specification and is an indication, that those containers have been changed by the camera manufacturer, i. e. the containers might renamed or stored in another portion of the file or containing values that cannot be treated like those from the former file-format.
---
BTW: It is impossible to produce 100% error-free code or 100% error-free applications because nobody in world would purchase an "100% error-free-application" because the related amount of money to be spent on this will exceed the budget of any user.
saludos redondos -
tom0 -
[quote="Thomas248" wrote:
Ever thought about that your "workflow" is a little buggy or at strange?
Please elaborate?
Deleting the the files in COne does not meant that all met data is deleted, unless the regarding sessionDb and related folders are deleted.
Yes it does, If you (Permanently) delete files in C1 as I said, it is meant to remove ALL working files as well and it normally does, but in v7.1 it does not remove the adjustment files but it does remove all other working files.
In v7.01 and 7.02 it removed most of them but not all the time?
Regarding file actions on OS level is something completely different than file actions in an application, that usually only applies "metadata" to the originals w/o touching them anyway. Changes in your file systems needs updating/synchonising COnes sources as well, before the changes are recognised and displayed. This action you initiate by newly reading in the data that are changed on fs level.
The reason why not all edit steps are displayed is not a bug in COne - it is a bug in Layer 8!
If the actual raw file specification is not supported by COne you can be lucky that most of the elements can be applied to the files by "downgrading" the file through renaming them to an older version of file specification and is an indication, that those containers have been changed by the camera manufacturer, i. e. the containers might renamed or stored in another portion of the file or containing values that cannot be treated like those from the former file-format.
❓
---
BTW: It is impossible to produce 100% error-free code or 100% error-free applications because nobody in world would purchase an "100% error-free-application" because the related amount of money to be spent on this will exceed the budget of any user.
saludos redondos -
tom
Dave...0 -
Sorry about that misconception - I was referring to the use of referenced catalogues - not to sessions.
Forget what I wrote, because that does not refer to your issue.
saludos redondos -
tom0 -
[quote="Kodakdog" wrote:
Hey Dave,
The bug I found is that if I drag a file from one folder to another, then go to that folder in CO, it doesn't appear. If I go into the folder via the finder, sure enough, the file is where I dragged it to. My work-around is to quit CO after I drag the files then relaunch it. The files appear!
Good luck to us all.....
Paul
yes I've noticed this as well. Using sessions (not catalog). Also, if you find the folder in the FINDER (not C1) and rename the missing file, it will appear (even just adding a number or something to the name). you will have to reapply any styles, but its faster than restarting the software.
Also, I've see some files just disappear - well, they are in the session with a dashed line around there there should be a file (like if there are 5 files in the session, the first few might be "invisible" and the remaining images show normally. So it is like the remaining images are floating in the window. You can't select the invisible previews with the mouse, but if you select one that is visible, you can use the arrows on the keyboard to select the invisible ones.
And yet another - sometimes the windows dont sort properly.0
Post is closed for comments.
Comments
6 comments