7.0.2 and Mac 10.6.8
so I downloaded v7 then saw all of the issues pop up.
can anyone report on how it works with 10.6.8?
i dont plan on updating my Mac Pro past this OS.
can anyone report on how it works with 10.6.8?
i dont plan on updating my Mac Pro past this OS.
0
-
I'm running 7.0.2 on my MacPro OSX 10.6.8 and it runs just like the beta version.
What issues are you seeing?0 -
actually i meant i downloaded 7.0 when it was released then didn't bother with it after reading about people's issues with it.
then read that v7 is not recommended for 10.6.8 according to Capture Integration's website so I was wondering if A. most issues were solved in 7.0.2 and B. if it did work fine on Snow Leopard.0 -
OK.
I'm having some issues with the Local Adjustment Auto Mask (keeps saying I don't have the right file type. Tried *.raf, *.tiff, and *.jpg and always the same). Also can't create a LCC file (same issue). Also, the Spot/Dust Removal Tool doesn't work.
So, I don't know if those problems are all caused by my running 10.6.8 or if they are bugs (or if I'm doing something wrong).
Other than that, it seemed to work fine.0 -
Edward: 10.6.8 runs CO just as well as 10.8 and 10.7 (if your computer has sufficient power)
6x6_Shooter: LCC and Automask are not supported for .raf / x-trans at this time.
Spot removal is, however. Be sure to select the right mode (Spot/Dust) for the job, when you use the tool.0 -
Thanks Christian,
I will update and give it a try.0 -
I am running 7.0.2 with Mac OSX 10.6.8
I have not experienced any problems at all.0 -
Christian:
Thanks for the information.
I tried the Auto Mask function on TIFF and JPG files & it doesn't work either. So I guess this function only works on RAW files that are currently supported ? Hopefully RAF file functionality will be available eventually?
As to the Spot Removal, I had misinterpreted this statement from the online help article:
"9. Remove a spot by pressing the - (minus) button."
I thought I had to hit the "-" button to delete the selected spot. What the above statement really means is hit the "-" button to cancel spot removal for that selected spot. The Help writeup is a little confusing.0 -
[quote="Christian Gr" wrote:
Edward: 10.6.8 runs CO just as well as 10.8 and 10.7 (if your computer has sufficient power)
can I tether to Canon cameras (5D mk II & 1Dx) ok or do I need any workarounds?
and can I use v6 and v7 on the same machine? I want to use v6 for upcoming tethered tech jobs but want to start working with v7 for some processing/retouching jobs.0 -
Okay... I'm running 10.6.8 and here's a light synopsis of my experiences with versions 7.0, 7.01 & 7.02 but first my hardware.
MacPro5,1
3.2 GHz Quad Core, 24GB RAM
ATI Radeon HD 5770
PCIe SSD
Version 7.0, while crashing occasionally, has been the most stable so far. I say 'so far' as I've JUST installed 7.0.2 so hoping that things get better with tweaking.
So... 7.0.1 was a bust (a lot of crashes) even though I disabled OpenCL on my graphics card that is listed as supported.
Reinstalled 7 which allows me to handle basic processing with the occasional crash.
After installing 7.02 the previously opened session opened fast so I was optimistic. However, after closing that session, choosing a different session (created with 7.0) consistently crashes the program. I can still open that same session in 7.0.
ck0 -
[quote="Chris Kane" wrote:
...
After installing 7.02 the previously opened session opened fast so I was optimistic. However, after closing that session, choosing a different session (created with 7.0) consistently crashes the program. I can still open that same session in 7.0.
You can try to do a verify (File menu) of the session from 7.0.2.0 -
I'm running 10.6.8 on a Mac Pro 1,1; 2 x 2.66 GHz Dual-Core Intel Xeon, 8 GB Ram, ATI 5770. All runs smooth for me. I probably don't push the software near as hard as some users but I'm working on 5D Mark 3 files with out issue. 7.0 had some slowdowns after working on images for a while. A restart of C1 seemed to fix it. 7.0.1 and 7.0.2 seem to be working great so far.....nock on wood. 😉
OpenCl is enabled.0 -
I'm on a MacBook Pro, 2.53 GHz IntelCore 22 Duo, 8 GB Ram, Nvidia GeFORCE 9400M, OS 10.6.8 (after having tried Mountain Lion and gone back to 10.6.😎. Canon 5D MII and 1DX. COP 7.0.1 It's so slow bring in files when tethered or from a card reader. Takes for ever to generate previews and very often the previews come up corrupted. I have to switch back and forth between thumbnails to final get a preview to come up cleanly.
I reach a plateau where everything works smoothly. Then I make the mistake of buying a new piece of hardware and everything goes to hell in a hand basket.
Anybody else having issues with previews? Is it different with 7.0.2?
Grrrrrrrr!.
A.T.0 -
Im working with Snow Leopard 10.6.8 and Capture One 6.4.3 on a MacBook Pro and everthing is fine. But Im really interested in the new features of CO7. Is it finally save to upgrade to CO 7.0.2 for daily use or should I wait until 7.1 is out? Who uses it already in their commercial workflow? Thanks! 0 -
I had been using 7.0.2 with Mac 10.6.8 with no trouble but it was very slow. I upgraded the OS to 10.8.2 and C7 runs quite a lot faster.
Bill0 -
i've been using C1P since early v3 professionally - now testing v7.0.2 for a week on a 10.6.8 MP, and I do not recommend using it on commercial jobs yet. 0 -
For what it is worth, I've been using C! 7.0.2 with OSX 10.6.8 for about a month now. I'm not a pro but I use it a lot and haven't seen any problems.
Jeff0 -
OK life with Mac OSX 10.6.8 and CP7.0.2 is fine but..... the Catalogs crashes frequently, it is fine in Sessions mode.
Support team says going to OSX10.8.3 will improve things. Hmmm. I think I will wait and see what Apple deliver in the way of new MacPro hardware before I commit to upgrading my Macbook Air 13" that runs so sweetly on Snow Leopard.0 -
It drives me crazy. A lot of problems with the sorting (date, name, rating ...) in sessions. All the files are mixed!
Even on import they get mixed (no difference if files are from 5DMK3 or IQ160). It's not nearly not possible to work with.
Costs me this weekend again. 😭0
Post ist für Kommentare geschlossen.
Kommentare
18 Kommentare