BUG: PNG saving at 72.09 dpi

This bug has plagued me for a couple YEARS now and yet Adobe has done nothing to fix it despite my reporting it 2 or 3 times and the support person acknowledged it was in fact a bug!
Create an image. Doesnt matter what size. Use standard web format: RGB, 72 dpi
Now, double check that DPI is 72
Save the image as PNG format (24bit) using regular Save-As.
Close the image. Now open it in Photoshop.
Look at the DPI. It will say 72.09
This does not happen if you use Save-For-Web
Now you may ask, "So What?" Well, if you do a lot of work with Flash, the fact that the DPI is wrong causes images to be displayed in Flash slightly wrong. For example a 300x250 pixel bitmap image might end up displayed at 299x249. Or sometimes it will show the correct size, but if you look at the Transform panel, the percent scale will show something like 99.9% instead of 100%.
Not only is that annoying in Flash, but in Photoshop if I want to do a quick edit of a PNG and then just hit CTRL-S to save it, I can't otherwise the DPI gets changed. I always have to go through the longer multi-step process of "Save-For-Web" !
Adobe: FIX THIS NOW. This bug was also present in previous versions of Photoshop.

*SIGH*
Listen, I know it's great to jump on the new guy cuz he appears here out of nowhere complaining etc... but listen:
I've been using Flash for over 10 years. Longer for Photoshop. I am intimately acquainted with optimizing techniques in Flash in conjunction with Photoshop. I'm behind by 1 version in Flash, so yeah, maybe I should explore the PSD importing a little more. However I need to make this point:
- Flash strips out the extra info you speak of, so it's irrelevant. Workflow is what matters and this "bug" (if we can agree to disagree on calling it a bug or not) interrupts what used to be a very fast workflow: Edit, CTRL-S, done
- Photoshop did not introduce "72.009" until (if memory serves correctly) version CS2 or maybe CS1. Prior to this it kept PNG's dpi to 72. I reported the problem back when I figured it out in CS2. Nothing changed.
- Actually, in the interest of being fair, Flash for many versions would display PNGs that had 72.009 correctly and then starting with Flash 9 it would display PNGs at the 1 pixel less sizing I mentioned above (ie: 299px instead of 300px)
- There is no practical reason for 72.009 regardless of it being a translation of inches to pixels. Pixels and screen resolutions use integers. That's the bottom line, and PNG is a web format, not a print format.
So, this is one of those situations where the buck can be passed from Photoshop to Flash and Flash to Photoshop for all eternity, as seems to be the case. But let me ask, is there any practical or rational reason for PNGs to keep automatically defaulting to 72.009 ? And if so, then why not also apply this logic to GIF, JPG, etc?
I'll go make noise in the Flash forum.
Bye

Similar Messages

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

Problem with screenshots--PNG displays at 72.009 DPI

Hi, I thought this might be the most appropriate forum... plesae move if it's not.
I've noticed that when I take screenshots that are saved as PNGs, they display in Photoshop as 72.009 DPI. But when I save as GIFs, JPGs, etc., they display as 72 DPI.
Why do screenshots saved as PNGs add this extra information?

*SIGH*
Listen, I know it's great to jump on the new guy cuz he appears here out of nowhere complaining etc... but listen:
I've been using Flash for over 10 years. Longer for Photoshop. I am intimately acquainted with optimizing techniques in Flash in conjunction with Photoshop. I'm behind by 1 version in Flash, so yeah, maybe I should explore the PSD importing a little more. However I need to make this point:
- Flash strips out the extra info you speak of, so it's irrelevant. Workflow is what matters and this "bug" (if we can agree to disagree on calling it a bug or not) interrupts what used to be a very fast workflow: Edit, CTRL-S, done
- Photoshop did not introduce "72.009" until (if memory serves correctly) version CS2 or maybe CS1. Prior to this it kept PNG's dpi to 72. I reported the problem back when I figured it out in CS2. Nothing changed.
- Actually, in the interest of being fair, Flash for many versions would display PNGs that had 72.009 correctly and then starting with Flash 9 it would display PNGs at the 1 pixel less sizing I mentioned above (ie: 299px instead of 300px)
- There is no practical reason for 72.009 regardless of it being a translation of inches to pixels. Pixels and screen resolutions use integers. That's the bottom line, and PNG is a web format, not a print format.
So, this is one of those situations where the buck can be passed from Photoshop to Flash and Flash to Photoshop for all eternity, as seems to be the case. But let me ask, is there any practical or rational reason for PNGs to keep automatically defaulting to 72.009 ? And if so, then why not also apply this logic to GIF, JPG, etc?
I'll go make noise in the Flash forum.
Bye

