10.7.2 update and Capture One tools
The 10.7.2 update for Lion seems to have broken something with variable cursor tools (things like local brush sizes and spot).
We are looking into the issue and will update here as soon as we know more.
We are looking into the issue and will update here as soon as we know more.
0
-
This is now fixed and will be implemented in the next release. 0 -
James, thank you for fixing the issue so quickly. When can we expect the next release? 0 -
Hi James,
Indeed this is where I was referring to.. hope you guys bring out the release very very very soon....
Regards
Jelle0 -
Awesome! 0 -
Having the release sooner rather than later would be a big help. At least it is reassuring that this is not just an idiosyncrasy of my system set up. It is good to hear that the issue is resolved. 0 -
+1 ^ I am hoping for this fast too, using the brush tool is almost impossible. Please hurry guys! 0 -
It's in test going through general 10.7.2 functionality check as we speak. We hope to have this released shortly.... 0 -
Thanks James! 0 -
It has been some time now for this update ☹️( I'm back to lightroom now... but do hope you guys will send out a fix very very soon.. it's getting painful
Txs, Jelle0 -
Agree: "it's getting painful"...
Working the full day, every day since that bug started with a broken tool/inefficient software is painfull.
I guess that might be plenty "good" reasons for the fixing to be delayed... the first one being "we, at PO, don't use CO at all !"
Let's beg: please, etc. 😭0 -
it is not possible to work with os 10.7.2 an d co 6.3.1 🤬 ,
i have so many trouble with tethering shoots and programcrashes. 👿
when exactly can we get the update that fix all the problems ?
regards marcus0 -
Come on guys.. please
I am sure you must have tested the Lion Beta extensively... 🤓
It is getting very very painful at the moment and yes, I am sure that there are many reasons why you are not publishing the update but work wise it is a big big pain.0 -
I'm sure P1 is working very hard on the 10.7.2 update. Any chance you could let us know what the status is?
Appreciate any input you can offer–thanks.0 -
+1 0 -
Pleeeeeeease fix sooooooon. I can't edit more than 30 images without getting a spinning beach ball for 1-2 minutes. It's so frustrating. 0 -
I notified them of some of the issues back on Sept 15 which they dismissed it as me running Beta software. I subsequently let them know with each update from Apple.
I love their software but I assume they are a smaller company. I just wish they were more receptive when community members told them there might be a bug and started working on this a month and a half ago. I am only writing this in the hopes they change their practices in the future.
And also for the record, I don't get freezes... I did a fresh install of 10.7.2 and my only issue now is I've lost all my brushes.0 -
Can anyone at Phase give an update on this? 0 -
Early October, I received a reply to a service case from the always kind and helpful James. The sentence used was shortly there will be an update. To my clients the word "shortly" does not mean in a month or two.
I am surprised that it takes Phaseone so long. I am even more surprised that this forum is not exploding with complaints about this? I herewith file a complaint to Phase One. My software is not working properly and that interferes me from working properly. Little more information about the progress would be very very good. Now I find myself every day checking for an update. I am not impressed by this and am glad I still shoot Hasselblad and am not in the hands of only one company. Yes, dear team at Phase One, I am not pleased at all by this issue and even more not pleased about the feedback getting from you. Have a good day.0 -
I must concur with the wording and lack thereof about an update. I figure that since there are quite a few users of Mac's and Phase products, this would be an all hands on deck. I am thankful that a update was issued to Lightroom so as I may fully use their software. I too have checked this site everyday for an update.
I am however patiently waiting for this. I see there is a tour coming around the states about Media One and Capture One and I do not see how this problem will not appear here or a ton of questions will be brought up about it.
O well
Tom Q0 -
I just bought Capture One and ran into this issue, so I would also like to see it resolved.
I wonder if they are busy working on Capture One 7. Either way, a fix for 6.x users would be much appreciated.0 -
Hi all,
Just to confirm my understanding, are we talking about the fact that after upgrading the Lion (10.7.2), when clicking on the cropping tool, the local adjustment tool, etc, the cursor remains to be the arrow?
I am having the same issue (making local adjustments is driving me insane), so will save me starting a new thread...
I am running 6.3.1, build 51979.
Thank you.0 -
Mac OS Developer betas of OS releases are not always the same as what's released to the public and there are often several developer betas for any given release. Phase, like any software company, runs developer builds to keep apprised of what may be coming, but they aren't necessarily going to panic (i.e. divert significant resources) if a developer beta creates a bug in their software - often such bugs are not there in a later beta or a public release.
10.7.2 public release was made October 12. In under 24 hours a warning was posted on our Capture One blog warning users not to update to 10.7.2 as it broke brushes and posts appeared here in the Phase One forum stating the same.
Phase One itself will be hesitant to be so blunt for PR reasons, but if you rely on your Mac to do significant work then you should either have a backup of your system prior to doing any OS updates or you should wait a day or two and then google to see if any of your critical programs have issue with the new OS. Either way would have saved a major pain for almost everyone on this thread (except for the gentlemen who only purchased C1 this week).
This is not a Phase One specific, or Mac specific, or recent thing: OS releases often break software. Use Time Machine (free), Super Duper (free), or any number of other programs to keep a backup of your system, making reverting to before an update (or any drive crash, data corruption, etc) a piece of cake.
You'll see an update to C1 VERY shortly at which point about three weeks will have passed since 10.7.2 was released. To me that is a very acceptably fast response to a problem created by Apple making changes to their OS.0 -
[quote="Doug Peterson - Capture Integration" wrote:
Mac OS Developer betas of OS releases are not always the same as what's released to the public and there are often several developer betas for any given release. Phase, like any software company, runs developer builds to keep apprised of what may be coming, but they aren't necessarily going to panic (i.e. divert significant resources) if a developer beta creates a bug in their software - often such bugs are not there in a later beta or a public release.
doug, do you have any proof for your opinion you post everywhere on the web when people criticize c1 for being slow on bugfix updates ? because it´s a matter of fact that most developers can keep up with os development or come up with a solution within a few days after a new release. even hasselblad has no problem maintaining phocus.
suggesting not to update the os because of c1 when os bug and security fixes are available is a stupid and maybe even dangerous advise when you don't have an offline mac only dedicated to run c1.
christian0 -
[quote="Horseoncowboy " wrote:
[quote="Doug Peterson - Capture Integration" wrote:
Mac OS Developer betas of OS releases are not always the same as what's released to the public and there are often several developer betas for any given release. Phase, like any software company, runs developer builds to keep apprised of what may be coming, but they aren't necessarily going to panic (i.e. divert significant resources) if a developer beta creates a bug in their software - often such bugs are not there in a later beta or a public release.
doug, do you have any proof for your opinion you post everywhere on the web when people criticize c1 for being slow on bugfix updates ? because it´s a matter of fact that most developers can keep up with os development or come up with a solution within a few days after a new release. even hasselblad has no problem maintaining phocus.
suggesting not to update the os because of c1 when os bug and security fixes are available is a stupid and maybe even dangerous advise when you don't have an offline mac only dedicated to run c1.
Do I have proof of what? That Apple's OSX public releases are often different than the first developer beta and that multiple developer betas are often issued for any given OSX public release? Sure the build number of the releases are different and the developer release notes specifically state it.
I'm not saying "Don't criticize them". I'm just saying it's something that happens with a lot of software and the only practical solution is not to install updates the moment they come out, or to keep a backup in place if you do.
For rental purposes we (Capture Integration) have to keep/maintain/test Capture One, LightRoom, Phocus, Aperture, and EOS Utility. ALL have had problems with an OS update at least once in the last three years I've been doing this - most have had several such issues. You're right that most of the time (though not always) Adobe and Apple address them within a few days and should get credit for that; they lead the pack speed-of-bug-fix-wise! EOS Utility definitely gets the award for slowest bug fixes as they often failed to fully support an OS update for months. Capture One falls somewhere in the middle of the pack as far as speed of update goes and right in the middle of the pack when it comes to the number of times an OS update has caused issues. You're very welcome to criticize them for that to encourage them to move towards the front of the pack speed-of-update wise.
Suggesting that it's dangerous not to install OS updates immediately upon release... honestly how often have you or a close colleague fallen victim to a security hole in OSX? I'm not saying that OSX is invulnerable or perfect, but the chance of your mac being hacked, zombie'd, or otherwise compromised because you're a single dot release behind is very small. Whereas updating your OS right away and/or without a backup in place causes issues to nearly everyone who works this way for a significant period of time.
Here is just a few off the top of my head that affected us:
- 10.6.8 broke printer drivers
- 10.6.7 caused issues with some high-end GPUs
- 10.6.8 caused issues with EOS Utility
- 10.5.2 broke canon tethering
- 10.6.7 broke Adobe+OpenType Fonts (problem if you do page design)
- 10.7 broke tethering in LightRoom
etc etc etc
By all means criticize Phase for taking three weeks to get this bug-fix update out. By all means let them know how it's effecting you to help them prioritize their time/resources. But for the love of Pete, don't think this only happens with Phase One. OSX updates breaking stuff is part of the "joys" of modern computing.
Pros: keep a backup of your production system in a known-good condition and don't update anything willy nilly. You can find that advice on video forums, newspaper forums, photo forums, 3D modeling forums, science forums across the internet.0 -
6.3.2 is now ready for download!
http://www.phaseone.com/en/Downloads/CaptureOne.aspx0 -
Doug,
1 - Of course we have back ups of our working system
2 - If you live in a corporate environment there is no choice about upgrading to a higher OSX
3 - a, itself, promoting as high tech, relatively well financed and equipped company as yourself should know that communication is key. The fact that companies are hesitant to communicate obvious challenges, will harvest the kind of forum entries you have seen. Also take into account that a lot of people do not actually write in a forum but are silent participants. Your entry of a update was not backed up by an email send out to your customers, at least I did not receive a reminder in my inbox.
My conclusion, you have all the technical reasons on your side, but we, the users of your products and services (i.e. we pay your salary) are left in the dark. I think I can speak for the majority of readers that we would be fine if you would communicate 5 weeks to wait. But not communicating at all? I always ask my staff to put themselves in the shoes of the customer. Self reflection. You guys are a relatively small team and I have seen errors in communication about repair prices of digital backs, software etc. at the end in favor of the client. But man, it is sometimes a hassle with you guys.
Have a good day.0 -
James, thanks for posting the update. We appreciate it!
😄0
Post is closed for comments.
Comments
27 comments