Capture One doesn't work on macOS High Sierra 10.13 Beta
Hi,
I have latest macOS High Sierra 10.13 beta (17A291m). C1 starts correctly, i can see thumbs but main viewer renders nothing.
https://www.dropbox.com/s/x01hk5l3yijd7r9/c1-main-viewer.png?dl=1
Is there any workaround or beta version?
I have latest macOS High Sierra 10.13 beta (17A291m). C1 starts correctly, i can see thumbs but main viewer renders nothing.
https://www.dropbox.com/s/x01hk5l3yijd7r9/c1-main-viewer.png?dl=1
Is there any workaround or beta version?
0
-
Workaround : don't use beta versions for production work. 0 -
You're right.
However phase one might be interested in this behaviour so they can investigate if their expensive SW will work in next version of macOS. I would expect more nice answer.0 -
Do you seriously believe they're not currently testing it, probably with the help of their beta-testers who signed an NDA? 0 -
Based on your reactions I really believe they do nothing about it. 0 -
Not sure what you mean. After 10.13 is released, Phase One will tell us if and when Capture One is compatible with it, that's all. 0 -
I'm not blaming phase one it doesn't work, just looking for some solution to be able use it. I have my reasons why I'm on latest beta version .... I would expect some kind of support / advice if it's possible. Not answer: "don't use beta", that wasn't kind at all. 0 -
Then you can try to file a bug report (link in my signature), but my feeling is they won't answer to such a question.
Or you can enter the beta program.0 -
[quote="vtajzich" wrote:
I'm not blaming phase one it doesn't work, just looking for some solution to be able use it. I have my reasons why I'm on latest beta version .... I would expect some kind of support / advice if it's possible. Not answer: "don't use beta", that wasn't kind at all.
I think you have no idea of the mountain of work faced vy a SW developer when Apple drops a new OS.
On June 5th Apple released the preliminary definition of the new APIs (Application Programming Interfaces - how an application like COP accesses the display, the file system, the GPUs..).
That's documentation only, some things willl have been missed, others wrong, and some will yet be changed.
At this point SW developers start reviewing their code, trying to figure out what is now broken, and how it should be fixed.
Some changes are minor, others require changes in the SW architecture.
Don't forget that a piece of SW like COP may have over a million lines of code, and hundreds of code modules.
Don't forget that code has to support both previous versions of OSX and the currrent one, and run on multiple versions of HW, and be consistent with the Windows version.
I would be totally unsurprised to hear that it takes over month to close the design for a major change to the API.
Last week Apple dropped the first Beta version of the new OS. It of course will be buggy (beta quality), and will not perfectly match the API documentation released a month ago.
Apple of course will start fixing bugs, and releasing new Beta versions and updated documentation every few weeks.
The application developers now start writing their new SW and testing code modules. (It doen't pay to be too eager, because Apple is stil changing stuff)
When the new SW doesn't run, the developer has to decide: Is my stuff wrong -or- Did I not understand the API document -or- Is there a bug in the Apple Beta SW?
The developers likely have some cases where they end up consulting Apple support and may have to raise bugs with them.
Now Apple comes along and says "Here's a new Beta - and new API documentation" (Oh Yes. That moving target thing.)
Some of the changes are only fixes inside the OS, but others may change the API.
So now the developers have to see how the new Beta affects the SW, and implement changes to keep up.
And test everything all over again.
Eventually all the code modules are integrated (i.e. verified to be working together), verification on various platforms and various OS versions is completed and all the major bugs have been fixed
Now the application developer has his Beta version ready.
One week is a totally unrealistic amount of time for that.0 -
An Excellent post Eric.
Moreover in cases where the developer is using specialist sub products licenced from 3rd parties - something that is incredibly common these days and about the only way end user costs can be kept down by not re-inventing "wheels" all the time - they may have to wait for for those specialist developers to do their work before they can understand the effects on their own code.
There are times when I stand back and wonder how anything ever works at all.
And then I remember that there are many large projects with huge budgets and often started using "government" money that don't work and never will before they are scrapped or further development is abandoned leaving just a very expensive subset of what was originally intended to be of any use at all.
Grant0 -
[quote="Eric Nepean" wrote:
[quote="vtajzich" wrote:
I'm not blaming phase one it doesn't work, just looking for some solution to be able use it. I have my reasons why I'm on latest beta version .... I would expect some kind of support / advice if it's possible. Not answer: "don't use beta", that wasn't kind at all.
I think you have no idea of the mountain of work faced vy a SW developer when Apple drops a new OS.
On June 5th Apple released the preliminary definition of the new APIs (Application Programming Interfaces - how an application like COP accesses the display, the file system, the GPUs..).
That's documentation only, some things willl have been missed, others wrong, and some will yet be changed.
At this point SW developers start reviewing their code, trying to figure out what is now broken, and how it should be fixed.
Some changes are minor, others require changes in the SW architecture.
Don't forget that a piece of SW like COP may have over a million lines of code, and hundreds of code modules.
Don't forget that code has to support both previous versions of OSX and the currrent one, and run on multiple versions of HW, and be consistent with the Windows version.
I would be totally unsurprised to hear that it takes over month to close the design for a major change to the API.
Last week Apple dropped the first Beta version of the new OS. It of course will be buggy (beta quality), and will not perfectly match the API documentation released a month ago.
Apple of course will start fixing bugs, and releasing new Beta versions and updated documentation every few weeks.
The application developers now start writing their new SW and testing code modules. (It doen't pay to be too eager, because Apple is stil changing stuff)
When the new SW doesn't run, the developer has to decide: Is my stuff wrong -or- Did I not understand the API document -or- Is there a bug in the Apple Beta SW?
The developers likely have some cases where they end up consulting Apple support and may have to raise bugs with them.
Now Apple comes along and says "Here's a new Beta - and new API documentation" (Oh Yes. That moving target thing.)
Some of the changes are only fixes inside the OS, but others may change the API.
So now the developers have to see how the new Beta affects the SW, and implement changes to keep up.
And test everything all over again.
Eventually all the code modules are integrated (i.e. verified to be working together), verification on various platforms and various OS versions is completed and all the major bugs have been fixed
Now the application developer has his Beta version ready.
One week is a totally unrealistic amount of time for that.
Actually I have idea what it means to adopt new version of OS. I'm using latest beta by no accident. I'm part of team who work on SW with over million of lines using 3rd party libraries. However it might be possible to fix it within a days / week.
There might be workaround, maybe some property in OS to be switched or something else. Maybe not. C1 worked with first beta release. It is broken with latest beta - it might be bug in OS itself or something in C1, that's why I'm asking here ...0 -
Thank you for your time guys.
I've contacted Phase One support to get more info on this.
I'll share my findings when I get answer or when new macOS beta is released.0 -
[quote="vtajzich" wrote:
Thank you for your time guys.
I've contacted Phase One support to get more info on this.
I'll share my findings when I get answer or when new macOS beta is released.
So far they are on a 2+ month back-order (and counting) for a mere warning when pressing the delete key.
A week to shed a new public build which is beta OS ready might be asking too much.
😕0 -
For the OP: I've found a workaround which is to plug in an external monitor before you launch C1P. This makes C1P display properly in 10.13 DB2. Moreover, loading RAWs seems to be snappier in 10.13 and C1P than I recall it being in 10.12.
For all the others who replied with unhelpful criticism: if the OP hadn't posted here, I wouldn't have seen it and been able to offer a workaround. Furthermore, C1P devs might not have been aware of such a workaround, and that might help cut their own debug time down. That is the whole point of these forums, collaboration and help. Unhelpful responses are just noise.
General note: I have no idea why this forum is so hostile to people asking about support for the next [announced] version macOS, especially since everyone here spent at least $300 to buy it. Given the price of the software and that we're all paying customers, it seems reasonable to expect a little bit of a heads up or an update on support for the next major version of the OS. My own thread asking about this very thing was deleted without explanation or notification. There is no need to be hostile towards your/other customers like this.0 -
[quote="kavehv" wrote:
For the OP: I've found a workaround which is to plug in an external monitor before you launch C1P. This makes C1P display properly in 10.13 DB2. Moreover, loading RAWs seems to be snappier in 10.13 and C1P than I recall it being in 10.12.
For all the others who replied with unhelpful criticism: if the OP hadn't posted here, I wouldn't have seen it and been able to offer a workaround. Furthermore, C1P devs might not have been aware of such a workaround, and that might help cut their own debug time down. That is the whole point of these forums, collaboration and help. Unhelpful responses are just noise.
General note: I have no idea why this forum is so hostile to people asking about support for the next [announced] version macOS, especially since everyone here spent at least $300 to buy it. Given the price of the software and that we're all paying customers, it seems reasonable to expect a little bit of a heads up or an update on support for the next major version of the OS. My own thread asking about this very thing was deleted without explanation or notification. There is no need to be hostile towards your/other customers like this.
I've been a little snarky, but I fully concur.0 -
[quote="kavehv" wrote:
For the OP: I've found a workaround which is to plug in an external monitor before you launch C1P. This makes C1P display properly in 10.13 DB2. Moreover, loading RAWs seems to be snappier in 10.13 and C1P than I recall it being in 10.12.
For all the others who replied with unhelpful criticism: if the OP hadn't posted here, I wouldn't have seen it and been able to offer a workaround. Furthermore, C1P devs might not have been aware of such a workaround, and that might help cut their own debug time down. That is the whole point of these forums, collaboration and help. Unhelpful responses are just noise.
General note: I have no idea why this forum is so hostile to people asking about support for the next [announced] version macOS, especially since everyone here spent at least $300 to buy it. Given the price of the software and that we're all paying customers, it seems reasonable to expect a little bit of a heads up or an update on support for the next major version of the OS. My own thread asking about this very thing was deleted without explanation or notification. There is no need to be hostile towards your/other customers like this.
I tried workaround you have mentioned and here is summary:- Connect external monitor in second display mode (not mirroring), it might be even TV 😉 Make sure that the second display is master (top bar is placed there)
- Start C1
- External monitor can be disconnected
- Do not de-select picture (by clicking between pictures), it will stop working ...
Thanks a lot. The useful post, finally 😉0 -
OP,
If you had fully explained your reasons for need to use the Apple beta (as you eventually did explain) in your first post I am sure you would have received a very different response.
Bear in mind that every time Apple release a beta it seems that the entire Apple user world decides to pile in and use it as if it was a fully supported and released product and then complain when something does not work as they expect it to.
Foolish, certainly, but it happens every time. It can be very frustrating and of course it would mean that the Phase team could be overwhelmed with Support Cases telling them, mostly, what they already know.
Now anyone (and especially someone in the depths of software development as you appear to be) who really would like what they know to be a temporary work around solution to help their purpose for using the beta could and should explain that up front. It will help them to get useful support and explain to everyone else that they understand what they are doing and have a reason (valid to them) for doing what they are trying to do and for asking the question.
Everyone would save some time. Everyone would be happier. You would still get your answer if someone has a workaround.
I would highly recommend full disclosure in such a situation.
HTH.
Grant0 -
[quote="SFA" wrote:
Bear in mind that every time Apple release a beta it seems that the entire Apple user world decides to pile in and use it as if it was a fully supported and released product and then complain when something does not work as they expect it to.
Not true. Only clueless users do that. And it seems to me the same happens with Windows betas, BTW.0 -
[quote="John Doe" wrote:
[quote="SFA" wrote:
Bear in mind that every time Apple release a beta it seems that the entire Apple user world decides to pile in and use it as if it was a fully supported and released product and then complain when something does not work as they expect it to.
Not true. Only clueless users do that. And it seems to me the same happens with Windows betas, BTW.
Fair comment John, at least for more recent releases but there still seem to be a large number of Apple users who dive in by choice despite, presumably, knowing that historically there are frequently some problems.
And your comments about Windows are perhaps more true with the Win 10 approach taken by Microsoft these days than they were in times past. On the other hand there are many like me who are quite satisfied with a much older version of the OS and can still use it perfectly well even with new releases of applications like C1.
From what I understand such longevity is not expected to the same extent from MACs if one want to keep up with application developments.
For a dual platform developer the situation must be extra challenging trying to deal with both errant masters at the same time!
Grant0 -
Only @kavehv posted something useful. Hint, advice, workaround. Thank you.
Hope that his and my findings will not be buried by other posts which making a lot of noise instead.0 -
Managed to get it to work by using Airplay mirroring to an AppleTV. Kept it in mirrored mode, so didn't make the airplay monitor the main screen. Still worked. Hope this helps others. 0 -
Beta 3 seems to have fixed this issue. 0 -
Could somebody else could confirm this? 0 -
It works again as usual on Public Beta 2. 0 -
Please tell me the release details of beta 3. I see three versions when submitting a feedback.
I am currently on 17a291m which appears to be the latest.
I cannot see any newer versions to download and a minor issues at the moment I don't have access to a good internet connection with a decent download value.
Going to buy a monitor.
Thank you
Ian M0 -
[quote="Ian1111" wrote:
Please tell me the release details of beta 3. I see three versions when submitting a feedback.
I am currently on 17a291m which appears to be the latest.
I cannot see any newer versions to download and a minor issues at the moment I don't have access to a good internet connection with a decent download value.
Going to buy a monitor.
Thank you
Ian M
Public Beta 3 was released today I believe.
Open the App Store and update.0 -
Public Beta 2 is 17A306f
EDIT: It is of course the second public beta0 -
Hi,
I downloaded that version, but is was called beta 2.
Now using a 32" srgb monitor, so much easier than the little screen.
Ian
Edited - added extra text.
said it was beta 2 downloading but installed beta 3. Anyway it is working and so is time machine.0 -
The latest update for high sierra came out today and now capture one works on my mac book pro, which is what i suspected should be the case. I just glanced, but the viewer window is now working from all appearances. yay )) 0
投稿コメントは受け付けていません。
コメント
29件のコメント