AE PNG export bug?

I thought this bug was squashed a couple versions ago, but it seems to be back.
"Save Frame As…" out as a PNG in After Effects CS6. Open that PNG in Illustrator CS6 and it's ginormous. I have to resave the PNG in Photoshop for Illustrator not to freak out.

Hi Navarro,
Yeah, I remember that problem. Here's the gist of it: when writing PNG files, AE writes a DPI of 1 pixel per meter into the file's metadata. Basically, AE is saying, "DPI? I don't care 'bout no stinkin' DPI. I'm a video application. PIXELS are where it's at, man." (Apparently in my head AE speaks with a New York accent.)
Some applications freak out about this value. Photoshop doesn't. Illustrator does. Flash used to but they fixed it way back in Flash CS4 so that if it sees weird data in the PNG file it just converts it to 72dpi and goes on about its business. I'm guessing that's why you (and I) thought this problem was fixed.
As usual, feel free to file a bug about the problem. Against Illustrator or AE, or better yet both.

Similar Messages

  • JSFL - PNG export bug in CS5.5, works in CS4 - 8000px limit

    We have a series of JSL scripts that export our ad banners in both SWG and GIF format. The GIFs are compiled by exporting each of the 3 frames of the SWF as PNG images then a .jsx script runs in Photoshop and compiles them into a GIF.
    This all worked fine in Flash CS4. Running the script on FLAs in FLash CS5.5 produces this error at the PNG export stage:
    The bitmap is too large. The largest bitmap that can be created is 8000x8000 pixels.
    The line of code that triggers this error is:
    fl.getDocumentDOM().exportPNG((pngPath+resName+".png"), true, false);
    The path variables are fine and produce a valid path (see below). As you know the first boolean states whether to 'use current PNG export settings' (true) or to show the settings dialog on export (false). The second Boolean states whether to export only the current frame (true) or all frames in the SWF (false).
    If I change the 'use current PNG export settings' to false and show the export dialog and OK the default values the export runs fine (which is how I know there is no issue with the export path).
    Showing the dialog box on each export is not acceptable because we have over 10,000 of these banners to export over the next couple of months.
    I'd like to know:
    [1] Is this an actual bug?
    [2] Can anyone suggest a workaround?

    To reproduce this behaviour create an FLA in CS4, make 3 keyframes, draw a filled rectangle (or whatever) on each frame then save it somewhere (ie C:\test.fla)
    Then create a Flash JavaScript file, paste the following code into it and save it in the same location as the FLA. (ie C:\script.jsfl)
    exportPath = fl.scriptURI.substr(0,fl.scriptURI.lastIndexOf("/"))+"/";
    fl.getDocumentDOM().exportPNG(exportPath+"Frame.png", TRUE, FALSE);
    The first line of code here just gets the location of the jsfl file and removes the filename to give an export path.
    The second line export each frame to the same location as the FLA and JSFL files.
    This should run fine in CS4 and you will see the following in your save location:
    test.fla
    script.jsl
    Frame0001.png
    Frame0002.png
    Frame0003.png
    If you change the first boolean in the export command to FALSE and run the script again you should see the PNG export settings dialog box and when you OK it you will get the same export result.
    Now open the FLA and JSFL files in CS5.5 and run the JSFL. With the boolean set to TRUE you should get an error (the 8000px error), however if you set it to FALSE so that you get the settings dialog when you OK it the export will run fine.
    Change it back to TRUE and you will get an error again.

  • PNG export with 72 dpi

    I want to export an image (bitmap PNG or PSD) as a PNG with transparency in 72 dpi.
    InDesign CC 2014 makes the PNG very pixelated. InDesign CC looks fine.
    Is this a bug or a feature?

    I meant the PDF export is no option for me. The 300 dpi PNG export is better for my workflow but not the best.
    But if you can export a PNG, open it into PS, resample, resave, you could also export the page as PDF/X-4 and open it as 72ppi and save as png.
    If you are using OSX this AppleScript will do that:
    http://www.zenodesign.com/forum/IDtoPDFtoPNG.zip
    There have always been problems with ID's png export

  • Keyword exporting bug also impacts catalogs imported from PSE 6

    Hi,
    I haven't seen any mention of it, but the keyword exporting bug reported for catalogs imported from LR 1.x also impacts catalogs imported from Photoshop Elements 6. i.e. all Keywords imported from my PSE 6 catalog have "Include in export", "Export Containing Keywords", and "Export Synonyms" properties set to false.
    I've reported the bug, but as it seems the same as described in KB 405074 (and more importantly, its fix works for formerly PSE catalogs as well!), I'm sure it will be fixed in the next update.
    http://kb.adobe.com/selfservice/viewContent.do?externalId=kb405074&sliceId=2
    Thanks,
    Matt

    Hi Brian,
    When I installed the trial for LR2 I was asked whether I wanted to upgrade my existing PSE6 catalog.
    Screenshot of this can be found here: http://dawsons.id.au/temp/pse6-to-lr2-catalog.png
    That's it. I haven't imported any keywords via any other method.
    Thanks,
    Matt
    PS I'm impressed with the level of Lightroom team involvement in these forums. I've been a PSE user for at least 5 years and have never received feedback from that team re posts/support calls/feature request/bug reports. I've been a LR user for about two weeks and I've already had Tom and yourself reply to my posts. You've got to be happy with that!

  • Indesign CS6 epub export bug

    I am using Indesign CS6 to export a book to epub. Having problems with automatic numbers and bullets as well as spacing issues; however, I've made some adjustments and am getting a pretty decent epub. Here's the issue: When I convert my epub to Mobi using Calibre, I get double bullets and double numbers in my lists. I used this same process to create a Mobi file a few months ago in Indesign 5.5 with no problem. So I took one of my CS6 files, exported it to IDML, opened it in CS5.5 and exported to ePub. I then took that epub and converted it to Mobi using Calibre. No double bullets or numbers. So the issue is coming from Indesign CS6.
    Anyone else had this issue. Any other ideas on how to get a clean Mobi file from CS6?

    Thanks a million.
    Re: Indesign CS6 epub export bug
    created by Steve Werner in InDesign - View the full discussion
    lotuscott,
    You should get the 8.0.1 update for InDesign CS6. It fixes several EPUB bugs including the "space before" problem and the "epub-ruby" (which is I believed intended for Japanese language.
    Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/4773256#4773256
    Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4773256#4773256
    To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4773256#4773256. In the Actions box on the right, click the Stop Email Notifications link.
    Start a new discussion in InDesign by email or at Adobe Community
    For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • Could someone help with question about PNG export from Illustrator?

    I am having issues with PNG exports from Illustrator not opening up once exported.

    ANd exactly sorry, this is useless. You have not provided any details about your export settings, version of AI, system info, how you are trying to view and so on. Just saying that it doesn't work is simply not good enough.
    Mylenium

  • PNG Export from Illustrator 8 Washed Out When Opened in Fireworks MX

    When I export a file containing line art from Illustrator 8 as a PNG and open it in Fireworks MX, the lines and colors are washed out. Why is this?

    If you are talking about the sharpness of shapes, it's probably because the image is now made up of pixels, not paths. When you export the AI file to PNG, you rasterize it.
    If you are talking about color accuracy, you will have to get into the whole issue of color management settings beween your applications.
    Was the AI document CMYK or RGB? What are your PNG export settings? Did you use Export or Save For Web?
    What versions of both programs are you using?
    Can you post AI and FW screen shots of at least a portion of the artwork?
    JET

  • CS6 After Effects PNG export very slow - Not Multi-Threaded?

    I am rendering an after effects project consisting of over 320,000 source frames of 4000x4000 resolution, outputting over 250,000 frames as PNG files.
    Rendering is instant on our machines, all time is spent "compressing and writing" frames. It is taking forever.
    We have several machines that are all windows 7, with 16 physical cores, 64GB ram, connected to a 4Gbit SAN.
    I did some experimenting, tried using all 16 cores, or 8 cores, or disabled multi-frame rendering even. When this project is rendering my cpu usage is almost non existent,. maybe 1%-5%  at times.
    with 16 frames at a time being rendered it is averaging between 1 and 7 seconds per frame depending on the content of the frame.
    Does Adobe have any plans to multi-thread the PNG exporter? or is there a faster 3rd party plugin out there i could use? It is very slow and doesn't tax the CPU's at all. Even on a single core it doesnt even use 100% cpu while its saving.
    I even tried loading one of the frames into photoshop and simpy hit save as a PNG and it took almost 15 seconds to compress and save. I did it again without compression and it saved the 40MB raw file instantly.
    That is terrible performance for machines like mine that are pretty much the fastest things out there.
    Thanks!

    I appreciate your attempt for a workaround solution, however as you well know you can't render to a video file from multiple machines. we must output directly to individual frames, I setup 8 machines to work on this project, if we did not use compression then we would be writing over 300MB/sec of data which would not be good for our fibre network which unfortunatly is only 4Gbit. And it would be about 10TB of data total.
    As for your workaround Im not sure we could gain speed with your method either way. spending the extra time to encode to a lossless format and then process again in AME sounds like it would take even more time, unless AME could create PNG files at some sort of ridiculous speed maxxing out every core at 100% or something to compress the PNG's. Out of curiosity I will throw some frames at AME and see how long it takes to compress and how much cpu it will use.
    thanks

  • Mono export bug

    strange export bug I experienced this weekend, I think its a metadata issue.
    Before the export I had to relink all the material because we had moved all the material from one SAN to another. Exported the show using Premiere, not AME, to Prores. The timeline have two mono audio tracks, each panned left and right. I then used AME to convert the new Prores file to export a MXF version and a h264 version.
    All the files came out with only audio in the left channel! But when I check on a different machine the Prores came out with sound in both channels, but the MXF and h264 did not. I then removed all the "Media Cache" and "Media Cache Files", located in the Library/Application Support/Adobe/Common/ folder.
    I then reimported the files, and now the Prores came up with audio in both channels but the MXF and h264 was still "corrupted".
    Have someone experienced the same? Why would the Prores file, with audio in both channels, produce a single mono track MXF/h264 file? Do people regularly delete the "Media Cache" and "Media Cache Files"? PEBCAK?
    Both machines where the new mac pro, 10.9.5, with similar specs, 3,5Ghz 32GB ram dual AMD FirePro D500, with Adobe Premiere 8.2
    Any thoughts is appreciated

    The Prores was exported with these settings:
    Audio Codec: AAC
    Sample Rate: 48KHz
    Channels: Stereo
    Audio Track Layout: 2 Mono Tracks
    Channel Layout: Mono
    The MXF was exported with these settings:
    Audio Codec: Uncompressed
    Sample Rate: 48KHz
    Channels: 2 Channel
    No multichannel

  • Bug with AE PNG export - Flash import?

    Anyone know what's up with AE CS3's PNG sequences? I open them in Flash CS3 and they are completely transparent. I have to batch open/save in Photoshop for them to read correctly in Flash.

    Hey, look what I found when I searched for 'PNG' using the
    After Effects Community Help search.
    The top result on this page is an Adobe Technical Support Knowledgebase article about this issue.

  • Motion export bug?

    Got some strange thing when exporting from Motion. Exported a movie in ProRes 422 (HQ), but the result was just ProRes 422. Then I tried exporting with different options and found that it exports not with the select format of the options in the export window, but with the codec above the selectet one. So if I select ProRes (LT) there, i get (HQ), if I select just 422 I'll get PNG, which is the one above the ProRes ones.
    Got this on our two installations, can someone check this and confirm, already searched the forum, but did'nt find anything, so that i can fill a bug report.

    : /
    just had to mark my surprise. I had this problem with FCP and other apps. Especially when i click a clip in the project window in FCP and it renamed all the clips to the one i selected >__<

  • CR6.4 RC1 - XMP export bug, anybody else has it?

    I think I found a bug, and although I also found a workaround, here it is.
    My environment: Windows 7, Photoshop CS5, Camera Raw 6.4 RC1, all of them 64-bits.
    Steps to reproduce the bug:
    1. Open several raw files at once in Camera Raw (in my case, Olympus E-PL2 ORF files, but it probably doesn`t matter). For this bug, take images that are likely to have different white balance settings. Also make sure that those are original files, never modified by Camera Raw (or anything else) and that they have no XMP sidecars yet.
    2. Wait until thumbnails are generated (may not be relevant...). Don't click on any of them, just let them be created.
    3. Click on "Select All". Again, don't change the displayed image, just select them all.
    4. In Basic/White Balance, select Auto. All thumbnails are properly updated
    5. Export settings to XMP (from the menu on the right-most toolbar, i.e. still "Basic" if you haven`t changed it)
    6. Keep Camera Raw open, and have a look at the XMP files.
    The BUG : they all contain the same white balance settings (crs:WhiteBalance, crs:Temperature and crs:Tint) which happen to be the computed settings for the first image (the only one displayed so far). All other settings seems to be fine though (i.e. they are from their respective image).
    However, if you go back in Camera Raw and then click on some other images, not all of them. You can see that their WB settings are different and properly computed (as far as "Auto" can properly compute them). Export to XMP again. WB settings are then right, but only for the images that you clicked on. Those that were never displayed full size still have the wrong WB settings (from the first image).
    Obviously, the workaround is to click on each of them. Still that's a bit awkward, especially in my "quite-automated" workflow, where I'm not yet to the point to look at each image individually. Can't tell if this bug exist too on any other version of CR, and my E-PL2 raw files can only be opened in CR 6.4 anyway (unless I change some tags to fool CR).
    Can anybody can reproduce that bug on similar or different environment? And could Adobe fix it, if it is a bug?

    btw, don't know why I wrote RC1... I just meant Release Candidate!

  • Color Shift Happening When Exporting - Bug in Acrobat Export?

    Hi, we are using InDesign CS3 and trying to output a file to send to a printer. We are desiring to have all colors converted to the printer's CMYK color space upon exporting (they sent us their ICC profile).
    But we are getting a bizarre bug that I cannot figure out. It seems like it's actually a software bug, not an issue with settings. I'll try to describe the issue here:
    Upon using 'Convert to Destination (Preserver Numbers or Not)' in the PDF export dialog in InDesign (using PDF/X-4 setting), using the 'Document CMYK' profile, there is a shift in color for 1 particular element. We have a grayscale image of a bunch of dots (black dots on solid white background) that is placed in a frame in InDesign. This image is 'colorized' in InDesign by setting an image color and a frame color (the image color appears as the 'foreground' and the frame color is the 'background'). We've been doing this all the way back to the Quark days (many years). But if the 'background/frame' color is a combination of C+M+Y (with no black), the Magenta and Yellow values are shifted to the Yellow and Black channels (for example - 52c, 5m, 10y, 0k becomes 52c, 0m, 5y, 10k).
    I have never run into this before, and we've run this job with the same element many times now over the last couple years. But I have always used 'No Color Conversion' in my PDFs in the past. So it has something to do with the 'conversion'.
    So far I've tried:
    - Creating new document with just the single element, also created from scratch. So it's not an error in the file.
    - Starting with different profiles (to make sure the profile wasn't corrupt).
    - Choosing 'Preserve Numbers' or not when outputting PDF.
    - All sorts of color combinations. It also appears that if there is black in the color, this value gets shifted to the magenta channel, then the magenta & yellow bump down.
    - Checked the grayscale image to make sure it was flat, and using pure black & white colors. It is.
    I've also tried printing to Distiller (we have Acrobat 8 Pro), but the settings are a lot different here so I'm not sure if I set it up properly. I made a duplicate of the default PDFX3 2002 profile, then edited the color settings to 'Convert Everything to CMYK' and set our printer's profile as the CMYK Color Space. But images are converted to 'DeviceCMYK' and not the profile I put.
    - ANYBODY have any ideas or even know where I would start???
    THANKS. This job needs to go out, but I'm also trying to get a solid workflow down for the future.

    Looks like the issue in the CM thread.
    I'm trying to replicate the issue but haven't done it yet. Still grasping at straws
    1. Did the ID doc ever undergo Convert to Profile?
    2. In Swatch Panel do "Add unnamed colors". Make sure the grayscale is colored with swatches, not colors created in the Color Picker
    3. Do the color values in the swatches have crazy decimal values? Is the color mode of the swatches CMYK?
    4. What format are the grayscale links - TIFF or PSD?
    5. Make certain they are links, not embedded (I'm sure they are links though)
    6. The colorization - are there tints applied to the object colors, or are they 100%?

  • MAJOR EDL Export BUG in 8.2!

    I just upgraded to version 8.2 and now there is a major bug when exporting EDLs with audio clips!   EDLs (cmx3600 format) should only export Timecode In/Out for Source & Record.   The latest 8.2 version is now incorrectly outputting SAMPLE FORMAT for EDLS for any audio clips!  This is a major bug and potentially show-stopping.
    What 8.2 is exporting:
    What it used to (and should continue to) export before 8.2:

    with my PP 8.2.0 (65) Build, I get the same error with edl WAV audio clips until I 'link' video clip with audio clip below on the timeline
    I believe after linking the video clip to the audio clip (below on the timeline), then exporting the edl, the timecode format displays properly
    However, my edl export ability still needs work, because I would think my video timecode needs to match my audio timecode (for linked clips) so I am still working on importing the edl into Speedgrade and 'hearing' the audio
    I was getting the same error audio text file as AjentJJ30, until I 'linked' video with audio,
    so far my edl text file appears as below
    TITLE: edl with wav link
    FCM: DROP FRAME
    001  AX       V     C        00:00:00:00 00:00:24:23 00:00:00:00 00:00:24:23
    * FROM CLIP NAME: bmpcc_1_2015-02-05_0951_C0005_[000000-002420].mxf
    002  AX       AA    C        01:03:06:05 01:03:30:28 00:00:00:00 00:00:24:23
    * FROM CLIP NAME: full shoot
    003  AX       V     C        00:00:24:23 00:00:41:22 00:00:24:23 00:00:41:22
    * FROM CLIP NAME: bmpcc_1_2015-02-05_0955_C0001_[000000-004258].mxf
    004  AX       AA    C        01:06:32:22 01:06:49:21 00:00:24:23 00:00:41:22
    * FROM CLIP NAME: full shoot
    005  AX       V     C        00:00:41:22 00:01:00:10 00:00:41:22 00:01:00:12
    * FROM CLIP NAME: bmpcc_1_2015-02-05_0958_C0003_[000000-004444].mxf
    006  AX       AA    C        01:09:17:29 01:09:36:17 00:00:41:22 00:01:00:12
    * FROM CLIP NAME: full shoot
    EDIT: as you can see my WAV file does not show the proper clip name, as well as not displaying the .wav file extension.
    I chase after the edl displaying proper WAV data, but could not achieve any solid results. My dng video clips from the bmpcc have wav files, normally they do not import into Speedgrade with the dng sequence, so using the video clips to test the edl process isn't very helpful.
    I can not get results to support having the WAV edl data working when importing into SpeedGrade.
    Sorry to think otherwise.

  • Flash not reading colour correctfrom an external PNG? Bug? Or am I missing something?

    Hi guys and gals.
    I have a very interesting bug I think.. Wondering if there is
    a way around the problem I'm having.
    ok.. Very Very simply script here..
    Make new flash movie..
    On frame one.. put this code.
    r=this.createEmptyMovieClip('currentImageMask',this.getNextHighestDepth());
    r.loadMovie('test.png');
    (because I'm lazy and didnt put in loading detection... on frame
    20 put this code.
    import flash.display.BitmapData;
    image_bitmap = new flash.display.BitmapData(r._width,
    r._height,false);
    image_bitmap.draw(r);
    curr_colour = this.image_bitmap.getPixel(5, 5); //0
    trace(curr_colour.toString(16));
    stop();
    Now... make a simple image with the rgb colour 100,100,100
    filled in it. (Mine is a simple 50x50 pixel image filled with that
    colour. save the png as "test.png" and put next to the fla with
    code above. You will see that the colour returned in the trace is
    not the hex value that matches color 100,100,100... it matches
    99,99,99. Flash isnt reading the colour correctly...
    Now this same test returns the correct color and works fine
    if using a .gif or a .jpg. but I cannot do what I want with these
    formats. it must be a png.. .it must read the rgb value 100%
    correct every time and the image MUST be loaded from an external
    file.
    It seems that regardless the rgb is off by one. so if colour
    was 25,25,25 it would be returned as 24,24,24
    Is there any other way to do what I need to do.. or is there
    a bug in my code.. please anyone help.. I'm pulling my hair out
    with what should be a simple damn thing to do.

    There are two reasons why I cant/wont to do that ....
    1... If it is a bug.. Adobe will fix it and my program will
    break... (Ina lot of places)
    2... the colour 0,0,0 comes back 0. teh coloru 1,1,1 also
    comes back 0... So regardless I cnat tell teh difference between
    0,0,0 and 1,1,1... (This is very important for the program to
    accuratly determine these colours)

Maybe you are looking for