Photoshop PNGs saved for web in CS3 v.10 still are not transparent in iWeb 08 2.0.4

I have read the topics and tried the tricks and still have black backgrounds on my photoshop graphics. After saving for web & devides as png8 with transparency I have a checkerboard pattern behind my graphic. I am using the magic wand tool, selecting the emptiness/checkerboard behind, then choosing to select the inverse, the ctrl c, then ctrl v in iWeb
Thanks for any help.
Kristie

When you use the Save For Web or Devices be sure to click on black in the pallet and then on the transparent "button" just below the pallet before saving as a png file.
OT

Apparent Bug in Saving ACR Presets

I was experimenting with some Camera Raw presets for a new camera and discovered that when I saved a preset for the Detail panel, some of the values were omitted. Specifically, the preset did not save the values for Luminous Detail, Luminous Contrast, and Color Detail from the Noise Reduction section of the Detail Panel. Shown below is a preset I saved with dummy values to illustrate this problem. You can see that the three values I mentioned above are missing from the preset. Would someone please try this on their computer to see if this is indeed a bug or if I have something else going on?
I’m using Camera Raw 6.3 on a 64-bit Windows 7 computer. Photoshop version is 12.0.3x64, and Bridge is version 4.0.4.2. If this is an actual bug, maybe someone who has ACR 6.4RC could check to see if it’s still a problem in this newer version.
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.2-c004 1.136881, 2010/06/10-18:11:35        ">
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<rdf:Description rdf:about=""
    xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/">
   <crs:Version>6.3</crs:Version>
   <crs:Sharpness>37</crs:Sharpness>
   <crs:LuminanceSmoothing>56</crs:LuminanceSmoothing>
   <crs:ColorNoiseReduction>37</crs:ColorNoiseReduction>
   <crs:SharpenRadius>+1.3</crs:SharpenRadius>
   <crs:SharpenDetail>27</crs:SharpenDetail>
   <crs:SharpenEdgeMasking>48</crs:SharpenEdgeMasking>
   <crs:HasSettings>True</crs:HasSettings>
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>
Thanks,
Chuck

