Looking for:

Capture one pro 12 bugs free.Capture One Pro 12 Crack

Click here to Download


I observed the same crashes in January when I first testes C1P. After long discussions with the C1P support they could not help me.

At that time my SynoIogy NAS was broken and to keep me working I had to fill my fusion drive right to the very edge – with instabilities occurring from time to time. When the NAS came back and I had relieved the Fusion drive of its overload everything seemed to work fine and stable again. So I attributed the crashes of C1P to this issue. And the crashes always happened within a minute or so of using C1P.

So not even living with them was and is an option as working with teh software simply is impossible under these conditions. Recently, I got an offer from PhaseOne to buy C1P with a strong reduction which I dared to do without being able to test the software on the mentioned iMac again. But I had tested the software on my slow MacBook Air – and everything seemed to work as intended. So, when the offer came in I simply decided to jump ship.

That was three weeks ago. With the license I gave C1P 12 a brief test run and when everything looked fine I started importing my Aperture data into C1P catalogs which took several days alone. Then the trouble started. It happens most likely when switching between two photos in the catalog. The little spinning wheel that indicates the the full size version is loading while the preview already is visible turns – and never stops turning.

The whole OS is freezing, so to speak as I cannot enter anything into the computer neither by mouse nor by keyboard. All I can do is to cut the current by long pressing the power button.

Of course I immediately contacted the C1P support – and as well the Apple support I talked to them a whole day from 9 am to 6 pm with first and second level supporters: my Mac seemed to be fine – and they were pretty sure that the problem was C1P related – which I think myself as all my trouble started with the installation of C1P, ended with deinstallation and started again with reinstalling C1P.

With the C1P support their latest message after three weeks was in my own words and after sending them several crash reports etc. They have no idea. They believe that some components of the macOS are just missing but they are not sure. By endless testing up to this morning I was convinced the crashes had to do with me exporting data from Aperture and importing data into C1P, and my focus was on the C1P Aperture importer as it seemed that C1P was running flawlessly with all my new shots which I imported directly as sessions into C1P.

Well, but not today anymore. A normal Nikon RAW file. C1P imported the files without issue but when I tried to change from one preset style to another my computer crashed. Well, I know and have never heard anything else that C1P is a very stable and reliable software and it better should be at the price. The C1P support does not seem to have any idea what else I could do. Or has anybody any idea what else I could try?

I have already spend the best part of three weeks on resolving this issue, I need a working alternative for my old software Aperture and I think C1P could be it – but, heck, I’m currently using C1 v My largest catalog is about 17K images, and several smaller ones.

Everything is stable at this point. Are the crashes occurring during Library Import into C1 or after the Library import is done and you are editting? I assume you are using referenced image storage for the catalog? Where are thee image files stored – Drobo? The crashes usually are occurring after the import and while I am editing – but it may be that the first crash happened while C1P was still generating previews.

After the frustrating crashes I reorganized my whole catalog and put every year of shooting in another catalog while still using Aperture. Each catalog now has less than 20, shots. With the current files I am just following C1P’s recommendation, i. I am working with sessions for each month and will later add all these monthly sessions to a catalog of My main catalog on Aperture had about , shots but it crashed on import but with another type of crash and without crashing even C1P.

There was a message about problems with some imports. That was the reason why I followed another route in parallel to secure at least copies of my RAWs. I also copied all my RAW files right from the package that holds the data in the Aperture library i. But these – as I understand it – untouched RAWs also crashed C1P after import, while editing plus, in one case, on import.

Yes, I am using referenced image files. There are Capture One users successfully using catalogs with greater than 20, images, and some greater than , images. In my opinion the size of your catalogs is not the root problem, however, a large catalog often makes it more difficult to manage or debug a problem. In older versions I observed that there is some kind of behaviour change at about 10, images. I’ve seen a setting in older Capture One preferences about some kind of internal threhold at 10, images; above I think that they cached images differently.

