Bug when saving transparent png

I just saved a few pngs with transparent backgrounds and somehow the icons for those new images are being merged or overlaid with previously saved jpgs in my photo stream. When I open them, I see the picture I expect so there's no damage occurring, just funky icons. When I viewed the same images from the photo stream on my iPhone 4 and AppleTV2, the same behavior occurred with those transparent png files as well.

Hi Ignacio,
Well I sort of owe you guys an apology as it appears to be an iPad/iOS issue actually. Apparently I've never tried sending a transparent png to either my iPhone or iPad until learning/using Photoshop Touch (which I'm really enjoying btw).
But to answer your questions anyway, I was opening them on my iPad/iPhone in the Photos app and on my AppleTV in the Photostream there.
I made a quick transparent png from my Photoshop CS3 as well as downloading one from a Google search, all which had the same overlapping results.
I grabbed a screen shot for you, and blurred out the icons of images I think you'd rather not see  ;-). Weird thing though too, which also points to this being an Apple issue, is that by accident, my first image, I saved as a png but with the background layer unlocked (being layer zero) and when I dragged it into this email, it overlaid the picture over the body of the email so that the black areas where transparent. So I dragged it out, resaved as a jpg but now I can't repeat the problem with the png, as I was going to create a screen shot of that for you as well. Either way, the icons on my desktop behave as normal and the images all open as normal. They all just get goofed up when displaying them in iOS as icons before actually opening the pictures.
So in this capture, there are six images with overlapping icons where the intended transparent png is on top of some random image pulled from the photostream.
Thanks again,
Eric

