Black files?
Hello C One 7 was installed and working fine for some time.
Today, ALL processed images (TIFF, 8 bit) are now all black. I changed nothing. RAW images show fine. Open Cl is on AUTO, everything worked fine until now!
Anyone else seen this behavior?
Jon
Today, ALL processed images (TIFF, 8 bit) are now all black. I changed nothing. RAW images show fine. Open Cl is on AUTO, everything worked fine until now!
Anyone else seen this behavior?
Jon
0
-
See a recent thread
viewtopic.php?f=47&t=130330 -
Same problem and same fix: Odd that with Open CL on auto it worked for some time and suddenly needs it set to NEVER to work.
P1 should fix this issue. Another annoying time waster.
Kind Regards,
Jon0 -
I got black files also...... 0 -
[quote="jonpaul" wrote:
... Odd that with Open CL on auto it worked for some time and suddenly needs it set to NEVER to work.
...
Yes, I agree. When I started in with CO 7.0, it worked just fine for quite a few days. Then it started acting up over a few days to a point it was unusable until I ran the "donotuse opencl" script. Nothing else on my system changed (to my knowledge) so it is difficult to explain what was going on. Even a so called clean install failed to get me back to square one, so I know that something somewhere was damaged.0 -
Strange symptoms.
2 thoughts came to me.
Firstly was that somehow some automated updates were messing with the system.
There are so many possible updates these days - Windows/iOS, graphics card drivers, maybe Java and who knows what else that the potential for adverse results is probably quite high. However if there is a similar pattern for iOS (is there?) then perhaps it's not an OS problem, nor a Java (or whatever else) problem. If it is anything to do with graphics cards then there ought also to be some observable pattern for those. Furthermore if it does not affect all installations of the same card/driver combination .... another reason to perhaps discount external influences.
Secondly, something that was erratic in when it made an appearance.
Using another package a few years ago things would be working fine and then rapidly slow in terms of performance followed by sudden crashes or less of files and edits. and similar. But not always.
The application had a setting to control the size of the working temporary Cache (within Java in this case). The idea was that by keeping as much recent edit work as possible in the available cache performance woould be perceptibly faster than reloading from scratch all the time. As the cache filled and spce needed to be free up the application calculated how much spec was required and attempted to find th oldest file or files that, if deleted from the cache, would make sufficient new space available to work smoothly.
Great idea and mostly seemed to work. But sometimes it seems it didn't. When I remembered to monitor the cache fill and manually delete files if it was looking a bit too full for comfort the problem went away for as long as it took to re-fill the cache if I forgot the check.
Now I can't reconcile that situation to a solution that involves turning off OpenCL - there does not seem to be an obvious likely comparison - but the nature of the timing and the seemingly sudden re-appearance of such problems may suggest a similar sort of underlying reason if the auto updates possibilities can be proven to be unconnected.
Grant Perkins0 -
Hello all: It is very interesting that many others have seen this issue.
To SFA, I do not think CO uses Java. Or that W7 sys updates are at fault.
My workstation HW and SW is not the problem, as both programs and graphics work fine otherwise. The RAM is 16G and the video card (Gigabyte GV-N98TSL-1GI nVidia GeForce 9800GT) is 1G VRAM and its drivers updated long ago.
Everything worked fine for about 2 weeks. Finally, No recent Windows updates (or otherwise) were installed between time it last worked and when it started to fail. And hardware has not changed in months.
I think its a bug deep in CO 7, probably in its use of Open GL.
Perhaps others with this issue can give P1 a HW and SW summary, or P1 can give us a tool (like the crash log) to gather system info in case of black files.
I feel that P1 tech support should be able to easily find and fix this ASAP.
I humbly recommend that P1 TECH add add a simple check function to the processing of any TIFF output file: If the resultant file is all black, delete it, turn open CL off and recalculate the process. It could be a temporary solution until the bug is found and fixed.
P1 should not burden the CO users with its SW failures.
Meanwhile we just turn off open CL (a nice feature touted for new releases!) and suffer the longer process times.
Kind Regards,
Jon Paul0 -
Hello Jonpaul,
I mentioned Java only as an example of commonly used applications that are "upgraded" regularly but due to their levels of interaction can be problematic to developers using them. As another example MS .NET has introduced similar challenges during its development lifetime.
In a similar context a company in a very different market and for which I have been a beta tester for several versions decided, some years and versions past, that the ability to extract text from PDF files would be very useful within their application. So they did some development, launched the product and promptly discovered that the majority of their customers were using some "non-standardised" PDF writing engines and so the files from those programs, which looked like PDF's in the PDF reader, did not interpret as expected using the code they had developed. Indeed some PDF's written by "correctly specified" prgrams did not convert well either. Some years of effort later (and at least a couple of new versions) they had developed a whole load of far more complex code than they thought would ever be necessary in order to support an array of customers using all sorts and ages of "PDF Writers" cobbled together by developers around the world on behalf of major business system vendors. Judging by the relative lack of new forum posts (on their forum) asking why the PDF method of data extraction does not work as expected, I'm guessing the problem is now mostly resolved but it all got a but heavy in there for a while and absorbed a lot of support and development time.
Internet Explorer has also been recognised over the years as a product that sets out some clear standards for developers (of web sites) to follow but does not always insist on or even respect its own rules. This can be quite a challenge for the unsuspecting code cutter. In fact even those that suspect that there may be "issues" cannot do much to mitigate them whilst they are still hidden.
It can take a while to gather enough information to work out what is going on - then a little longer to work out why. Unless, of course, the developers had some suspicions that things might not be entirely as they appear and possibly already have some ideas about how to do things differently. We might hope that is the case and that enough well documented examples allow for a solution to be created reasonably quickly.
Grant Perkins0 -
got black files too 0 -
[quote="Peter72" wrote:
got black files too
And the solution? (Because not everyone who posts also read posts)0 -
We are aware of this problem. We will get it resolved as soon as possible. Meanwhile use should just set "Use OpenCL" to "Never" for processing only. You should be fine for the "Display" part.
To help us, please forward your graphics card, and possibly driver version. This will help localizing the problem.
-Lionel0
Post is closed for comments.
Comments
10 comments