I can't figure out how to use this plugin in Photoshop CC - any info on whether that is still supported? Seems they are trying to run everything through that Extension Manager thing now.

Also, I found a couple forum posts mentioning the same issue (not getting it to run in anything newer than Photoshop CS3).

It seems other plugins (e.g. http://www.flamingpear.com/ps-win-other-install.html) are still working in CC 2017 & 2018, so it seems it's possible in general, but is it for SuperPNG?

Hello,
Thanks for awesome plugin! I am super dumb so please excuse me if I am just stupid.

I am trying to use the plugin in a script in PS with that action manager stuff which is already quite peculiar for my tiny mind, and when I save the png, it comes out as indexed colour. The source image is 8 bit RGB.

If I set the source image to 16 bit rgb, the script-saved pngs are 16 bit RGB too.

I am not sure whether there is a setting I should use or how to get 8 bit RBG out of the 8 bit RGB source image - if you can give me a hint I would be super grateful.

thanks again,
cw

I put SuperPNG.8bi in the following location
C:\Program Files\Adobe\Adobe Photoshop 2020\Plug-ins\Generator
After starting PS, I still don’t see superPNG, should this option be in the filter?

If this project is still alivie would it be possible to add an option in the save dialog box that premultiplies colour with alpha please?

Nervermind, just tested CC2018, works great?
Thanks!

Hi
i downloaded the .zip form the web page, then extracted
(3 files, the pdf, a png, and the plugin, but NO folders of 64 or 32bits)
I put the plugin in the -File Formats- folder,
open both photoshops, load a image, and save as... Nothing.
i check - about/plugins... no SuperPNG.

i have win10 - 64bits, but idk what is the problem

On macOS Ventura, after Installing the SuperPNG Plugin, the option for "SuperPNG" shows up in the "save as" dialog, but the import options window doesn't come up as expected when holding the shift key when opening a PNG.

macOS 13.2.1 (22D68)
Photoshop 24.2.0 20230218.r.315 28c9f72 x64

• Compression could start in a background thread immediately as the window is open. This could make perceived save time much shorter.
• If compression is done immediately, then we can show expected file size right in the window.
• For small images the speed setting may not be very important. Instead of a manual setting I suggest either adjusting speed automatically (e.g. if image is 2000*2000px or larger) or showing the control only when the image is large.
• Metadata could be broken down into textual and color data. Some users may want to embed authorship information, but not color profiles.
• Have a visual selector for interlacing (the icons in the mockup could be improved still) to make this option clearer to non-technical users

WDYT?

This is opening an image saved via SuperPNG using File->Open As. If I just open it normally (either Open, or by dragging into PS) then PS uses its default PNG importer and it works fine. However, the reason I installed SuperPNG (which I used to use years ago--thanks for it!!) is because SuperPNG imports transparency as alpha.

Is this a known issue with a known fix? I googled a bunch and didn't see any hits. Opening a PNG saved via SuperPNG without Alpha works fine.

Hi,

I'd like to build SuperPNG with VS 2015 CE. Can you please provide another project?

After auto converting the VC++ projects I tried to import all of the projects in the repo and did not succeed due to unreadable resource files, dependencies etc.

Any help would be appreciated.

thx in advance

so, i'm typing in lowercase right now because i discovered an extremely inconvenient problem with superpng and batch operations - shift/alt keys will open input options even when photoshop is not in focus/minimized/etc, and it does not respect the batch operation option to suppress file open dialogs.

as you might have guessed, i'm running a batch operation right now, one of several i'll need to do tonight

this means that holding down shift to select text in another program can trigger it, or alt tabbing, or, yes, holding shift to capitalize things.

i beg of you to fix this

Hi, first of all, thanks for sharing the source of this! I am trying to find a solution modifying RGB values for transparent pixels (see attached image), and I came across this.

I managed to recompile the plugin in Xcode using your source, after a few changes to the photoshopsdk (some headers not found and such). I am unfamiliar with the PS plugin SDK, but I have a question.

I am wondering, when the plugin gets the pixel data hands off from Photoshop, is the data already "dirty" with the fully transparent pixiels turned to white? Or it's something that the plugin does? If so, is there a way to tell Photoshop not to do before you get the pixel data? I'm really looking for a way to disable this behavior.

Thanks!

I noticed that there is a lot of blank space in the meta data tEXt chunk after </x:xmpmeta> tag and before . I counted 12048 bytes divided into 64-byte long strings each ending with a .