Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Comments

38 comments

Date Votes
  • volatus
    OK, what I have learned today is to hold Shift-Command+D to process all selected files.

    This is completely different than in 3.5 Pro. I select the images and klick on the process wheel and batch processing starts.

    Maybe I am missing something?
    0
  • Andy 5
    Yesterday i inadvertantly selected all 152 images and began a batch process. I could not get it to stop the processing. restarting the software , even deleting the session file did nothing... esch time I restarted the software it began the batch all over again. I finally removed ALL the files, raw etc, re installed the raw data into a new folder and started over again. SOOO... how does one stop the processing?
    regards , Andy
    0
  • Paul Steunebrink
    [quote="ajd" wrote:
    (...)SOOO... how does one stop the processing?
    regards , Andy

    Stopping is not allowed in CO4! You MUST process! (just kidding)

    Go to the Batch tools tab, in the Queue sub tab there is a Stop button below. You can stop a queue at any time immediately with a single click. Delete the queue when stopped (Cmd+A, Delete or BackSpace). Even deleting the queue (or a selection of the queue) when running is no problem.
    0
  • Leonardo12
    I am just not using C1 4 since it is not a professional program. It is better to just ignore it and wait for C1 4 PRO -whenever it will come-

    There is no point in changing the work flow to step down in to a light program and change again when the real C1 is ready?

    Also I work tethered, plus, the files are not compatible.
    0
  • Leonardo12
    That was then... now I'm liking C1 4.5 PRO. Good job !

    [quote="barretophotography" wrote:
    I am just not using C1 4 since it is not a professional program. It is better to just ignore it and wait for C1 4 PRO -whenever it will come-

    There is no point in changing the work flow to step down in to a light program and change again when the real C1 is ready?

    Also I work tethered, plus, the files are not compatible.
    0
  • Neil Burger
    why is it when i hold shift and click process to batch, it only shows the number 1 next to the progress bar. very confusing. it should show the number of images that I am batching and count down to one. or am i missing something? (using C1Pro 4.5.2)
    0
  • Ulf Liljegren
    Should be fixed in 4.6 also you can change so you do not have to hold down shift anymore to process a range of images.
    New icon in the tool bar to "edit primary only" turn this off and shift is no longer needed.
    0
  • Neil Burger
    It is NOT FIXED in 4.6. Luckily I can now batch process without the option key but the number to the left of the progress bar still says "1" only. Can we fix this so that the number displays the amount of images that are being processed and the numbers will decrease as images process??
    0
  • Paul Steunebrink
    Clearly a slight misunderstanding between Neil and Ulf. While you (Neil) wait this to be fixed I like to show you that each image in the queue shows the number of total images in the queue and and its position in the queue (for 10 images in queue: 1/10, 2/10... 10/10). For each image processed, the counter adapts to new queue size.

    In other words, the requested information is already available since CO4 was introduced over a year ago...
    On the other hand is the "0" or "1" next to the process rather meaningless to me other then that process is running (1) or not (0).
    0
  • Andrew852
    Hi guys,

    Can't seem to figure this out...

    In the thumbnail view, I select 9 images.. the first image has a bold white frame, the others have a thin white frame.

    I think press Shift + Command + D and my Mac beeps at me.

    If I go to Shift + Process Button, it only processes the first image

    If I drag the thumbnail icon, it grabs all 9 images but I can't drop them into the queue either ( a long shot!)


    ( I figured it out.. I had Edit Primary Only enabled )
    0
  • Chris1012
    I don't have the edit primary only button enabled and I am trying to batch process about 165 images. I am on image 56 and COP has crashed on my no less than 10 times. I cannot understand why it is crashing on me, sometimes it will do 5-10 images, other times it won't even get through one. Anyone else having these crashing issues? I am running the latest version of COP 4.6 and also the latest update of Leopard. Driving me insane...

    Thanks,

    Chris
    0
  • Paul Steunebrink
    [quote="Chris" wrote:
    I don't have the edit primary only button enabled and I am trying to batch process about 165 images. I am on image 56 and COP has crashed on my no less than 10 times. I cannot understand why it is crashing on me, sometimes it will do 5-10 images, other times it won't even get through one. Anyone else having these crashing issues? I am running the latest version of COP 4.6 and also the latest update of Leopard.

    I do not have a sensible solution I am afraid but 2 question and 2 suggestions.
    Question1: what is the amount of RAM in your Mac?
    Question2: what is your output profile and file setting (TIFF, JPEG)?
    Suggestion1: clear your batch history (Clear history button on Batch tool, History tab)
    Suggestion2: restart your Mac before processing with CO4
    I apparently have my suspicious thoughts in the direction of processing parameters or a memory leak.
    0
  • Chris1012
    Sorry, I have been away for a while.

    I realized that if I run a batch process but do not click to show the batch window (stay on the process window) it will complete with no crashing. I have not tried to replicate the crash since my last post, but I will.

    Paul - to answer your questions I have 5 gb of RAM running on a MacPro Dual-Core Intel Xeon. The latest version of Leopard 10.5.6

    The output profile was set to 8-bit Tiff at 100%, 300dpi.

    I'll let you know if I can replicate this crash when I have time.

    Chris
    0
  • Paul Steunebrink
    Tip: empty your batch history every now and then.
    0
  • teng1
    Batch processing crash with only ONE image selected to process.

    Support, please hurry give us the new patch. TQ!
    0
  • Paul Steunebrink
    [quote="teng" wrote:
    Batch processing crash with only ONE image selected to process.

    Support, please hurry give us the new patch. TQ!

    Tip: clear the history queue from the Batch tool tab and try again. And if you run 4.6.1, go back to 4.6. More tips to recover from crahes:
    viewtopic.php?p=26161#p26161
    0
  • Catherine Opie
    I am having the same problem. It crashes in the middle of batch processing - sometimes after 2 images, sometimes after 15. It happens on all sizes of images-- jpegs and tiffs. If I stop and start the queue it will restart and go through a couple more images. Sometimes I can do this and make it through the batch- sometime I have to restart because it can't make it through one image after many stops and starts. Is someone working on this? It's a huge huge pain to have to babysit the queue while it batch processes.
    0
  • Paul Steunebrink
    [quote="Catherine" wrote:
    I am having the same problem. It crashes in the middle of batch processing - sometimes after 2 images, sometimes after 15. It happens on all sizes of images-- jpegs and tiffs. If I stop and start the queue it will restart and go through a couple more images. Sometimes I can do this and make it through the batch- sometime I have to restart because it can't make it through one image after many stops and starts. Is someone working on this? It's a huge huge pain to have to babysit the queue while it batch processes.

    clear the batch queue history from the Batch tool tab, History tab.
    0
  • Permanently deleted user
    I also tried Chris' method of just staying in the process window and not the batch window and all files processed without stopping.
    0
  • Catherine Opie
    Thanks Paul.
    I cleared the batch queue history and processed a batch of small jpegs. Again, after about 10 it got hung up on one and I had to start and stop the queue. After doing this five times after processing 9 or ten images the program eventually crashed.
    Any other suggestions?
    Thanks!
    0
  • Mark Astle
    Having the same issue. cleared the history etc. still crashing. Before it even finishes one image. And I have a deadline of yesterday. I never had any problems with version 3 -what's happening?
    0
  • Paul Steunebrink
    See my checklist to fight crashes. Add 'reboot system before start processing' to the list.
    viewtopic.php?p=26161#p26161
    0
  • thomas heydon
    I have completely random imgcoreprocess errors whilst batch processing. Processing stops and when you restart it 4.8.1 crashes. The same file that caused the crash can then be processed, so this is not a corrupt file issue. What causes the processing to stop? It is completely random. Sometimes I can process 200 files without a problem and sometimes it stops every 5 files. I have only noticed this problem on my macpro, it hasen't happenned on my macbook pro.
    (I am devoloping P45+ raw files into jpegs)
    Anyone found the reason for this yet?
    0
  • Paul Steunebrink
    [quote="thomas326" wrote:
    I have completely random imgcoreprocess errors whilst batch processing. Processing stops and when you restart it 4.8.1 crashes. The same file that caused the crash can then be processed, so this is not a corrupt file issue. What causes the processing to stop? It is completely random. Sometimes I can process 200 files without a problem and sometimes it stops every 5 files. I have only noticed this problem on my macpro, it hasen't happenned on my macbook pro.
    (I am devoloping P45+ raw files into jpegs)
    Anyone found the reason for this yet?

    Clear the process history.
    0
  • thomas heydon
    i did clear the process history, still get the same crashes......
    0
  • Paul Steunebrink
    [quote="thomas326" wrote:
    i did clear the process history, still get the same crashes......

    Because you experience the problem on the MacPro (and not on MacBook Pro), it might be a memory problem. Although a bit of a guess, MacPro systems typically have larger amounts of RAM (> 4 GB) resulting in CO4's memory use growing beyond healthy limits.
    I suggest to restart your MacPro (assuming you have use CO4 for adjusting etc) before starting a batch process and let it run. See what happens.
    0
  • thomas heydon
    thanks for the tip but still no success. i rebooted, deleted batch history, and deleted both the batch queue folders in library/application support/phase one (or capture one)......the only difference is that now i can sometimes relaunch the process queue (after it randomly stops) without CO4 crashing. this is very frustrating......
    0
  • jamew3
    Could someone please help me. I have successfully used the batch process functionality on several occassions. This morning I added 59 images to the batch process and nothing is happening. I have tried Stop/Start and clearing the history and queue and starting again, but nothing works. Any advice would be greatfully appreciated.
    0
  • Paul Steunebrink
    [quote="jamew3" wrote:
    Could someone please help me. I have successfully used the batch process functionality on several occassions. This morning I added 59 images to the batch process and nothing is happening. I have tried Stop/Start and clearing the history and queue and starting again, but nothing works. Any advice would be greatfully appreciated.

    I would suggest to remove the preference file and if that does not help the session (*.col45) file. Details:
    http://www.phaseone.com/HOME/Content/Su ... 20-%20Main
    Start with processing one image. Check for sufficient disk space and check your output parameters of your process recipe.
    0
  • Permanently deleted user
    Did anyone ever find a solution to the random crashes for processing images? My C1Pro 4.8.3 was processing just fine a few days ago. But, now it's crashing after every few images get added to the queue. I'll add one, the queue will have two or three images in it, and kablooey! Once I restart C1Pro and the queue, the images in process fine. And the one causing the failure will process, too.

    I have tried clearing my process history and restarting. Random crashes continue. I am OK with deleting the session file and the preferences. But, before doing so, can someone give me advice on what I need to preserve (e.g. screen shots of the C1Pro preferences screens) so I can rebuild the app/session to work as how it was set up.

    Thanks!

    Gary
    0

Post is closed for comments.