Severe CO7 Tether Issues with Nikon D800
I am running Sessions on CO1 7.1.3 & 7.1.2 with the same problems. Camera is a Nikon D800 Tethertools USB 3, Open CL is off, Canon is disabled, I have already run disk utility and verified disk and disk permissions etc. There is 2.79 TB available space on the computer with the RAM being dedicated to just running CO7. This is the only application we use on this computer - Apple 10.6.8, 3.4 Ghz Intel i7, 32 GB memory.
The application says the camera is attached, but whenever I click the shutter (or select the Capture button), nothing goes through. There is no pending bar, and I know which shot folder it is. The application recognizes when I turn off and on the camera, but no matter what I do, the images wont go through. When I look at the Nikon, A symbol "{PC}" pops up on the right hand part of the screen, and there is a line that continuously goes across the screen, getting larger and smaller.
This is a new tether cord, and when we used this system 1 month ago it worked fine.
Please advise--what is going on with the Nikon and why wont CO7 shoot?
Also, the connection often goes in and out even if I use different (high quality) tether cords. CO1 will just drop the connection, and pick it up, even if the camera hasn't been fired or moved.
When I am shooting tethered, there is a memory card in the camera-I'm not sure if this makes a difference.
The application says the camera is attached, but whenever I click the shutter (or select the Capture button), nothing goes through. There is no pending bar, and I know which shot folder it is. The application recognizes when I turn off and on the camera, but no matter what I do, the images wont go through. When I look at the Nikon, A symbol "{PC}" pops up on the right hand part of the screen, and there is a line that continuously goes across the screen, getting larger and smaller.
This is a new tether cord, and when we used this system 1 month ago it worked fine.
Please advise--what is going on with the Nikon and why wont CO7 shoot?
Also, the connection often goes in and out even if I use different (high quality) tether cords. CO1 will just drop the connection, and pick it up, even if the camera hasn't been fired or moved.
When I am shooting tethered, there is a memory card in the camera-I'm not sure if this makes a difference.
0
-
We are experiencing slow performance, "beachballs", crashing and the program becoming unresponsive. We have encountered problems ever since loading C17.
We purchased 2 new Mac Pros with 12GB of ram and a clean install of the OS 10.8.4 and C1 7.1.3 to try and alleviate the problem at great expense but to no avail.
We shoot tethered with a Nikon D3X and nikon D800 and encounter multiple crashes daily. Very annoying when you have a client on the set looking over your shoulder!
They seem to be pointing to the tethering or camera in this case. Now they want me to see if I can make it fail untethered, it's hard to experiment in a working studio.
I'll keep you updated although it seems to be a widespread C17 issue on all platforms (Windows user with same issues), so it will be up to phase one to make the fix.
We have an open support case.0 -
[quote="Steve Mac" wrote:
...
I'll keep you updated although it seems to be a widespread C17 issue on all platforms (Windows user with same issues), so it will be up to phase one to make the fix.
For the record: a Windows user currently discussing in the parallel CO7/Win forum had the issue solved by proper activating into Pro instead of DB.0 -
[quote="Photocor" wrote:
I have also a thread with C1 support but their conclusion is the fault is with windows.
I'm confused. Am I missing something?0 -
Update. We have changed nothing in our hardware, setup or workflow. After months of multiple daily crashes, beach balls and the program becoming unresponsive, we loaded 7.1.4 last Thursday and have only experienced one crash! 0 -
We are having a similar issue in co7.1.5
D800 tethers but the capture button will not work randomly. Can shoot with manual triggering but cannot control from camera. Have tried on os10.8.4 and 10.9
Has anyone figured this out?0 -
I would try using a powered usb hub and maybe an active usb cable. What about the "app nap" in 10.9? Otherwise, revert to capture 1 ver.6 if you have clients on-set. 0 -
we have a powered hub it's actually given us even more problems 0 -
I use the d800 a lot on jobs with my usb2 laptop and imac running 10.7.4. I generally use a powered usb hub with a 30' cable. C1 7 seems to work ok and C1 6 is faster and more stable. I am awaiting a new retina laptop with 10.9 and will be curious to see how that goes. I always think it's a good idea to wipe a drive clean and reinstall the system software, more than occasionally, on capture computers. Maybe that's the answer. Otherwise you might just have an offending file, saved icc profile, or style crashing your software. 0 -
Just to ask a stupid question but I'm assuming that you've tried other cables? I had a faulty cable that caused similar issues (blank pending bar, stuck shots which then cause the software to crash). I'm pretty sure that leaving the card in the camera only aggravates the issue. Are you also able to try another camera body? That usb port on the side of the D800 isn't the most secure thing in the world and gets much worse with age, cable practically removes itself. 0 -
Have you tried other cables, or D800 bodies, is an excellent question. I've experienced both those problems too. 0 -
Just out of interest, how long are the cables that you're using? 0 -
I've used 1 or 2 15' active usb 2 and 3 cables with a 40" nikon usb cable going into camera. The longer set-up requires a usb hub. 0 -
So, just to clarify - are you linking 2 cables together (a nikon cable and a longer cable)? Have you tested the camera just using one cable straight to the computer (minimising points of failure)?
Are the cables you are using different brands too. The reason I ask is because an experience i had with a brand new but faulty cable with an active repeater. The repeater wasn't getting along with the Usb 2 port on the machine but was fine when on a PC with USB3. Weird. For the sake of argument as well, did you trash your preferences and do a clean reinstall?0 -
[quote="NN206299UL" wrote:
So, just to clarify - are you linking 2 cables together (a nikon cable and a longer cable)? Have you tested the camera just using one cable straight to the computer (minimising points of failure)?
Are the cables you are using different brands too. The reason I ask is because an experience i had with a brand new but faulty cable with an active repeater. The repeater wasn't getting along with the Usb 2 port on the machine but was fine when on a PC with USB3. Weird. For the sake of argument as well, did you trash your preferences and do a clean reinstall?
Your repeater problem might be something to do with voltage stability on the USB port. It can be rather critical. I have no idea how the output of a USB3 port on a PC and a USB2 port on a Mac compare but experimenting with input power leveles on other devices working at a nominal 5V USB standard showed that quite small deviation from 5V (it will usually be on the low side) made a huge difference to successful operation. A powered hub might be expected to solve that sort of problem BUT I guess there is always some potential for problems even with that sort of solution.
Grant Perkins
ETA: I quickly checked the power specs uisng Wikipedia.
Signal 5 volt DC
Max. voltage 5.00±0.25 V (pre-3.0); 5.00+0.25-0.55 V (USB 3.0)
Max. current 0.5–0.9 A (general); 5 A (charging devices)
This suggests that USB 3.0 is more tolerant of lower voltages than USB2 and might explain why you can use the USB3 equipped PC IF the USB2 voltage on the Mac port drops to or below 4.75V during operation. I have no idea if that might be the case but it could explain the results you see.0
Post is closed for comments.
Comments
14 comments