Love Capture one 6 pro so far but...
The black and white tool and keystone editor is worth the $99 to upgrade by themselves, but I feel that Capture one 6 pro is a little left unfinished. 🤭
I am crashing every now and then, for completely different reasons. And sometimes when I make an adjustment, the picture looks completely corrupted for a few seconds then returns to normal with the adjustment applied ☹️
The local adjustment tool is slower than Capture NX 2, 🤓. Speaking or slow adjustments, it really does seem much slower than Capture one 5 pro. I might make a support case later, but would like to hear if anyone else feels the same way.
Windows XP 32 bit
Nvidia 9800 GT (latest drivers)
2GB memory
Athlon 64 6000+
I am crashing every now and then, for completely different reasons. And sometimes when I make an adjustment, the picture looks completely corrupted for a few seconds then returns to normal with the adjustment applied ☹️
The local adjustment tool is slower than Capture NX 2, 🤓. Speaking or slow adjustments, it really does seem much slower than Capture one 5 pro. I might make a support case later, but would like to hear if anyone else feels the same way.
Windows XP 32 bit
Nvidia 9800 GT (latest drivers)
2GB memory
Athlon 64 6000+
0
-
I have v6 Express and it also at first crashed often and now only sometimes. I found that most often there was a crash when switching to a new image. After I went thru each image in a set and waited at each one for a moment the crashing stopped when I returned to that set. But it took a bit as to go thru 100 images it crashed every 5-6 images. But once all had been gone thru once w/v6 it stopped.
So thinking there was an issue with the old proxies, I deleted all the .cop and .cof files for a new (to v6, but not to v5) set and there was no more crashing! At least not for well over an hour of moving thru and editing image. Then I ran a slide show and it crashed half way thru that.
I too will open a support case once I figure out a pattern so I have some meaningful data to report, like what specifically causes the crash, that will take some time to fiddle which I don't have now. For now I will use v5 until I have some jobs done.0 -
In terms of speed I've seen nothing but improvement so there may be something to go on in that regard for a support case. However, in any event if there are crashes it's important that the crash reports be submitted to help us understand the issues. 0 -
I just submited a crash report via a support case. I included two log files which seem to indicate some recent errors.
Specifically these from the ImgCore.log which seem to correlate with the crashes:
[color=#400000:2dmfrwjn]"2010-12-05 14:09:35.531> (ERROR) Exception in CTileExecuter::lowLevelExecute, current operation=[Convert16To32f], step=10
2010-12-05 14:15:13.312> (WARNING) A call to ICB_Release() is trying to delete a bitmap still being used by a processor.
This is possibly caused by calling ICB_Release() more than once."[/color:2dmfrwjn]0 -
[quote="ben43456" wrote:
The black and white tool and keystone editor is worth the $99 to upgrade by themselves, but I feel that Capture one 6 pro is a little left unfinished. 🤭
I am crashing every now and then, for completely different reasons. And sometimes when I make an adjustment, the picture looks completely corrupted for a few seconds then returns to normal with the adjustment applied ☹️
The local adjustment tool is slower than Capture NX 2, 🤓. Speaking or slow adjustments, it really does seem much slower than Capture one 5 pro. I might make a support case later, but would like to hear if anyone else feels the same way.
Windows XP 32 bit
Nvidia 9800 GT (latest drivers)
2GB memory
Athlon 64 6000+
-------
In case you experience "momentarily scrambled images", you have memory overflow using OpenCL. This is an issue when your graphics card is "too old/small". If you set the "Use OpenCL" to "never" in the preferences your problems should disappear.
-LKU0 -
I also see that temporary scramble. I have a ATI Radeon 3800 card (driver 10.11) and OpenCL option is greyed out and permanently set to 'never' as it should be as 3800 does not support OpenCL. Also I ran the DONOT_useopencl.reg script. 0 -
Is 512MB DDR3 of video memory not enough?! 0 -
We have identified issues with 512MB graphics cards. These issues will be fixed soon.
-Lionel0 -
That is good news (I hope).
Do the problems I describe seem likely related?
Thanks.0 -
Thanks, Lionel12, I didn't think 512MB of video memory was already obsolete. It's still enough to play some of the latest video games 😄 .
I have uninstalled Capture one 6 pro for now, I hope the 30 day trail timer stops ticking when I do that 😐. But so far, I like what I see, and will upgrade for sure when it gets fixed.0 -
I have a NVidia GTX 260 - 896 MB and am wondering if it will be usable with open CL or GL for CaptureOne ver 6? I'm also using Win 7 64 bit with 12 gigs of RAM. Thanks in advance. 0 -
[quote="Jaz57" wrote:
I have a NVidia GTX 260 - 896 MB and am wondering if it will be usable with open CL or GL for CaptureOne ver 6? I'm also using Win 7 64 bit with 12 gigs of RAM. Thanks in advance.
This should help answer your question, scroll to bottom:
http://www.phaseone.com/en/search/artic ... nguageid=10 -
Are these kind of errors recorded in the logs when v6 Express crashes consistent with the 512MB video card issue noted in this thread? I opened a support case a few days ago and am very happy to wait for a fix if this is related to the known issue, but if it is something else what more is needed to help me fix?
(WinXP, ATI Radeon 3800)
Thanks!
From the application.log:
[color=#000080:3fqpj6mg]"[2010-12-06 10:00:16 AM.281][468][ID:20, ProcessQue] {VIEWE} Error: The ImageCoreBitmap could not be converted to a Bitmap: (1574;1049) : System.ArgumentException: Parameter is not valid.
at System.Drawing.Bitmap..ctor(Int32 width, Int32 height, PixelFormat format)
at P1.C1.Common.BitmapHelper.DeepCopyBitmap(Int32 width, Int32 height, Int32 stride, IntPtr data, PixelFormat pixelFormat)
at aa.c()
at P1.C1.Tools.Viewer.BitmapTask.Execute(bw processor, aa bitmap)"[/color:3fqpj6mg]
From the ImgCore.log:
[color=#000080:3fqpj6mg]"bmpRef = 331897048
procRef = 9
2010-12-06 09:47:56.015> (WARNING) A call to ICB_Release() is trying to delete a bitmap still being used by a processor.
This is possibly caused by calling ICB_Release() more than once.
bmpRef = 329551968
procRef = 9
2010-12-06 09:58:20.640> Shutting down
2010-12-06 09:58:22.250> OpenCL skipped
2010-12-06 09:58:22.984> (ERROR) Timed out waiting for executers.
2010-12-06 09:58:24.578> System ready"[/color:3fqpj6mg]0
投稿コメントは受け付けていません。
コメント
12件のコメント