Photoshop plugin error RRS feed

  • Question

  • When trying to make a HD View file more than 7000 pixels wide I get an error message:

    returned hr = 80004005

    Works fine on smaller images.
    15 gig temp on c: and 2 gig ram.
    PS CS8.
    Monday, October 15, 2007 6:16 PM

All replies

  • I'm not sure about that one.  Since the release we have fixed two issues that users have reported.  The first is that the menu item was grayed out for images > 30K on a side, the second is that images with additional channels weren't handled correctly.  We will be releasing an update later this week.


    It sounds like your case is not either one of these issues.  The current plugin should handle images up to 30K wide so I'm not sure why you see an issue at 7K.  What are your other settings in the HDView export dialog?

    Tuesday, October 16, 2007 6:08 AM
  • I have tried multiple settings. Flat projection, cylindrical, different quality settings. When I reduce file height/width enough theres no problems.

    A 1000*8000 px works ok, a 8000*1000 px works ok, but not 8000*8000 px.
    Tuesday, October 16, 2007 7:11 PM
  • I would try allocating more ram to photoshop.

    When using the photoshop plugin I would get the following error:

    returned hr=8007000e

    im not sure what the code means but i think its a memory issue.

    The photo is 15640 by 6069.  I use flat and cylinder projection, range of qualities.  Randomly medium will work.  Photoshop is set to use 1200mb of ram (of 1700 availabe on a 4gb Visa business system)
    the c scratch disk has 7gb free.  the L drive (usb) has 160 gb free.  If i reduce the size of the image it works fine. 

    However when I allocated 1650mb ram within photoshop, I could export the full image at lossless quality.

    HDview guys:  could you look at optimizing the amount of ram used by the plugin, 2gb of ram useable by photoshop is a bottleneck i think more people could have a problem with.

    Smile my 2cents/guess

    Sunday, October 21, 2007 9:16 PM
  • Sorry about this.  A few people have reported this bug.  As you surmised this is an out of memory issue in our plugin.  We have a fix that hopefully should be out tomorrow.


    Monday, October 22, 2007 9:27 PM
  • Wednesday, October 24, 2007 6:27 PM