Commentaires

34 commentaires

  • SFA
    I think you need to have a little patience until the revised Release Note makes its way through the server updates during the day.


    Grant
    0
    Actions pour les commentaires Permalien
  • Dave R
    [quote="Petr5" wrote:
    Release_Note_CO12.0.1... what's new, patches?

    What version 12.0.1? Just ran Check for Updates and it is still showing 12.0.0 as current.
    0
    Actions pour les commentaires Permalien
  • IanS
    [quote="David532" wrote:
    [quote="Petr5" wrote:
    Release_Note_CO12.0.1... what's new, patches?

    What version 12.0.1? Just ran Check for Updates and it is still showing 12.0.0 as current.

    Just go to the main PO site and download C1Pro. You get V12.01.

    Ian
    0
    Actions pour les commentaires Permalien
  • Thomas Demmelmaier
    Thank you for advise.

    Notes Still not Online.

    Downloading 12.0.1
    0
    Actions pour les commentaires Permalien
  • Dave R
    [quote="IanS" wrote:
    [quote="David532" wrote:
    [quote="Petr5" wrote:
    Release_Note_CO12.0.1... what's new, patches?

    What version 12.0.1? Just ran Check for Updates and it is still showing 12.0.0 as current.

    Just go to the main PO site and download C1Pro. You get V12.01.

    Ian

    Got it. Installed and running.
    Seems to have sorted out the problem that RGB readings at top of viewer were not displaying for Fuji RAF files.
    0
    Actions pour les commentaires Permalien
  • Paul Steunebrink
    Have been in touch with Phase One support. Release notes of 12.0.1 will be online shortly.

    Update:

    Release notes 12.0.1:
    0
    Actions pour les commentaires Permalien
  • Radomir Carapic
    My copy crash on first window couple of times....
    I installed over version 12.00,
    Anybody with similar experience?

    Windows 7 Pro, 32 Gb of Ram
    0
    Actions pour les commentaires Permalien
  • IanS
    [quote="NNN636164283498758748" wrote:
    My copy crash on first window couple of times....
    I installed over version 12.00,
    Anybody with similar experience?

    Windows 7 Pro, 32 Gb of Ram


    No problem for me on Win 10 (1809), 16Gb of Ram.

    Ian
    0
    Actions pour les commentaires Permalien
  • Jaromír Šafář
    [quote="NNN636164283498758748" wrote:
    My copy crash on first window couple of times....
    I installed over version 12.00,
    Anybody with similar experience?

    Windows 7 Pro, 32 Gb of Ram


    Capture one 12.0.1 crash at startup.
    I use Windows 7 Pro - 16 GB RAM.
    The error log dialog box remains blank.
    I have installed version 12.0.0 and everything works.
    On my second computer with Windows 10 everything is OK.
    Can you give me advice on what information to send to support?

    Thanks

    jaromir
    0
    Actions pour les commentaires Permalien
  • Ian Wilson
    [quote="Jaromir_Safar" wrote:
    [quote="NNN636164283498758748" wrote:
    My copy crash on first window couple of times....
    I installed over version 12.00,
    Anybody with similar experience?

    Windows 7 Pro, 32 Gb of Ram


    Capture one 12.0.1 crash at startup.
    I use Windows 7 Pro - 16 GB RAM.
    The error log dialog box remains blank.
    I have installed version 12.0.0 and everything works.
    On my second computer with Windows 10 everything is OK.
    Can you give me advice on what information to send to support?

    Thanks

    jaromir

    Just ask them! Open the support case. Tell them everything you can about the problem, and they will ask you for more information if they want it.

    Ian
    0
    Actions pour les commentaires Permalien
  • Paul Jones
    Unfortunately they haven't reinstated the 'edit with' and 'open with' keyboard shortcuts. Was really hoping for this one... sigh...
    0
    Actions pour les commentaires Permalien
  • Petr Bajer
    [quote="NNN636164283498758748" wrote:
    My copy crash on first window couple of times....
    I installed over version 12.00,
    Anybody with similar experience?

    Windows 7 Pro, 32 Gb of Ram


    Same problem here. I cannot start Capture One after update.

    Windows 8.1, 8 GB RAM
    0
    Actions pour les commentaires Permalien
  • Jaromír Šafář
    [quote="NNN636827167704545316" wrote:
    [quote="NNN636164283498758748" wrote:
    My copy crash on first window couple of times....
    I installed over version 12.00,
    Anybody with similar experience?

    Windows 7 Pro, 32 Gb of Ram


    Same problem here. I cannot start Capture One after update.

    Windows 8.1, 8 GB RAM


    After communications with support for me is a problem with the introduction of OpenCL.
    I had to disable OpenCL using the registry. Then comes standard CaptureOne run.
    Support advised me to download new drivers.Here is the last piece of advice:

    Supporter -
    It could be that we are taking advantage of more options and utilizing the GPU more extensively in this new release. most likely the GPU driver fails in some way and then crashes and takes Capture One along. I would like to suggest to keep your eyes open for new driver releases for your GPU on the GPU manufacturers website as that will likely solve this issue.

    So if you see a new driver set, install it. use the "enable opencl.reg" key to re-enable opencl on your machine and check if that solves it.

    Even though I have the latest graphics driver NVIDIA GeForce GTX 1050 Ti - version 25.21.14.1771 (driver date 11.1.2019), OpenCL is not working.
    I think that if OpenCL worked in CO 12.0.0, then there's no reason not to work in a new version that was released a month later.

    Jaromír
    0
    Actions pour les commentaires Permalien
  • SFA
    [quote="Jaromir_Safar" wrote:

    I think that if OpenCL worked in CO 12.0.0, then there's no reason not to work in a new version that was released a month later.

    Jaromír


    Unless the driver update is not all that one would hope it is (which sometimes happens);

    or

    the new driver is not being used.

    Have you been through the process of deleting the old driver build files and allowing C1 to create new ones?

    https://www.phaseone.com/en/Search/Arti ... nguageid=1

    Grant
    0
    Actions pour les commentaires Permalien
  • Jaromír Šafář
    [quote="SFA" wrote:
    [quote="Jaromir_Safar" wrote:

    I think that if OpenCL worked in CO 12.0.0, then there's no reason not to work in a new version that was released a month later.

    Jaromír


    Unless the driver update is not all that one would hope it is (which sometimes happens);

    or

    the new driver is not being used.

    Have you been through the process of deleting the old driver build files and allowing C1 to create new ones?

    https://www.phaseone.com/en/Search/Arti ... nguageid=1

    Grant


    Yes, I did all the steps:
    1. I forbid OpenCL using DONOT_useopencl.reg - CaptureOne version 12.0.1 was started without OpenCL OK
    2. I removed all the files from the directory - C:\ProgramData\Phase One\Capture One\ImageCore - CaptureOne version 12.0.1 was started without OpenCL OK
    3. I enabled OpenCL using useopencl.reg - Then CaptureOne version 12.0.1 always crashes.

    I install CaptureOne 12.0.0, including all of the above steps. - CaptureOne version 12.0.0 was started with OpenCL OK.

    Jaromír
    0
    Actions pour les commentaires Permalien
  • Paul Steunebrink
    [quote="Jaromir_Safar" wrote:

    I think that if OpenCL worked in CO 12.0.0, then there's no reason not to work in a new version that was released a month later.

    No offense, but I am afraid I entirely miss the logic behind this reasoning. To reverse the idea: what period would in your opinion qualify for such a change?

    Nevertheless, I much appreciate the feedback and I think that more users are helped with crash issues after the 12.0.1 update.
    0
    Actions pour les commentaires Permalien
  • Jaromír Šafář
    [quote="Paul_Steunebrink" wrote:
    [quote="Jaromir_Safar" wrote:

    I think that if OpenCL worked in CO 12.0.0, then there's no reason not to work in a new version that was released a month later.

    No offense, but I am afraid I entirely miss the logic behind this reasoning. To reverse the idea: what period would in your opinion qualify for such a change?

    Nevertheless, I much appreciate the feedback and I think that more users are helped with crash issues after the 12.0.1 update.

    Paul, I bought CaptureOne as a new version of 12. This version supports Windows 7® SP1 64-bit (according to release notes).
    If the monthly update later does not work properly with the same configuration on my computer, I am disappointed.

    Jaromír
    0
    Actions pour les commentaires Permalien
  • Paul Steunebrink
    I can understand disappointment. Win7 SP1 is still supported. This issue seems to be related to GPU acceleration. There could have been changes in 12.0.1, no sure.

    Has support asked you to delete C:\ProgramData\Phase One\Capture One\ImageCore folder? You could try that. It is the OpenCL kernel. If you delete it, it will generate a new one.
    0
    Actions pour les commentaires Permalien
  • Jaromír Šafář
    [quote="Paul_Steunebrink" wrote:
    I can understand disappointment. Win7 SP1 is still supported. This issue seems to be related to GPU acceleration. There could have been changes in 12.0.1, no sure.

    Has support asked you to delete C:\ProgramData\Phase One\Capture One\ImageCore folder? You could try that. It is the OpenCL kernel. If you delete it, it will generate a new one.


    But I did my steps already described:
    2. I removed all the files from the directory:
    C:\ProgramData\Phase One\Capture One\ImageCore and CaptureOne version 12.0.1 was started without graphic acceleration (OpenCL) OK.
    3. I enabled OpenCL using use opencl.reg and then CaptureOne version 12.0.1 always crashes.

    Jaromír
    0
    Actions pour les commentaires Permalien
  • Mika Leinonen
    Useless update. I have reported few bugs in early December 2018 and not one was fixed in this "update". Seems to me that folks in PhaseOne are just sitting on their hands and not fixing bugs reported.
    0
    Actions pour les commentaires Permalien
  • Dave R
    I can't help noticing that most problems (though not all) seem to occur with Windows 7 and 8. Both these are now only supported by Microsoft for security fixes. From the fact that installing Capture One 12.0.1 also results in the installation of Microsoft Visual C++ 2017 Redistributable (X64) I assume that Phase are using MS Visual C++ 2017 to compile the application. I am sure that MS have optimised Visual C++ for Win 10 applications. Just a thought 😐
    0
    Actions pour les commentaires Permalien
  • Irvin Gomez
    [quote="Paul_Steunebrink" wrote:
    [quote="Jaromir_Safar" wrote:

    I think that if OpenCL worked in CO 12.0.0, then there's no reason not to work in a new version that was released a month later.

    No offense, but I am afraid I entirely miss the logic behind this reasoning. To reverse the idea: what period would in your opinion qualify for such a change?

    Nevertheless, I much appreciate the feedback and I think that more users are helped with crash issues after the 12.0.1 update.


    The question is perfectly valid. After all, users are entitled to a working product, aren’t they? Yes, bugs and problems exist in every software. Capture One is not the only one - but blaming users for expecting the bugs to be solved by Phase One is in very bad taste.
    0
    Actions pour les commentaires Permalien
  • GrahamB3
    [quote="David532" wrote:
    I can't help noticing that most problems (though not all) seem to occur with Windows 7 and 8. Both these are now only supported by Microsoft for security fixes. From the fact that installing Capture One 12.0.1 also results in the installation of Microsoft Visual C++ 2017 Redistributable (X64) I assume that Phase are using MS Visual C++ 2017 to compile the application. I am sure that MS have optimised Visual C++ for Win 10 applications. Just a thought 😐


    Great observation. End of life for Win 7 is January 14, 2020, less than 1 year from today.

    I resisted Win 10 for years. I upgraded a Win 7 pro notebook during the free upgrade time, but doggedly hung onto Win 7 pro for my 2 desktops. Doing so prevented me from using the newest versions of some software, (Davinci Resolve ended support for Win 7).

    I built a new system in Oct. of '18, and installed Win 10. It's been great. No more software incompatibilities. I've had 0 BSOD's since the first boot. I still prefer Win 7, but as far as performance, there's no comparison. Win 10 is the way to go.

    For anyone who refuses to use Win 10, I suggest you move over to Linux, or (heaven forbid), go the Mac route. Win 7 isn't where you want to be in 2019.
    0
    Actions pour les commentaires Permalien
  • IanS
    [quote="GrahamB3" wrote:
    [quote="David532" wrote:
    I can't help noticing that most problems (though not all) seem to occur with Windows 7 and 8. Both these are now only supported by Microsoft for security fixes. From the fact that installing Capture One 12.0.1 also results in the installation of Microsoft Visual C++ 2017 Redistributable (X64) I assume that Phase are using MS Visual C++ 2017 to compile the application. I am sure that MS have optimised Visual C++ for Win 10 applications. Just a thought 😐


    Great observation. End of life for Win 7 is January 14, 2020, less than 1 year from today.

    I resisted Win 10 for years. I upgraded a Win 7 pro notebook during the free upgrade time, but doggedly hung onto Win 7 pro for my 2 desktops. Doing so prevented me from using the newest versions of some software, (Davinci Resolve ended support for Win 7).

    I built a new system in Oct. of '18, and installed Win 10. It's been great. No more software incompatibilities. I've had 0 BSOD's since the first boot. I still prefer Win 7, but as far as performance, there's no comparison. Win 10 is the way to go.

    For anyone who refuses to use Win 10, I suggest you move over to Linux, or (heaven forbid), go the Mac route. Win 7 isn't where you want to be in 2019.


    Unfortunately, this situation is all too common. Having watched the same scenario play out since DOS. Win 98SE is the greatest, no Win XP, no Win 7... Some people find change very difficult but it is a personal choice.

    Ian
    0
    Actions pour les commentaires Permalien
  • SFA
    [quote="GrahamB3" wrote:
    [quote="David532" wrote:
    I can't help noticing that most problems (though not all) seem to occur with Windows 7 and 8. Both these are now only supported by Microsoft for security fixes. From the fact that installing Capture One 12.0.1 also results in the installation of Microsoft Visual C++ 2017 Redistributable (X64) I assume that Phase are using MS Visual C++ 2017 to compile the application. I am sure that MS have optimised Visual C++ for Win 10 applications. Just a thought 😐


    Great observation. End of life for Win 7 is January 14, 2020, less than 1 year from today.

    I resisted Win 10 for years. I upgraded a Win 7 pro notebook during the free upgrade time, but doggedly hung onto Win 7 pro for my 2 desktops. Doing so prevented me from using the newest versions of some software, (Davinci Resolve ended support for Win 7).

    I built a new system in Oct. of '18, and installed Win 10. It's been great. No more software incompatibilities. I've had 0 BSOD's since the first boot. I still prefer Win 7, but as far as performance, there's no comparison. Win 10 is the way to go.

    For anyone who refuses to use Win 10, I suggest you move over to Linux, or (heaven forbid), go the Mac route. Win 7 isn't where you want to be in 2019.


    Graham,

    You may be right but my system came with Win 7 Pro back when Win 10 was unknown and has been extremely solid since it arrived in 2013 (iirc).

    Hopefully by now Win 10 is about as mature as Win 7 was then and MS have grown out of their habit of treating the users as beta testers of alpha software.
    0
    Actions pour les commentaires Permalien
  • NNN636637684199314126
    Hi,

    When I start Capture One 12x the load window starts and then crashes. in the log file that contains the error report has the following:

    ColorProfileLoad: failed to acquire color profile [C:\WINDOWS\system32\spool\drivers\color\wscRGB.cdmp].

    This is repeated again and again in the log. I have tried everything from reseting the Color profiles in windows to copying the ones from Capture one. Nothing works. My Capture one 11, never had this issue.

    If anyone has any ideas to help I would appreciate it.

    Thanks.
    0
    Actions pour les commentaires Permalien
  • SFA
    Is that profile in the location specified?

    As far as I know it is a standard Windows profile installation and has been for years.

    If the file can be found at the path specified then that might suggest a permissions issue?

    If it is not there that would be a puzzle.

    Whether that is a direct or indirect cause of a system crash is another matter.


    Grant
    0
    Actions pour les commentaires Permalien
  • Jaromír Šafář
    [quote="Paul_Steunebrink" wrote:
    [quote="Jaromir_Safar" wrote:

    I think that if OpenCL worked in CO 12.0.0, then there's no reason not to work in a new version that was released a month later.

    No offense, but I am afraid I entirely miss the logic behind this reasoning. To reverse the idea: what period would in your opinion qualify for such a change?

    Nevertheless, I much appreciate the feedback and I think that more users are helped with crash issues after the 12.0.1 update.


    I am happy because problems with malfunctioning hardware acceleration, I solved it.
    I installed the older driver 416.34 (Release Date 11.10.2018).
    Link - https://www.geforce.com/drivers/results/138695
    Tips for installing the latest driver that I received from technical support were bad.
    Jaromír
    0
    Actions pour les commentaires Permalien
  • Russell Elloway
    I'm surprised they couldn't have brought back the "Edit with ..." keyboard shortcut.
    0
    Actions pour les commentaires Permalien
  • MPW1950-2
    Over the years I have occasionally had new releases of Nvidia drivers cause problems, not with C1Pro particularly. I seem to recall my PC becoming generally flaky after such an update, rolling back just the Nvidia change solved the problem.

    I am very careful about new Nvidia driver updates.
    0
    Actions pour les commentaires Permalien

Vous devez vous connecter pour laisser un commentaire.