Dialogue sheet interaction
Hi. I'm a professional user of C1pro. We shoot with a Hasselblad and a couple of H25s (not at the same time!) on a G5. The entire setup has been tweaked and tuned to cope with the demands of (on average) 1500 images shot per day.
My question is this: When C1 pops up a \"Failed to capture image, A timeout error occurred. Please check the thaat the sync cable... If you are using mirror up...\" dialogue box, why, oh why is it necessary to insist on user interaction to dismiss the sheet. And WHY does it stop the camera from being able to shoot?
During a day we get hundreds of erroneous pop ups of this sheet (and another different one, the details of which escape me) and we have to have an operator by the machine AT ALL TIMES just to dismiss these sheets. When dismissed, everything continues as normal, so clearly this isn't any kind of crisis for either the camera or software, so why stop us from shooting until it's dismissed?
If anyone can explain, I'd be happy to hear, otherwise I very much hope to see this behavious gone in v3.7.
NOTHING should stop the camera from shooting under any circumstances. Tell us there might have been a problem, pop up a flag sure, but don't stop us shooting.
Any thoughts?
My question is this: When C1 pops up a \"Failed to capture image, A timeout error occurred. Please check the thaat the sync cable... If you are using mirror up...\" dialogue box, why, oh why is it necessary to insist on user interaction to dismiss the sheet. And WHY does it stop the camera from being able to shoot?
During a day we get hundreds of erroneous pop ups of this sheet (and another different one, the details of which escape me) and we have to have an operator by the machine AT ALL TIMES just to dismiss these sheets. When dismissed, everything continues as normal, so clearly this isn't any kind of crisis for either the camera or software, so why stop us from shooting until it's dismissed?
If anyone can explain, I'd be happy to hear, otherwise I very much hope to see this behavious gone in v3.7.
NOTHING should stop the camera from shooting under any circumstances. Tell us there might have been a problem, pop up a flag sure, but don't stop us shooting.
Any thoughts?
0
-
you get this message with hasselblad if the lens sync does not transmit information, and you have to desmiss this error so you do not end up shooting and think you have the image in the box when in reallity you do not.
You should check your lens sync cables and maybe lenses, it might be one lens causing this or simply the contact is getting oxidation.0 -
Your explanation is accurate, but misses the point. I am well aware of the need to warn about a failed capture but, as I explained in my post, it is unacceptable to require user interaction to restore the computer to a shooting condition. We have the screens visible at all times and myself, several other assistants, and the photographer are constantly checking the captures - not for technical reasons only. We all would be the first to notice if a capture was not occurring and would not continue shooting if there were a problem.
However, with the current dialogue sheet, someone has to physically move to the computer and dismiss it before we can continue. We shoot 1000-3000 images a day and the time wasted and frustration on having these enforced pauses adds up very quickly.
It is not a specific camera/back combination problem because we hire equipment the world over and this problem always occurs, generally around 50-100 times a day.
As I say, warn us by all means, but please don't stop us shooting. We may have missed a frame, but please don't make us miss the next ten!!0 -
We have thought about this and the fact is, if you do have a interaction and the failure is permanent (lens, cable etc) you could be shooting 300 captures just to discover that none of them was stored.
On P20 and P25 you have the error message on the back which you can simply accept with out walking over to the computer.0 -
you may try to use quickeys. is a nice automation application that lets you program macros or actions that can be triggered by events or hotkeys.
i have been looking at it, and the new version x3 has a new feature that checks for windows (this could be a dialog message) and then you can program what you want o do with it.
your macro can be constanty running each 10 seconds (or the amount of time you need) checking for the dialog to appear.
give it a try. download the demo and play with it. it has 30 day trial.0 -
This also happens to us, shooting with the H25 with the sliding adaptor on a 4x5. Can't we fix the problem so it doesn't happen in the first place? I don't even understand--what IS the problem exactly? Why does this dialog pop up and need to be dismissed and the shutter recocked and fired again? What's different about the second time around or third time around that finally makes it accept the shot? There must be a way to fix it.
If there is another earlier thread that deals with this issue, please direct me to it.
Thank you,
Matt Holmes0
Post is closed for comments.
Comments
5 comments