Luminous Landscape Forum
Equipment & Techniques => Medium Format / Film / Digital Backs – and Large Sensor Photography => Topic started by: david.westphal on July 20, 2009, 10:51:44 am
-
I have a p65+ H mount for about a month now. I've been getting this error while shooting. I've shot with both the H2 and alpa 12max. This error has come up on both camera systems with 2 different mbp with multiple firewire cables. Anyone else seen this error with their p65+?
(http://www.westphalphotography.com/p65error.png)
-
I would suggest you contact your Phase dealer. You shouldn't be getting this error. eleanor
I have a p65+ H mount for about a month now. I've been getting this error while shooting. I've shot with both the H2 and alpa 12max. This error has come up on both camera systems with 2 different mbp with multiple firewire cables. Anyone else seen this error with their p65+?
(http://www.westphalphotography.com/p65error.png)
-
I've already got a case going and talking with phase about this issue. I am trying to determine if the issue is systemic or if it's a specific defect with my back. I've also used a second p65+ that had the same problem. Phase is saying that it is a heat issue with the sensor. If this is the case, then there is an engineering issue with the new back. Basically, zero latency would be unusable as phase has not engineered effective cooling system for the chip in that latency mode.
-
I've seen that once or twice in non-back formatted cards. but its gone away on proper formatting.
you probably are, but be sure to freshly format your cards in the actual P65+ back once or twice to be safe, before EVERY use.
also - check its not card specific - i.e. keep track which card gives it, and whether it occurs across a range of CF cards/brands
-
The errors are from shooting tethered.
-
The errors are from shooting tethered.
ok well scratch that...
I've been working outdoors in summer with my P65+ back for hours on end, continuously on, and the backs got pretty hot - but I've not suffered from it like you appear to be.
I'm not tethered, so ?
-
I have a p65+ H mount for about a month now. I've been getting this error while shooting. I've shot with both the H2 and alpa 12max. This error has come up on both camera systems with 2 different mbp with multiple firewire cables. Anyone else seen this error with their p65+?
(http://www.westphalphotography.com/p65error.png)
Interesting, I can't give you other suggestion except consulting with your dealer, I use P backs for many years and so far lucky not having such issue, I hope when I get my P65+ next month it will be free of issue. Anyway, I am interesting to have your comment about the overall performance of H lenses and Alpa lenses? I also use H3D39, and Phase back on Contax, and I got a few Alpa with C adapter for Phase back, I am thinking about moving the P back from Contax to H mount, something I hate to do, but Contax as good as it is, it gets older everyday and no official support.
Regards,K
-
deleted by author.
-
Hello,
I have had that occur with P65+ tethered with Macbook Pro when the battery in the Mac gets too low.
Phase had some convoluted workaround external battery booster thingy--never tried it--but now keep Laptop spare batteries fully charged and no problemos!
Good luck,
DesW
-
Hello,
I have had that occur with P65+ tethered with Macbook Pro when the battery in the Mac gets too low.
Phase had some convoluted workaround external battery booster thingy--never tried it--but now keep Laptop spare batteries fully charged and no problemos!
Good luck,
DesW
Never had it with my P65. Certianly no heat problem. (Shooting in 130 degrees for quite some time) However I'm not using a mac.
-
It looks like it is an issue shooting tethered with zero latency on the back. If anyone encounters this error, please post. That would be with a P5+ only.
David
-
I had something like this a few times with H3DII. I think it was a firewire synchronization error. Restarting software and reconnecting the camera helped in my case. I blame it on the computer software.
Have you tried it with a different laptop?
-
Didn't know you can mount a P65+ on a H3DII.
David,
My guess is insufficient power coming from the MBP.
Hope Phaseone will get this resolved for you quickly.
Good luck.
-
Didn't know you can mount a P65+ on a H3DII.
David,
My guess is insufficient power coming from the MBP.
Hope Phaseone will get this resolved for you quickly.
Good luck.
Not a power issue. Engineering defect. Told not to use zero latency unless I had to use it. Phase has told me that it is a heat related issue with zero latency. It's a crock of shit as far as I am concerned. So far no word that they are going to fix this. Instead offering a work around which is not to use zero latency. Not an acceptable response as far as I am concerned.
I believe that in my previous post, I indicated to post as it relates to phase backs, not imacon/hasselblad backs.
-
Not a power issue. Engineering defect. Told not to use zero latency unless I had to use it. Phase has told me that it is a heat related issue with zero latency. It's a crock of shit as far as I am concerned. So far no word that they are going to fix this. Instead offering a work around which is not to use zero latency. Not an acceptable response as far as I am concerned.
I believe that in my previous post, I indicated to post as it relates to phase backs, not imacon/hasselblad backs.
Once again looks more like a very special problem. I'm using Zero La. All the time with my large format camera. No problems so far. I have never seen it. So perhaps it really is a mac problem.
-
Once again looks more like a very special problem. I'm using Zero La. All the time with my large format camera. No problems so far. I have never seen it. So perhaps it really is a mac problem.
I don't see how it is a mac problem but I will look further into it. I believe this error comes even when using the back on battery power. I don't see, other than this, how it could be mac related? If it's a transmission issue, then I believe that it would occur with either normal latency or zero latency.
-
I don't see how it is a mac problem but I will look further into it. I believe this error comes even when using the back on battery power. I don't see, other than this, how it could be mac related? If it's a transmission issue, then I believe that it would occur with either normal latency or zero latency.
What else could it be ? It could be a specific back problem or specific mac to back problem. I'm just saying that it probably is not a zero lat. problem. Or I am just lucky and it works just fine with my back.
-
Not a Mac Problem: http://luminous-landscape.com/forum/index....showtopic=34352 (http://luminous-landscape.com/forum/index.php?showtopic=34352)
Could be voltage, Firewire cable, CF card, sync error or something else.