I got a lot more - including I think the ones you're saying you're missing - when I tried it with 6.3, as shown below.
Did you check all the boxes in the dialog asking you what you wanted to save?
-Noel
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.2-c004 1.136881, 2010/06/10-18:11:35        ">
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<rdf:Description rdf:about=""
    xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/">
   <crs:Version>6.3</crs:Version>
   <crs:ProcessVersion>5.7</crs:ProcessVersion>
   <crs:WhiteBalance>As Shot</crs:WhiteBalance>
   <crs:Exposure>-0.25</crs:Exposure>
   <crs:Shadows>0</crs:Shadows>
   <crs:Brightness>+50</crs:Brightness>
   <crs:Contrast>+25</crs:Contrast>
   <crs:Saturation>-8</crs:Saturation>
   <crs:Sharpness>15</crs:Sharpness>
   <crs:LuminanceSmoothing>40</crs:LuminanceSmoothing>
   <crs:ColorNoiseReduction>0</crs:ColorNoiseReduction>
   <crs:ChromaticAberrationR>0</crs:ChromaticAberrationR>
   <crs:ChromaticAberrationB>0</crs:ChromaticAberrationB>
   <crs:VignetteAmount>0</crs:VignetteAmount>
   <crs:ShadowTint>0</crs:ShadowTint>
   <crs:RedHue>0</crs:RedHue>
   <crs:RedSaturation>0</crs:RedSaturation>
   <crs:GreenHue>0</crs:GreenHue>
   <crs:GreenSaturation>0</crs:GreenSaturation>
   <crs:BlueHue>0</crs:BlueHue>
   <crs:BlueSaturation>0</crs:BlueSaturation>
   <crs:FillLight>0</crs:FillLight>
   <crs:Vibrance>0</crs:Vibrance>
   <crs:HighlightRecovery>0</crs:HighlightRecovery>
   <crs:Clarity>0</crs:Clarity>
   <crs:Defringe>2</crs:Defringe>
   <crs:HueAdjustmentRed>+1</crs:HueAdjustmentRed>
   <crs:HueAdjustmentOrange>+3</crs:HueAdjustmentOrange>
   <crs:HueAdjustmentYellow>+5</crs:HueAdjustmentYellow>
   <crs:HueAdjustmentGreen>-5</crs:HueAdjustmentGreen>
   <crs:HueAdjustmentAqua>-25</crs:HueAdjustmentAqua>
   <crs:HueAdjustmentBlue>0</crs:HueAdjustmentBlue>
   <crs:HueAdjustmentPurple>0</crs:HueAdjustmentPurple>
   <crs:HueAdjustmentMagenta>-3</crs:HueAdjustmentMagenta>
   <crs:SaturationAdjustmentRed>-5</crs:SaturationAdjustmentRed>
   <crs:SaturationAdjustmentOrange>-4</crs:SaturationAdjustmentOrange>
   <crs:SaturationAdjustmentYellow>+1</crs:SaturationAdjustmentYellow>
   <crs:SaturationAdjustmentGreen>+8</crs:SaturationAdjustmentGreen>
   <crs:SaturationAdjustmentAqua>-2</crs:SaturationAdjustmentAqua>
   <crs:SaturationAdjustmentBlue>-13</crs:SaturationAdjustmentBlue>
   <crs:SaturationAdjustmentPurple>-2</crs:SaturationAdjustmentPurple>
   <crs:SaturationAdjustmentMagenta>-2</crs:SaturationAdjustmentMagenta>
   <crs:LuminanceAdjustmentRed>-5</crs:LuminanceAdjustmentRed>
   <crs:LuminanceAdjustmentOrange>-3</crs:LuminanceAdjustmentOrange>
   <crs:LuminanceAdjustmentYellow>0</crs:LuminanceAdjustmentYellow>
   <crs:LuminanceAdjustmentGreen>+8</crs:LuminanceAdjustmentGreen>
   <crs:LuminanceAdjustmentAqua>+12</crs:LuminanceAdjustmentAqua>
   <crs:LuminanceAdjustmentBlue>0</crs:LuminanceAdjustmentBlue>
   <crs:LuminanceAdjustmentPurple>0</crs:LuminanceAdjustmentPurple>
   <crs:LuminanceAdjustmentMagenta>0</crs:LuminanceAdjustmentMagenta>
   <crs:SplitToningShadowHue>0</crs:SplitToningShadowHue>
   <crs:SplitToningShadowSaturation>0</crs:SplitToningShadowSaturation>
   <crs:SplitToningHighlightHue>0</crs:SplitToningHighlightHue>
   <crs:SplitToningHighlightSaturation>0</crs:SplitToningHighlightSaturation>
   <crs:SplitToningBalance>0</crs:SplitToningBalance>
   <crs:ParametricShadows>0</crs:ParametricShadows>
   <crs:ParametricDarks>0</crs:ParametricDarks>
   <crs:ParametricLights>0</crs:ParametricLights>
   <crs:ParametricHighlights>0</crs:ParametricHighlights>
   <crs:ParametricShadowSplit>25</crs:ParametricShadowSplit>
   <crs:ParametricMidtoneSplit>50</crs:ParametricMidtoneSplit>
   <crs:ParametricHighlightSplit>75</crs:ParametricHighlightSplit>
   <crs:SharpenRadius>+0.5</crs:SharpenRadius>
   <crs:SharpenDetail>100</crs:SharpenDetail>
   <crs:SharpenEdgeMasking>0</crs:SharpenEdgeMasking>
   <crs:PostCropVignetteAmount>0</crs:PostCropVignetteAmount>
   <crs:GrainAmount>0</crs:GrainAmount>
   <crs:LuminanceNoiseReductionDetail>100</crs:LuminanceNoiseReductionDetail>
   <crs:LuminanceNoiseReductionContrast>0</crs:LuminanceNoiseReductionContrast>
   <crs:LensProfileEnable>1</crs:LensProfileEnable>
   <crs:LensManualDistortionAmount>0</crs:LensManualDistortionAmount>
   <crs:PerspectiveVertical>0</crs:PerspectiveVertical>
   <crs:PerspectiveHorizontal>0</crs:PerspectiveHorizontal>
   <crs:PerspectiveRotate>0.0</crs:PerspectiveRotate>
   <crs:PerspectiveScale>100</crs:PerspectiveScale>
   <crs:ConvertToGrayscale>False</crs:ConvertToGrayscale>
   <crs:ToneCurveName>Custom</crs:ToneCurveName>
   <crs:ToneCurve>
    <rdf:Seq>
     <rdf:li>0, 0</rdf:li>
     <rdf:li>34, 22</rdf:li>
     <rdf:li>67, 60</rdf:li>
     <rdf:li>138, 144</rdf:li>
     <rdf:li>193, 204</rdf:li>
     <rdf:li>255, 255</rdf:li>
    </rdf:Seq>
   </crs:ToneCurve>
   <crs:CameraProfile>Camera Standard</crs:CameraProfile>
   <crs:CameraProfileDigest>F0D06C559756F7BD7331A9DB44BF84DD</crs:CameraProfileDigest>
   <crs:LensProfileSetup>LensDefaults</crs:LensProfileSetup>
   <crs:HasSettings>True</crs:HasSettings>
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>

