Adam52 wrote:LOL Keith !! .I don`t use sessions, just use it as a raw converter but that you have to do the Kill-with-taskmanager thing at all shows that Phase one still haven`t sorted this bug ridden mess out even in V8 ........ BTW I`m using an approved NVidia graphics card .
I like the better NR and CA correction of V7 but I use this software in my job and I`d give those up for the stability and speed of V5 without open CL .. I didn`t have the issue until 7.22 but as soon as I see a corrupt thumbnail In the navigator, it`s lockup time .
Your experience with V8 leads me to think that Phase one don`t even care about any kind of beta testing ...
I wish that they`d make a fully stable version of the software and then let us stick with that and just pay for camera support separate to software upgrades , that way I could have added new cams to V5 or upgraded the whole package depending on needs .
Adam,
A couple of observations, the first being that I think Keith has been very unlucky for reasons unknown. In my case I have been able to process loads of files in V8 without problems. Occasionally responsiveness slows for a few seconds but I've been using an external USB 3 drive mainly and I suspect that the 'slow, almost a freeze' may be something to do with Windows and external drives. The only lock up I have seen was during such a situation and was not actually a complete lock up - almost like Windows had switched into some sort of special mode after repeated use of certain keys and refused to come out of it. I got bored of waiting and trying to work out what was happening so killed the process with no loss of work done and no subsequent problems to date. Not have I been able to reproduce the problem although it might have had something to do with repeated fast scrolling attempts going backwards and forwards.
Why I get a different experience to Keith I have no idea.
Secondly if you are opening an image directly in C1 you are likely using a session concept by default. Just not one you have set up for a 'project'.
In which cases there will be a cosession file. That links all the components files together and seems to be used for a few other things as well.
"but as soon as I see a corrupt thumbnail In the navigator, it`s lockup time ."
I saw something that sounds like this just once back in about 7.1 ish time. About 2000 images in a session and now and again, especially scrolling left and right in the browser, C1 would lock and I was forced to crash out. I could then process the next 10 or so images (working sequentially in file name order) before the next problem arose. All the thumbnails looked fine but By pure chance I spotted a corrupt thumbnail displayed (in image name order remember) a long way away imn the browser from where the problem seemed to exist (in human terms). Deleting the dodgy edit file for the image with a bad thumbnail fixed the whole problem. I then created a new edit file for the image and all was well. I have no idea how the original edit file came to be a problem ... but to find a corrupt file once in a while in any sort of application is not unheard of.
If the session concept as such is not important to you try creating a completely new "session" and making it the default session file. With luck you may find the problem disappears.
Grant