C1P 11 still doesn't request discrete GPU in macOS 10.13.*

Permanently deleted user

• 2017年12月02日 18:03

I reported this bug in version 10 expecting it to be a quick fix. The response from Phase One was "10.13 isn't supported". Well, the release notes say Capture One Pro 11 supports macOS 10.13. I downloaded the trial to give it a shot, and while performance improvements on the surface seem to be pretty good, this bug is still present and overall hinders those performance improvements on my Macbook Pro.

I have to say I'm really disappointed. For something like this, which should be a quick fix, phase one has given me the run-around on version 10 and still hasn't fixed it in version 11. How do you expect to justify the steep upgrade cost to your customers if you:
1) don't fix bugs that have been very clearly reported to you in previous versions, and
2) don't show any appreciation whatsoever for your customers doing a little bit of free QA work for you and actually reporting these bugs

This is a pricey piece of software. For the price, I would expect much better customer service/engagement than I've experienced.

0

• 

  Permanently deleted user

  • 2018年03月15日 10:19

  Yes, I had the same "issue" when I beta tested C1 v11 while working on v10. When I switched from v10 to v11 and vice versa, I had to wait for the updating of hardware acceleration process. But I think this is merely because the two versions are different !!

  0
• 

  Christian Gruner

  • 2018年03月15日 16:25

  [quote="kavehv" wrote:
  You can disable it in energy settings or just open any app that requests the discrete GPU (like Photos.app).
  
  The workaround posted about deleting some files is untenable. CP1 is supposed to be able to run versions side-by-side. I have both 10 and 11 installed, and every time I switch GPUs and versions, it has to set up hardware acceleration again. I keep getting told there is no problem here, yet I see it every time I open either version of C1P. Quite frankly, it's starting to get really frustrating.

  
  
  While rebuilding the kernels when a new/other version is launched as designed (and rarely encountered in a normal workflow), I can’t reproduce the rebuilding when switching GPU’s.
  As mentioned, even though macOS might change output adapter to the display, CO will still be using all available GPU’s.
  
  I suggest you contact our Support team, if you haven’t done so already.

  0
• 

  Permanently deleted user

  • 2018年03月20日 01:55

  [quote="Christian Gruner" wrote:
  

  [quote="kavehv" wrote:
  You can disable it in energy settings or just open any app that requests the discrete GPU (like Photos.app).
  
  The workaround posted about deleting some files is untenable. CP1 is supposed to be able to run versions side-by-side. I have both 10 and 11 installed, and every time I switch GPUs and versions, it has to set up hardware acceleration again. I keep getting told there is no problem here, yet I see it every time I open either version of C1P. Quite frankly, it's starting to get really frustrating.

  
  
  While rebuilding the kernels when a new/other version is launched as designed (and rarely encountered in a normal workflow), I can’t reproduce the rebuilding when switching GPU’s.
  As mentioned, even though macOS might change output adapter to the display, CO will still be using all available GPU’s.
  
  I suggest you contact our Support team, if you haven’t done so already.

  
  
  As I mentioned earlier in this thread, the support team closed my case with no resolution. Here I am, a paying customer of both version 10 and 11 (and 9 and 8 before that), and I use both. I use 10 for all my older Canon stuff, and I use 11 for all my new Sony stuff so I can save money on the license fee. C1P is supposed to allow multiple versions to be in use, so if rebuilding the kernels when new/other versions are launched is truly by design, then it is poorly designed. What is my solution here? To pay more to PhaseOne to upgrade to a full version of 11? That's also not a good solution.
  
  As I mentioned before, support was unhelpful and I cannot reopen the support case and carry over the context it previously had.

  0

投稿コメントは受け付けていません。