[Bug Report] saving issue

just wanna report some bugs in LP8.
1. Pack/Unpack Folder
When we unpack the track folder,
Some of Track Names are not saved.
(default name appears)
Empty track in folder can't be unpacked
2. Ultrabeat
Editing voice name is not saved
3. Mouse Button
Assigning Mouse button is not saved
Message was edited by: korri78

Apple probably doesn't see things posted here, try this:
http://www.apple.com/feedback/logicpro.html

Bug while saving multi select list

Hi,
My requirement is to construct a region where user can select their answer from available option. answer field can be multiple select/single select or text area.
I have written below query to achieve different type of answer field.
/**query****/
DECLARE
v_sql VARCHAR2 (32767);
v_answer VARCHAR2 (32767);
v_main_sql VARCHAR2 (32767);
BEGIN
FOR cur IN (SELECT question_id, question, answer_type, available_answer FROM question WHERE status= 'ACTV')
LOOP
v_sql := 'SELECT ';
v_sql := v_sql || ' APEX_ITEM.hidden(4,question_id)||question question, '; /*do not show question id as per requirement*/
IF cur.answer_type = 'MS' -- Multi Select List
THEN
v_answer := cur.available_answer;
v_sql :=
v_sql
|| ' APEX_ITEM.SELECT_LIST_FROM_QUERY(3,null,''SELECT * from table(
AU_F_LOV_FN('''''
|| v_answer
|| '''''))'',''class="multiselect" multiple="multiple"'',''NO'') Answer ';
ELSIF cur.answer_type = 'SS'
THEN -- Single Select List
v_answer := cur.available_answer;
v_sql :=
v_sql
|| ' APEX_ITEM.SELECT_LIST_FROM_QUERY(3,null,''SELECT * from table(
AU_F_LOV_FN('''''
|| v_answer
|| '''''))'') Answer ';
ELSE -- Free text
v_sql := v_sql || ' apex_item.textarea(3,available_answer,2,20) Answer ';
END IF;
v_sql := v_sql || ' from question ';
v_sql := v_sql || ' where question_id=' || cur.question_id;
IF v_main_sql IS NULL THEN
v_main_sql := v_sql;
ELSE
v_main_sql := v_main_sql ||' UNION ' || v_sql;
END IF;
END LOOP;
RETURN v_main_sql;
END;
/***end of query***/
If I select two options from multiple select list it is saving two records into table instead of saving one record with colon delimeter.
/**query to save**/
FOR i IN 1 .. APEX_APPLICATION.G_F03.COUNT
LOOP
IF APEX_APPLICATION.G_F03(i) IS NOT NULL THEN
UPDATE question_answer
SET answer = v_answer
WHERE question_id = APEX_APPLICATION.G_F04(i)
and call_id=p_sourceid;
IF sql%rowcount =0 then
INSERT INTO question_answer (question_id,
answer,
call_id,
status,
customer_id)
VALUES (APEX_APPLICATION.G_F04(i),
nvl(v_answer,APEX_APPLICATION.G_F03(i)),
p_sourceid,
'ACTV',
p_customer_id);
END if;
END IF;
END LOOP;
/**End**/
Can anyone please help me? Why is it happening? How to tweak my query so that it saves one record with colon delimeter.

