7.1.4 Pro crashes ...
... when I try to import files. It also doesn't show thumbnails (jpeg or raw) in the catalog (just outlines with a message about can't locate / incompatible format, although they are correctly located).
Both the catalog and pictures are on a network drive, which is accessible even from CO (via the session mode). Everything was fine in earlier versions.
This is Win 8x64.
I have tried reinstalling, have the latest AMD drivers.
Both the catalog and pictures are on a network drive, which is accessible even from CO (via the session mode). Everything was fine in earlier versions.
This is Win 8x64.
I have tried reinstalling, have the latest AMD drivers.
0
-
[quote="Paul_Steunebrink" wrote:
Relax Jim. I explicitly mentioned session. Does not apply to catalog.
<sigh> You know, Paul, I'm as relaxed as I can be, considering that I seem to be stuck in software that is making my life more difficult than it should. I'm trying to get a lot of work done using a tool that stops working from time to time, forgets what it was working on, Still does some annoying things incorrectly, and, need I go on? catalogs are problematic for a few reasons. Some people are getting around those issues by using sessions, but that's not an option for me, for reasons that YOU have explained. MY solution is getting more obvious by the day. I'm just glad that you had a 50% sale last year, when I bought Capture One 6. I'm just sorry I didn't decide on that other product back then. I think I might have saved myself some annoyance. Really.
The product doesn't work the way a pro product should. That is to say, it falls seriously short in the reliability department. 7.1.3 rollback has been my remedy to date, but, if I don't see another release soon, and one that fixes the issues I've reported, then I'm outta here and on the the product that the pros I know are using. It'll cost me a little less than the price I paid for C1 last year. What can I say? "Disappointed" is not quite an adequate term for what I'm feeling about this product right now.0 -
I have been running 7.1.4 without any crashing issues. I'm just curious as to the hardware you're running. When I first started using CO 7 I had all kinds of issues. I eventually upgraded my video card, and power supply to meet the demands of the software. I don't use the catalogs so I can help there, but the freezing is either a drivers, or hardware related issue.
Hope this helps.
Paul0 -
Well it's Oct 2013 and I also have crashes, lockups mainly. I was told to upgrade my Graphics Card. Well I went one further I replaced my M/Board, 750w PS with a 850w P/Supply. Reinstall win8 64bit and replaced my Graphics card with a Titan. My i7 3.4G with 32Gb of Ram, 2 x SSD 480Gb drives with 1 x Sata 1,5Gb Drive plus 2 x USB 2.5 Gb Backup Drives connected to my FileServer over a Gigabit network still is slow with CO7.1.4. I do all my work from my second SSD drive.
All other software flies. LR is about to become my default program for my photos now.
Could someone from Phase One please let us users know if they are working on this or at least looking into why some of us have problems are some aren't?0 -
In an attempt to mitigate crash issues, have any of you deleted the compiled OpenCL kernels after update to 7.1.4? I have seen some amazing recoveries lately.
How to:
- close CO7
- delete C:\ProgramData\Phase One\Capture One\ImageCore\ICOCL.BIN
- start CO7
CO7 will now create ICOCL.BIN again, which can take a few extra seconds, slowing startup only this time.
Hope this helps.0 -
[quote="Jim Casler" wrote:
[quote="Paul_Steunebrink" wrote:
Relax Jim. I explicitly mentioned session. Does not apply to catalog.
<sigh> You know, Paul, I'm as relaxed as I can be, considering that I seem to be stuck in software that is making my life more difficult than it should.
...
What can I say? "Disappointed" is not quite an adequate term for what I'm feeling about this product right now.
Jim, I sincerely feel sad for your misfortune regarding CO7 in its current state on your system.0 -
[quote="Paul_Steunebrink" wrote:
In an attempt to mitigate crash issues, have any of you deleted the compiled OpenCL kernels after update to 7.1.4? I have seen some amazing recoveries lately.
How to:
- close CO7
- delete C:\ProgramData\Phase One\Capture One\ImageCore\ICOCL.BIN
- start CO7
CO7 will now create ICOCL.BIN again, which can take a few extra seconds, slowing startup only this time.
Hope this helps.
Yes Paul I did this..and it didn't make a difference CO7 didn't want to start ...I rolled back to 7.1.3 ..now looking at LR5 as a CO replacement due to buggy software although LR5 isn't what I really want ..what I really would like is a CO that just works as advertised !! ..its just too darn hardware sensitive and in a world of PC users each machine is so different0 -
From the middle to I am sorry
If I am also 7.1.4 Pro, I cannot import a photograph.
If it is 7.1.3 Pro, a photograph can be imported from NAS of QNAP.
The error of 7.1.4 Pro cannot be read from a folder.
Please teach me a solution.0 -
[quote="NNN635089805724523973" wrote:
From the middle to I am sorry
If I am also 7.1.4 Pro, I cannot import a photograph.
If it is 7.1.3 Pro, a photograph can be imported from NAS of QNAP.
The error of 7.1.4 Pro cannot be read from a folder.
Please teach me a solution.
Are you using UNC paths to your nas ?0 -
[quote="Christian Gr" wrote:
[quote="NNN635089805724523973" wrote:
From the middle to I am sorry
If I am also 7.1.4 Pro, I cannot import a photograph.
If it is 7.1.3 Pro, a photograph can be imported from NAS of QNAP.
The error of 7.1.4 Pro cannot be read from a folder.
Please teach me a solution.
Are you using UNC paths to your nas ?
Thank you for your reply.
Of course, since it is LAN in a house, it passes along the path.
However, C1 is going down the class using GUI.
It access from the network of OS(Win7 64bit).
It can access also from Adobe Bridge (CS6).0 -
[quote="NNN635089805724523973" wrote:
[quote="Christian Gr" wrote:
[quote="NNN635089805724523973" wrote:
From the middle to I am sorry
If I am also 7.1.4 Pro, I cannot import a photograph.
If it is 7.1.3 Pro, a photograph can be imported from NAS of QNAP.
The error of 7.1.4 Pro cannot be read from a folder.
Please teach me a solution.
Are you using UNC paths to your nas ?
Thank you for your reply.
Of course, since it is LAN in a house, it passes along the path.
However, C1 is going down the class using GUI.
It access from the network of OS(Win7 64bit).
It can access also from Adobe Bridge (CS6).
As a work-around you can map the network drive to a letter instead. Now CO will handle it. It's a known bug, and is fixed in an upcoming version.0 -
We have released Capture One 7.1.5 for Windows only to address the crashes experienced by some users. Download it here: https://www.phaseone.com/en/Downloads/C ... Pro-7.aspx
Should you still experience issues, don't hesitate to contact our Support Team right away!0 -
Hello Christian Gr
Please accept this post as directed at Phase One rather than you as an individual.
A couple of weeks ago I bought into Cap1 7. Unwittingly I downloaded the then latest version, 7.1.4, only to find it was crashing all over the place. I then discovered this forum and found I was by no means the only guinea-pig being used to test and give feedback on my awful experience. Fortunately I discovered 7.1.3 and all is as it should be (I think).
So, where is the apology from Phase One to all their customers who struggled and swore at 7.1.4?
Will I be trying 7.1.5? Of course not. I have learned my lesson.
Strangely enough I am just trying a v9 manifestation of one of your competitors. As usual their first release of a significant upgrade is running smoothly. Makes you wonder, doesn't it?
I leave you to feed this feedback into the Phase One system.
Best wishes.0 -
[quote="Peter" wrote:
Hello Christian Gr
Please accept this post as directed at Phase One rather than you as an individual.
A couple of weeks ago I bought into Cap1 7. Unwittingly I downloaded the then latest version, 7.1.4, only to find it was crashing all over the place. I then discovered this forum and found I was by no means the only guinea-pig being used to test and give feedback on my awful experience. Fortunately I discovered 7.1.3 and all is as it should be (I think).
So, where is the apology from Phase One to all their customers who struggled and swore at 7.1.4?
Will I be trying 7.1.5? Of course not. I have learned my lesson.
Strangely enough I am just trying a v9 manifestation of one of your competitors. As usual their first release of a significant upgrade is running smoothly. Makes you wonder, doesn't it?
I leave you to feed this feedback into the Phase One system.
Best wishes.
Maybe you should indeed try 7.1.5, you have nothing to loose, as you can always find the old versions and downgrade, if you really want to. You will find that 7.1.5 is running more smoothly and more stable than both 7.1.3 and 7.1.4.0 -
[quote="Peter" wrote:
Strangely enough I am just trying a v9 manifestation of one of your competitors. As usual their first release of a significant upgrade is running smoothly. Makes you wonder, doesn't it?
It is sometimes enlightening to read around web forums to make a quick assessment of the views of others, though one has to accept that humans like to complain about things and sometimes praise although the majority will say nothing and perhaps have neither cause for complain nor cause for praise above their original expectations.
I have no idea which V9 product you are talking about but I have just performed a quick Google trawl and come across a discussion for a newly released product that seem to suggest a few people are having problems with crashes and performance and a larger number are not reporting seeing those problems but are unimpressed with the results they are seeing compared with whatever they have as a current favourite tool. There seems to be a familiar pattern to all of that.
I'm pretty sure I could find something much the same, in one aspect or another, for every application out there.
For what it's worth my C1 V7 installation has been remarkably stable - more so than a new Windows V7 installation on the same new machine - for the past 7 months. No doubt others are having a similar experience to me but not finding a need to say much about it.
I have enormous sympathy for anyone suffering poor results for whatever reason but if some are suffering yet the majority are not even when using the same downloaded installation files it suggests to me that there is more to the issues than simply pointing at QA processes and suggesting there are none in place that are effective.
Of course everyone is entitled to their own opinion and the right to share it somewhere should they so choose. Phase seem quite generous in terms of accepting negative opinions. Other places are not always quite so welcoming.
A cent or two from me, probably not worth much.
Grant Perkins0 -
Hello Christian GR
You wrote:
"Maybe you should indeed try 7.1.5, you have nothing to loose, as you can always find the old versions and downgrade, if you really want to. You will find that 7.1.5 is running more smoothly and more stable than both 7.1.3 and 7.1.4."
Sorry, I am not a masochist. Also, I do not knowingly clutter my computer with software that has a history of problems. I am waiting to see what others make of 7.1.5. For the moment 7.1.3 suits me well - "if it ain't broke don't fix it"!
GFA/Grant Perkins always produces thoughful posts. Perhaps Phase One should make more use of him?
The bottom line, for me, is very simple. If I spend £200+ on a software package that is in its 7th generation I expect it to work. For me, and others, 7.1.4 did not, and there is no guarantee that 7.1.5 will be any better.
Best wishes.0 -
It doesn't hurt to try. It's painless and doesn't crash.
Paul0 -
My situation is like Jim Casler's, except I use Sessions.
I was having some rendering issues. At sometime working, the selected picture gets stuck in a slightly pixelated state. It doesn't complete the rendering of the image to display clear and sharp. Other selections are the same. So I updated to 7.14. Using Sessions with source images being on a network it never launched for me. I sent a bunch or the reportings with added notes, but never heard back in my email.
But I did see an update 7.15 I have the rendering issue MORE often now. So I have to restart each time. This is PAINFUL, as C1 for some reason take a LONG time to populate the thumbnails to start working on the last file. Why not let this occur in the background?
Other thoughts suggestions for C1 users:
This maybe not popular, but I wish C1 would have a Shoot version. I was VERY happy with the stability of 3.78 etc.
It was super fast, and no fuss shooting. YES I love the new dev engine. But I don't use ANYthing like gradients, local adjusts, etc.
Once the master image is taken with PhaseOne Db, then developed in C1, I do all the others on a TIF in PS or Lightroom.
My master image is developed in C1, I can't afford to work with a new animal of tools on a unstable system when I can get the best developing, and then the easiest and stable LR or PhotoShop to further enhance my images.
C1, I use Crop, Develop tools, Focus Sharp tools, and Color tools. All the rest I personally have ZERO use for. It sounds like MANY here can gain from such practive. Perhaps C! will one day deliver such a version to meet our needs.
If not I wish C1 would open up their RAW files for other companies besides just Adobe. I would like DxO and others to have the ability to develop, and perhaps even tether with it. These options would help Phase and C1 keep a professional reputation while it plays "catch-up" with the temporary success the "popular" folk follow and struggle in some occasions.0 -
Raffi,
Do you always load into the same session. Or maybe a default 'session' as a starting point?
I cannot be sure but your problem sort of sound similar to one I had a few months ago. Several thousand images in a folder and scrolling through using the browser C1 would suddenly freeze. Crashing the application was the only way out.
Eventually I spotted a badly created thumbnail. It refused all attempt to re-generate it correctly so I deleted the edit file for that image in the session. After that all worked well. I added a new edit to the problem file and had no further problems.
I wonder if your problem is something similar - maybe an random error in the cosession database? It is difficult to know or to suggest an approach to diagnosis without knowing what you do for each session and my similar looking problem could have a completely different cause - but it should not take too long to see if you have something similar in the session(s) that are causing problems.
HTH.
Grant Perkins0 -
I Grant,
thanks for the reply,
Yes, I use the standard My Pictures/CaptureOne Sessions...etc
Then I reroute the Capture Folder to where I need the files to go as I shoot. Then process out to yet another folder I prefer.
I've found the standard stack of folders C1 automatically makes to be confusing, redundant, and simply littering all over my folder structures. I wish it would stop such wasteful practices and let the user control where and when to make such folders.
7.13 was not crashing, nor is 7.15. 7.14 was crashing without ever taking off.
With that many images, how did you find the problematic thumbnail?
I had this happen a few times recently, and I am pretty sure they were different projects, different thumbnails.
I'm willing to give it a go. I'm a bit limited with my knowledge regarding C1 internal processing and file usage, so I hope I can help....but always willing to learn 😊0 -
[quote="Raffi3" wrote:
I Grant,
thanks for the reply,
Yes, I use the standard My Pictures/CaptureOne Sessions...etc
Then I reroute the Capture Folder to where I need the files to go as I shoot. Then process out to yet another folder I prefer.
I've found the standard stack of folders C1 automatically makes to be confusing, redundant, and simply littering all over my folder structures. I wish it would stop such wasteful practices and let the user control where and when to make such folders.
7.13 was not crashing, nor is 7.15. 7.14 was crashing without ever taking off.
With that many images, how did you find the problematic thumbnail?
I had this happen a few times recently, and I am pretty sure they were different projects, different thumbnails.
I'm willing to give it a go. I'm a bit limited with my knowledge regarding C1 internal processing and file usage, so I hope I can help....but always willing to learn 😊
Hi,
It sounds like you have a rather different normal requirement to me - I don't often shoot tethered as I suspect you do.
I am not bothered by empty folders that are always in a known location. I don't use selects though perhaps I use deletes more! I find Output very useful although I did not realise how useful it was for some time after starting with C1.
My other favourite editor was and is a similar open folder style rather than a catalogue centric design so starting with C1 I ignored the extra folders as I was used to creating my own structure. However, when I thought about it a bit more it just seemed like I was doing something (probably less than successfully some times) that C1 could do for me just as well. At least for my purposes. It might not suit everyone.
I noticed the faulty thumbnail by chance at the time although I would have arrived at it eventually as I was processing the session's images. When visible it was very obviously faulty.
The problems I had seemed random, sort of, although scrolling through would tend to crash at the same image. So I would delete or move that image after restarting, carry on and have the same problem some images later. And so it went. After a while I was coming to the conclusion that it was probably not the individual images at which the scrolling failed that were in fact the source of the problem. So I was trying a few things from different places in the set - using different sort order selections and so on, and happened to see a thumbnail that was about 2/3rds processed. I tried to regenerate the thumbnail but the result was exactly the deleted the edit file and re-edit the image and normal operation returned.
I think what may have happened was that the session database, for whatever reason, had ended up with a bad internal link and so was attempting to making the wrong connections between files somewhere. (In very simplistic terms). Removing the offending edit file 'link' in the database fixed the error in my case. I don't think there was anything wrong with the edit as such - it worked but the thumbnail build didn't. It's the only time anything like that has happened so I think it was just a glitch.
If 7.1.5 seems to be OK it may be that your problem has (or had) a similar underlying cause but for a totally different reason. Quite honestly if you are not seeing the problem in 7.1.5 I would suggest that you don't worry about it and carry on enjoying your sessions.
If you find a thumbnail that does not look right firstly try re-generating it. If it still looks the same be prepared to re-edit the file. Probably best to discuss how to do that if the need arises since there are safe ways to approach it without losing anything unnecessarily but what the actual steps are may vary a little depending on what work you have done to the image up to that point (Local adjustments for example ....). And of course having something that sounds like the same sort of symptom does not guarantee the success of the same solution so a little caution may be required to ensure getting to the most effective resolution of the problem as quickly as possible
HTH.
Grant Perkins0 -
Thanks for explaining that as I am still having this issue with 7.15.
I would love to hear the step to regenerate etc. Its OK that I have to re-edit as I have many like files with the same edit.
The output for me I have needed more specific TIF_Processed. Selects for me are not an issue as under Tif_Process as Sharp. This is because once I process the Raw, then I make a base sharpenss ready for PShop or LR enhancements.
C1 for me as been for many years the workhorse, not the multi faceted Jack of All Trades Swiss Army knife! It is my Chef knife. And thats what one does, uses the right tool for the job. No gimmicks. C1 to LR to PS to LR to Final, along with a proper browser/DAM application. Even LR is a half-a$$ DAM. It just doesn't work in fast pace editing. It is there 70% , but not having a LIVE browser and needing to Synch to see what is there is counter intuitive.
Since C1 3.X I have tried to adapt, I have taken all courses and since it is not a daily routine (more weekly), and I use other apps that ARE more standard to OS way of working, it has been hard to adapt even after 9 years..But I know most every function I need. Thanks0 -
Oh, and the Capture folder is called "RAW" 😊 0 -
Raffi,
I am getting the impression that you are happy enough diving into file systems so ...
Before continuing have you run the "Check document" process from the C1 File menu? I'm thinking about the Pro-forma session file I assume you use as the basis for each new session you create and save. The Check seems to be useful for an empty session structure verification but for any of my sessions that are or have been actively worked on it always seem to report a failed status even though the session seems to be fine to work with. There may ba a specific purpose to the Check routine with which I am not entirely familiar. With that in mind ...
Firstly, if you have not already tried this, just create a completely new session from scratch. Leave it untouched - no folder deletions or name changes for example and work with it to see if the same problems occur. If they do it might suggest that the problem is not a purely session related issue and that is important to assess if you want to avoid spending a lot of time chasing a phantom that appears randomly.
Secondly you can try some fixes for an existing session. There are some posts by Paul Steunebrink on a few threads in the forum that cover this and they would be worth reading but I'll tell you what I did for my problem as well.
Obviously you should back up your session before doing much digging around - or work with a copy of the entire session.
Now, I usually import images from a card so I have a folder (or several folders in my case as I keep content separate by camera and possibly even greater granulation if, for example, the camera creates a folder per day or per month ) in the session structure that contain s the original files. If you have not imported a folder related to the session might be anywhere. However the folder containing the original files that you have accessed in the session will have a sub-folder for Capture One use.
At the top level folder for the session you should find a ".cosessiondb" file. This contains the links to keep the session together.
In a fully imported session or, usually, a tethered capture session you should also see one or more folder that contain your original images. Each of those folders will have sub folders created by C1. If you have not imported the folder will be referenced by the cosessions file but will have been left wherever they were originally and the sub-folder should be found there. Note that there may also be a cosessionsdb backup file if you have at some point after the session was created upgraded C1 version or, in some of the updates for V7, changed from one release to the next where fundamental internal changes required regeneration of the cosessiondb files. Backups were created in case anyone should have a need to roll back to an earlier release.
So, in your Originals folder you will also find a Capture One folder if C1 has been used to access the files.
In the Capture One folder you should find two more folders. Cache and Settings70 (Settings50 for V5 and V6 of C1)
The Cache folder contains a subfolder called Proxies and in there you will find .cof and .cop files. Basically pre-created Preview related files that can be recreated (or are recreated automatically) when edits are applied. If is likely that is os one of these that is displaying as a corrupt output but the corruption will be caused by something else during its creation. You can delete one of all of these files and C1 will regenerate when next required. They are, as is evident, named for the original files.
The Settings70 folder contains .cos and, maybe, .comask files for any files that have been edited in some way. So RAW files will have a .cos file as they will always have some settings recorded for them whereas unedited jpgs will not have a .cos file unless they have been edited. (It can be slightly confusing if the Windows system is not displaying file extensions since the full file name shown includes the RAW name extension (e.g. <name>.CR2(.cos) which, at a glance, seems to indicate the presence of a full RAW file which is not normally the case!)
.comask files exist for images where local adjustments have been applied.
Now here is where we discover whether what worked for me will work for you. (You have taken that backup right?)
Figuring that my problem had something to do with the links in the cosessiondb file - in that the problem appeared seemingly randomly anywhere in a set of files displayed in the browser even if they looked fine themselves - I deleted the .cos file for the image I had found that had the obviously corrupt browser thumbnail. In effect this left the image unedited.
Returning to C1 and accessing the folder containing the original file meant that C1 'rediscovered' it, a new .cos file with just the basic conversion information but none of the edits was created and, presumably, the database cosessiondb file was updated with the new file and links information. Whatever it was that actually happened the newly generated thumbnail and preview was fine and the problem I had with scrolling through the browser disappeared.
I think it might be possible to arrive at the same result by deleting the file through the C1 Delete function, restoring the original RAW file from a pre-saved copy or the backup and re-editing. Indeed if my suspicion about the internal links is correct the .cos file for the original RAW might also be OK and perhaps could be re-instated as well thus saving all edits. However I also suspected that the problem originated in my attempted restore activity after an inadvertent deletion action so at the time I was a bit wary about my knowledge of the delete process and did not have the time to get into studying and analysing it. I thought I would leave that until it happened again. So far, after several months and many sessions, it has not happened again.
Having described that - if you are seeing the problem in every session you create the solution required may be specifically different. If you are starting from a 'My Session' type recipe and renaming the session it could be that the original pro-forma session file is the source of the problem. Hence the suggestion to create a completely new session to see if that too ends up suffering the same problem.
I did think about digging in to the database file directly to look for something 'odd' but once the problem was resolved and did not return to do so seemed unnecessary.
I am mindful that your problem might be very different at source but given the circumstances this procedure, or a variant of it, is probably worth trying since it does not take long and there is little or nothing to lose.
HTH.
Grant Perkins0 -
Ok, I'm gonna print this one out, and take it step by step 😊
Yes, I edit and can do command line, regedit etc. just don't know much program language past basics of basic...I did a little Unix/Python ages ago. 😊 OK! so...let me get on these instructions.0 -
[quote="Raffi3" wrote:
Ok, I'm gonna print this one out, and take it step by step 😊
Yes, I edit and can do command line, regedit etc. just don't know much program language past basics of basic...I did a little Unix/Python ages ago. 😊 OK! so...let me get on these instructions.
They have more words than they need as basic instructions - I get the impression that you like to have an understanding to support the "do this, do that".
Drew's guide to creating the session structure you want is more direct - as it needs to be for that clearly defined purpose.
The diagnostic path for the problem may be direct .... but maybe not, so I included a broader picture of my experiences some of which, maybe not all, might be applicable for your problem. No coding required. Just a careful investigative approach that can be reversed easily if the problem is not resolved.
Strip out the filler words and the steps are simple enough.
Grant0 -
I appreciate and prefer the thorough explanation.
I also submitted a ticket to support as Drew recommended. I still think a lot of folks would greatly benefit from a C1 "Shoot" version without the catalog, bells and whistles and just simple fast workhorse...not some jack of all trades with local adjusts, and special gradients, with bloated overhead, fumbling ever new step it takes.0 -
[quote="Raffi3" wrote:
I appreciate and prefer the thorough explanation.
I also submitted a ticket to support as Drew recommended. I still think a lot of folks would greatly benefit from a C1 "Shoot" version without the catalog, bells and whistles and just simple fast workhorse...not some jack of all trades with local adjusts, and special gradients, with bloated overhead, fumbling ever new step it takes.
My feeling is that C1 is about right. I can totally ignore catalogues. I do use local adjustments. They are simple enough and only there when you make them there. That functionality might do a little more at some point but they cover most needs. I have another editor that can stretch the local adjustment facility if I feel a need to take that path. It's a bit more involved to use but offers more functions and features. Good when you need them, somewhat time consuming, compared with C1, when the changes are relatively simple and quite common.
I don't have Photoshop. (Well, except elements V2 that, iirc, came with a Pentax Optio some years ago. I don't think I ever used it.). I have a similar application to PS that I really don't feel at home with but use it, only if I must, maybe 2 or 3 times a year for specific images or requirements.
I think I may be typical of the Software industry in general in that at least 80% of the programs I have purchased over the years were never or hardly ever used. Some not even installed. In fact when 'bundles' have been available at an attractive price they have often meant that stuff of no interest was included so I suppose a non-installation or several is no surprise.
For me, especially since I upgraded my hardware to allow me to use 64bit applications, C1 is stable, as fast as I can sensibly use to work with an editor and offers about 99% of the functionality I typically need. Maybe if I move into other things that will change but right now it's fine and especially as I have discovered how to let it do more and more of the simple "filing" stuff for me.
However I can understand that others may have a different opinion.
Grant Perkins0
Post ist für Kommentare geschlossen.
Kommentare
57 Kommentare