C1 stops processing with error
Yeserday I started using crop in C1.
I processed and queued about 400 pictures, then went to bed to let C1 process them.
To my surprise when I came back to the comp enough hours later, it showed an popup error message 'invalid crop' and just ***STOPPED PROCESSING*** after only a few pictures.
Whats worse, it didn't even show the name of the raw file the error occured on. And in the file explorer this file had a green dot for 'has been processed', which it had not.
For me this is a quite nasty bug, since I can't rely on C1 to process alone anymore but got to check back on it every now and then ☹️
Is this a known bug? Any workaround other than not to use crop?
Sam
I processed and queued about 400 pictures, then went to bed to let C1 process them.
To my surprise when I came back to the comp enough hours later, it showed an popup error message 'invalid crop' and just ***STOPPED PROCESSING*** after only a few pictures.
Whats worse, it didn't even show the name of the raw file the error occured on. And in the file explorer this file had a green dot for 'has been processed', which it had not.
For me this is a quite nasty bug, since I can't rely on C1 to process alone anymore but got to check back on it every now and then ☹️
Is this a known bug? Any workaround other than not to use crop?
Sam
0
-
Sam,
This should work as intended.
Please make a Support Case on this issue.
Support Website: http://support.phaseone.com
Include type of camera files, workflow - rotation/arbitrary rotation, cropping steps etc. with all details.
Thanks,
k c0 -
This error occured about every 150 pictures, and I got no clue how to reproduce it.
My guess is I somehow managed to set the cropping boundaries outside the picture - maybe showing the full cropping coordinates and image size in the error message would help understanding the error.
Another, maybe related thing I noticed: when I used cropping every few hundred pictures I switched to a fresh picture, and it already had a cropping area set, even though I never touched this picture before.
I'll file a bug when I find a way to reproduce the problem, without knowing how to do this I don't think it would help - my request was not about the error, but about C1 *stop processing* upon showing the error!
Sam0
投稿コメントは受け付けていません。
コメント
2件のコメント