Tethered Nikon Issues
Mac Pro (5.1) OS 10.8.4 and Capture One 7.1.3
2X6-Core Intel Xeon
2.4 GHz
12GB RAM
Is anyone else experiencing problems (freezes, beachball and crashing and program becoming unresponsive) when shooting tethered with a Nikon D3X?
2X6-Core Intel Xeon
2.4 GHz
12GB RAM
Is anyone else experiencing problems (freezes, beachball and crashing and program becoming unresponsive) when shooting tethered with a Nikon D3X?
0
-
[quote="NNN634637274286310223" wrote:
Mac Pro (5.1) OS 10.8.4 and Capture One 7.1.3
2X6-Core Intel Xeon
2.4 GHz
12GB RAM
Is anyone else experiencing problems (freezes, beachball and crashing and program becoming unresponsive) when shooting tethered with a Nikon D3X?
Please create a support case with Support.
Be sure to include all CO logs, system profile, camera firmware version.
Also, if you experience a crash, make sure that you fill out the crash-report, and submit it.0 -
The support case is already in progress. I was curious to see if any users were experiencing the same issues. 0 -
Not with D3X but with D800. I updated to 7.1.3 and now the camera doesn't connect at all. So frustrated with every.single. update of C1. 0 -
[quote="JAYSEN" wrote:
Not with D3X but with D800. I updated to 7.1.3 and now the camera doesn't connect at all. So frustrated with every.single. update of C1.
Have you enabled the Nikon Tethering from the preferences?0 -
I have had the same issues. And have done everything that has been suggested when tethering a Nikon. My first time running 7.1.3 was a disaster--it crashed almost immediately, camera was connected but would not load images--not even a pending bar--if I clicked the shutter or selected Capture button. This is the worst one I've had experience with, and I test all of the new versions when they come out. I ran disk utility, disabled Canon, Open CL is off...
Do you also have an issue with a dropped connection? Mine will go in and out intermittently.
The only thing I noticed that made a large difference was removing a CF card from the camera when shooting tethered.
My case is below, sounds similar to yours.
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.0 -
[quote="NN200218UL2" wrote:
I have had the same issues. And have done everything that has been suggested when tethering a Nikon. My first time running 7.1.3 was a disaster--it crashed almost immediately, camera was connected but would not load images--not even a pending bar--if I clicked the shutter or selected Capture button. This is the worst one I've had experience with, and I test all of the new versions when they come out. I ran disk utility, disabled Canon, Open CL is off...
Do you also have an issue with a dropped connection? Mine will go in and out intermittently.
The only thing I noticed that made a large difference was removing a CF card from the camera when shooting tethered.
My case is below, sounds similar to yours.
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.
Have you check your port in the d800? The connection dropping all the time usually is a hardware issue.
We can't repro this behaviour with our in-house d800e, so next step to check is the hardware.0 -
[quote="NN200218UL2" wrote:
I have had the same issues. And have done everything that has been suggested when tethering a Nikon. My first time running 7.1.3 was a disaster--it crashed almost immediately, camera was connected but would not load images--not even a pending bar--if I clicked the shutter or selected Capture button. This is the worst one I've had experience with, and I test all of the new versions when they come out. I ran disk utility, disabled Canon, Open CL is off...
Do you also have an issue with a dropped connection? Mine will go in and out intermittently.
The only thing I noticed that made a large difference was removing a CF card from the camera when shooting tethered.
My case is below, sounds similar to yours.
We have had no problems with the Nikon dropping connections but the crashes and slow performance had made it almost unusable. We would crash several times daily. However we loaded 7.1.4 yesterday and have not experienced a crash yet! Maybe to early to tell but, it seems like it was a C17 issue, as we have changed nothing and not hardware as suggested. Good luck.0 -
My experience with my Mac has been terrible with the new 7.1.4 upgrade. I have been shooting a Nikon D800e and the program just freezes. If I go into photoshop to do a little work and come back to C1 it requires a force quit. I stepped back to a previous version and it was better, but still not great.
I have ended up going back to a H20 back with Version 7.1.3 and it's much more stable.
These leads me to believe it's one of the following: USB issue, Nikon issue, Poorly written software issue.
The Old firewire 600 connection to the H20 back will have to be my solution for now. I hope Phase one can figure out the issue.
Also as a side note, I run a windows machine with C1 and on it's first time firing up, it crashed before I could do anything. And to my unpleasant surprise, it still does........I can't even using it. Will roll that back to a previous version and hope it's as stable as it used to be. In this case because of the instability I believe it is software as nothing has changed on the machine.0 -
[quote="Steve Mac" wrote:
Mac Pro (5.1) OS 10.8.4 and Capture One 7.1.3
2X6-Core Intel Xeon
2.4 GHz
12GB RAM
Is anyone else experiencing problems (freezes, beachball and crashing and program becoming unresponsive) when shooting tethered with a Nikon D3X?
Both my D3s and D800 work just fine0 -
[quote="NNN635156169528295822" wrote:
Both my D3s and D800 work just fine
What is your set up?0 -
Just curious....Are any the other users having crash issues connected to a LAN? We found that the crashing instantly stopped (for the most part) when we disconnected from our LAN. We created a support ticket and they told us to start shooting to a catalog instead of a session and that seemed to work pretty well. It's still not the most stable program...crashes a few times a day, usually.
While shooting in a session, our best solution was to disconnect from the LAN while shooting. Then close C1 and transfer images, and eventually re-disconnect when ready to shoot again. Not the best, but it worked.
Like I said, the shooting to a catalog while connected to the LAN has taken care of most of the problems, although we would prefer shooting in sessions. Even in the catalog and connected to the LAN, though, we can't use an overlay image that is on our network without the same problems
It just seems that anything to do with a LAN locks C1 up, for us at least.
I'm not going to list all of our specs, because we have the same problems of various machines with different specs, be we are running OSx 10.6.8 with Intel processors and at least 8gb ram. We also experienced the same issues with various cameras including; Phase One, Canon, and Nikon.0 -
[quote="NN635156371651061744UL" wrote:
Just curious....Are any the other users having crash issues connected to a LAN? We found that the crashing instantly stopped (for the most part) when we disconnected from our LAN. We created a support ticket and they told us to start shooting to a catalog instead of a session and that seemed to work pretty well. It's still not the most stable program...crashes a few times a day, usually.
While shooting in a session, our best solution was to disconnect from the LAN while shooting. Then close C1 and transfer images, and eventually re-disconnect when ready to shoot again. Not the best, but it worked.
Like I said, the shooting to a catalog while connected to the LAN has taken care of most of the problems, although we would prefer shooting in sessions. Even in the catalog and connected to the LAN, though, we can't use an overlay image that is on our network without the same problems
It just seems that anything to do with a LAN locks C1 up, for us at least.
I'm not going to list all of our specs, because we have the same problems of various machines with different specs, be we are running OSx 10.6.8 with Intel processors and at least 8gb ram. We also experienced the same issues with various cameras including; Phase One, Canon, and Nikon.
I assume you are on 7.1.4 ?
Just out of curiosity, as I cannot reproduce your flow on 10.8, have you tried the exact same thing you always do, but on 10.8 instead?
Also, are you connected to the LAN via wireless or cable (or both?)0 -
[quote="Christian Gr" wrote:
[quote="NN635156371651061744UL" wrote:
Just curious....Are any the other users having crash issues connected to a LAN? We found that the crashing instantly stopped (for the most part) when we disconnected from our LAN. We created a support ticket and they told us to start shooting to a catalog instead of a session and that seemed to work pretty well. It's still not the most stable program...crashes a few times a day, usually.
While shooting in a session, our best solution was to disconnect from the LAN while shooting. Then close C1 and transfer images, and eventually re-disconnect when ready to shoot again. Not the best, but it worked.
Like I said, the shooting to a catalog while connected to the LAN has taken care of most of the problems, although we would prefer shooting in sessions. Even in the catalog and connected to the LAN, though, we can't use an overlay image that is on our network without the same problems
It just seems that anything to do with a LAN locks C1 up, for us at least.
I'm not going to list all of our specs, because we have the same problems of various machines with different specs, be we are running OSx 10.6.8 with Intel processors and at least 8gb ram. We also experienced the same issues with various cameras including; Phase One, Canon, and Nikon.
I assume you are on 7.1.4 ?
Just out of curiosity, as I cannot reproduce your flow on 10.8, have you tried the exact same thing you always do, but on 10.8 instead?
Just downloaded the update this morning... I actually just got on the forums to check out any new features. I will keep you posted on the performance!
I haven't tried it on 10.8. I'm stuck with 10.6 for now ☹️
Like I said, I have a pretty decent workflow using a catalog, so don't spend too much time spooling over it. I wrote the post more as an FYI of a possible solution for others. Thanks for looking into it for me!0 -
[quote="NN635156371651061744UL" wrote:
[quote="Christian Gr" wrote:
[quote="NN635156371651061744UL" wrote:
Just curious....Are any the other users having crash issues connected to a LAN? We found that the crashing instantly stopped (for the most part) when we disconnected from our LAN. We created a support ticket and they told us to start shooting to a catalog instead of a session and that seemed to work pretty well. It's still not the most stable program...crashes a few times a day, usually.
While shooting in a session, our best solution was to disconnect from the LAN while shooting. Then close C1 and transfer images, and eventually re-disconnect when ready to shoot again. Not the best, but it worked.
Like I said, the shooting to a catalog while connected to the LAN has taken care of most of the problems, although we would prefer shooting in sessions. Even in the catalog and connected to the LAN, though, we can't use an overlay image that is on our network without the same problems
It just seems that anything to do with a LAN locks C1 up, for us at least.
I'm not going to list all of our specs, because we have the same problems of various machines with different specs, be we are running OSx 10.6.8 with Intel processors and at least 8gb ram. We also experienced the same issues with various cameras including; Phase One, Canon, and Nikon.
I assume you are on 7.1.4 ?
Just out of curiosity, as I cannot reproduce your flow on 10.8, have you tried the exact same thing you always do, but on 10.8 instead?
Just downloaded the update this morning... I actually just got on the forums to check out any new features. I will keep you posted on the performance!
I haven't tried it on 10.8. I'm stuck with 10.6 for now ☹️
Like I said, I have a pretty decent workflow using a catalog, so don't spend too much time spooling over it. I wrote the post more as an FYI of a possible solution for others. Thanks for looking into it for me!
Thanks for getting back so quick.
Stuck on 10.6 due to limited hardware or just because of company policy or something completely different?
My own personal experience with my own D3x, CO and a 10.6 mbp vs 10.8 installation, is that 10.8 seems to be more stable, so I would of course advice you to try it out on one of your machines, if possible.0 -
[quote="Christian Gr" wrote:
[quote="NN635156371651061744UL" wrote:
[quote="Christian Gr" wrote:
I assume you are on 7.1.4 ?
Just out of curiosity, as I cannot reproduce your flow on 10.8, have you tried the exact same thing you always do, but on 10.8 instead?
Just downloaded the update this morning... I actually just got on the forums to check out any new features. I will keep you posted on the performance!
I haven't tried it on 10.8. I'm stuck with 10.6 for now ☹️
Like I said, I have a pretty decent workflow using a catalog, so don't spend too much time spooling over it. I wrote the post more as an FYI of a possible solution for others. Thanks for looking into it for me!
Thanks for getting back so quick.
Stuck on 10.6 due to limited hardware or just because of company policy or something completely different?
My own personal experience with my own D3x, CO and a 10.6 mbp vs 10.8 installation, is that 10.8 seems to be more stable, so I would of course advice you to try it out on one of your machines, if possible.
Not so much policy as it is corporate life. We get upgrades according to a time table, not out of necessity, unfortunately (which is completely unsterdable in our environment, not speaking negatively).
I've been shooting for about an hour now, so far no crashes. #highhopes0 -
I am running 7.1.4, and have had constant crashing issues with this version, as well as all previous versions of the software. I'm shooting with a Nikon D800E, tethered. I've tried using a shorter USB cable, extending my connection with a powered USB port, to no avail. My program crashes regularly several times throughout the day. Also, several times a day, I loose camera connection for no apparent reason. I can almost guarantee that if I go to Photoshop for a while, when I return to Capture One, that the program will either crash or just not respond. Extremely frustrating. It's to the point that I'm seriously looking at going to an alternate software. It's great when it works, but the reliability factor is non existent. 0 -
[quote="tonyszcz" wrote:
I am running 7.1.4, and have had constant crashing issues with this version, as well as all previous versions of the software. I'm shooting with a Nikon D800E, tethered. I've tried using a shorter USB cable, extending my connection with a powered USB port, to no avail. My program crashes regularly several times throughout the day. Also, several times a day, I loose camera connection for no apparent reason. I can almost guarantee that if I go to Photoshop for a while, when I return to Capture One, that the program will either crash or just not respond. Extremely frustrating. It's to the point that I'm seriously looking at going to an alternate software. It's great when it works, but the reliability factor is non existent.
Have you tried with another cable ? I have seen a lot of issues with the USB3 mini plug at the D800 end.
What graphics adapter and Photoshop version are you running ? PS and CO can be competing or the Video-ram, and if there's not enough, someone will loose this fight over resources. 1 gb VRAM is alright for CO alone, but if you run CS6 or CC at the same time, you can run into trouble (or get a very slow performing CO). In that case it would be a good idea to have a graphics adapter with 2 gb or more VRAM.
We are always trying to improve the software, especially by using user input. If you continue to have problems, be sure to submit a Support-case.0 -
[quote="tonyszcz" wrote:
I am running 7.1.4, and have had constant crashing issues with this version, as well as all previous versions of the software. I'm shooting with a Nikon D800E, tethered. I've tried using a shorter USB cable, extending my connection with a powered USB port, to no avail. My program crashes regularly several times throughout the day. Also, several times a day, I loose camera connection for no apparent reason. I can almost guarantee that if I go to Photoshop for a while, when I return to Capture One, that the program will either crash or just not respond. Extremely frustrating. It's to the point that I'm seriously looking at going to an alternate software. It's great when it works, but the reliability factor is non existent.
Regularly flushing the PRAM, Caches and fixing disk permissions helps. Also on our Studio machines we have no software loaded that will compete with C1 for ram. On our retouch computers closing Photoshop, InDesign while using C1 seems beneficial.
I understand your frustration! I hope this helps.0 -
When shooting tethered with a mac, other USB connections and the order at which you connect USB devices can grief you. Connect all USB devices including Camera and then restart your computer - or switch to wireless mouse and keyboard 😂 0 -
just bought a new macbook pro running 10.10.4 - capture would not work properly so I upgraded to Capture 8 - I am shooting Nikon D800 - I connect the camera and Capture sees it for about 3 seconds then it says no camera attached - hoping to shoot feathered for a big client in the morning - anybody have any suggestions?
boswell0 -
[quote="boswellcreative" wrote:
just bought a new macbook pro running 10.10.4 - capture would not work properly so I upgraded to Capture 8 - I am shooting Nikon D800 - I connect the camera and Capture sees it for about 3 seconds then it says no camera attached - hoping to shoot feathered for a big client in the morning - anybody have any suggestions?
boswell
The USB3 connection and low power from new MacBooks are the most common cause of disconnections. Try another cable, power USB3 hub and make sure you have your MacBook connected to an AC outlet, if possible. Remove all other USB connections if any exist.0
Post ist für Kommentare geschlossen.
Kommentare
21 Kommentare