Bug in 3.6 SE: Error in processed image ....
Looks to be the same as the reported 1D2 problem already reported - a problem with cached information.
-
A further thought - These images were originally processed with the previous version of CaptureOne SE, and so had saved settings. Perhaps the saved settings are not compatible, and are not migrated either.
-
Original post:
It doesn't seem that anyone else has found this yet, and it may be that I'll never see it again, but today I found a bug in the processing stage of 3.6 SE (3.6.0.88).
I set up a load of images to be processed having changed the Contrast Correction setting (Nice feature 😄 ), which caused a stripe across the bottom of the images from my 1D2 to be a repeat of the same area just above.
This was strange because yesterday the images had been processed just fine. To see if it could be fixed, I changed various things and found that even though there had been no crop set on the image I found this in, the first of the session, and which I was using to find the problem, by resetting crop in the tool menu the output images were processed ok again.
Before finding this, I found it was not due to the CC adjustment, or the zoom size in the window, at least, changing these again did not make the problem go away. I may have trie a couple of other random things too.
I had applied a crop to the last few of the group being processed, but even the first image I processed today had the defect, and the crop hadn't been used until after that had been processed. The cropped images later in the batch did not show the defect, only the full frame images.
I can't say for sure that I hadn't played with the crop tool before starting the batch, or that I hadn't used it yesterday, but I'm pretty sure I didn't.
Stopping and restarting CaptureOne did not cure the problem - it did the same thing when the application was restarted, until the crop tool was reset (Remove crop, even if none applied).
If it's relevant, I had also been using the tool to apply settings to a selection of images, but again, not to the one on which I noticed the defect - being the first of the session.
Of course, it may be I got some details of my processing wrong, as I left a batch to be processed and came back an hour or two later, but I'm sure I didn't use the crop tool at all on the first image, as I don't much like it (see below), and do my cropping in PSE. All I use this crop tool for is to make a rough cut of the image to speed up processing.
I can't think of anything else relevant, except that I've not made any great effort to see if I can make it happen again - I'd like to get on with the job I started!
As others have said, this is the best tool so far for this job, and it has a lot of good features and good ideas, but it's not there yet, and it certainly could also do with some quailty process improvements. I can only imagine there must be heavy pressure from investors to get income from new products, but really the lesson has to be learned by now. You've read all of this before - sorry about that! - but I wonder if the message has been received at the right place yet.
-
A further thought - These images were originally processed with the previous version of CaptureOne SE, and so had saved settings. Perhaps the saved settings are not compatible, and are not migrated either.
-
Original post:
It doesn't seem that anyone else has found this yet, and it may be that I'll never see it again, but today I found a bug in the processing stage of 3.6 SE (3.6.0.88).
I set up a load of images to be processed having changed the Contrast Correction setting (Nice feature 😄 ), which caused a stripe across the bottom of the images from my 1D2 to be a repeat of the same area just above.
This was strange because yesterday the images had been processed just fine. To see if it could be fixed, I changed various things and found that even though there had been no crop set on the image I found this in, the first of the session, and which I was using to find the problem, by resetting crop in the tool menu the output images were processed ok again.
Before finding this, I found it was not due to the CC adjustment, or the zoom size in the window, at least, changing these again did not make the problem go away. I may have trie a couple of other random things too.
I had applied a crop to the last few of the group being processed, but even the first image I processed today had the defect, and the crop hadn't been used until after that had been processed. The cropped images later in the batch did not show the defect, only the full frame images.
I can't say for sure that I hadn't played with the crop tool before starting the batch, or that I hadn't used it yesterday, but I'm pretty sure I didn't.
Stopping and restarting CaptureOne did not cure the problem - it did the same thing when the application was restarted, until the crop tool was reset (Remove crop, even if none applied).
If it's relevant, I had also been using the tool to apply settings to a selection of images, but again, not to the one on which I noticed the defect - being the first of the session.
Of course, it may be I got some details of my processing wrong, as I left a batch to be processed and came back an hour or two later, but I'm sure I didn't use the crop tool at all on the first image, as I don't much like it (see below), and do my cropping in PSE. All I use this crop tool for is to make a rough cut of the image to speed up processing.
I can't think of anything else relevant, except that I've not made any great effort to see if I can make it happen again - I'd like to get on with the job I started!
As others have said, this is the best tool so far for this job, and it has a lot of good features and good ideas, but it's not there yet, and it certainly could also do with some quailty process improvements. I can only imagine there must be heavy pressure from investors to get income from new products, but really the lesson has to be learned by now. You've read all of this before - sorry about that! - but I wonder if the message has been received at the right place yet.
0
La publicación no admite más comentarios.
Comentarios
0 comentarios