Technically, my understanding is that a Shuttle is just two multiselect lists where javascript moves the items from one to the other. Technically its the same thing, just different presentation and methods for selection. When you go to process, its seen the same way as you initially had your code setup so no code changes would have been necessary. As it's a built in item type and with APEX's backwards compatibility policies, if your code works now it should continue to work.

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

Saving bufferedimage as 300 DPI tiff

Hi !
I have a tiff image (300 dpi) which i read process (rotate, scale, apply icc profile ...) And when I save it (see below) it ends up in a 72dpi image ... I have browsed the forum and I see lots of people have problems with this issue, but I didn't find any answer :(
Please help if you can :)
Regards
How I Write The Image
OutputStream out = new SeekableOutputStream(new RandomAccessFile(Destination,"rw"));
TIFFEncodeParam param3 = new TIFFEncodeParam();
param3.setCompression(TIFFEncodeParam.COMPRESSION_DEFLATE);
ImageEncoder encoder = ImageCodec.createImageEncoder("TIFF", out, param3);
encoder.encode(GeneratedImage);
out.close();

public class ris{
public static void main(String args[]) throws IOException{
final int XRES_TAG = 100;
final int YRES_TAG = 100;
int[] resolution = { 150, 1};
String input = "C:/a/01.tiff";
String output = "C:/a/nuovo.tiff";
RenderedOp image1 = JAI.create("fileload", input);
TIFFField xRes = new TIFFField(XRES_TAG, TIFFField.TIFF_RATIONAL, 1, new int[][] { resolution });
TIFFField yRes = new TIFFField(YRES_TAG, TIFFField.TIFF_RATIONAL, 1, new int[][] { resolution });
TIFFEncodeParam tep = new TIFFEncodeParam();
tep.setExtraFields(new TIFFField[] { xRes, yRes});
OutputStream out = new SeekableOutputStream(new RandomAccessFile(output,"rw"));
tep.setCompression(TIFFEncodeParam.COMPRESSION_DEFLATE);
ImageEncoder encoder = ImageCodec.createImageEncoder("TIFF", out, tep);
encoder.encode(image1);
out.close();
i wrote the same codebut it throws this exception
java.lang.ClassCastException
at com.sun.media.jai.codec.TIFFField.getAsRationals(TIFFField.java:267)
at com.sun.media.jai.codecimpl.TIFFImageEncoder.writeValues(TIFFImageEncoder.java:1804)
at com.sun.media.jai.codecimpl.TIFFImageEncoder.writeDirectory(TIFFImageEncoder.java:1608)
at com.sun.media.jai.codecimpl.TIFFImageEncoder.encode(TIFFImageEncoder.java:1436)
at com.sun.media.jai.codecimpl.TIFFImageEncoder.encode(TIFFImageEncoder.java:161)
at Image.immagini.ris.main(ris.java:35)
Exception in thread "main"
What could it be?

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 !

[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)

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

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.

Bug in fireworks CS4 when exporting 24/32bit png with transparent alpha?

Hi there,
I recently upgraded to CS4 from CS3 and am quite disappointed to find that the png export facility for 24 or 32 bit png's is next to useless on my installation of Fireworks (Vista). I have a colleage who has reported the same behanviour on his mac.
Please see this native fireworks CS4 png file and attempt to export it as 24 or 34 bit png, ensuring the canvas is transparent (it shuold be already)...
http://www.capitalh.net/demo-bug.png
Viewing in preview mode in CS3 would show the png with its alpha channel indicated by the chequered transparent pattern. Exporting it as such would produce the desired result > a png with a nice blended alpha channel.
Viewing in preview mode in CS4 shows a horrible render of the image on a white background. Exporting the image produces the same result. Please see this link for confirmation:
http://www.capitalh.net/demo-bug-export.png
Please also see this simpler image, this time using a simple ellipse shape:
http://www.capitalh.net/demo-bug-export-simpleshape.png
You'll notice that it is not transparent, and the ellipse has not been anti-aliased.
Can anyone shed some light on this behaviour?
Exporting png's as such is something that I do daily at work, and is a basic requirement of an image editting application targetted at web design.
Am I doing something wrong? I've been using Fireworks since 2003 so I'm inclined to think that I'm not.

That's a bit, um, oh never mind. Would've been a rubbish joke anyway.
Aww...pooh. I love "rubbish" jokes!
If fireworks is unable to export a transparent png at 24bit, then why have the option?
(granted the option is acutally implied, not given)
Also, why the horrible rendering on preview and export?
Transparency for 24-bit isn't an option and isn't implied. Create a FW document with a transparent canvas. Go to File>Image Preview. If you select PNG8 as your export option, then you have drop-downs for No Transparency, Index Transparency, or Alpha Transparency. PNG32 shows the checkerboard where the document is transparent. If you select PNG24, you do not have the transparency options. Transparent areas in your document are set to white, just as they are if you select the JPEG format. Try it.
I don't know why your rendering is horrible. I'd have to see your image.
And also, why all this confusion related to Photoshop, seems Adobe really aren't helping the issue:
http://forums.adobe.com/thread/152434
Possibly Adobe thought it was less confusing, as they didn't have to go into the math. However, you do see Linda Rathgeber's answer, that the Photoshop convention is...well...misleading? (I'd call it wrong, but that's just me. ) It's just one other issue to bring into alignment as Adobe works to merge the Macromedia offerings into their line.

Png in pdf : acroread bug

If you put a png image in a pdf (with latex → pdflatex), it works with other viewers (evince, kpdf), but not correctly with acroread.
Please look at the screenshots :
evince : http://www.monsterup.com/upload/1212654879.jpg
kpdf : http://www.monsterup.com/upload/1212655058.jpg
acroread : http://www.monsterup.com/upload/1212655093.jpg
Is this bug already reported?
How to report a bug in your site, you don't have a launchpad-like?

I added :
\pdfminorversion 5
So the generated pdf is pdf 1.5 (seen in pdf properties in acroread).
But the problem with png files still occurs.
To resolve the problem, I just remove the alpha channel (in gimp for example) of my png, and acroread displays it correctly.
EDIT: with \pdfminorversion 7 (pdf 1.7), acroread has no the bug.
png are correctly displayed.

BUG: PNG saving at 72.09 dpi

Similar Messages

Maybe you are looking for