Similar Messages

  • Color Profile issues / Colors darken when saving as png/jpg

    Hello Adobe Community!
    I got a problem with the color settings / profiles in Photoshop and I hope someone can help me.
    For the record: I Am working an a PC (Windows 7) with Photoshop CS4.
    I work on a digital painting in Photoshop and to keep track of my progression I save frequently as pngs.
    I noticed that the colors don't match and are much darker as you can see in the picture below:
    I tried the things suggested in many forums, checking and converting my color profiles. For many that seemed to fix it, but not for me.
    In the source space you can see the Profile I am using.
    Many suggested when saving for web and devices one should untick the "convert to sRGB" checkbox, but for me, that didn't change anything and the colors were still messed up.
    I hope someone has a solution for this problem. After trying so many things I'm getting quite desperate!

    always CONVERT to sRGB (if not already there) when saving for the web and unmanages apps
    there are both pros and cons for tagging/untagging images for the web
    the slight darkening and saturation difference i see in in your posted image is expected between managed and unmanaged apps, but you didn't embed a profile so it is my guess what you are seeing there
    to duplicate the phenomenon, in Photoshop, open your tagged sRGB image, then
    View> Proof Setup: Monitor RGB (be sure to turn it back off)
    the shift you see there is the difference between sRGB and your monitor profile (Photoshop is in essence stripping the sRGB profile and sending the RGB numbers straight through to the monitor with no changes)
    as you probably know, Photoshop normally transforms (changes) the source colors to the monitor profile...

  • Bug when saving - files are all inverted and transparent

    Hi there,
    I've been working on a job for a few hours now and I have still have it open in photoshop CS5 extended.
    Basically if I save it out in ANY format (tiff, psb, psd, jpg) it is inverted and the transparency is all messed up.. when I look at it in bridge or reopen it in photoshop or preview, it's the same.
    I have the file still open in photoshop and I'm scared to close it because it looks just fine on screen but when I try to do anything it is behaving strangely. for example if I convert to CMYK it goes to the inverted image which it saves out.
    I deleted all the layers I am not using and rasterized all the dynamic objects and it's still doing the same thing
    Is there any way I can save my file ? I've been working on it for a long time ???
    Thanks in advance for any help.

    After numerous attempts to rescue the file, I ended up having to recreate it..
    I think it was down to a memory bug.. I did empty the clipboard as well during the creation of the file because I was having problems.. maybe it was down to that but I think it actually just became corrupted somehow !
    I must admit, it's the first time I've encountered this problem in 15 years of working with photoshop !!
    Many thanks for your replies !

  • Why photoshop Lose a LOT of quality when saving in PNG ?

    Hello
    Why does photoshop lose a lot of quality when you save something in Png ? ( web intended ).. Even if i go through the "save for the web " or not, the result is always sloppy...
    I save Png-24, with transparency and interlaced. like always.
    Sometime it does a good job.. some time it is just sloppy.. Is there anyway to fix that ?..
    Here is the image as it should be ( minus the 3 guide i forgot to remove ).. this is a screenshoot from Photoshop.
    And here is the result.
    Any idea why ?... and what is even more confusing is that when you hit "preview" in the "save for the web" tool you get the perfect picture... but once saved it will be scrap.
    Both the Logo and the Menu button are blurred... ( this is not an effect of zoom here.)
    Any clue ?
    Thanks

    the_wine_snob wrote:
    For Web use, why are you Saving with Interlacing? That is for Video, with Projects like DVD-Video.
    Not quite... Interlacing is used for web images as well... particularly where bandwidth is an issue.
    Chorale0001 wrote: What is even more weird is when i use the blurred png file and insert it in my website, in IE the image stay blurred.. but on Firefox and chrome it is perfect.. and if you just do a "preview" of the picture itself using your window explorer, it is blurred.
    That is a typical symptom of an image scaled via HTML/CSS.
    The images look identical here when I view them in Photoshop. Scaling in the HTML seems to be the problem.

  • Intermittent Bug when saving pdf files in Illustrator CS6

    I save a pdf file in Illustrator CS6 with a specific art board size. When I open it in Acrobat the size is off. When our print's RIP's the file, it is off the same amount. I will re-open it in Illustrator and re-save it and just change the name, the artboard is then correct. This is very intermittent. It has happened on two copies of CS6. Both prograns are current with the updates. I am on a iMac running OS 10.6.8.

    Document size is: 36.01 x 98.12
    I can open up both documents in Illustrator and they are identical.
    We have been using these presets for a couple of years without issue. The problem started happening about 3 weeks ago on 2 seperate computers. We have not seen the problem with CS5.5 and earlier.
    Below are the preset settings summary:
    Warnings
    Adobe PDF Preset: CCC High Res PDF 
    Compatibility: Acrobat 6 (PDF 1.5) 
    Standard: None 
    Description 
              [Based on 'CCC High Res PDF'] [Based on 'CCC High Res PDF
              04-28-08'] PDF Workflow For Custom Color Corporation Output
    General 
              Preserve Illustrator Editing Capabilities: On 
              Embed Page Thumbnails: On 
              View PDF File after Saving: Off 
              Optimize for Fast Web View: Off 
              Create Acrobat Layers from Top-Level Layers: Off 
    Compression 
              Color Bitmap Images: 
                        No Sampling Change 
                        Compression: None 
              Grayscale Bitmap Images: 
                        No Sampling Change 
                        Compression: None 
              Monochrome Bitmap Images: 
                        No Sampling Change 
                        Compression: None 
              Compress Text and Line Art: Off 
    Marks and Bleeds 
              Trim Marks: Off 
              Registration Marks: Off 
              Color Bars: Off 
              Page Information: Off 
              Printer Mark Type: Roman 
              Trim Mark Weight: 0.25 pt 
              Offset from Artboard: 0.083 in 
              Use Document Bleed: On 
    Output 
              Color: 
                        Color Conversion: No Conversion 
                        Profile Inclusion Policy: Include Tagged Source Profiles 
    Advanced 
              Subset embedded fonts below: 100 % 
    Security 
              Document Open Password: Off 
              Permissions Password: Off 
              Encryption Level: High (128-bit RC4) - Acrobat 5 and later 
    on: Off 
              Printer Mark Type: Roman 
              Trim Mark Weight: 0.25 pt 
              Offset from Artboard: 0.083 in 
              Bleed Left: 0 in 
              Bleed Right: 0 in 
              Bleed Top: 0 in 
              Bleed Bottom: 0 in 
    Output 
              Color: 
                        Color Conversion: No Conversion 
                        Profile Inclusion Policy: Include Tagged Source Profiles 
    Advanced 
              Subset embedded fonts below: 100 % 
    Security 
              Document Open Password: Off 
              Permissions Password: Off 
              Encryption Level: High (128-bit RC4) - Acrobat 5 and later 

  • [SOLVED] Inkscape bug when saving

    Hello,
    I need help. As I specified in the subject, Inkscape crashes when I try to save my work with "Save as" or "Save a copy ...". In the Following, the output (useless I believe):
    (inkscape:27996): GLib-GObject-WARNING **: gsignal.c:2459: signal `child-added' is invalid for instance `0x3e905d0'
    Emergency save activated!
    Emergency save completed. Inkscape will close now.
    If you can reproduce this crash, please file a bug at www.inkscape.org
    with a detailed description of the steps leading to the crash, so we can fix it.
    I am running archlinux with kde 4.9.1 and Inkscape 0.48.3.1 r9886. Any help is very appreciated. Or, at least, is someone experiencing the same issue?
    Thank you
    Last edited by @ilio (2012-09-12 10:55:05)

    Stebalien wrote:That output isn't useless. It contains instructions on what to do. If this happens reliably, file a report. The Inkscape developers should be able to help you debug it.
    Yes... I meant useless in debugging. I am sending a bug report.
    Thanks
    Edit: Sent as bug#1049179.
    Last edited by @ilio (2012-09-11 15:09:44)

  • Colour loss when saving PNGs.

    Hi there,
    I'm fairly new to photoshop and am having a few difficulties when saving a PNG.
    I'm using a Mac Book Pro.
    I'm using Photoshop CS6.
    The problem I'm encountering is when I save a PNG file I'm losing a lot of colour saturation. It goes from a vibrant red to a dull red colour.
    The workspace is RGB 8bit.
    I'm using the SAVE AS function because I don't want it for web I need it for print and I need the transparent background too.
    The only way I've managed to get the full colour is by using the save for web option and selecting PNG-24.
    Any help would be greatly appreciated.

    I'm using the SAVE AS function because I don't want it for web I need it for print and I need the transparent background too.
    Then I see no reason for using png but think you should use psd.
    The workspace is RGB 8bit.
    Workspaces are something completely different in Photoshop (and concern Panels, Menus etc,) and RGB is not a Color Space but a Color Mode.
    What is the image’s Color Space or if it isn’t embedded what is your RGB Working Space (Edit > Color Settings)?

  • PNG-24 images have slight white halo when saved in CS5 but not 7

    I've been using Photoshop 7 for several years to create artwork, and export that artwork as transparent PNG-24 images for use on the web, to be included in other images, etc.. The images usually need to be drasticallly reduced in size when I'm done with the coloring and shading (usually to around 20% of the original size, for a final size of around 500px high or wide), and the resulting smaller PNGs Photoshop 7 created always had clean and crisp edges.
    I've been looking at finally making the move to CS5, however, and so I tried working with another image in the CS5 trial. At first everything seemed fine, but when I went through the Save for Web dialog, shrank and saved the image as PNG-24 and then opened it again to paste the result into another image, there was a slight whitish halo around the outline. I'm not sure why this happened as I don't remember using output settings any different from those in the 7 dialog; I tried changing the quality from bicubic to the other options, but nearest neighbor obviously made the outline look messy and the other options didn't have any noticeable effect (though I didn't really expect them to).
    As an example, here are links to the image I recently created on a background: the first is what CS5 seems to do (add the halo); the second is technically a much larger version of the PNG with cleaner lineart (since I didn't shrink it first), but scaled down to the right size, since I don't have 7 itself to try re-saving the PSD.
    Image with Halo (CS5 output)
    Image without Halo (7 output)
    Saving as PNG-8 or GIF leaves clean outlines if I turn off Matting, but I need the subtler color shifts of PNG-24; JPEG obviously isn't an option because I want the transparency.
    The last time I noticed this with a trial on an older computer, I simply reinstalled Photoshop 7 and continued working with that. This newer computer is 64-bit, however, and I can't install Photoshop 7 without jumping through a few hoops. I can do it if I must, as I don't need any of CS5's newer features that desperately, but I would like to move up to CS5 in general and so want to know if there's a solution to this before I just give up and go back to 7.
    So I'm curious: is there a reason for this difference in behavior? Was this an intentional change, or is something wrong with CS5? I understand that there may not be much that I can do, as CS5's behavior does make some sense given the way Photoshop has to recalculate the image when resizing it, but 7's behavior, even if it is somehow "incorrect", is more desirable because the result is cleaner outlines. Is there a setting I can adjust, is there some sort of problem I can fix, or should I just go back to Photoshop 7 for saving this kind of work when I get the chance to reinstall it?
    Thanks in advance for any insight you can give me; let me know if you need any other information.

    Absolutely! Here are a few of the files in question:
    and these that work perfectly for my client:
    Thank you!

  • Streaking across PNGs when saved to PDF.

    I'm seeing some streaking/banding across PGN images when I save a PAGES2.0.2 doc to PDF...
    Have others onticed this?
    Is there a FIX?
    The layout is fine and shows no "streaking/banding " in the PNGs in the Pages202 Project itself. Only when saved to a PDF do they appear...
    thanks

    I was working in Photoshop, flattening/merging layers as I go and dragging across the flattened/merged layer w/alpha into Pages202 from the open Photoshop project.
    Seemed like a good way to work since Pages202 doesn't auto-update any corrected art/files saved out of Photoshop it might be using/linked to. If I needed to modify/correct an image, I did it on the spot in PS-CS2 and simply dragged it across to replace the ones in Pages202 I wanted to update.
    Sometimes I saved the PS files as PNGs (because I need the alpha transparency) and imported them into Pages202 directly. They all exhibit the banding problem when the project is Exported/Printed to PDF from Pages202.
    It's still odd, however, that if I drop the exported Pages202 PDF back into Photoshop and re-export as a PhotoshopPDF--the banding isn't there.
    It only is visible when looking/printing from a Pages202 PDF in Preview or Acrobat.
    I'll see how the PNG-24 method goes (though it changes overall color saturation of the picture, which I'll have to compensate for) It would be great if pages202 could "update" it's imported image files automatically...
    Thanks.

  • Error message when saving a PDF to PNG: Error attempting to write file.

    I get an error message when saving a PDF to PNG. JPG and TIFF works, but no PNG.
    Disk space is sufficient! 100GB of 250
    A few weeks ago it was no problem to save as PNG. But now! (Perhaps from last update?)
    Messages:
    When clicking "Ignore":
    Adobe Acrobat XI Standard
    Version 11.0.09

    I have this issue too, but my colleagues do not have this issue(we have same Acrobat Pro 11.0.09). I am sure this issue happens only you updated to 11.0.09, because when you use Windows Restore back to 11.0.08, no issues.

  • Strange lines appear around transparent PNG's when document PDF'ed

    Hi
    I have inserted some transparent PNG images into my Pages document, and they look fine on my screen, and they also look fine when I export to PDF and view in Preview.
    However, if I view the PDF in Acrobat (or send it to a Non-Mac user and they view it in Acrobat), there are thin lines around many of the PNG images, which make them look ugly and sloppy, and very un-Mac-Like! Any ideas why these lines are appearing and how to prevent them?

    Hi logree
    Welcome to the forum.
    My guess is that it is showing just the edge of the masked background used to hide the alpha channel background of the .png.
    This happens I think, because the postscript mask may be centred on the outside rows of pixels in Acrobat, with half the pixels still being revealed.
    You can try masking in Pages' instead:
    +Menu > Format > Instant Alpha+
    or try a Photoshop file with transparent background, to see if that eliminates the problem.
    Peter

  • BUG? ORA-01461 in Unit Tester when saving a long Dynamic Value Query

    I get an ORA-01461 "can bind a LONG value only for insert into a LONG column" error when saving a Test Implementation with a Dynamic Value Query whose length of the SQL statement is roughly 2,000 characters - I'm UNIONing ALL about 30 test case values together, but it seems to be choking on such a long SQL string for some reason....
    I am running version Early Adopter Release #2 (2.1.0.63), build MAIN-63.10.
    Thoughts?

    Confirmed.
    Bug 9119144: ORA-01461 IN UNIT TESTER WHEN SAVING A LONG DYNAMIC VALUE QUERY (OR OTHER CLOB)
    Brian Jeffries
    SQL Developer Team

  • How to make white shapes turn transparent when exporting to .png?

    I'm trying to cut out parts of my image with white shapes, but when exporting to .png with transparent backgrounds, the white shapes remain as white shapes instead of becoming transparent and applying the cut.
    How do i fix this?
    Thanks,
    Rokas

    Use a mask, most probably an opacity mask should help.

  • Why can't I save transparent pngs or gifs... CS5.5, CS6

    I just installed CS6 and after using for a while and realizing all the bugs I decided to go back to 5.5. This bug in particular is when saving for web I cannot set the matte to no color for transparency. When I click on the color sample I only get the eye dropper no color box for selection... This is now happening in CS5.5 as well. Kinda screwed here...
    Any help is greatly appreciated.
    Thanks

    So there's no color picker when you attempt to set the Matte color within the Image Preview dialog? Here are a few ideas:
    For PNG-8 or GIF, you can set transparency using the dropdown menu, located just above the Matte color chip.
    Have you tried using the Optimize panel (plus Preview, 2-Up, or 4-Up view) to set the Matte color?
    You haven't mentioned your platform or operating system, which is good information to include in a post like this. You may also want to file a bug report on this matter; however, it sounds like you may be suspecting an installation error of some sort (?). This is Adobe's official bug report page:
    https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

  • Errors when saving to SMB mounts (a thorough examination)

    Several of the users I support have reported the following issue when trying to save files to the network from Photoshop. I have found several threads about this on both the Adobe forums and the Mac forums. However, in most of the threads the information provided is incomplete or does not control for enough variables. And the result is that Adobe seems to blame Apple, and Apple seems to blame Adobe. So blame aside, here is information that I hope helps Adobe solve the issue at hand.
    When saving to a mounted SMB point, users report one of two errors:
    Could not save <filename> because of a program error
    Could not save <filename> because write access was not granted
    I can replicate the issue on:
    Lion 10.7.X with Photoshop CS 5
    Lion 10.7.X with Photoshop CS 5.1
    Snow Leopard 10.6.X with Photoshop CS 5
    Snow Leopard 10.6.X with Photoshop CS 5.1
    Details:
    We have only seen this error in Photoshop.  << Adobe has seen the same problems in several other applications >>
    I have not tested out whether the issue applies to any other products in the CS suite.
    At first I thought the issue might have to do with permissions, but it does not. I have reapplied permissions and the issue persists. And it affects all users, including Domain Admins, such as me, who have no R/W restrictions at any level.
    The issue only occurs when Finder is in a view that shows a thumbnail/preview of the image.
    Switching Finder to list mode resolves the error in all scenarios
    So far I can replicate this with any file on any mount on any of our servers
    It only occurs on mounted network points (ie - if I move the files locally, no errors are encountered)
    For the following tests, presume the following:
    Source folder: smb://example/source/folder
    Target folder: smb://example/source/folder
    Target sub-folder: smb://example/source/folder/sub
    Here are the steps I tested:
    Opened the file problem_file.psd.
    A warning pops up prompting me to resolve a font vector issue, I chose "Update"
    Note: that this error does not pop up for every file, just the original file I worked with, but this warning has nothing to do with the errors being received
    Moved a layer so that there would be a change to save
    Clicked save
    Received the error: "Could not save <filename> because of a program error"  << probably related to the known MacOS bug on SMB, or a known Finder/thumbnailing bug >>
    The original file, problem_file.psd, is *DELETED* (very problematic)  << Known MacOS bug in SMB service, Apple is working on it >>
    Then I tested with multiple variations of the following to conrol for things such as layers or font issues:
    To eliminate the source file being the issue, I used a .png file that I had created locally with the OS-X screen shot keyboard command. This eliminated layers and fonts as issues.
    In step 2 I chose to not update the font vector issue
    In step 4 I tried saving as different file types (.jpg, .png, .gif)
    Prior to step 6 I flattend the image to eliminate fonts and layers. This eliminated layers and fonts as issues.
    Prior to step 6 I flattened the image, duplicate the image, closed the original (without saving), and attempted to save the new duplicate. This eliminated layers and fonts as issues.
    Each variation still resulted in "Could not save <filename> because of a program error" and resulted in the deletion of the source file.
    Next I controlled for saving image previews:
    Photoshop -> Preferences -> File Handling
    Under File Saving Options -> Image Previews, I set it to "Never Save" previews
    Now when I repeated the tests from aobve, I receved the error "Could not save <filename> because write access was not granted".
    Next I controlled for .DS_store files:
    Disabled .DS_Store file creation on remotely mounted points.
    Deleted the .DS_Store file for the source folder
    Verified that .ds_store files were not being created on remotely mounted points
    Ran the tests above, and the issue persisted: "Could not save <filename> because write access was not granted"
    Now I decided to test sub-folders:
    Created a target sub-folder.
    Repeated the test above, and its variations, but saving the problem_file.psd to the target sub-folder.
    Still received one of the two errors, depending on the variation, but the source file is no longer deleted. This make sense because saving in another directory is really a "save as", and one would not expect safe saving (talked about more later) to affect source files in this scenario.
    Sort of a Solution:
    Open the file from Finder
    Depending on the Finder view, Finder shows a thumnail of the image
    Go back to Finder and select a different file
    Make changes to the file
    Save the file
    No error is received
    This is when I discovered that the error only occurs when Finder is in a view that shows a thumbnail/preview of the image. Further testing of Finder show that in Cover Flow the error only occurs for the selected image. For example:
    Cover flow shows thumbnails/previews of files: A, B, C, D, E
    Open A
    In Cover Flow select file B
    The thumnails of of files A, B, C, D, E are still visible
    Make a change to the open file
    Save the change
    No error is received
    This shows that Finder is treating the thumbnails/previews of unselected files different than selected files.
    An Interesting Twist:
    If from the last scenario with Cover Flow...
    Open file A
    Go back to Finder and select a different file
    Then make a change and attempt to save to the target sub-folder
    Receive the error "Could not save <filename>" because of a program error.
    Discussion:
    Photoshop does something called safe saving.
    Photoshop saves the current document to a temporary file with a unique name
    Photoshop deletes the original file << this is incorrect >>
    Photoshop moves the temporary file to a file with the name of the original file that was deleted in step 2  << incorrect: the temp file replaces the original with an OS call to a function that is supposed to be an atomic operation >>
    However, you can see that "safe saving" is misnamed, because while the original is deleted, Photoshop does not appear to be correctly ensuring that permissions exist to allow the temporary file to be ranemd or that the temporary file was renamed without error. Photoshop is either:
    Not checking for the error  << yes, it is >>
    Checking for the permissions and not catching the error  << incorrect >>
    Checking for the permissions and giving an error to generic to discern the exact problem from. << also incorrect >>
    Somewhere there is a conflict (perhaps a race condition) between:
    Photoshop creating the temporary file
    The server applying permission to the newly created temporary file
    OS-X reporting the file has been created
    Photoshop deleting the original file
    Photoshop saving the new file
    Finder updating the thumbnail of the file
    As I've shown here, the problem doesn't seem to reside fully with Apple or fully with Adobe. Hopefully this post provides enough information for some clever engineer to create a fix.
    My information about safe saving is from an Adobe mod on a previous thread regarding this issue << and copied incorrectly, plus added bad assumptions>>. He detailed the process and also explained that Photoshop uses OS APIs to create and delete the files during safe saving. If his details are accurate, it seems that a temporary fix would at least change the safe saving process to the following:
    Photoshop saves the current document to a temporary file with a unique name
    Photoshop moves the original file to a temporary backup file (original-file-name.original-extension.bak)
    Photoshop moves the temporary file to a file with the name of the original file moved in step 3
    Photoshop checks to make sure that the temporary file has been succesfully renamed
    If the temporary file has successfully been renamed, it deletes the backup file from step 2 OR if the temporary file has failed to be renamed, the backup is returned to its original file name
    The appropriate error message, if any, is displayed
    A Few Sources:
    http://adobe.hosted.jivesoftware.com/message/4016324
    http://forums.adobe.com/thread/732422
    https://discussions.apple.com/thread/3380971?start=0&tstart=0

    You got several details wrong.
    And it sounds like you are describing 2 known MacOS bugs:
    1) The OS fails when creating or swapping files on SMB servers, and this happens more often on files that have a resource fork.
    2) The Finder/QuickLook/Thumbnailing holds a file busy when it should not, causing program errors or file is busy errors.
    We did as much as we could to work around these issues in Photoshop CS6 - after spending a lot of time debugging the OS issues and working with Apple.
    Apple is still working on proper fixes within the OS.

Maybe you are looking for