CO7 wont start on MacOS (SOLVED)
☹️ Hi,
I am running a two computer setup (Windows7 64bit for studio work, Macbook Pro Retina 10.8.3 for field work).
Until today I was running latest version of CO 6, which I have been quite happy with.
As it happens, I had to do some editing on both systems today, so this morning I started with the Windows machine, and CO6 wouldn't start. It complained about not being able to read the session folder, and when I then manually selected a session, it just shut down. I deleted preferences etc. and managed to avoid the session error - but CO just shut down before it even started up. This was pretty annoying - I was shooting on this system yesterday tethered with no problems. Being in a hurry and on client time, I decided the only way to get on with working and not waste any more time, I upgraded to CO7 even though I previously decided not to, as there's really nothing new for me there.
Anyways, problem solved, I got the job done. Later this day, I had to do more work, this time on the macbook pro - having upgraded my license codes to v7, I went ahead and upgraded the Mac as well so I could work on the pictures on that. Now, to the real problem - the damn software wont start.
Getting REALLY tired of this now - googling turns up nothing. I tried to completely remove CO from the mac (following the guide on Phase One website, removing library, application support and preference items etc.) and reinstall - nothing helps. After a successful install, I get the initial questions (do you want to allow feedback, are you a n00b or do you want sessions? ) Once answered, the software just hangs. Never starts up. Right clicking the icon says "Application not responding" and the only way to do anything, is to force quit the program - unfortunately, that wont deliver any files to my client.
Any suggestions on how to get this up and running? I guess for now, I will have to throw the Macbook in the waste bin and copy my raw's to the windows environment.... *sigh*
My system specs are:
Capture one 7.1.2 (downloaded today)
Mac Os 10.8.3
Macbook Pro Retina 15"
16MB Ram
512GB SSD
I hope that anyone can help - I have been the biggest fan of this wonderful product since version 3 - never had any problems, now this; forcing an unwanted upgrade and preventing me completing my client work ☹️
I am running a two computer setup (Windows7 64bit for studio work, Macbook Pro Retina 10.8.3 for field work).
Until today I was running latest version of CO 6, which I have been quite happy with.
As it happens, I had to do some editing on both systems today, so this morning I started with the Windows machine, and CO6 wouldn't start. It complained about not being able to read the session folder, and when I then manually selected a session, it just shut down. I deleted preferences etc. and managed to avoid the session error - but CO just shut down before it even started up. This was pretty annoying - I was shooting on this system yesterday tethered with no problems. Being in a hurry and on client time, I decided the only way to get on with working and not waste any more time, I upgraded to CO7 even though I previously decided not to, as there's really nothing new for me there.
Anyways, problem solved, I got the job done. Later this day, I had to do more work, this time on the macbook pro - having upgraded my license codes to v7, I went ahead and upgraded the Mac as well so I could work on the pictures on that. Now, to the real problem - the damn software wont start.
Getting REALLY tired of this now - googling turns up nothing. I tried to completely remove CO from the mac (following the guide on Phase One website, removing library, application support and preference items etc.) and reinstall - nothing helps. After a successful install, I get the initial questions (do you want to allow feedback, are you a n00b or do you want sessions? ) Once answered, the software just hangs. Never starts up. Right clicking the icon says "Application not responding" and the only way to do anything, is to force quit the program - unfortunately, that wont deliver any files to my client.
Any suggestions on how to get this up and running? I guess for now, I will have to throw the Macbook in the waste bin and copy my raw's to the windows environment.... *sigh*
My system specs are:
Capture one 7.1.2 (downloaded today)
Mac Os 10.8.3
Macbook Pro Retina 15"
16MB Ram
512GB SSD
I hope that anyone can help - I have been the biggest fan of this wonderful product since version 3 - never had any problems, now this; forcing an unwanted upgrade and preventing me completing my client work ☹️
0
-
Solved the problem - guess letting out some steam helps.
Sorry to say guys, this is just poor coding on your part. The issue was my firewall. I can certainly understand why you want your software to be registered and all that - it's your bread on the table.
But, if a Firewall blocks the application it should never hang in the system, with no error message whatsoever and no indication on where to go.
Even the logs were empty and useless, except for this little tidbit:
"(ERROR) Could not create external processor" which yielded one result on google.... some guy had problems on 4.5.2. and his firewall.
So I checked my firewall, and yes - outgoing requests from C1 and ImgCoreProcess were being blocked.... after adding those to my whitelist, I was able to start the program.
(though, I was not able to register the software - unless I totally disabled my firewall! That should not be necessary!).
You guys really need to log some more and provide feedback to the enduser- this has cost me far too many hours for such a small and needless issue.... really. ☹️0 -
Can you share with us what firewall you were using? It is the first time I see this on Mac, I have seen this issue more often on windows.
Capture One only needs TCP port 80 (same as HTTP browsing) to activate and check activation. In addition it uses port 2525 for crash reporter (but only if it crashes). If your firewall prevents these kind of connections, Capture One will run without problems.
The issue might be that your firewall prevents Capture One to connect to a local port or the local loop address (the computer itself through the network stack). The is not bad programming on Phase One's side, but on the firewall's side, IMHO, but that's open for debate. 😉
Thanks for sharing and I am happy you're back on track again.0 -
Found the link you were referring to:
viewtopic.php?p=25998#p25998
Indeed the local loop address (IP 127.0.0.1) issue.0 -
Hi Paul,
The firewall is blocking all outbound requests, except those I manually whitelist. Firewall is TCPBlock btw.
The "bad programming" part was not the fact that it interfered with the firewall (or, as it may be, the other way around) - that's ok, that is the purpose of the firewall 😉
The "bad programming" was in regards to the fact that there was no error or log messages from C1 - it simply stopped responding with no indication of what was wrong. A simple timeout and a popup saying "Can't contact C1 registration server" and a "quit" button to exit gracefully, should take roughly 4 minutes to implement and is really standard coding practice 😉0 -
The error handling in CO 7 could be more smooth, indeed. 😁 0 -
If you've ever worked with enterprise grade software (think SAP etc.), you may find that CO7 isn't that bad at all. It could be (quite a bit) better though, i agree. 0 -
I develop enterprise grade software for a living - and I am still unhappy with CO7 😉 0 -
Well, i don't actually develop it, but i'm architecting solutions in the ERP area. I figure you're developing better error handling and messages then 😉
I know i have spent many hour trying to figure out what the dang error could be if we just received a non-descriptive error code/text, or just nothing at all.
That was what i was pertaining to in regards to CO7.
I concur with the others here that error handling and notification should be much better, but it so seems software vendors focus on the functionality first. And they don't seem to consider good user information functionality.0 -
[quote="HCS" wrote:
Well, i don't actually develop it, but i'm architecting solutions in the ERP area. I figure you're developing better error handling and messages then 😉
I know i have spent many hour trying to figure out what the dang error could be if we just received a non-descriptive error code/text, or just nothing at all.
That was what i was pertaining to in regards to CO7.
I concur with the others here that error handling and notification should be much better, but it so seems software vendors focus on the functionality first. And they don't seem to consider good user information functionality.
I would guess that developers cannot always guess what things might go wrong well enough to provide specific errors rather than generic or, for some type of error, any message at all. Even predicting that an error might occur could be a challenge.
Moreover I suspect that, in most cases, only people who make a living from dealing with software development would care about an error message. Others would just be upset that the system they were using "crashed" (for whatever reason) and error messages would be of little interest to them except as a further example of how useless the software must be if it can report an error in detail rather than prevent it happening .... 😉
Grant Perkins0
Post is closed for comments.
Comments
9 comments