Trouble shooting tethered with Canon EOS 1Ds, C1 3.7 and Win
When shooting tethered with the C1 (3.7) software there are very annoying delays while frames are transferred to the computer. Problem scenario:
1) Shoot one-shot frames in quick succession until the camera's buffer is full (approx. 10-11 frames). The camera will then be 'locked up' until some of the shots have been transferred to the computer, when shooting can resume. It seems that it takes a lot of time to get the first frame over to the computer, while the following shots gets across somewhat faster. When doing the same experiment with Canon's own 'EOS Capture' utility it seems that the first picture gets across quicker and that the camera lock is 'lifted' somewhat sooner. Anyways, this is not a big deal, but the next one is:
2) Shoot two one-shot frames, pause for a few seconds, and continue shooting. The camera is suddenly 'locked up'! Only once the first frame has been transferred to the computer it becomes possible to continue shooting. The delay is probably less that five seconds, but feels like an eternity when the models are lined up and ready..... To me it seems that the C1 3.7 sw unnecessarily locks the camera even when there is plenty of buffer capacity available in the camera. Canon’s ‘EOS Capture’ utility handles this nicely by the way.
Because of the issues described above we find it very difficult to work with C1 3.7 in tethered mode when ‘shooting’ models. Unless someone has a workaround for this problem we will have resort to using Canons utilities, which limitations are more acceptable for that type of work.
The problem is the same for both the 1ds and the 1ds MkII versions of the camera.
Any suggestions?
1) Shoot one-shot frames in quick succession until the camera's buffer is full (approx. 10-11 frames). The camera will then be 'locked up' until some of the shots have been transferred to the computer, when shooting can resume. It seems that it takes a lot of time to get the first frame over to the computer, while the following shots gets across somewhat faster. When doing the same experiment with Canon's own 'EOS Capture' utility it seems that the first picture gets across quicker and that the camera lock is 'lifted' somewhat sooner. Anyways, this is not a big deal, but the next one is:
2) Shoot two one-shot frames, pause for a few seconds, and continue shooting. The camera is suddenly 'locked up'! Only once the first frame has been transferred to the computer it becomes possible to continue shooting. The delay is probably less that five seconds, but feels like an eternity when the models are lined up and ready..... To me it seems that the C1 3.7 sw unnecessarily locks the camera even when there is plenty of buffer capacity available in the camera. Canon’s ‘EOS Capture’ utility handles this nicely by the way.
Because of the issues described above we find it very difficult to work with C1 3.7 in tethered mode when ‘shooting’ models. Unless someone has a workaround for this problem we will have resort to using Canons utilities, which limitations are more acceptable for that type of work.
The problem is the same for both the 1ds and the 1ds MkII versions of the camera.
Any suggestions?
0
-
Hi Norlas
Thanks for reporting this
We are analyzing the problem. We are testing a method to improve speed and avoid long delays.
If it works reliable we will implement it in the next release.0 -
Looking forward to it! There is also an issue related to the white-point adjustment for groups of pictures. We haven't taken the time to investigate this in any detail yet, but I have a feeling that this already is a known problem? 0 -
norlas,
I also am having problem shooting tethered with my 1ds & 20D. Can you tell me if you have tried to start a \"new session\" while tethered. Although I do not shoot as fast , I very seldom take more that 2 or 3 images in quick succession, I do use the \"new session\" icon to seperate my images into different folders. I am trying to find out if any other photographers are have a problem creating a new session. I am on PC's with windows xp pro and home where ver 1.3 works flawlessly with my 1ds but cannot get ver 3.7 to either use the camera counter or display the images automatically.
Any input on this would be greatly appreciated. I have just tried to create another support case but for some reason it was never posted.. I have pasted a copy of it here to see if any other photographer that use a 1ds and windows xp are having the same problem.
I should start this by saying I have a support case #9197 but could not figure out how to get back to it. I am using a pc, pentium4, windows xppro. I have been told via support to remove all copies of C1 and reinstall program. I have done this and have completely gone thru my registry and removed anything to do with phase one, cleaned all Phase One files off of my drive, completely emptyed my recyle bin, reinstalled Phase One C1 and am still having the same problem. C1 will not automatically display the captured images unless I close the program down and restart. To reiterate my workflow.
I create a job file and select it as the root folder. I create a \"new session\" with the clients name via the green \"new session\" folder icon. The folder shows in the session tab and has the \"camera\" icon in it. I then take images that never display unless I click the \"referesh\" icon. (I have checked the box to \" display immediatly\") If I close C1 and restart C1 the images will then display automatically but the normally green \"new session\" icon is greyed out. If I take an image the \"new session\" icon becomes green again while the image is downloading but then goes \"greyed out\" and the only way to get it green again is the click on another folder tab but if I make another new session I have to close C1 and start all over. No matter what I do C1 will not use the camera numbers even tho I have that box checked in preferences and starts each session with ... Smith-000001, Smith-000002 or Jones-000001, Jones-000002.
I have no problems using ver 1.3 on any of my 4 computers I only have this problem in Ver 3.7.
Paul0 -
Hi Paul,
Sorry, we have not been shooting the way you prefer with a lot of folders. We are typically doing studio shoots and thus create one folder for each project/assignment. We have not experienced any problems akin to yours in that respect.
We've been running C1 under WinXP Pro for three years now, using both LightPhase backs and Canon EOS 1Ds (once it became supported by C1). We're currently at SP2 on all computers. The problems we have experienced during this period have turned out to be partly cable related and partly related to apparent software incompatibilities.
The Firewire cable problems were solved when we swapped the 'economy' cables for high-quality units. That made one hett of a difference for the system stability. This was apparent with the LightPhase back, and even more so for the Canon cameras. The combination of WinXP's native FireWire driver and Canons WIA-drivers seems to make a brittle bridge. Communications disruptions due to inferior cable quality or short breaches in cable connections with camera or computer are not handled very well by that driver-combo.
After some initial trouble five years ago we have not had any serious problems with the LightPhase-FireWire-C1 software. Since we got the EOS 1Ds two years ago we have also used Canons own software without and considerable problems (except for the cable issue). It is therefore my belief that the problems we have experienced with a mix of Canon drivers and PhaseOne software is due to immaturity in the integration software between the two.
I am, by profession, a computer professional, and my wife is the (demanding!) pro photographer. When our computer stuff fails it falls upon me to analyze and solve. And, I don't get away with quick fixes:) I've therefore spent a considerable amount of time trying to come up with lasting solutions/fixes when problems arise.
In my experience there is nothing more effective than a complete reinstall of WinXP when things go awry. Currently we have installed C1 3.7 on three separate WinXP computers (One is a Dell Inspiron 8600 with 1.4GHz cpu, 1Gb memory and a 60GB hd (7200rpm), the second is a custom AMD Athlon 64 3200+ based computer, and the third is another custom AMD Athlon 32.) The latter have been running its current installation of WinXP for a year and a half, and have had several versions of C1, Photoshop, and related drivers installed, de-installed and reinstalled several times. When I installed C1 3.7 on this computer it simply didn't connect to either camera anymore, so that computer is due for a complete make-over pretty soon. The Athlon64 computer received a clean install of WinXP only two days before we installed the Canon drivers and the C1 3.7 trial. It currently runs without a hitch, and it is pretty fast too:) Initially the Dell unit had the same problems as Athlon32, but a clean installation of WinXP Pro SP2 did the trick. It now works fine.
So, my recommendation is to do a clean install of WinXP (including disc formatting), then install the latest (very important!) drivers available from Canon. (It seems that Canon have various versions of their drivers and software available for download depending on which Canon site you enter, so make sure that you browse both the American, the European and the Japanese sites to get the ones with the highest version numbers.). Then test that everything works fine with Canons own utilities before installing the C1 3.7 software. If you plan to install other utilities and/or scanner and printer drivers do that AFTER you have verified that C1 works fine.
Good luck!0 -
norlas,
I am having the same problem with 4 computers..2 athalon 3200's with xphome, 1 pentium4 with xpmedia and 1 pentium4 with xppro. On one of the athalon machines I did a full format and reinstalled windows and have the same problem. I also do all of my computer work. I worked for IBM for 30 yrs and now do photography full time. I noticed the problem with the ver 3.7rc and brought it to Michael Tapes attention but that was at the time he was in transition so I guess nothing ever got done with it before 3.7 was released. I can get the program to work tethered as long as I dont need to create a new session. I have created a support case but have not heard anything yet except to completely uninstall all ver of C1, flush the registry, delete all folders and reinstall which I have done to no avail. My next thing is to go back to a friends with cable and redownload the program maybe something was messed up in my first download.
It sure would be nice to know If others can create new sessions without problems.
Paul0
Post ist für Kommentare geschlossen.
Kommentare
5 Kommentare