I suspect that your problem may lie with your storage media, or the connection to it. Ethernet connections e. I’ve been very successful with my catalog files on an external SSD drive connected via USB 3 and the image files somewhere else. Thank you for your input and thoughts again, Eric. Meanwhile Capture One has informed me that their software development team in Copenhagen will take over the case. Also, as I had cross-posted the case in the retouching forum as well and the thread has found more contributors there, I think it would be a good idea to focus the discussion over there – and close this thread here.

You wrote that you copied the Aperture Raw files as a second step to preserve them. Did you copy them from the aperture folder or did you use the Aperture export feature to export the original raw files.

If you did the former you may have copied some aperture instructions that are causing a problem. So I used Aperture to export my original raw files to a folder on my desktop and then used Capture One to import those files. The whole process was time consuming as I moved 30, images many very large taken with a Canon 5dsr. I am using Capture One on a later 5K mac running Capture One 12 is held on my internal SSD but all of my catalogs with the raw files are held on two external drives.

I use multiple catalogs. As far as I understand the structure of Aperture libraries the folder “Masters” inside the package of your library – right click on your library then “show package content” just holds a copy of your unaltered RAW files.

And it would have been extremely time consuming as I have about , shots in my libraries. Capture one needs the catalogs and logically the linked files on the fastest drive you can afford. What do you mean by ‘needs’? It has to be there, because otherwise the App will crash, including the whole OS, while changing from foto 3 to 4 in a row of consecutive shots? But what does this have to do with the fatal crashes I experience when changing from one image file to the next or while I am trying to correct highlights a bit.

And then, after restart, smc reste pram reset etc. Using a slow HDD should never be a reason for crashing a system. Slowing down, yes. But fatal crashes? And wouldn’t the support have told me? With 20, NEF images in a catalog you really aren’t doing anything unusual. With , in one catalog I would have said you are pushing the boundaries.

I am not sure, though. The reason is that I suffered from the “same” well, at least they looked the same All in all there seem to be massive problems with large databases in Capture One. This sounds as if the whole database part of C1P urgently needs an overhaul to modern standards.

And this is really discouraging as this would take rathe years than months. And it sounds as if some rathe old code is used. At the moment I am deeply frustrated by C1P as I have purchased the software a month ago but all summed up I could use for not more than 1 hour.

I have spent 2 weeks full time to sort out my data – and it has brought me just nowhere. I just have opened a second support case to get a reply what is going on with the first one To speak it out: this is ridiculous. The only reason why I am still sticking to C1P is that its results just look gorgeous and that something in my brain whispers: “Come on this is professional software – they will sort this out. But more and more I am thinking I am just a bloody fool – and I just should let go, as they simply do not seem to know how to build reliable file systems for their catalogs.

And actually: what kind of sorcery should the apply to some simple RAW data to let an otherwise extremely stable OS crash? It reminds me of an early alpha version of a. An they are telling me “it looks as if some components of macOS were just missing from your computer”. From a computer that has run without issues over months – until I installed C1P products. But with version I’ve had little problem with subsequent versions, and now on CO V A few months ago I expressed an opinion on one of the DPR forums possibly this one that I thought there might be a practical limit to catalog in the 50, image range, but I was corrected by a gentleman with a CO catalog over , that was working well.

If you decide to walk, all I can do is wish you well, and commiserate about your loss, both monetary and time. However, I think that if you are going to stay and make this a useful tool for yourself, you will have to do a little more methodical testing to determine what’s affecting this behaviour. In this case, if you want, I will try to help you.



Capture One Pro Retouching Forum: Digital Photography Review.12 tips and tricks you probably didn’t know | Capture One Blog

Very helpful and I learned so much more with this course and in a short period of time, than all the official Capture One You Tube videos put together! If they added features that i really care about maybe I will upgrade, I am not a digital artist. So yeah imma wait a bit on v20 as well.


Leave a Reply

Your email address will not be published. Required fields are marked *