Luminous Landscape Forum
Equipment & Techniques => Digital Cameras & Shooting Techniques => Topic started by: JohnAtBurn on January 07, 2009, 03:32:59 pm
-
By now all y'all who shoot Canons tethered to their Macs have probably upgraded their OS to 10.5.6 in the past few weeks. Apple managed to supercharge the USB bus and now we can all shoot 1DSmkIIIs tethered without pulling our hair out waiting right? RIGHT,
UNTIL:
you shoot more than 120-150 frames
Then both EOS Utility or Capture One grind to a standstill until you force-quit and restart the computer. We also always lose the last remaining shots in the buffer when the crash happens.
We can reproduce this every-time we try it with both our MacPro tower and MacbookPro17. Both of these machines are configured the same except the MacPro has 8GB RAM, and the MBP has 5GB RAM. They are running Mac OSX 10.5.6, Capture One 4.6, and EOS Utility 2.5.1 and have plenty of HD space.
This problem didn't exist in 10.5.5, but the tether-speed with that OS is so slow we don't really want to downgrade either.
Can anyone here with a similar setup try and reproduce the problem? We have been emailing PhaseOne and Canon about this but so far we haven't heard much back. We also have this problem with our new 5DmkII.
-John Simmons
-
sorry, I meant the MacBook Pro has 4GB of RAM.
-John
-
i have had the same experience with the dsIII, canon capture and aperture.....thanks for posting this, i thought it was an aperture limitation....very annoying during a shoot, in the end i just shot to card again....
-
This is not isolated to the 1Ds III btw. I get the same behaviour with the 50D and Canon EOS Utility.
And yes extremely annoying since you have to stop it and possibly do a restart. I shoot to both card and computer because at least the 50D doesnt take too kindly to being interrupted like that and the buffer images may be lost unless you save to card aswell.
-
This is not isolated to the 1Ds III btw. I get the same behaviour with the 50D and Canon EOS Utility.
Yes, I've read that Nikon's are also affected. I would bet any tethered USB DSLR camera probably has this problem with OS 10.5.6.
And yes extremely annoying since you have to stop it and possibly do a restart. I shoot to both card and computer because at least the 50D doesnt take too kindly to being interrupted like that and the buffer images may be lost unless you save to card aswell.
Someone in another thread suggested switching to a new folder before you get up to 120 frames, which might work for you. Also I've found that if I force-quit the "Image Capture extension" from the Activity Monitor I can reconnect the camera without having to restart the computer.
-John
-
Ah good tip about killing the extension. Ive noticed that just killing the EOS utility doesnt always help so that might be it.
And it does smell badly of a memory leak in that extension then. Hopefully it will be fixed soon
-
And it does smell badly of a memory leak in that extension then. Hopefully it will be fixed soon
Yeah well I ain't holding my breath with Apple... maybe they'll fix it with 10.5.7. I guess it's work-around time until then.
-
I can only confirm this problem when shooting with EOS utility
using canon 5 D mark 2 .
-
Nikon has the same problem. Camera Control 2 just locks up at some point. I never counted but it probably is around 100-150 frames. I only get to these numbers when shooting models which is the worst time for it to lock up. It also locks up after approx 5 minutes of running LiveView. LiveView sometimes runs sporadically during those 5 minutes, sometimes not. If it locks up I have to force quit the app or wait a minute or two for the beachball to stop spinning. The only fix is to bring production to a halt, quit CCP2, turn off the camera, relaunch CCP 2, then turn the D3 back on.
I hate to say it and no offense, but I'm kinda glad to hear it's happening to canonites too. I've been holding off buying D3x's until someone fixes this screw up. Apple had better fix this sooner rather then later.
-
Same here with 1ds3 and 5d2. And i was blaming that crap eos capture for that!
-
I had several lock-ups during a slow and careful interiors shoot Friday. It's like shooting tethered with the MkII's and that wiggly FW400 conncetion. Here we go again!!
I'd revert if I could at this point to the slower import speed annoying that was but this just looks amateur.
-
Today lots of lock-ups but the problem seems to be Canon Utility. I have the latest version. LiveView is very flakey and locks up the computer. Color Temp whilst tethering jumps back to a custom white balance which is odd and glitchy. Aperture is okay but the hotfolder needs refreshing and this would take an Apple tech - what - 20 minutes but we'll probably have to wait 6 months. Honest to god nice products lousy follow-through - Apple!
Camera gets backed up only to have to pull the battery. Probably more things than I can remember but we are going slow and carefully to avoid the pitfalls.
Wow, give me the old slow and sure days!
-
Apple is aware of the problems
-
Apple is aware of the problems
last time i called Apple Care (a few days ago), the weren't.
-
last time i called Apple Care (a few days ago), the weren't.
Apple Care folks are always the last to be informed. The above issue has probaly already been reported to Apple via the Apple bugreporter website. Sometimes, fixes take months to be released and sometimes they make it into the next system release…
-
Anyone have a work around thats working??
-
Anyone have a work around thats working??
Might be a poor comment but why not shoot into a BootCamp booted volume for the sole purpose of capturing?
I just bought a 5DII and shot 8-900 images into LightRoom but on a PC running XP. Since this thread is obviously showing great worry about 10.5.6 which is on my MacBook Pro then I won't be able to use it on location. I will try however to load the BootCamp XP with all that awful Canon Soft needed to drop tethered images into a LR watched folder.
Drats for the workarounds whom ever the fault might be with.
-
The only work around I have found is to limit the use of LiveView and keep that use really quick and expect it to fail once in a while. (1Ds Mk3 using Canon Utility 2.5.1 into Aperture 2.1.2)
When it does fail reboot without asking questions or messing around saving things and get back to work.
If you find images stuck in the cameras buffer and that little blue progress clock going around and around, pull the USB form the computer and it should write them to the card.
Not always but it can.
It would take Apple about 20 minutes to design and publish a new Hotfolder script, unfortunately redesigning the iPod Nano for the 1000th time takes precedence.
-
Hi
Did two shoots this week one into our 3.5 year old Mac tower with 10.4.9 ( no problems ever ), next shoot was location into a new 17" laptop (rental) with 10.5 something & we had 3 crashes!!!!!!! Same camera. There are days that MAC really SUCKS, you pay premium for this too!!! I have yet to invest into a new MAC machine & I think I will wait & they better get prepared for USB 3.0 as it is coming.
BTW we got great shots but this is the first time since shooting with the Canon 1DsMKIII that we have had any problem.
Denis
-
Hi
Did two shoots this week one into our 3.5 year old Mac tower with 10.4.9 ( no problems ever ), next shoot was location into a new 17" laptop (rental) with 10.5 something & we had 3 crashes!!!!!!! Same camera. There are days that MAC really SUCKS, you pay premium for this too!!! I have yet to invest into a new MAC machine & I think I will wait & they better get prepared for USB 3.0 as it is coming.
BTW we got great shots but this is the first time since shooting with the Canon 1DsMKIII that we have had any problem.
Denis
Well I've got a MDD dual not being used . Do you think it would be alright for a 5D II into Light Room under 10.4.11?
If I remember right when I ran Lightroom, must have been 1.3 or 1.4 it was pretty slow compared to MacIntels. Was the old mac a G5 or MacIntel?
-
I've not had the problem and I tether to a MacBook Pro and iMac, but I don't push hundreds of images off my cameras during a shoot.
I'd hack at this problem a couple different ways. To simply get the system to lock up, run the software (EOS Utility & Capture One, Bridge or whatever) and also run the Activity Monitor. Float the inspection windows and start shooting tethered. Set the 1Ds3 to small-raw and just fill up the pipeline. The information derived will show what's happening (maybe a buffer or cache overrun?). Send this to Apple & Canon.
Second, for live jobs, shoot the lighting setup tethered (i.e., a digital Polaroid session) and once everything is dialed in, untether and use a card reader. This will allow for fast shooting of unlimited frames.
I know this is a lousy hack, but something is better than nothing. A locked up computer kills all levels of productive workflow.
One of the problems photographers face is that Canon isn't the most nimble software developer on the planet, and Apple is constantly updating the OS. EOS Utility is designed to accommodate all their cameras, too.
-
this issue was driving me nuts and my work requires permanent tether fo the big preview and live view. one workaround is to shoot to card and have a screen attached to the camera, no computer required.
nice with the 5dmk2's HDMI, but i have to find a mini-HDMI to DVI cable, now i need a converter.
-
Well considering that Nikon users (and i assume Sony aswell) also experience this 120'ish image limit i would say the problem lies not directly with the Canon / Nikon software unless Apple issued a breaking-change update which is about as bad as it being Apples bug to start with.
I guess we'll just have to live with this until Apple releases working drivers
I tend to hit the limit on pretty much every shoot, but it's fairly ok to shut down eos utility, rip out the usb, reconnect the usb (which starts up eos utility) and download the missing frames.
-
yesterday i had a roughly 8 hour shooting without one crash, we only shot about 250 pictures. that is the best performance of 10.5.6 yet....no use of live view, as i was using an external monitor for that
-
I just completed a five day shoot and found that as long as I didn't use Live View in the Eos Utility that it would only freeze up a couple of times a day. Which required me to restart the computer each time. Still it's a bit of a pain and hopefully it gets fixed soon. I will say that waiting only a few seconds for each image to come through is much better than before.
-
Whilst all of us are struggling with this problem does anyone really think Apple is working on it? ( I challenge yee -Apple!)
As I said before Apple could write and re-issue the "hotfolder" application in 20 minutes. Do they? Hell No! Instead they prefer terrible PR (Photographer Relations).
Beware all MBP up-graders especially if you are using a 1D MkII series. No FW400 on the new MBP. (you saw that right) It looks like you can't just use a FW adapter because the software needs to "see" the FW400 connect and since there isn't such a port you're SOL. Any driver is probably dormant so you're stuck. Maybe Aperture or Lightroom will see your camera. (let us know)
MKIII users you all just keep ripping your hair out for other reasons.
Apple did this last time with the first MBP where they dropped the FW800 only to bring it back in the next bump. What gives with that sort of nincompoop engineering? Hold out and hope or spend $5,000 (5D MkII) chasing the white rabbit.
Everyone write Apple and Canon and lodge a sound complaint. TV series are saved and FaceBook policies are changed by vigorous campaigns - we here should be doing the same.
Example :
Dear Steve Jobs,
WTF...
-
Whilst all of us are struggling with this problem does anyone really think Apple is working on it? ( I challenge yee -Apple!)
As I said before Apple could write and re-issue the "hotfolder" application in 20 minutes. Do they? Hell No! Instead they prefer terrible PR (Photographer Relations).
Beware all MBP up-graders especially if you are using a 1D MkII series. No FW400 on the new MBP. (you saw that right) It looks like you can't just use a FW adapter because the software needs to "see" the FW400 connect and since there isn't such a port you're SOL. Any driver is probably dormant so you're stuck. Maybe Aperture or Lightroom will see your camera. (let us know)
MKIII users you all just keep ripping your hair out for other reasons.
Apple did this last time with the first MBP where they dropped the FW800 only to bring it back in the next bump. What gives with that sort of nincompoop engineering? Hold out and hope or spend $5,000 (5D MkII) chasing the white rabbit.
Everyone write Apple and Canon and lodge a sound complaint. TV series are saved and FaceBook policies are changed by vigorous campaigns - we here should be doing the same.
Example :
Dear Steve Jobs,
WTF...
any FW800 is completely backwards compatible...just use a FW800-FW400 cable or adapter....the drivers are the same...
the first MBP had both FW400 and 800...at least mine did....
the 5DII is 2700$...but you can buy mine for 5000$ or more if you want to...
save your rants for the apple forum, steve won't read this one....and he will pull anything that sounds remotely like a rant from the apple forum....so good luck....
other then that you are right....
-
tomorrow i will have to shoot a setup with the camera on a boom, about 4m high shootinh straight down, no way to access the camera once it is out there other than taking down the whole rig. there is a lot of cables, long ladders lots of sandbags, pocketwizards and other stuff involved, would have been rather easy with working live view. i am starting to get paranoid. i guess I' use bootcamp/windows for this one...
-
tomorrow i will have to shoot a setup with the camera on a boom, about 4m high shootinh straight down, no way to access the camera once it is out there other than taking down the whole rig. there is a lot of cables, long ladders lots of sandbags, pocketwizards and other stuff involved, would have been rather easy with working live view. i am starting to get paranoid. i guess I' use bootcamp/windows for this one...
the canon utility and live view with DPP work fine with me in 10.5.6....quick and relyable....and fine for previews....i only have problems when i try to work in aperture.....
your set up sounds like it could make good use of the wifi grip/adapter?
-
Just back from my shooting. had a few crashes which was big time annoying, as the camera wasn't really accessible, as you can see from the pictures... eos utility in windows on my mac crashed, too.
so i stopped using live view and shot slowly, no more hick-ups.
as the whole boom thing was swaying like mad, i used a second set of pocketwizards to trigger the camera with mirror up engaged. Pictures came out nice and sharp! again, the 5d mk2 amazed me.
PLEASE APPLE! i want 10.5.7!
-
I am also having problems with Nikon Transfer freezing and stalling half way thru transfers and 10.5.6. on both a Mac Book Pro and a Mac Pro. I reloaded the OS and backed it up to 10.5.5 and the problem went away. What a hassel...
-
Has anybody had any success with using Nikon Camera Control Pro without crashing?
-
tomorrow i will have to shoot a setup with the camera on a boom, about 4m high shootinh straight down, no way to access the camera once it is out there other than taking down the whole rig. there is a lot of cables, long ladders lots of sandbags, pocketwizards and other stuff involved, would have been rather easy with working live view. i am starting to get paranoid. i guess I' use bootcamp/windows for this one...
I used it the other day with XP and Bootcamp. It worked perfectly shooting faster than the transfers were happening. Only thing I quickly used up my 40GB Windows partition, so be sure to have enough volume with free space.
-
lucky to find this. Yesterday shooting tethered I got crazy after image 120. Suddenly the whole system would freeze up after one or two images. Never used on live-view.
Only after seconds to 30 seconds I could do one shot before everything would go to a halt again.
Just have to wait for Apple to solve this problem.
Using D300 with Camera Control Pro 2.4
-
I just noticed that Canon have updated their firmware for the 1Ds III to 1.1.4 and it mentions improved USB communication. Not sure if this is the fix we've been looking for but will update and test and see what happens. The firmware can be downloaded via the link http://web.canon.jp/imaging/eosd/eos1dsm3/firmware-e.html (http://web.canon.jp/imaging/eosd/eos1dsm3/firmware-e.html)
Cheers,
Derryck.
-
I made the uppdate of firmware on my 1DS Mark 3 two days ago , and nothing is better when shooting tethered .
Heavy crash - restart of everything is needed after 90- 120 images .
Looking at a published list what is going to be improved in 10.5.7 ( that is already close to Golden Master ) - nothing that I can read about USB memory leak -
it looks like Apple is pretending it is canon and Nikons fault , and camera makers blame on Apple .
It feels really ridiculous to restart my box every 100 or so images .
I have lost a lot of nice shots because of this crap.
( I can actually shoot , but nothing is saved to computer )
-
This is ridiculous!
Does anyone know how to raise a complaint like this to apple??
If so you should put it here with a link and we can all start bombarding them with this problem and hopefully get some attention.
-
This is ridiculous!
Does anyone know how to raise a complaint like this to apple??
If so you should put it here with a link and we can all start bombarding them with this problem and hopefully get some attention.
Fill a bug report at Apple ( http://bugreporter.apple.com (http://bugreporter.apple.com) ). This is the only way to get Apple to listen! Without bug reports, bugs will never be fixed.
-
Fill a bug report at Apple ( http://bugreporter.apple.com (http://bugreporter.apple.com) ). This is the only way to get Apple to listen! Without bug reports, bugs will never be fixed.
i have reported this "bug" just about every other month for the last year....
at this point this can't be considered a bug anyway...i mean they know that this just does not work...and that it hasn't int he last year or so....
as much as i love my apple stuff and really think it provides by far the best value out there, i sometimes can't believe how almost arrogant they are about these issues.....phone calls, bug reports, forum posts...nothing helps.....
the problem is that apple makes its money with ipods and iphones these days....and (what used to be the apple core) the graphics, photo, media community is being left behind a bit...mac pros, macbook pros, aperture!,....
i am guessing they have all hands full with snow leopard for summer....and i am pretty sure all these little problems will be fixed for good..... i really hope we will also see a aperture 3 release by then.....with full tether support as promised....
-
i have reported this "bug" just about every other month for the last year....
at this point this can't be considered a bug anyway...i mean they know that this just does not work...and …
Did you report the bug via the bug reporter website or via and standard feedback page? If you used the bug reporter page, then Apple should give you a bug# and its current status. Either Open, Duplicate or Closed. I've never seen much effect in reporting bugs through the standard feedback page.
-
Anyone tried Vmware with the canon software to get around this? At the moment I'm booting of a Fw800 drive that has 10.5.5 on it for when I need to capture tethered.
-
shot yesterday with 5DII and tried the canon utility and DPP....in 10.5.6...crash every 100+ files.....switched to canon utility via VMware and XP (or what i call the ultimate insult to apple).....no problems....noticed the whole thing slowing down at around 1500 files, but also had the client editing from the same folder that we shot into.....but no more crashes this way....
lets hope 10.5.7 will fix this BS....
-
Anyone tried Vmware with the canon software to get around this? At the moment I'm booting of a Fw800 drive that has 10.5.5 on it for when I need to capture tethered.
Not VM ware but a simple Bootcamp XP. No problems at all until the Bootcamp volume was full.
I just emptied a portable disc and reformatted in Fat32 for storing the copied files to to avoid the too small BootCamp volume.
-
Today I was at the Northern Short Course which I highly recommend from what I experienced these last two days.
The Canon Rep when asked about this problem blamed it all on Apple and that they have over-done the speed supercharge and the camera can't handle it. Nikon and everything else is crashing too.
(take that anyway you like!!)
He also said Canon had been testing all the previous versions of OSX 10.5.1 etc.
The problem is the speed bump - obvioulsy!!
Apparently the only fix is to revert to the earlier OSX 10.5.5 or whatever it was.
The glimmer of light was that he read me the Canon company email and a fix is being worked on.
He had only heard of this problem a week ago!!
Therefore I suggest we have ben doing a lot of grumbling to each other but forgot to broadcast it widely enough.
We'll all have to just sit and stew..
-
I just want to reconfirm and warn anyone attempting to shoot with USB tethered with 10.5.6>
it crashed out and stopped recording images at exactly #150 CR2 on my MacBook Pro. All images shot after #150 were lost. I think I looked at the portable at or around 40 images later.
Crazy why can't Apple fix this darn bug.
The only reason I switched to OSX on the MacBook PRo was Canon updated the EOS Utility to 2.6.1 and it crashes on Windows XP which the original CD installed 2.5.1.1 does not.
So two warnings ; one avoid 10.5.6 and shooting into from USB, and hold off on EU for Windows at least until you fully test it.
-
Yesterday after reinstalling the original disk version 2.5.1.1 onto the Windows XP Boot Camp partition we had zero problems shooting fast into the MacBook Pro. 600 or so images. Sure like to be able to shoot into Apple without XP. Anyone know if 10.5.7 will fix this?
-
No idea, i think everyone is waiting for the release (possibly on friday) and hoping ...
Me i dug up my old PC based laptop and switched to that temporarely for tethered shooting with my DSLR.
-
No idea, i think everyone is waiting for the release (possibly on friday) and hoping ...
Me i dug up my old PC based laptop and switched to that temporarely for tethered shooting with my DSLR.
Buy a PC not a Mac? I thought Macs were perfect?
I was considering getting a MBP for tethered shooting but now I guess I will have to reconsider...
-
Buy a PC not a Mac? I thought Macs were perfect?
I was considering getting a MBP for tethered shooting but now I guess I will have to reconsider...
nononono... i said DUG up my old laptop, not buy one =)
Hopefully it will be fixed with next release so i can dig my old laptop a new hole and let it rest in peace
-
nononono... i said DUG up my old laptop, not buy one =)
Hopefully it will be fixed with next release so i can dig my old laptop a new hole and let it rest in peace
ah... I really want a MBP, I just don't want any hassles with my Canon gear. I can't wait to deep 6 my heavy Dell.
-
10.5.7 is out. Anyone test yet?
-
10.5.7 is out. Anyone test yet?
Yep, OS X 10.5.7 fixes it !!! At least for Nikon Camera Control 2.5. Finally, 6 months almost to the day, actually a little over.
Apple didn't mention any usb fixes in this update. I suspect the weren't willing to admit it publicly.
-
Yep, OS X 10.5.7 fixes it !!! At least for Nikon Camera Control 2.5. Finally, 6 months almost to the day, actually a little over.
Apple didn't mention any usb fixes in this update. I suspect the weren't willing to admit it publicly.
I installed it already but didn't shoot today. Tomorrow is stills so I won't hit 100+ images.
Did you test it today?
-
Did you test it today?
Early days, but 10.5.7 installed without a glitch, then I used the Canon 5DMKII tethered and with a hot folder to link with Lightroom and everything was working perfectly as far as I could tell. I also installed the latest Canon upgrades (EOS Utility update 2.6.1) just before upgrading to 10.5.7. I tried just over 150 consecutive pictures, some in very rapid bursts of 10/15, and it didn't crash, so it appears to be fixed now. Before it used to crash at around 100 pictures.
I also tried it with my Leaf software (which was working fine before the upgrade) and it all seemed to work just as good after the upgrade.
Happy so far.
Edward
-
I installed it already but didn't shoot today. Tomorrow is stills so I won't hit 100+ images.
Did you test it today?
I did. The last two days actually. But I'm shooting stills as well. The problems I had with Nikon were very similar to canons, but roughly a month ago nikon updated their shooting software that fixed the 120 shot drop dead bug that I can confirm (they never mentioned they were fixing that bug either until I called them). The other half of the tethering troubles was with LiveView locking up the software after a minute or so. This was just as crippling because we like to use LiveView for stills.
Everything works fine so far without any super rigorous testing just normal day to day work. Previews load a millisecond or two faster too.
-
No problems at all today with the 5DII tethered into 10.5.7. As I said I did not shoot past 100 yet but so far so good. Actually the power management is now working better from EOS utility too. The Utility launches after a power down very quickly , which may have been the Apple usbKext.