Fast shooting on H25 = psychedelic garbage

Comments

11 comments

  • aaanorton
    Well, I just installed C1 Pro 3.6 and I am still having this problem:

    http://aaanorton.home.mindspring.com/phase%20images2/shot01-00011.jpg

    If anything, it is now easier to reproduce this. Following is the SECOND frame in a capture session. So it only took 2 fames to completely fubar the back.

    http://aaanorton.home.mindspring.com/phase%20images2/shot01-00002.jpg

    I'm really disappointed, as I was hoping this would be fixed in 3.6. Any Phase feedback would be MUCH appreciated.

    These were done with an H25 and a Hasse 503.
    0
    Comment actions Permalink
  • Brian Eaves
    I think its a firewire transmission problem (corruption). I've experienced this when the firewire cable is next to a eletric cable, or using a poor quality cable w/ firewire repeater.

    There's my 2 cents


    Brian
    0
    Comment actions Permalink
  • aaanorton
    Thanks for the input. I've seen this capturing to a laptop and G5s, in the studio, on the beach, at a house and in our office. It's happened on battery and AC. I've used at least 4 different firewire cables. I wish it WERE this simple, but I can't see the same firewire problem occurring in all these situations.
    But thanks again, keep 'em coming!
    0
    Comment actions Permalink
  • NYCshooter
    Wow, a few friends of mine here have described this to me, but I figured it was just their setups. I guess not! 😄

    I've been shopping around for a deal on an H25, but now I'm glad I waited. I shoot pretty fast. Does this always happen? Do Leaf backs do this too? Hey P1 people, what's up? 😡
    0
    Comment actions Permalink
  • E Michelson
    Hi aaanorton-

    Please let me know what what camera and lens combination you are using. Also let me know what what firmware version is in your H 25. You can find the firmware version by control clicking a thumbail image, selecting Show info and dropping down the camera data tab.

    I have seen similar when a capture writes on top of a black calibration file that is being sent to the software from the previous capture. In essence this is capturing ahead of the back before it has finished the previous capture sequence. If that was the case just be sure to wait for the ready beep (also known as the clear signal) before you capture again.

    However we can discuss this further. Would you please create a support case at http://support.phaseone.com? I don't visit the forum as often as I would like and was alerted to this post by one of our dealers. Please include the information requested above as well as your computer system information.

    Feel free to comment on the support procedure in the forum as we work on your case but creating the case and working together that way is more efficient. Please don't forget to include your telephone number in your support notes in case we want to call you.

    thanks
    Eric Michelson
    0
    Comment actions Permalink
  • aaanorton
    Sorry so long for a reply, I've been on jobs and unable to respond.

    The firmware is listed as C1 PRO 3.5.2. Most recently, I've been using a Hasse 503 with a range of lenses from 80mm up. However, I have also seen this from 555s with multiple lenses. I rent the camera gear (and usually in duplicate), so I know this is not only on \"my\" eqpt.

    I will start a trouble ticket on this, but it's always been my impression that Phase was aware of this issue. I have even discussed it with tech support people. All the people I know using this gear are familiar with this.

    Your assessment sounds about right; this is what the files look like. Unfortunately simply \"waiting for the clear signal\" is not an option. I work with many many different pro photographers. Most shoot a couple hundred frames before catering starts setting up lunch. Before even the model shows up. They have a pace they are accustomed to and I can't tell them to slow down. Now, I realize that digital can't keep up with film's speed (yet), but it seems reasonable that C1 would just not capture in this case. As it is, the s/w is destroying files. This is terrible. At the very least, I should be able to stop the shooting and recover without having to relaunch the app, but I'd much prefer never seeing these again, even if it means missing a capture once and a while.

    Thanks for you input, Eric.
    0
    Comment actions Permalink
  • Mark2
    Hi, aaanorton,
    We have the same problem here. H20 back, on Arca Swiss camera, slow shooting. We shoot food so we don't tend to shoot speedily. I would describe the effect as reproducing part of the upper third of the capture at the bottom and then doing a weird difference blending mode a la Photoshop.
    0
    Comment actions Permalink
  • aaanorton
    [quote="NYCshooter" wrote:
    Does this always happen? Do Leaf backs do this too?


    Yes, this always happens with a Hasse 503 and almost always with a 555, when shooting very quickly. Leaf backs do not do this. Leaf just takes its time bringing the files in. After certain long shootings, with many frames captured, I've had to wait as long as 5 minutes while the Leaf software imports and displays the files. This can be a drag, but the files are rarely destroyed. Leaf has its own issues, but file corruption is not really one of them. Not like this anyway.
    0
    Comment actions Permalink
  • E Michelson
    Capture rate is dependent upon many factors but especially computer speed and installed RAM. But regardless of how fast your computer is the photographer still has to wait for the clear signal from the back before taking the next picture. If not the black calibration file gets screwed up into the capture.

    Digital capture with Phase One, and all the medium format solutions that I'm aware of, do not capture like a digital 35 style SLR with 5 fps etc. It does take some adjusting to get used to working with one capture every 2-3 seconds. If you are capturing to a slow G4 PB with small RAM it will be even slower with an H 25. P series does not require a tethered comptuer and it relies on the very fast internal processor. It will capture abou one frame every 2-3 seconds.

    If you obey the rules, wait for the beep, slow down the pace of the shoot which can be done with a confident, strong photographer in control of the model (no missives my way, please:-) you should not have the problems as seen in the images above nor will there be any five minute delay as described with the Leaf back.

    If the problem remains and you are certain that the photographer has waited for the clear signal then we can look for some fault with the back.
    0
    Comment actions Permalink
  • aaanorton
    Thanks for getting back, Eric.

    No doubt digital capture is slower and photogs need to retrain themselves as such. However, in certain circumstances mistakes will be made. People will push the button to quickly when they see great things happening in the prism. My point is that when that does happen, CO should simply not fire or cause the back to squeal a long obnoxious beep. Anything but let captures continue while at the same time destroying the files. And then to require a relaunch of the app is just miserable in such a situation.
    Well maybe this will be moot after our P arrives for the H1. I'll of course let you know...
    0
    Comment actions Permalink
  • E Michelson
    hey--

    Yes I agree. It would be nice if exposure was blocked when the back is not ready. It's a feature request that has been made \"several\" times but until such time as it is implemented we play the hand that is dealt us. (There is a provide feedback option in the C1 menu. Use it for important issues and feature requests. Make sure your comments are well documented. Provide our development team with all sorts of relevant facts about your setup.)

    I'm going to stop monitoring this thread for now. I think everyone has all the information they need. If you want to continue the thread send me a message.
    0
    Comment actions Permalink

Please sign in to leave a comment.