Crash after crash

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Dustbak

I think that is the way we all see things, which is probably also why we respond here. BTW I sold my software company 12 years ago ;)

Dustbak

:)

You are right, I am have the dreaded tunnel vision syndrome and sometimes forget to look beyond my own narrow reference.

Yes, that was a smart move. There was quite a period in which I wished I was a lot smarter with the investments I made after that ;) Who was it that said, 'life is a casino, the house always wins'?

David Grover

I wrote a program in Pascal at School which read OCR time sheets for Motorcycle couriers.

Can I join the ex-programmer club?

;)

koukei

Quote from: Dustbak on February 10, 2010, 07:48:59 AM

BTW, there have been multiple threads lately of people that had issues with the 50 that were resolved with the latest firmware.


The day Phocus performs like Flexcolor did I will be extremely happy, the goal is to have it more stable and faster. I find it already renders a better file BTW.

Restart back issue was resolved with the new firmware but the corrupt files are still the same, I have worked our the problem is heat related. On a day below 20 degrease C I can shoot for about an hour before I start getting corrupt files, but today was 33 degrease C and I started getting corrupt files in ten minutes. both tethered and on card. 40% of the files where corrupt, the same problem on two different backs  ???

cunim

Koukei, any progress with your issue?  I noticed something interesting today that may be related.

Shooting tethered, normal temperatures.  I took shots using the camera shutter button as I haven't figured out how to make rapid acquisitions from the software interface.  After the buffer is full and the system slowed down I let it think for a while and hit it with a bunch more shots.  Again it slowed.  Did this a few times.  Now the shutter operates (mirror locked up), but it shows the image for an instant and then replaces it with black on all subsequent images.  Did the same thing twice so replicable.  Not corrupt - images are completely destroyed - but could be a variation on a theme.  Are you pushing the pipeline volume when you see corruption?