C1 5.1 & 5D MkII Tethered
Using a Canon 5D MkII in tethered mode with CO v.5.02 has always been troublesome, like Lanny described it in a previous post:
But now with CO v. 5.1 the situation got worse and makes Capture One unusable:
even if all shots have been uploaded (unfortunately not faster than before...) the capture acquisition progress bar get stuck at 99% and if new shots are done it will take toooooo long (3~5 minutes) to acquire them, if you are lucky before CO freeze or crash...
Before that happens, if we try to quit CO to do a kind of reset, we get a caution message saying:
"Terminate Capture
A capture is currently in progress.
Do you want to terminate the capture and exit?"
But there is nothing to terminate... except for sure CO code !
Thank's in advance for the models standing in front of the camera... 🤭
[quote="Lanny " wrote:
I have had a long history of failure on tether with the 5D II and C1 Pro. I am now using 5.02 and the same issues keep happening. Unlike the previous poster I can't get the program to unfreeze. The only thing that works is opening the battery cover in the grip and force quitting the program. I can almost guarantee it will happen during a session but not always deep in. It usually happens when I shoot fast. I have sent in a support ticket a number of times. The folks at Phase One are trying but no solution seems to have been found. They have not been able to recreate the issue. I am posting here with the hope that someone has found a solution.
Here is some info: Macbook pro 10.6.2 using only the internal hard drive. 4 GB RAM
Any thoughts are most appreciated.
But now with CO v. 5.1 the situation got worse and makes Capture One unusable:
even if all shots have been uploaded (unfortunately not faster than before...) the capture acquisition progress bar get stuck at 99% and if new shots are done it will take toooooo long (3~5 minutes) to acquire them, if you are lucky before CO freeze or crash...
Before that happens, if we try to quit CO to do a kind of reset, we get a caution message saying:
"Terminate Capture
A capture is currently in progress.
Do you want to terminate the capture and exit?"
But there is nothing to terminate... except for sure CO code !
Thank's in advance for the models standing in front of the camera... 🤭
0
-
Is there a CF card in the Camera?
If so, please remove the CF card and performance should increase drastically.0 -
Is there a CF card in the Camera?
If so, please remove the CF card and performance should increase drastically.
No, no card inside.
Since 6 months, i read and apply all tips available on the Net to make the configuration working better, or at least just working.
And this one, no card inside, did "drastically" changed... nothing 😕
Thanks' anyway for your support.
Philippe.
p.s. (nothing to do with this post):
is there a possibility to change the "by default" ID on this forum (mine is NN884921, i don't know why) ?0 -
Philippe,
Create a support case and we'll take a look into your setup, this hasn't been our experience in testing so we can try to find what makes this setup different.
In regard to editing your Forum Name, you can do so from your Phase One account.0 -
Thank you Drew for the info about opening a support case, which i did.
And thank's also for the way to change my forum name, which i did.
Ph.0 -
Is there an update on this? We tried our first tethered session with 5.1 and the 5D MkII this morning and are experiencing the same problem outlined above. Reverting to 5.0.2 has solved the problem for now. 0 -
In an unrelated case to Philippe's we found a customer tethering with a Canon 5D Mark II had both a faulty cable and (coincidently) a faulty Canon Camera.
The Cable, which was first causing communication drops, was replaced but the "progress bar" issue remained. After ensuring that they were shooting RAW and not some other format (RAW + JPEG, SRAW, MRAW) the customer borrowed a colleagues identical camera (down to the firmware) and everything was fine. Upon looking at the captured RAW files closer it was found that there was some slight corruption, which is what caused Capture One to crash and the Progress Bar to stall.
The customer serviced their camera and now all is well. So, be sure to:
-Shoot RAW only (SRAW and MRAW are not RAW, JPEG + RAW can cause some communication confusion)
-Shoot with a known good quality cable (having a few on hand is not a bad idea)
-Ensure your RAW files are not corrupt from the camera and that your camera is working properly.0 -
Thanks for the suggestions Drew. We've been shooting tethered for a few hours now with 5.0.2 without any problems. The camera is set to RAW only and there doesn't appear to be any corruption in the raw files. Both C1 5.0.2 and OS X are able to open them. Other than trying to open the files I don't have any tools to check for the slight corruption you mentioned. I'll reinstall 5.1 and try a second cable once our day is over and if that doesn't work I'll open a support case.
What firmware version are you guys testing against with this camera?0 -
The Firmware tested is always the latest version supplied by Canon. In this case I believe that is 1.2.4.
If you do run into trouble create a case and let us know, since there was adjustment made to the Canon Tether ability to accommodate the Mark IV we want to make sure nothing is conflicting with that adjustment.0 -
I am having the same problem on a shoot today. Very frustrating....
A small work-around (until Phase sort out a patch) is to create an empty folder and once the file has been captured (but not appeared) switch to the empty folder and then switch back to the capture folder. Hey presto, the new captured file will appear.
I am running without a CF card, brand new cable (albiet worth only $8).
Tom0 -
Thanks Tom that worked! I just tried your suggestion with the same camera tethered to another machine running 10.6.2 and C1 5.1 and am seeing the same behavior. After playing around a bit it seems the issue here is when starting with a new session captured images don't show up in the browser. Also the progress indicator stops shy of 100%. When you navigate out of the capture folder and back in the images show up. Subsequent images captured seem to appear fine in the browser but the progress indicator always sticks.
Tom, did you find the tethered session reliable after the workaround?
paul0 -
[quote="Paul94" wrote:
Thanks Tom that worked! I just tried your suggestion with the same camera tethered to another machine running 10.6.2 and C1 5.1 and am seeing the same behavior. After playing around a bit it seems the issue here is when starting with a new session captured images don't show up in the browser. Also the progress indicator stops shy of 100%. When you navigate out of the capture folder and back in the images show up. Subsequent images captured seem to appear fine in the browser but the progress indicator always sticks.
Tom, did you find the tethered session reliable after the workaround?
paul
Hi Paul
I'm having to go into the empty folder and back into the capture folder to view any new shots. i.e. subsequent are intermittently not coming in (about 90% of the time).
I'm actually tech-ing on a shoot as we speak, so I haven't had a chance to fully investigate it yet (i.e. starting new session folder - re-installing C1 etc) - so this work-around is at least showing me the new shots for now.
I'm dubious about the faulty camera/faulty cable explanation though, as this problem seems to be spread across a whole bunch of 5D2 users.
Tom0 -
Paul,
Can you create a support case and ask for me. I want to test a few things with you on this.0 -
Sorry to hear that Tom. If it's an option reverting to back to 5.0.2 worked for us.
I'll submit the bug report later today Drew. Thanks for the help so far.
paul0 -
Paul,
Great. I'll be in the office until 6pm (EST) today so whatever works for you would be great.0 -
I would like to weigh in on this thread. I have been plagued by this tethering issue for quite a while. I have had numerous freezes and the only way to get back up and running is to open the door of the battery force quit the program and create a new session. I used to think it was the buffer filling up that caused the problem but I'm not sure that is the case. The newest issue in 5.1 is the stalled progress bar. I have two 5D Mark II cameras and a number of cords so I do not think it is an issue with either. I have submitted support cases on numerous occasions as recent as yesterday with all the documentation that was requested. The folks at Phase One support have been trying to figure this out but no answer seems to be found. I switched back to the Canon DPP to see if it would freeze but it did not. As you all know a freeze and crash in the middle of the shoot is disruptive and at times embarrassing. 0 -
Lanny,
I can see your history of issues with Canon tethering on Capture One 4 and as recent as the Beta of 5. All of which were forwarded to the software department to investigate.
The most current case was in reference to a Photoshop conflict so I didn't catch it when I was looking through for cases related to this thread. I'll get back to you through that case and hopefully we can get to the bottom of this issue for you.0 -
I saw same kind of issues while tethering (5D mkII & 1Ds mkIII, CO 5.1 Pro, 10.5.8):
- Pending progress bar stops working after a few captures
- "Capturing in progress" message when closing CO 5.1 (solved by switching off the camera and waiting till the Capture button turns gray)
- excessive memory use during capturing which is not released when CO 5.1 closes (general CO 4 & 5 issue IMHO)
Capturing with the 1Ds mkIII (yesterday with a client I installed 5.1 for) resulted in a freeze of CO 5.1 after a few captures. Resolved with Activity Monitor (general Force Quit beyond reach). Could not copy that behavior today with my 5D mkII.
Will try with OS X 10.6.2 later. I will open a case and upload some screen shots.0 -
Drew and I have been working on this issue through a support ticket. It would be great if those who have the same issue would start a support ticket and supply the info the support folks need. I would love to find out what the auto select new capture is set at when the freezes happen. I am by no means a software expert but I think there may be some connection there.
Lanny0 -
Like all troubleshooting, the more the merrier.
Thanks to Paul and Lanny for helping us get to the bottom of this one. We're still not 100% but things are looking up.0 -
Has anyone updated their camera to the latest 2.0.3 firmware?
I don't believe this release is public just yet but I would like to know if others have had access to it.0 -
[quote="Drew " wrote:
Has anyone updated their camera to the latest 2.0.3 firmware?
I don't believe this release is public just yet but I would like to know if others have had access to it.
Not public yet as far as I know. Do you have any indication that it might affect tethered performance? Or is it general interest?
Remark: I noticed in the Canon ImageBrowser 6.5.x update last week that it contained support for the 5D mkII 2.0.3 firmware. Not sure what that support means but I remember that a previous firmware update affected the raw file and CO4 needed re-profiling the camera in an update.
Edit: I read your other post (viewtopic.php?p=36506#p36506) after this one.0 -
I have the same problem when capturing tethered with 5d mkii and mac book pro. (everything is up to date!)
Really look like an amateur when working with client in your back!
D.0 -
[quote="Drew " wrote:
Has anyone updated their camera to the latest 2.0.3 firmware?
I don't believe this release is public just yet but I would like to know if others have had access to it.
The new 2.0.3 firmware for the EOS 5D mkII is public now.0 -
[quote="Paul_E" wrote:
[quote="Drew " wrote:
Do you have any indication that it might affect tethered performance? Or is it general interest?
I have my suspicions of the entire firmware upgrade process and it's coinciding with upgraded components/software for Snow Leopard. So, general interest is all I can admit to but I will retain my suspicions about the global conspiracy.0 -
[quote="dimitri" wrote:
I have the same problem when capturing tethered with 5d mkii and mac book pro. (everything is up to date!)
Really look like an amateur when working with client in your back!
D.
Dimitri,
Follow the suggestions laid out so far in this thread and let us know if you've noticed improvements.0 -
New job tethered today, same think, C1 crashed after +- 20 shoots
I think I'll give up and I'm very disappointed!
D.0 -
Dimitri,
Giving up is certainly up to you. However quitting isn't our motto.
If you want to create a support case we can look into it further, it's your call.0 -
any update on tethering problems with Canon cameras? I have had issues with every setup on a high volume fashion shoot with canon USB cameras I've used - I know you want the crash logs but I can't access them now, not my computer. but i know its a widespread issue. has Phase One identified the problem. is it all b/c of the new Canon SDK (not so new cameras have been out for awhile at least 2 years). if so I will move back to eos utility to tether. i would just like to know the official stance because it definitely isn't working as intended. 0 -
Edward,
There is currently no definitive issue. There certainly is potential for some conflicts when tethering in certain scenarios. If you can create a support case and provide a system profile we can see see if that scenario is something that you should be concerned with.0 -
Drew-
Can you outline some of these conflicts others are having? I'm sure all Canon users would appreciate it. If there is a suspected configuration of C1P5 that is contributing to tethering problems, I'd like to know. I've stopped using C1P5 with Canons for the time being, EOS utility and LR2 are ok for now.0
Post ist für Kommentare geschlossen.
Kommentare
41 Kommentare