Capture One Express for Sony license doesn't work
Sorry to ask a question regarding the free version but is there a time limit on Capture One Express? I can no longer get the license I have to start the program, which has worked reliably for many months.
-
No time limit that I am aware of.
But .... what has required you to reactivate the installation?
Have you changed computers or some significant component of your system?
If so you may need to de-active the "old" activation and then activate the "new" one. You can do that after logging in to your account on line.
Also I assume you are writing about C1 Express for Sony or Fuji (or Nikon?) not a very old version from several years ago?
0 -
Thank you so much for your prompt reply! Yes I'm using C1 Express for Sony. I haven't made any change to my computer recently. A while back I had a hard drive problem and fixed it by going to a cloned back up drive. C1 noticed that change and at that time, months ago, it told me to deactivate then re-activate. I did this and everything was fine. This problem is different, when I try to start C1 a box pops up (I can send a screen grab if you'd like) it says top left License and below this Activate Capture One. There is a box for my license code, which is - 3475-MNUE-TCN4-E554 . When I enter that number the box pops up a new message which is to "Run Diagnostics" and below that "Unable to connect to server to look up profile". I did as you suggested and went on line to deactivate the program but that didn't seem to go to well. After I clicked on deactivate it gave me a message saying an email message was sent but I received no message...so far. I then uninstalled and re-installed the DEACTIVATED program with the same results above...the pop up box I mentioned. I was thinking of purchasing the program soon but as I am unable to get express working, for whatever reason, I'm afraid I might encounter the same issue with the purchase version of C1 for Sony. Let me know if you think there's any solution to my problem and once again thanks you so much for you quick response.
0 -
Ah, ok.
I have recently had that problem (Windows 7) and it is to to with revised security requirements for the server at C1's end.
Basically they now require certain security setting that my Win 7 system did not set by default.
Win 10 probably should set them ... but may not in all cases.
For Win 7 this was a useful reference document.
If you are running Win 8 or Win 10 then there may be some relevance although the expectation (I think) would be that the SSL/TSL settings would already be set by default. However, they may not be set, so it's worth checking.
0 -
SFA
Once again thanks for the quick reply. I DO indeed have Win 7 but after reading the link you sent I'm not at all sure I want to make those changes, as I'm not sure what impact they may have on how Win 7 operates in other areas. I guess that leaves Capture One a no go for me as I don't intend to upgrade beyond Win 7. That's too bad as C1 really has some feature I like very much.
Thanks again for your help...
0 -
Hi David,
I applied the suggested settings and all has been well.
I suspect that the only reason that they are not set in Win 7 by default is that back in the day when WIn 7 was released they were probably not commonly used and the defaults were have never been updated.
Sadly I think we will be forced to move on from Win 7 very soon. Microsoft will ensure that change one way or another If not to Win 10 then to another platform and right now I cannot think of a platform that is still being developed and supported which does not conform to the same sort of approach to obsolescence. Indeed most seem to offer a shorter period of support and compatibility but my prediction is that MS will do everything they can to go the same way.
In fact they all want a cut of the rental (subscription) model to the exclusion of anything alternatives.
Soon, perhaps, we will need an activation code for a monthly license to breathe.
0 -
With multi-boot systems being more common now, perhaps C1 can use a stripped down version of some OS to build on and then use that as a base and emulate and extend the other supports to the more popular platforms like Windows, maybe Linux?. But I too have had one issue or another and has kept me from using C1 as a main RAW capture processor, and I go back to LR.
If I was not able to use it on my Mac laptop with an old version I would have stopped upgrading my license long ago for the Windows use. But I keep doing it and with how things are, its not so easy to find a solution for the problem unless it is a widely common one. So I am the sucker paying every year, except more recently, itrs been almost bi-yearly with 21 coming out shortly..Sadly the users is not the one smiling to the photo shoot.I have posted in a couple other somewhat related topics on how I cannot get the newly tethered captures to render the image other than seeing a blurry mess of it. I restart C1 and it renders them until the next shoot, which I am back to blurry image.
This issue has happened before with no resolve. Its just frustrating, thinking I upgrade so things get better...Nope. New features added and less stability induced. Perhaps the tether capture can go back to the older extremely lean and fast roots of 3.7 or something, lol...OK, maybe with some of the new features, but at least it will be a tether tool, and then the full C1 processing? IDK, but maybe this is a simple issue that just never got resolved and I am going on about it for nothing. I dont know...I have Windows 10 with SSD drives, with 80+gb ram, with a 4K 6core i7 processor, C1 latest version, Sony A7RIII tethered with proper working USB cord(all tested and working on another system using MAC), Nvidia GTX970 I think has 4 or 4GB?....So It shoudl work...
Oddly, C1 was a Windows sw first, if I recall. :-)0 -
I like many of the features of of C1 but I have some very pricey hardware that apparently hasn't been made compatible with Win 10, and at this stage I don't think it will ever be, so I'm rather wedded to Win 7 for better or for worse. I still have and old XP computer that encountered the same issue, expensive hardware that NEVER migrated to Win 7, I still use it and all works well. To say the least I'm a fan of backward compatibility and for that reason I'll be looking at other software that will remain compatible with my system, too bad it won't be Capture 1 but so it goes.
0 -
Hi David,
If you are using a specific version that works on your hardware and software combination and that does not change then there is no reason that I am aware of for the application to stop working with whatever is currently installed upon it. Unless, of course, eventually something fails and replacement, whether hardware of software, becomes impossible or grossly uneconomic.
By way of illustration I have an old Sony desk top from 2003 (iirc) that was an XP machine but currently has Win 7 installed. I still use it with an old finance application that itself became obsolete somewhere around 2006 I think. So far they both do a job. The Graphics card failed under warranty. The fan on the replacement card failed and I was able to change that. The original HDD failed and was replaced. I use it for about 1 day a quarter and for doing annual tax returns.
I would not see a problem continuing to run C1 20 on Win 7 since if runs now. However at some point soon, since Win 7 has now been out of MS support for nearly a year, C1 will probably be justified in dropping any support through the support team. And I fully expect Win 7 support guarantees for new versions to be dropped imminently for the same reason.
That's not a problem, for a while, if the program still runs in new versions of Windows. However at some point the changes pushed by Microsoft and other vendors will mean some parts of the application will break and that will be that. And of course if any new functionality of camera/lens support needs come into your life your older versions may not be supportive of them.
All quite normal in the modern "agile development " world.
If you are running Express there is no cost involved for trying new releases to see if they work.
Back in 2013 I was forced to upgrade because both C1 and a business application with which I was significantly involved at the time (on a test project) were biting the bullet and moving to 64bit code at the behest of the Microsoft development path road map. Not much could be done to counter that but as it turned out the replacement has been a very sound investment.
There were some other very good reasons for moving to 64bit form 32bit code. One obvious reason was that the programs would be able to work with much bigger data sources that had many more records.
I think you will find that, in general, few if any developers will try to retain support for Win 7 into the future. The additional complexity and performance compromise their applications would face will make it a little pointless for both them as developers and their users in a year or two. Once the numbers of users fall there will be little point in making the effort even if it remains possible to offer support of new products - which it probably will not. Apple taught others that lesson in recent years.
More recently we have seen a rather stagnant global economic situation. Some think that one way to regenerate a buoyant economy is to stimulate growth by forcing things to change with planned obsolescence being a tool to that end.
There may be one or two half decent freeware products around that will possibly continue to be available in old versions but with some form of camera and lens updates possible. They are typically run on a non-commercial basis and updates, especially timely updates, are not always available.
It's awkward as a consumer. However I don't think the developers, like C1, would be able to realistically resist the "progress" even if they wished to do so.
I am perhaps slightly more fortunate than you in that my main notebook can be updated to Win 10. I'm just reluctant to do so when it is currently stable but it is also 8 years old and more than likely getting to the point that things will start to fail (not too much so far) and be difficult to replace.
At least this time the need to replace is not being driven by an fundamental technology change together with a machine that could not support 64bit and in any case had come to perform disappointingly when really not very old.
0 -
SFA
I can't tell you how much I appreciate your feedback...thanks so much for it. You've communicated and ENORMOUS amount of useful information that will be incredibly helpful to me and your insights are very profound. I'll be copying your post and using it as a much looked at reference in the future.
Once again...INCREDIBLE, and thanks again!
David
0 -
Hi David,
Thank you for your very kind comments.
I have edited a few parts of my previous post to correct some typos and make some points a little more readable (hopefully).
I rather suspect that anyone who has been around a while and remembers the early days of personal computing (and how expensive it was to do just about anything back then) will not feel entirely comfortable with the strong trend we see to influence and enforce the acceptance of "renting" computing services from providers who seems to wish to become ever more controlling on the pretext of providing a "better" solution.
By the time such a development can be truly assessed with any degree of realism I think we can be sure that there will be few options available - especially in a technology controlled world.
An example.
In the post today someone had sent me a cheque. Quite unusual in these days of electronic banking. In the past I would wait until I had a few cheques and then go to the local branch of my Bank to pay them in. I could do that while doing some regular shopping.
That Branch closed down earlier this year. The next nearest is further away and not anywhere I tend to visit regularly.
I think I can use a local 3rd party facility but that is not without some potential concerns in my opinion. Heck, the banks can be bad enough on their own!
So I checked the bank web site to see what they suggested. Paying in cheques was not a subject I could find anywhere.
I am aware that other banks (and some ATMs) provide an electronic paying in facility via a hole in the wall machine. My now closed branch had one on the banking hall and I used it last time I paid in some cheques.
No mention of that that I could find.
I know that most banks now have a service via a web app as part of their Mobile Banking strategy that offers the option to pay in cheques using a mobile phone camera scan. So I checked the mobile app and - sure enough - there was the facility. Great!
The downside is that the last time my Bank updated the App they allowed me to install it but forgot to tell me that the new version would not work on my phone. Eventually I discovered that the version of Android was too old. Thus the phone would need to be replaced. That was about 2 years ago when the phone was only 3 years old.
Checking today the only thing that has changed in that, having delete the App the Play Store does not offer it any more for installation - it knows my Android version and/or phone is not compatible.
As for my other equally old business phone ... well, that is a Windows phone and Microsoft, having bought Nokia just after I got the phone for its potential Windows integration options, quite swiftly changed policy tracks and abandoned Windows Mobile. For now the phone still works although some applications stopped working some time ago.
To paraphrase some old observations - the only thing that is certain these days is that nothing is certain. Except change. Maybe. But not everything changes, especially in the area of human planning.
0
Post ist für Kommentare geschlossen.
Kommentare
10 Kommentare