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. ⚠️

C1 Pro v4.5 not working???

Comments

10 comments

  • David1161
    [quote="Keith" wrote:
    I upgraded to c1 pro v4.5 today, and can't seem to get any of the tools to work. I can set preferences, but can't use the crop tool, for instance. The sliders seem unresponsive, as well. Anyone else experiencing problems? FYI I installed it on my intel iMac with 10.5.5 OS. Thanks, Keith.

    I can't help but I can sympathise. I have the same iMac, same OS, and 4.5 is not reading the majority of my existing files, so I've not got as far as trying the tools. And I find the user support section of the website impossible to use for my particular query. And the old version - C1v.4 wants me to sign up as a new user. Is anyone out there listening?

    David
    0
  • Paul Steunebrink
    David/Keith,
    Being unable to adjust settings for raw images might be due to choosing Capture One DB in the Licenses dialog. It allows you to view all supported raw files, but only adjust Phase One back raw files.
    Go to menu Capture One, License and select the Try option (if you have still days left) or Activate and you will be up and running again!
    0
  • David1161
    [quote="Paul_E" wrote:
    David/Keith,
    Being unable to adjust settings for raw images might be due to choosing Capture One DB in the Licenses dialog. It allows you to view all supported raw files, but only adjust Phase One back raw files.
    Go to menu Capture One, License and select the Try option (if you have still days left) or Activate and you will be up and running again!

    In my case 4.5 was not even recognising most of my files and nothing I could do would persuade it to do so. So I de-installed it and re-installed 4.0.1, which I've been using until now with complete satisfaction. But there's still a problem, in that everything works, but very slowly, with long delays. Something somewhere is corrupted, but I can't work out what it might be. And apparently I have only one activation remaining now, so I'm unwilling to experiment. Not happy right now.

    David
    0
  • Paul Steunebrink
    David,
    With CO4.x you can always reset your activation to the max. of 2, either from within the application (before you de-install) or from the web site at any time.
    0
  • Stefan Diaz
    Ater installing 4.5 Pro on my Macbook Pro OS X 10.5.5 intel dual core 2.6 ghz 4 gig DDR2 ram 160g HD with 7200.it was working albeit not very stable and random crashes. Yesterday I installed the Apple update for the migration assistant and now c1 pro will crash while opening or sometimes it opens but as soon as I do anything(like clicking a thumbnail) it crashes again. Worked all day on location with 3.7.9 I guess I have to stay with it although the creating of thumbnails is much quicker with 4.5 which is very good on location. Also I couldn´t figure out how to custom name my images before the import. we shoot 20 to 30 fashion pictures a day and each must be named as the client needs and not just with the job name.Also in output processing I could make a folder for each recipe(layout jpegs, preview jpegs for mail and 16bit tiffs for fein data) but no second subfolder for each model. In 3.7.9 you can. ex: preview jpgs/model_01/selection.
    C1 4.5 might be ok for people who shoot limeted amounts of shots but I need to handel 2-3000 shots a day. So far I am very disapointed after such a long wait. I also looked very dumb showing my clients the new long awaited software.... that constantly crashed.

    ☹️
    0
  • David1161
    [quote="Paul_E" wrote:
    David,
    With CO4.x you can always reset your activation to the max. of 2, either from within the application (before you de-install) or from the web site at any time.

    Thanks Paul, that's a useful piece of information. I looked under "licence" but couldn't find it there, but I'll check the website too. I think it would be best for me to start from scratch with a clean copy of 4.0.1, which I found suited me fine. I normally use a small utility for de-installation. Is there an "official" way of de-installing CO4.x that I ought to use?

    David
    0
  • thowi
    On Vista 4.5Pro is running pretty well.
    But on Macbook (OS X 10.5.5, Intel2Core, 2.4GHz, 2GB RAM) I can't get it running.
    Mac License is C1 DB. But just P45 files are loaded.
    C1 starts but if I adjust something... it crashes immediately. No way to try out anything...
    Horror!
    0
  • thowi
    [quote="thomas" wrote:
    On Vista 4.5Pro is running pretty well.
    But on Macbook (OS X 10.5.5, Intel2Core, 2.4GHz, 2GB RAM) I can't get it running.
    Mac License is C1 DB. But just P45 files are loaded.
    C1 starts but if I adjust something... it crashes immediately. No way to try out anything...
    Horror!


    Strange things is... V4.1.2 DB runs okay
    0
  • thowi
    [quote="thomas" wrote:
    On Vista 4.5Pro is running pretty well.
    But on Macbook (OS X 10.5.5, Intel2Core, 2.4GHz, 2GB RAM) I can't get it running.
    Mac License is C1 DB. But just P45 files are loaded.
    C1 starts but if I adjust something... it crashes immediately. No way to try out anything...
    Horror!
    On the Macbook with 3GB RAM now it's running okay. No crashes... actually pretty good.
    0
  • Stefan Diaz
    I had extensive contact with support for the same reason but everything they asked me to do(remove certain files uninstall and reinstall.. even 3 clean installs of my OS, nothing worked but after much studying of my crash logs and intensive testing I discovered that the the output icc profile was the cause of all the trouble. Using Adobe RGB 1998,Profoto and srgb I could not get the program to crash but as soon as I changed my output profile to the needed eciRGB_v2.icc the program crashed either immediately or as soon as I tryed to make an adjustment. Phase one R+D are now aware of the problem and have written to me that they will have a fix in the next update(4.6) at the end of november or early December.
    Try using a different profile in the output recipe and see if that helps.

    kind regards,
    Stefan
    0

Post is closed for comments.