5D MkII tethered capture stall/hang
My 5D MkII will tether just fine, but periodically Capture One will stall during the import process. What this looks like, is an image that doesn't render a complete preview. When it happens, I can continue shooting until the camera buffer is full. If I wait several minutes, capture will resume as though nothing has happened. The problem is intermittent. By this I mean, I am unable to isolate the specific situation that causes it. I can shoot hundreds of test frames without trouble. It's as though the irregular rhythm of a real shoot changes the way the drivers deal with the file transfers.
I first posted about this problem in February.
viewtopic.php?f=21&t=8353
Since that time, I've been through 3 different Mac Pros, and many OS/boot configurations, trying to track down the source of my trouble. I'm now running a brand new 8 core 2.66 with 12gigs of ram, on OS 10.6.4. C1 Pro 5.1.2 ran a few days in test mode without trouble. Not long after I put it to work on real shoots, the problem resurfaced. I resurrected my support case, and was told that 5.0.2 was the last version to use the older Canon drivers that were stable. Downgrading to 5.0.2 did not solve the problem. I should have checked my notes, because that's where the problem started. In the release notes, there is mention of this activity with "certain configurations," but I can't get an answer as to what configurations these might be. The last stable build for tethered capture was, 4.8.7, running on OS 10.5.6. I would gladly keep using it, but it crashes if I leave it processing more than 300 images. I've spent the last 5 months running two different versions of C1Pro on separate boot drives, to be able to shoot and process.
Has anyone else had a similar issue, and been able to solve it?
I first posted about this problem in February.
viewtopic.php?f=21&t=8353
Since that time, I've been through 3 different Mac Pros, and many OS/boot configurations, trying to track down the source of my trouble. I'm now running a brand new 8 core 2.66 with 12gigs of ram, on OS 10.6.4. C1 Pro 5.1.2 ran a few days in test mode without trouble. Not long after I put it to work on real shoots, the problem resurfaced. I resurrected my support case, and was told that 5.0.2 was the last version to use the older Canon drivers that were stable. Downgrading to 5.0.2 did not solve the problem. I should have checked my notes, because that's where the problem started. In the release notes, there is mention of this activity with "certain configurations," but I can't get an answer as to what configurations these might be. The last stable build for tethered capture was, 4.8.7, running on OS 10.5.6. I would gladly keep using it, but it crashes if I leave it processing more than 300 images. I've spent the last 5 months running two different versions of C1Pro on separate boot drives, to be able to shoot and process.
Has anyone else had a similar issue, and been able to solve it?
0
-
Jamie111,
i won't bring any help or give advice on CO1/camera configuration for your, my, AND all of us problem with a 5D MkII tethered to a Mac with Capture One v. 5+.
The post i started on March this year,
(),
did not bring me any clear solution to the problem, same as yours, we had when shooting a bit too fast with our 5D MkII : beach ball for 2 to 3 mn, then, if luck at home, captures were imported.
Otherwise the application, even the Mac sometimes, will crash...
The only solution we found was to shoot "slowly", not faster than 1 image per second, even less.
OK for still life but irritating when we have photos sessions with models.
My conclusion: Phase One still does know how to acquire and buffer data from a 5D MkII.
Also it looks like Canon does not help at all on the other side...0 -
I've had shoots where shooting slowly didn't solve it either. I think that's the most frustrating part, it's totally intermittent. I can shoot hardware tests, where I stand on the button for 500 frames, without a problem. The next day I'm shooting for real, and it locks up at random intervals.
What I really need are straight answers. What is the specific hardware configuration that's problematic? Is there a CO 5.XX version that's stable for the 5D MkII? How many Canon users are dealing with this issue?
When I first ran into this problem, CO 5.0.2, they told me that there had been no changes in the camera modules since 4.8.3. In fact, my support on this has been terrible. At first, they had no idea what the problem was. Now they're pointing the finger at Canon's SDK, and saying that 5.0.2 is stable. But wait, 5.0.2 is where I first encountered this problem?
I'll probably go back to 4.XX for capture, until they get this sorted out. It's just a pain that batch processing in that version is so unreliable.0 -
Jamie -
Basically it comes down to Canon using USB for tethering. It just cannot keep up like firewire. If you shoot about a frame a second you could probably shoot all day w/o a problem. But faster than that you will crash the software. Trust me I've battled it on big shoots for years as a tech. Every single Canon USB camera and all C1P version will suffer from this. Strangely enough recently we've used a P65 (3x larger raw file than canon) and never had a crash even shooting fast to a laptop. I have gripes w/ C1P being slow to move and edit around in a session with canon files (on an i7 macbook pro) and that i do not understand (and it is very frustrating) but for tethering its all on Canon and their decision to use USB to move closer to the PC/windows world.0 -
I'm inclined to agree that it could be USB, but like Jamie said, I'll have photographers literally take 500 frames non-stop with no problems on catalog shoots, and then have it crash 3 frames into the next shot. I also have this issue when once it crashes, it will crash 2-3 more times before stablizing and will run perfectly for a few hours before crashing again. Has anyone tried the old trick we used to shoot 1Ds Mark III in 3.7.9? Maybe if you shoot through EOS utility in the background and ONLY have C1 generate the previews it would be more stable? I know that was an annoying workflow, but when you lose the entire buffer everytime C1 crashes, photographers tend to get a bit upset....
Jamie, have you tried 4.8.7 with snow leopard? I need to have a stable build of this software (more and more photographers want to use the 5D II) but all my laptops are i7 and I REALLY don't want to start having to dual boot my mac pros....Any help would be appreciated!
-taylor0 -
While I too question using USB, previous versions of C1Pro dealt with it pretty well. I doubt that I shoot faster than 1fps most days, given the constraints of my studio. I have experienced this issue, shooting at much lower rates.
The fact of the matter is, this problem didn't show up until version 5.xx. When I contacted support about this issue, they claimed that nothing had changed as far as tethered shooting was concerned. I'm frustrated, having spend months trying to create a configuration that's reliable, only to learn that we're now blaming the Canon SDK. I could even accept that, if it were actually documented in the release notes, or the known issues posts.
I don't want to degenerate into complaining about customer service, and how I don't feel like I'm being supported. I would like some straight answers from Phase One, as to what's actually going on here. If in fact there is an across the board problem with Canon drivers in Snow Leopard, put that in the release notes or post it in the known issues. If on the other hand there are problems with specific system configurations, give me some insight on those configurations. If my best option is to shoot to C1 ver4.8.3, then just tell me. Will I be able to run that in Snow Leopard? Will I need to continue running a dual boot system to overcome the processing issues of that version? Will the release notes for future versions advise me of new Canon drivers, or the resolution of this problem?
Finally, I'd like to hear from other users. There has been very little traffic about this on the forum. I assume there are more than a few people shooting the MkII tethered. What are your experiences? Is the consensus that shooting 1 frame per second solves the problem with this camera? Does it occur with all Canon USB cameras? Are there users that are not experiencing this problem at all?0 -
This may be of help;
viewtopic.php?f=21&t=8745&p=38895#p38895
And if anyone still has questions we would be happy to clarify them in a support case.0 -
That link does not work 0 -
All fixed. 0 -
I'm going to offer a solution that I discovered with CP5 Pro AND Lightroom 3 (tethered), We shot a 1 day shoot and capture one was stalling randomly. We sometimes had to just turn the camera off. (tho we realized sometimes the images were TRYING to come in, it was just taking minutes! until the stall stopped and we could resume shooting.) We were shooting up to 2 frames a second if not more. Not a good situation!
IMPORTANT: WE were shooting with a 16' usb cable...on a new MacBook Pro. 5dMark2
We were about to embark on a 4 day shoot. We needed to solve the issue.
In studio, I tested both Capture One and Lightroom 3 just to see if it was the software (and we use LR3 extensively). I used the same selection of 16' USB cables, same MacbookPro, and same camera. Symptoms were similar to the previous shoot. Not good.
I brought another new MacBook Pro into the equation to see if it was the hardware, and a second 5dmark2 body (same cables). Same problem.
I then changed one thing. I went to a 10' USB Cable... which we don't use...too short for shoots.
Results: ROCK SOLID CAPTURE! On both Capture One and Lightroom 3. I could not make it Fail! Unplug, replug, camera on, camera off. Fire as fast as shutter could release...SOLID.
Because we use LR3 ALOT in the studio we decided to go with LR3 on the 4 Day Shoot. But 10' cables were going to be too short. We contacted http://www.bearimages.com in Palo Alto ,Ca and asked how we could extend our cables safely and reliably. They recommended using a usb extender/repeater and to not add anything longer than 10' to it. The repeater is about 12' long ( I don't have it in front of me right now, could be longer). I think any reliable (but not too cheap) extender/repeater may give the same results.)
We shot 4 solid days in hot New York weather indoor and out and not once did LR3 Fail to capture! We were pushing the shutter on camera until the buffer filled onboard the 5dM2 repeatedly, and those were the only slow downs we encountered.
I'm sure that Capture One would have worked the same.
I think what is happening here is that the USB hardware on board the computers keeps changing in terms of power output specs, and the computers are also now managing how much power is directed to the various ports at any given time (read this online).
This creates havoc anytime you upgrade a to a new machine, or really push the USB cable length. Your old set-up all of a sudden doesn't work anymore.
Sorry for the long post but I hope it helps other with the same issue.
Norbert0 -
Norbert,
There are two important things missing from your report;
The Mac OS that you were testing on and the version of Capture One PRO.
As has been previously mentioned on other threads, the reported "Stall/Hang" is nonexistent on 10.5.8 and Capture One 5.0.2.
In regard to your cable adjustment findings I haven't done similar testing personally so I cannot say one way or the other if these findings are true. What we do know, in regard to this reported issue, has been stated by Lee in the previously mentioned post;[quote="Lee" wrote:
Ulf advised me that due to problems with the Canon SDK, I need to downgrade from Snow Leopard to Leopard to resolve this.
Further, based solely on the nature of the communication and the spec for USB 2.0 it seems that a cable length adjustment from 16' (Spec) to 10' would have little to no effect... unless of course the computer is not up to spec 🤓 . Since the USB connection draws power from the machine ONLY to facilitate the communication and carry the signal, I would further suspect any power issue that may contribute to your findings would be on the side of the laptop and not the cable.
Regardless, I think your report is valuable to chasing down a solution for users that cannot downgrade. I'll put in an order for similar components and see if I can't replicate your findings.0 -
I actually began experiencing this problem with 5.0.2 on OS 10.5.8
I've got a drive configured to test that combination again. I'm just waiting for the right circumstances to try it.
Can I get a detailed explanation of the configurations that experience this problem? I can't get an answer to this in my support case. Will this issue be more clearly documented in future releases?0 -
[quote="Jamie111" wrote:
I actually began experiencing this problem with 5.0.2 on OS 10.5.8
Hmm, I'm inclined to think that this is NOT the same issue. We know definitively what causes tethered issues with 10.6 and 5.1.2, which is what I have tried to point out in this and other threads. With 5.0.2 and 10.5.8, if there is a stall or communication issue it is likely very different in nature from the one discussed here.[quote="Jaime111" wrote:
Can I get a detailed explanation of the configurations that experience this problem? I can't get an answer to this in my support case.
I'll take a look into your support case and give you all the specifics you want.0 -
[quote="Drew" wrote:
[quote="Jaime111" wrote:
Can I get a detailed explanation of the configurations that experience this problem? I can't get an answer to this in my support case.
I'll take a look into your support case and give you all the specifics you want.
Jaime,
I took a look and found that your last case is quite extensive and the supporter (me) has given you all the details to the issue that was reported. If you want to continue with that support case you are welcome to do so.0 -
Take a closer look at your usb cord, currently we are using (2) 16' active extension usb cables and the stock 3' cable that Canon supplies, knock on wood no hickups from day 1, in studio or location
I have also seen cpu issues when then operating temperature gets close to 95° F
5d2 tethered to Imac running 10.6.3 and C1 5.1.1
16' active extension usb is manufactured by tripplite U026-016 (lifetime warranty) product also states, daisy chaining multiple cables (up to 5 for a 80ft reach)0 -
[quote="Michael4811" wrote:
Take a closer look at your usb cord, currently we are using (2) 16' active extension usb cables and the stock 3' cable that Canon supplies, knock on wood no hickups from day 1, in studio or location
I have also seen cpu issues when then operating temperature gets close to 95° F
5d2 tethered to Imac running 10.6.3 and C1 5.1.1
16' active extension usb is manufactured by tripplite U026-016 (lifetime warranty) product also states, daisy chaining multiple cables (up to 5 for a 80ft reach)
Hi Michael,
are you using a repeater or powered usb hub?0 -
It’s a active extension cable, but looks like a repeater cable 0 -
Hello,
i have the completely same Problem with my 5DMkII, but also with my 1DMkIV. As the german hotline told me yesterday, the problem is the canon sdk and at the moment there is no solution in sight despite working with OS 10.5.... ☹️ .
Br
jens0 -
The issue is in fact the Canon SDK. Any program that uses the SDK which Canon provides will have the same affliction. We are hopeful that Canon will address this issue and provide a workable solution in Snow Leopard but at present the options are between the following two;
1) Run Leopard 10.5.8 and Capture One 5.0.2 (Old SDK)
2) Tether using Canon DPP (different SDK we cannot use) and implement the "Hot Folder" option in Capture One
Neither solution is perfectly elegant and without it's downfalls. The unfortunate reality however is that for this particular issue we are at the mercy of Canon and their SDK which is the engine behind the Canon Tether ability. In this case, that engine is about as robust as a Daewoo. Pray they produce some Detroit Muscle and all will be well once again.0 -
I have the same problem: Shooting tethered to a 5d mk2, running C1 Pro 5.2 on a 17" MBP 2.66 i7 8gb RAM, 10.6.4. I use a 15ft active USB extension and a 6-foot USB cable.
I have been doing some testing with a Nikon D700 and Nikon D3s since they are now supported for tethered capture. I could plug either of them into the exact same system and fire off 12-20 shots at high speed (2-3 per second) and they would all begin popping up in C1 within a second or two, and continue appearing at a rate of about 2 per second until finished. I never saw the spinning beach ball.
If I fire off even 4 frames with my 5dmk2 at a speed faster than 1 per second, I get the spinning beach ball, and although I can continue shooting, I must wait approximately 2 minutes for the shots to begin appearing, and then they appear reasonably quickly.
I certainly seems like a Canon SDK problem to me. And it is making me seriously consider the Nikon. This sort of thing usually involves a lot of finger pointing without a lot of action.0 -
[quote="Greg1" wrote:
I certainly seems like a Canon SDK problem to me.
If it looks like a duck and quacks like a duck... 😉0 -
Does PhaseOne have any direct communication with Canon to know if a fix to the SDK is coming? or a timeline?
greg0 -
My problem is similar. Canon 1ds mark 2 (firewire connection) will not connect to C1 5.2. It will connect to 3.79. It does show up in the "update" list in the prefs even when it won't connect. 0 -
The 1Ds II failure-to-connect is actually a different problem. See: http://www.captureintegration.com/2008/ ... -osx-1052/ 0 -
Thanks,
I'll look in to that. I have found a way to get i connected. In 3.79, the order was launch C1, turn on the camera with no CF card. In 5.2, Camera on 1st, while the is trying to connect, fire a frame and it has connected a couple of times in a row.
I'll check out the link, Thanks again.
Tim0 -
Type8Camera was not present on my computer. Not on my 10.58 or my 10.63. C1 4.X was never installed on either of these machines nor were leaf drivers.
Thanks anyway.0 -
This is just a repeat of the disaster that they called C1 4. I took ages to upgrade to 5 pro just because of all of the issues I've had with 4 and my 5d and 5d2. It's the same old, same old with C1. Blame the camera.
Just upgraded from 4.8.2 (or 3, can't remember as I had to downgrade to find a stable version) and onto Snow L. Buffering can't be any slower shooting tethered, computer locks up and camera goes down, it's bullshit. The last version 4 I had installed was far more stable than 5. So after all the headaches dealing with Phase one playing around with 4 for a year, it appears that we're back to square one and the same games.
There's no chance in hell that I'll invest in another phase one back or software.
I'm saying hello to Hasselblad and Phocus. Sorry Phase one and Canon, you've lost me with your bullshit sandbox he said, she said...0 -
The truly sad thing in all this 3.79 so much promise. Making 3.79 SL capable and compatible with newer Canon cameras and I would be a happy camper! 0 -
I mainly shoot still life so not much pressure on speed of shooting but on a recent people shoot with 2 of us shooting we both separately had this issue on 2 separate macbook pros and 5d2s (one 10.5.8, 2.2 Core Duo 2G ram and one 10.6.4 2.4 core2 Duo 4G ram) with 16' cable and also a 10' cable. Both cables were tried on both set ups. This is first time we had encountered this problem (my college shoots people mainly) and we had multiple failures. I wouldn't say we were shooting quickly but sometimes 2/3/4 frames in succession was enough to cause a hang. The only new thing in our set up at this point was C1 5.2 so we assumed there could be an issue there.
But both machines had photoshop (CS3 and CS5 respectively) open and what seemed to solve the problem was making sure PS was quit. After that no problems (even with 5/6 or so waiting in the buffer) at all or since (although no subsequent rapid shooting either) which make me wonder if it's some sort of memory issue somewhere in one of the components involved in tethering and downloading the images.
The only other tethering issue with the 5D2 which causes a hang (that I've come across) is if you shoot a frame to quickly after connecting the camera. Sometime the camera says busy and wont let you shoot but there is a short period after that before C1/camera is fully connected which can cause an issue. Most often this comes up if the camera has gone to sleep. 5.2 seems much quicker to tether though and I haven't had this problem recently.
Hope that lot might be useful to someone!0 -
Obviously USB cameras and firewire have different connectivity problems. If you are trying to connect a firewire camera, try firing a few frames while the camera is trying to connect. (5.2 or newer). It has worked every time for me. If you become disconnected during a shoot, turning the camera off will not usually clear the camera. You need to remove and replace the camera battery and start over. We were replacing the battery even when it indicated that the battery was good. I started to think that maybe removing the battery would give the same result and that turned out to be true. 0 -
Hi,
I have the same problem of "hang" for about a year know (or two), using different camera, and software release.
When it's a bad day I just use Canon software and have no problem.
I think it'll never be working properly, you just have to live with it.
For me, it's not really a problem; but for my client looking over my shoulder, they just thing that I'm an amateur with cheep gear!!
D.0
Post is closed for comments.
Comments
33 comments