chromatic aberration anomaly in C1 v 7.0.1
When I remove chromatic aberration in version 6 it will be visually gone also when viewing at full (fit) size. You can see the red-green lines disappearing when viewing a picture a normal full size (fit) the moment you enable removal of CA. When doing the same in version 7 the red-green lines will remain visible when viewing at full size and will only be gone when viewing at 100%!
I hope I am doing something wrong here, but if I am correct then personally I consider this a serious bug.
Cheers, Bob.
PS I have sent in a support case with screenshots in C1v6 and in C1v7. I do not know how to attach pictures to messages otherwise I could show what I am talking about.
I hope I am doing something wrong here, but if I am correct then personally I consider this a serious bug.
Cheers, Bob.
PS I have sent in a support case with screenshots in C1v6 and in C1v7. I do not know how to attach pictures to messages otherwise I could show what I am talking about.
0
-
Could it be that the same is being said here?
http://www.luminous-landscape.com/forum ... ic=72500.0
Cheers, Bob.
PS Will get back once I have feedback from support. My original message to them somehow did not make it with the attachments so I sent everything again.0 -
I have similar issues except it is noise reduction.
I reported the issue and was told to turn off Open CL in the settings. I did, and it didn't help.
Evidently, corrections don't show up in full view mode. If I zoom in just a little, the corrections will be apparent.
When the file is processed, the corrections are there.0 -
[quote="Sysyphus" wrote:
Evidently, corrections don't show up in full view mode.
This was not the case in v6. There most corrections showed up also in fit-size. That is one of the reasons I liked working in C1 so much. It is of course important that corrections are there when you output to TIFF or JPG or when you print, but it is simply very enjoyable and pleasant to work with when you also see them in fit-size. Moreover if it could be done in v6 there seems to be no reason why it cannot be done in v7.
Cheers, Bob.0 -
I cannot remember when I jumped on the C1 bandwagon, but yes, this new bug is a v7. I just checked and like you I found it hasn't been fixed in 7.01.
I have a strong feeling that they'll fix as it could be a deal breaker for some if not many.0 -
This is not really a bug, but a consequence of several "speed improvements".
To get back to Capture One 6 "behaviour", you need to change the preview size to 1024 (the default from Capture One 6) - and re-generate the previews - or move the raw files and import them again.
Capture One 7 uses much larger previews - to be able to speed up "zoom to fit" on large screens. Some may find they prefer smaller previews (and somewhat slower views - at 33%).
-Lionel0 -
[quote="Lionel12" wrote:
This is not really a bug, but a consequence of several "speed improvements".
To get back to Capture One 6 "behaviour", you need to change the preview size to 1024 (the default from Capture One 6) - and re-generate the previews - or move the raw files and import them again.
Capture One 7 uses much larger previews - to be able to speed up "zoom to fit" on large screens. Some may find they prefer smaller previews (and somewhat slower views - at 33%).
-Lionel
Interesting.
I think I can see the potential for compromise here but it also seems like something that would benefit from a more complete understanding of the underlying concepts and default decisions that were considered.
Is there already a document or help entry that describes this?
If not could someone create one? Maybe something for the blog?
I can see this being a perpetual and repeating question and point of come confusion if it is not fully described in publically available resources.
Grant Perkins0 -
Thanks Lionel12, that seems to have done the trick! 😄
Cheers, Bob0
Post ist für Kommentare geschlossen.
Kommentare
7 Kommentare