Crash, crash, crash...
Thought I give CO a try, reading a lot of good things about it - compare it with LR4, which I like pretty much in general.
Downloaded V 7.01, installed, started the import of my photos. Crash after about 6000 photos - no chance to start it again, crash after every start.
Opened a support ticket - very fast response, great! Did like I was told, deleted one file, could start it then, and switched off Open GL support. Fine.
Continued the import of my photos - crashes again after about 24.000 photos. Again no further start possible, crashes at once. OK, de-install, re-install - no chance, crash.
Sorry guys... your product might be great, but if I have efforts like this to even make it run to see finally ONE SINGLE PHOTO in it - then you will not see me as a paying client. Sad, hope for you that you get these problems fixed very soon!
(WIN64 Ultimate, 16 GB RAM, i7-3930K, ATI Fire V4900)
Downloaded V 7.01, installed, started the import of my photos. Crash after about 6000 photos - no chance to start it again, crash after every start.
Opened a support ticket - very fast response, great! Did like I was told, deleted one file, could start it then, and switched off Open GL support. Fine.
Continued the import of my photos - crashes again after about 24.000 photos. Again no further start possible, crashes at once. OK, de-install, re-install - no chance, crash.
Sorry guys... your product might be great, but if I have efforts like this to even make it run to see finally ONE SINGLE PHOTO in it - then you will not see me as a paying client. Sad, hope for you that you get these problems fixed very soon!
(WIN64 Ultimate, 16 GB RAM, i7-3930K, ATI Fire V4900)
0
-
Give it a try in the mode they call sessions.
I don't like their "catalog" way of doing things, and I, like you, could not import a large number of photos into catalog.
If you stick with sessions, you can see your file folders, where you can choose the ones you want to open and process.0 -
If you just want to see how some photos look on a trial basis (at this point) why are you importing 24,000?
Surely any problems in that area, usually a one off exercise when changing to a new product, are of greater significance at some future point after you have decided whether or not you like the results obtainable and the features and functions offered?
If I knew I would eventually be importing a large number of images I too would want to assess how smoothly and efficiently that works and a final purchase decision might be influenced or delayed depending on the results of such a test. But my first objective would be to avoid spending time on that sort of task whilst I ran a few selected images through the software to assess the results of its core functionality. If that turned out to be unexciting then bothering about the import to a catalogue of 24,000, or even a few hundred, images would seem a little pointless. Thus your last paragraph, notably the words in CAPS, defeats my logic analysis. I am, however, interested to understand if you feel like sharing.
It's a personal interest related to my background in specifying and supporting customer service systems and testing those systems (and others - not image processing stuff - as an independent beta tester) during which one tries to work out what the initial response from user clients are likely to be so that one can be ready to respond accordingly especially if there are likely to be some challenging areas, outside of any realistic beta test environment random "what if"s, that could be seen as potential early negatives, perhaps even deal breakers.
Maybe this should be taken off line if you are willing?
Grant Perkins0 -
Thanks for the hint regarding "sessions" mode... if I get it to start somehow again at all, I can give it a try.
As I have no clou about CO, of course, coming from LR it was a logical decision to start with the big button "import" that was shown after the fresh install - in LR you can't do anything without importing the photos first, different to e.g. DPP (and CO as I learned now). Yes, I could have tried to import only a few photos first, but then again - choosing my photo folder and click "import" does not hurt, is not more effort and finally should of course also work without problems.
Having a database where all photo metadata is stored improves all search functionality dramatically. So long term - esp. for the price of the pro version - I would of course also like to use this option, otherwise CO would be an "add-on" to LR, instead of a complete switch to it. I want to focus on one single product to use (with PS "in the background" for additional punctual work if needed), so one could also say: What a pity and waste of time, to figure out that the RAW engine is really superior, but the rest of the tool sadly not usable?
However, will try one more new installation.
Thanks!
Klaus0 -
OK, de-installed, deleted the complete "Capture One" folder under AppData manually, re-installed - crash right after start, before I even have a chance to go to the menu to disable OpenGL support... feel like beta tester... 0 -
Not everyone want a all inclusive Software (RAW-Converter; somewhat-DAM-Solution).
I prefer to have a real DAM-Software (still looking about it, but IMatch or IDimager mostly a good job; and I wait for IMatch 5). I don't want the Lightroom DAM. From this software I can also start directly my RAW-Converter.
And I want a software you can convert RAW-Files with a very good quality and a fast workflow.
So every software producer can focus, what he can do best and I didn't have to use a compromise like Lightroom. 😉
Try to use something like "Total uninstall" to uninstall C1 completely. This help me with a problem of Media Pro some weeks ago.0 -
[quote="NN634898089934889647UL" wrote:
OK, de-installed, deleted the complete "Capture One" folder under AppData manually, re-installed - crash right after start, before I even have a chance to go to the menu to disable OpenGL support... feel like beta tester...
sounds like a graphic card driver issue to me , the new CO needs the latest card drivers to work0 -
Klaus,
When you manage to get things running you might want to use either catalogue or sessions mode - just don't waste the time at that stage filling the system! 😉 A few selected files will be enough to tell you whether you think it is worth going further.
Now, you had the system running but somewhere along the road something is not causing it to fail at a very early stage.
That suggests a 'bad' file somewhere. Could be a video card driver (or a setting for the driver) or is could be something lying around on the system as C1 attempts to open the previous session to put you back to where you were (not knowing that the reference will give you a problem.
There should be an process log file somewhere or at least a windows event log that might give some indication of where the program is having problems.
I would be tempted to make sure that any temporary work files are removed, catalogues that may still exist are removed (though of course that may be part of the problem) and any Registry entries are not set to invalid values. Hopefully the log file(s) will offer some clues about where to look.
Also, just in case you have not previously done so, re-boot the system, maybe more than once, and especially after a de-install.
I would guess that a support case with Phase One could be useful as they will know which common problem areas to check and where you might find them. Your problem might be something different of course but at least any known issues can be checked and assessed.
It's amazing what can crash a system. I am using quite an old HP Notebook with Win 7 32bit. Most things work fine most of the time, although it does sometimes seem to "hang" for extended periods with no reason obvious.
However I can almost guarantee to crash and freeze the entire system when using IE and Google Maps if I do anything much more than look at a selected map and maybe try to scroll it around the screen a little. Quite soon it will kill the machine to a black screen. It needs a power-off re-boot to get the thing responding again. I have no idea why it does it. I try to avoid any extended use of Google Maps on that machine. Sometimes I wish it would just crash in start up - it might be easier to diagnose!
Grant Perkins0 -
[quote="NN634898089934889647UL" wrote:
OK, de-installed, deleted the complete "Capture One" folder under AppData manually, re-installed - crash right after start, before I even have a chance to go to the menu to disable OpenGL support... feel like beta tester...
You should read what a PO rep posted above:
This article give links to graphic card driver updates
http://www.phaseone.com/en/search/artic ... nguageid=1
Also, if all fails there is scripts for disabling the use of OpenCL in Capture One.
I tried to update my card and ran into what you did. I ran the "do not use Opencl script that he talks about. That got me up and running just fine.0 -
Thanks to all, after de-installation, deleting all traces manually (incl. registry) and installing again it seems to work now - although, I do not touch the import button for the time being...
Seems like quite some work to get used to the totally different GUI compared to LR4... will see if this is worth it for me. I will perform some comparisons of RAW rendering, and then let's see.
Klaus0 -
I'm glad you got it running Klaus.
As for the GUI - when I first started to use C1 I arrived from another application that had very similar GUI design concepts so in some ways it was easy for me. But in other ways it was more difficult BECAUSE it was so similar!
I keep finding new ways of working and customising the tool tabs in my desktop to suit what I am trying to do. Maybe I should do more - you can make things very personal and specific to your needs.
I am looking forward to V7 - need to upgrade some hardware first though. V6 will keep me going for a few more weeks while I ecide what to do. (There are other projects in the decision making process just to complicate things.)
Grant Perkins0 -
Hi Klaus,
great, that it is running. 😊
Tipp: Use the Q(uick) Panel and custom it (btw. to move the symbols left: hold "alt"-Key and drag&drop (I always forget this)).
In the Quick-Panel you can put all this stuff inside, you need mostly. 95% I never change the tool-panels.
Regards.0 -
I haven't dared to try any import of photos yet... but regarding RAW processing I have to say that I am really impressed by what I see so far! I am quite experienced with LR4 already, but seeing what CO (or is C1 more common?) makes out of them is really *wow*. Playing around in LR I can nearly achieve the same results - but a) only with "playing around" where C1 makes it nearly perfect already with first try, and b) it is only "nearly" (so far)...
Only thing missing so far is an option to create a profile for my specific camera with the x-rite color checker... seems not possible? Also I cannot find how to at least upload my existing camera profiles - there is an "import" option under "ICC Profile", but when I select it I only get the message "No profiles were imported" - well thanks, that's exactly what I would like to do... 😉
But ok, I will figure out, and this is now "out of topic" for this thread!
Thanks again!
Klaus0 -
Last comment - as I have stayed away from the CO catalog, I find that sessions work v well for me. I then use Media Pro as my catalog for my photos. It talked very well with CO 6 before, and soon will with CO 7. In Media Pro I choose the newest photos that I want to process, then open them in Capture One in a session. I also find Media Pro is a easier to use catalog than Lightroom, though I keep my LR catalog up to date as well by simply sync'ing it to my Media Pro sidecar files. 0 -
I am still having major problems with version 7 using up all 12 GB of my memory and then becoming VERY slow. This program has become a memory hog and the developers ruined it because version 6 never did this. And yes I have reported it. 0 -
Also have seen crash problems. Crashes during processing and then won't reopen and run. Simply keeps crashing when restarted. Tried a different solution. Opened up version 6 and changed the output folder. Then reopened 7 successfully and changed the folder back to the one I wanted. It worked again.
There is a bug of some sort in what happens during processing. It loses its ability to find the same folder, for no known reason that I can see, on my system. Something goes wrong under the hood where the engine is. So it stops working. Even though it shows the right output folder still there, it is not finding it. Changing the output folder to another project, another place, using 6 then enables 7 to work again. It can find the output folder again.0
Post ist für Kommentare geschlossen.
Kommentare
15 Kommentare