Tethering Issue - Auto Adjustment
I am attempting to tether with my Sony A7R3.
I have opened a new session and attempted to take a photo, I am immediately presented with the activities window with one activity "Auto adjusting - about 20 seconds left" this then doesn't move.
When its in this loop any adjustments I make aren't displayed in the viewer but after a few seconds the browser version will update.This obviously makes tethered shooting very difficult. I am on build 13.1.3
Any ideas would be greatly appreciated. Hope this isn't carried into Version 21 as I have already pre-ordered it.
-
Hi Adam,
I encounter the exact same issue in build 13.1.3.13 while tethering with a Canon 5D4. As giving it a try, I've already disabled all kinds of autocorrections in the Auto Confige Adjustments Menu, trying to prevent Capture One even from starting doing this. Anyway, Capture One will still start this activity and then runs into a stuck state. Sometimes even for hours if you shoot multiple pictures tethered!
I can't find a way to abort this activity, nor stop it from starting this activity. On my site, Capture One 20 Pro is running on a 7th gen i7, equipped with 16GB of RAM, which should be way enough for Capture One to feel comfortable with. So I'm very curious to find out what I'm/we're doing wrong here or how we can solve this very annoying issue. Please help!0 -
I see this Activity window open up but only when switching on the camera. (In my test a Canon 1D3)
It appears before the Windows screen that asks what one wants to do with this newly discovered device.
Nothing happens and I can close the Activity window and carry on.
It sounds like you are experiencing something more disruptive.
If you have not already done so I would strongly suggest using the "Submit a request" function found on most of the Community pages to create a personal Support Case with the C1 support team in order to investigate what is happening in greater detail.
I have taken a look at the Log files. They seem very detailed but not in a way that is totally meaningful to someone without knowledge of the possible entries and their meanings.
0 -
@Vincent I have more RAM, I don't think its a system issue because previous versions I have been able to tether fine. Seems like a bug in a recent release.
I have submitted a request, if you are having the same issue it would be beneficial if you also submitted a request stating the issue. That way they know its just not one person having an issue, nut potentially a software bug that needs investigating.
0 -
Hi Adam, SFA,
You're both right!
This morning, I've submitted a request too.
Let's hope they'll come with a solution soon
Thnx @all for your replies :).0 -
After opening a request with C1 I was told that it's a bug. A rather big bug as tethering is such a core part of C1
0 -
@Adam: my ticket was marked as "solved" already on the very same day. There was no explanation, no solution, no corrective action at all, except for "solved". Would have been nice, at least polite and correct, if I was told the same. Because thanks to your feedback, now I know that there's a bug in play... I don't blame C1 for this bug as much I do for support leaving me behind with a simple "solved" 😕...
0 -
Hi guys. I am having the same issues! Lets hope the co team can solve this bug soon!
0 -
@Vincent seems odd to mark it solved when the bug is still present, did they ask you for logs?
@Diethelm hopefully it's fixed for the C1 21 release, not great for people not upgrading.
0 -
@Adam: Nope. As said: there was absolutely nothing, except for "Solved".
@All: Well, Surprise!: my ticket was reopened super spontaniously today :). They apologized for closing my ticket even before being submitted. Maybe they took a glance here. Or they were possibly triggered by my given critical feedback. But as long as Adam's ticket is still live, they now will have at least two live tickets regarding this issue.
Wether or not the issue persists in release 21, it should also be fixed in release 20 anyway. Because they simply can't leave cu$tomer$ behind like that (i.m.h.o).
0 -
There is some interaction going on regarding this issue. At the end, I was advised by Support to completely wipe my installation and then do a full fresh reinstall of C1 (latest downloaded version, which still is 13.1.3.13) to see if the issue would persists.
Well, bad news: It does. And this result was already reported to Support, so they don't have to wait to carry on...
Now, I'm curious if there is any progress on your side? Were you guys (at least Adam) requested by Support to try anything they suggested / give any feedback?
0 -
I have not heard back from support since I was told it's a bug. It's my first time dealing with C1 support and it's been dreadful. If it's a bug could they not tell me what version it was released in so I could roll back. It's not a small feature that is easily avoided. It's the main reason for using C1 over the competition.
0 -
I rolled back to 20.1.0 and shot a whole day of Christmas portraits tethered without an issue. Being able to set capture folders and have names automatically generated depending on the folder name makes data management so much easier. Would need to test it further to say it definitely doesn't have the issue but I'm going to stay here until 21, hopeful it doesn't have the issue present.
0 -
Well, I didn't dare to buy 21 because of this issue. I did a rollback to some previous 20-versions and they all came up with the same issue. Next, I've tried the demo version of 21 and it also came up with the exact same behavior. As a next step, I did an uninstall of all C1 versions, wiped all PhaseOne driver stuff, cleaned up the disks as far it was related to C1 and cleaned up the registry. So there was not a single trace of a C1-installation left anywhere. Then did a fresh install of 20 again...without any result. The same for 21... As a next step, I performed a OS repair. Result: none... :(
Time for a massive approach: I've wiped the entire OS (W10Pro) installation and did a fresh OS install (no repair). And now, finally, the issue is gone. At least it is in 20. So I expect some intolerance between W10Pro x64 (initially installed somewhere in late 2017) and C1 causing the issue. Maybe due to one of many Windows updates (?), since there are other users experiencing the same issue while tethering with other camera brands. It took me a lot of effort. But finally, it's solved (for now...).0 -
Glad to hear you have resolved the problem but having to go that deeply into a Windows based fix process was inconvenient.
I have only once had anything like an OS update cause problems in C1 - nothing like as bad as you described but inconvenient anyway - with Win 7. That was an update and I rolled it back. A year or so later I had forgotten about the specifics and inadvertently applied a mass correction update of Win 7 and re-introduced the problem. As I could not recall which update introduces the problem and was unable to find enough Win update History to be certain I lived with it via a partial solution.
At some point in V21 beta testing the problem disappeared again in Win 7 for both Win21 beta and V20.
I am about to dive into the MS Win V10 cesspit of update policy. I have all crossable digits crossed that the experience will be less ghastly than one can read about on line.
0 -
I have been using 21 (Build 14.0.0) fine until today.
Now I get the auto adjustments hanging the tethering (Nikon D850), out of the blue.
Can't seem to fix it. Upgraded to build 14.0.2, no fix.
Uninstalled, reinstalled. New catalog, deleted user preferences, config.
Nothing works. Driving me mental.
Windows 10Pro
I have had to stop production and use a MAC laptop which isn't ideal.
This is nuts, what are the developers response to this?
0 -
I cant tether with any of the new versions. I have 20.1.0 just so I can shoot tethered. Must be a bug in the windows version and non apple development seems slow at best.
0 -
Or it might be a problem with Windows 10?
Do the log files provide any clues?
0 -
Well, this makes clear that 21 has inherited this vulnerability from previous versions. Good reason for you to submit a support request right away, because my request was closed by C1 the other day, after fixing it myself.
And a good reason for C1 to significantly increase priority to get this issue fixed on VERY short terms!
My guess: it has something to do with either your display/graphics driver, or the .NET-runtime environment. Maybe one of these (or both) were hit by updates? Because after C1 initial install, it will start executing some sort of finetuning procedure to speed up its performance. Once finished, it wil never come up again doing so. So it's a one time run. Would be nice if there was an option to start this procedure manually, as a workaround to fix the issue? Maybe there is, but I haven't found it yet...
@FirstName LastName, Why not giving it a try by stepping back to your latest restore point? Maybe you're able to roll back the latest Win10 update? Otherwise, try reinstalling your graphic driver and see what happens. Keep us posted here, please.
@Adam: so now you've bought 21, which is unable tot tether? And you're now on 20 again? Wow, C1 needs to get this one sorted out soon now! I've bought 21 too and it runs well for the last two month now... Not eager to run into the same troubles again.
0 -
Are there any fixes for this? Not fair for Windows 10 users! The only fix I've had for the auto-adjust hang is to close and reopen the app. But once I return to shooting tethered, its back to the auto-adjust hang.
Imagine a doing this a couple hundred times during a shoot....
0 -
Hi everibody.
I had the same problem yesterday while shooting at a client's showroom. Hopefully I still have a Lightroom subscription, but it's not the same.
I installed C1 20 une year and half ago and it never happened, but since yesterday I can't use C1. I uninstalled and re-installed C1 but nothing canged. I run C1 20 for Nikon Build 13.1.4.3 on Windows10.
Any fix for this issue?
Thanks
0 -
Hi @all tether issue victims,
This issue finally popped up again in my C1-21 last week ... on the very same day that I've updated my Graphics Card Driver ...
Completely Uninstalling that latest Graphics Driver (files AND Registry!) and have it auto-replaced by a generic Windows Driver did the trick to eliminate C1 to stall on auto update. YESSS!!! :):):) So somehow, somewhere, there is a slight incompatibility issue between C1 and my brand of Graphics/Video Adapter. And that confirms the fact that a fresh reinstall of C1 won't solve the issue (and a fresh install of Windows will do)
As far it might help you: I use a MSI GE72 series laptop, which is equipped with a nVidia GTX1060 adapter. (Yup, I know, aged parts by now :(). Installation of a dedicated nVidia driver (like the recent updated "nVidia Studio Driver", anyway, regardless which one), will (re)introduce C1 to stall at this point again. So now I'm curious what brand/type of Graphics Cards you guys use...
Hope this is of any help to someone?0
Post is closed for comments.
Comments
21 comments