Can't get C4.0.1 to process file.
Just downloaded the update and am trying it out. Only one problem - it won't process the file. Zip, Nothing, Nada. Made my adjustments, reset the process parameters from the update, and hit "Process" and I get a big ole nothing.
Has anyone else had this issue? Any ideas? Thanks.
Has anyone else had this issue? Any ideas? Thanks.
0
-
Nevermind! C1 crashed right after I posted the first post. Upon re-start, it worked correctly. Hopefully, this won't happen every time! Nice work on the update Guys! 🤬 0 -
I noticed that the same thing happened to me when I loaded the update. I found that after the update is loaded, C1_4 initialized with the batch process stopped. I had to go to the batch window a click on "start" at the bottom near the progress bar. I would think that the default would be in the start mode, probably just an over site with the final build. 0 -
Hi,
I recently downloaded / bought C 4.01 and during my first test I thought too there was a bug and the program won't process the files.
But then I found out that this version works different to the Beta version when each file was processed after hitting the "Process" button.
Now the files to process go into the processing queue when hitting the "Process" button and processing only starts if one goes into the Queue Processing Sub-Menu hitting there the Start button. It seems to be in the Stop position by default but once hitting the Start button it will remain active so each file sent for processing will be processed immediately. So it's up to the user to decide whether he/she prefers block processing at the end of doing the correction jobs or to send each and every file directly for processing.
Hope this helps,
Cheers,
Michael Fritzen0 -
[quote="Michael Fritzen" wrote:
Now the files to process go into the processing queue when hitting the "Process" button and processing only starts if one goes into the Queue Processing Sub-Menu hitting there the Start button. It seems to be in the Stop position by default
Now this is interesting to hear. Yesterday I found to my frustration that 4.00 seems to default to "Start" mode even if the program is in "stop" mode when it is closed...then, when it's re-opened, I found that files still in the queue were processed immediately -- absolutely NOT what I wanted (especially not, considering the other settings that do persist between sessions.
I guess I'd better download 4.01 and see if the behavior has changed. If they aren't going to provide any option in the Preferences dialog (such as it is), I would prefer that the default always be "Stop" mode.0 -
This happened to me too and I did a system rollback to get rid of the thing. After I tried it once, it did nothing at all when I hit process. I did not know that process no longer really meant process in this update. Didn't expect I would have to re-learn Capture One yet again.
Restarted it, and I got a message that I had a number of files in the batch que. This was news to me as I placed none in the batch que. C$ did it for me. How nice.
I tried to process a file yet again. Same results, nothing at all happened when I hit process. Sort took some of the usefulness out of it. So I went to the system restore--which I had made a restore point before installing the update as I have had so much fun with Capture One in the past and I knew I might need it---and rolled the system back and trash canned the upgrade.
Unbelievable. What next?0 -
[quote="drichi" wrote:
So I went to the system restore--which I had made a restore point before installing the update as I have had so much fun with Capture One in the past and I knew I might need it---and rolled the system back and trash canned the upgrade.
Unbelievable. What next?
This and a few other messages about 4.0.1 are giving me pause about whether to update it at this time. Hopefully a 4.00-to-4.02 update won't first require doing the 4.00-to-4.01 update. Then again, I wonder if there's a way to preserve the 4.00 installation, just in case...0
投稿コメントは受け付けていません。
コメント
6件のコメント