Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Why do some of my 16bit TIFF files fail in Adobe Bridge

Lance Blackburn
I have just "upgraded" to Windows 10 and now my 16bit TIFF files are corrupted when I open them in Adobe Bridge. Sometimes the first TIFF file that I upload in a session will be fine, but then each file after that is corrupted in some way. The thumbnails in Bridge, and also when I open the full image in Photoshop, I sometimes almost completely red file, then sometimes black and white squares and sometimes a full white file. Sometimes I have an out of focus thumbnail and when I try to open that thumbnail I did get an error message saying: "Could not complete your request because of a problem parsing the TIFF file".

Anyone else having this issue?
0

Comments

6 comments

Date Votes
  • Lance Blackburn
    It seems to happen with jpegs or any output file type..
    0
  • SFA
    Assuming you have the default option (Preferences) to deploy OpenCL when processing set to "Auto" you could try changing it to "None", reprocessing a problem file or two and checking if anything is improved.

    I am assuming that you have a GPU that is powerful enough for C1'a pre-assessment to decide it can make use of it. I'll also assume that you have not installed a Win 10 "Insider" beta release.

    If switching OpenCL off (None) makes a consistent difference then it would suggest that the WIN 10 driver for your GPU may not be working optimally. You could check for updates in Windows 10 but you may need to go to the GPU software provider's web site and work our which alternative driver it would be worth installing and testing. You may fins some useful guidance via a web search - unless you are unlucky enough to be an early adopter for the particular combination of WIn 10 release/hardware/Device driver software.

    If that's not the problem .... then you need to have a look at the C1 log files to start a better understanding of what seems to be happening. Maybe open a Support Case for that one ....



    Grant
    0
  • Lance Blackburn
    Thank you very much for your help. It seems that changing OpenCL to "never" rather than "auto" has fixed the problem, why that would work I have no idea. Do you know whay?

    The GPU is definitely plenty powerful enough.

    Thank you very much, Grant! 😄
    0
  • SFA
    [quote="Lance31" wrote:
    Thank you very much for your help. It seems that changing OpenCL to "never" rather than "auto" has fixed the problem, why that would work I have no idea. Do you know whay?

    The GPU is definitely plenty powerful enough.

    Thank you very much, Grant! 😄


    Glad that was of some use to get you going.

    OpenCL is, as its name suggests, Open in development terms. Another description would be "leading edge". Some might consider it "Bleeding edge".

    It's a great idea to use the GPU facility to speed up processing and take load off the CPU. However it's all relatively new and still developing and there are a lot of vendors and people involved in the chain of sub components that go towards making it all work. Sometimes things get out of step and for a while one might have to revert to the "slower" (maybe, much depends on what you regularly do in editing terms) approach using the CPU only.

    Normally the problems revolve around the driver program that interfaces an application to the hardware and the software that the hardware uses to run itself. They don't always work in all circumstances and applications interfaces may work fine with one release of a driver but not with the next.

    However there can be other reasons too. For instance a modification to an application to introduce extended or even just re-written functionality may appear to work fine in testing but suffer from erratic performance in some situations "in the field" for reasons that are not immediately obvious.

    Usually device drivers come with the Operating System. Unfortunately problem drivers, that may work well enough for 98% of most users and their often simple needs, may not be updated in a very "timely" fashion by the operating system supplier. In other cases the hardware or software may need something particular to work correctly but an OS update overwrites the code that they need.

    All you can really do it run the check for updated drivers for the device - windows has a utility to do this as you may know, and see what happens. In most cases it will tell you you have the latest and greatest version.

    In that case you need to do a little research to find the recent versions of the device driver as made available by your computer manufacturer or, possibly more likely, by the organisation that writes the drivers for the GPU control code. Even they don't always get things right. There are times when the "latest and greatest" driver will not be a good choice. However it's easy enough to check what you have, decide whether you need to consider moving up to something more recent or whether you should perhaps go back one or two releases.

    If you can provide details of your system here - Operating system version and GPU card details in particular - there is a good possibility that someone will have relevant experience with the same or a very similar configuration.

    Or you could raise a Support Case with the C1 support team and see what advice that can offer. A benefit of doing that is that it is possible that you have stumbled across a new problem in the chain of controls and Phase might find it useful to be able to gather some information about it. This would certainly be the case if the device driver turned out not to be the problem.

    HTH.


    Grant
    0
  • Lance Blackburn
    Hi Grant,

    I did do some research and found a driver update for my Nividia GForce GPU. After the update, I reverted back to "Auto" in both cases for "Hardware Acceleration" and it all seems to work fine now.

    Thank you again for your assistance. Much appreciated.
    0
  • SFA
    [quote="Lance31" wrote:
    Hi Grant,

    I did do some research and found a driver update for my Nividia GForce GPU. After the update, I reverted back to "Auto" in both cases for "Hardware Acceleration" and it all seems to work fine now.

    Thank you again for your assistance. Much appreciated.


    Excellent news.

    It seems likely that driver updates are becoming something to monitor outside the usual "OS updates will deal with it" standards.

    If I suspect I may be missing something sue to lack of device driver updates I usually check through Windows (7 in my case) first and invariably there is no update "found". Checking the developer's own information (NVidia in my case too) will often show that there have been several updates although not always containing (documented) changes relevant to my lowly card.

    However one still has to be cautious. One of my early updates for this card introduced problems and I had to step back one release to eliminate them. From memory that was still 2 or 3 releases beyond what was originally installed and the regular check through Windows and the PC manufacturer's own site had offered nothing.

    Glad my pointers proved to be of some help.


    Grant
    0

Post is closed for comments.