Skip to main content
Participating Frequently
November 18, 2008
Question

Change in EXR open from CS2 to CS3 can this be fixed?

  • November 18, 2008
  • 166 replies
  • 259016 views
It seems the monkeys have been at the file formats again...!

Open an exr with an alpha in CS2 and the image displays normally and the alpha is retained.

Open an exr with an alpha in CS3 and the alpha channel is applied to the transparency and then lost... which is really STUPID considering you might apply 0 alpha values to parts of the image you retain visually, as you might just want to use the alpha to drive an effect and not just be myopic and think it's just for transparency.

So, can this be fixed? I can't see any info on it?

Will CS2 non intel plugin work on an intel system in CS3

If not, effectively PS is useless for exr work for us.

Or is this fixed in CS4?
    This topic has been closed for replies.

    166 replies

    Chris Cox
    Legend
    February 4, 2009
    Brendan - you should be working in larger tiles (256 rows, or 256x256 makes a good starting point) instead of writing a row or a small area at once. The fewer times your plugin calls back into Photoshop, the faster it'll run. (we have a lot of cross DLL overhead to deal with, plus error checking on each and every call)
    Participant
    February 4, 2009
    Apologies!
    Known Participant
    February 4, 2009
    Travis,
    >C:\Program Files\Adobe\Adobe Photoshop CS3\Plug-Ins\File Formats

    Note that this is a Macintosh forum.

    Neil
    Participant
    February 4, 2009
    Participating Frequently
    February 4, 2009
    "We also use ProEXR sometimes, but it is really sloooooow, so at the moment we have a separate machine with CS2 installed and save all our EXRs as PSB files, which is very annoying too."

    Christoph, I'm aware of the speed issues when dealing with big images. The slowness is actually not within ProEXR itself but with Photoshop when I request/provide pixels. You can verify this by checking your CPU meter in those instances and seeing that none of the processor cores are very active. ProEXR is currently optimized to use as little memory as possible, but perhaps that's not meshing with however Photoshop works internally.

    I'm in the process of experimenting with different combinations of memory usage and pixel region requests - hopefully it'll yield some improvements.

    I'd welcome any help from Adobe on this one!

    Brendan
    Participant
    February 4, 2009
    The time wasted arguing here could've been spent implementing all the remaining useful features of OpenEXR.
    Participating Frequently
    February 4, 2009
    holy cavalry batman!

    Thanks for the backup from the pros!

    Chris is one stubborn dude. Good luck!
    Participant
    February 4, 2009
    Hi Chris-

    This is not a game where you score points by belittling the work of your customers.

    The folks who have commented on this thread as a result of cross-posting in the nuke list are not a bunch of drive-by hecklers, and we seem to be doing our best to add some clarity and represent our interests.

    The computer graphics and visual effects community does have a sense of ownership over OpenEXR, because it was designed to work well in our pipelines. Adobe's customer base is so large that a seemingly miniscule change like we're talking about can break the things that we depend on. TIFF is a good example of this.

    The EXR spec hasn't been updated for a while- probably because the folks who wrote it have moved on to other problems. Perhaps if you're not interested in listening to the concerns of the community, you could simply not support it, and give some breathing room to the plugin developers.
    Participant
    February 4, 2009
    Chris Cox:

    - Either make it an option in preferences ("Treat additional channels as transparency or leave them alone")

    - Or apply the Alpha as a layer mask, so the user has the option to enable or disable it at will.

    The current implementation is destructive and very very very annoying.

    And this is true for EVERY single format that supports more than RGB, not only EXR.

    I do graphics for 15 years and I NEVER EVER even once wanted the behaviour that Photoshop is showing.

    Photoshop it THE melting pot for billions of images from thousands and thousands of sources.
    This is not about being right or SPECs etc. (you can't win this uphill battle anyway)...
    This is about creativity software.
    People want a choice.

    Cheers,

    Thomas Helzle
    Participant
    February 4, 2009
    You seem to be confusing your segment of an industry with the larger audience of Photoshop users. People are using the EXR plugin shipped with Photoshop, in many industries. Only a few have complained. VFX represents a very small fraction of the people using the EXR file format. But Photoshop has to support everyone using the format, in many different workflows, interoperating with many other applications.


    Chris, we've been over this before on the CS4 beta forums and it really surprises me how you stick so much to the "EXR File Specs"

    Obviously a lot of people are really annoyed that they can't use EXR (a file format created BY the FX industry FOR the VFX industry!) anymore like they did in CS2. First I thought it was just Mental Ray's Problem, but it turns out that Renderman creates the same problems.

    I really think it is Adobe's time to move on this and make a little File Open dialog where you can choose how to treat Transparency and Alpha channels.

    It doesn't matter if it's different from the EXR specs Chris!
    People need to be able to use their renders and pipelines and need this flexibility!

    We also use ProEXR sometimes, but it is really sloooooow, so at the moment we have a separate machine with CS2 installed and save all our EXRs as PSB files, which is very annoying too.

    Best Regards - Christoph C-: