Liquify

[jim100361]

Not trying to be negative here, but can you or someone please post more samples of what exactly this plugin does before I consider installing it? I'm sure it's great, but the sample you provided in your first post doesn't really show much of what it does. Thanks ahead of time.

Just a simple example using the "Push" feature in the plugin.

Before:

After:

And yet another:

[oma]

from pg 49 in my gallery I did a tulip using the very first version of smudge. If I was to do this picture again. Liquify would be a better option for some of the shaping.

Edited November 23, 2011 by oma

[onegray]

Is there a way to save mesh to some kind of "human readable" format? Are there any current mesh file format specs?

I need it coz I want to use saved meshes in my computer game.

Thanks!

[Ego Eram Reputo]

Try searching for the Photo Shop mesh file format. This is the format that Liquify uses.

[Ego Eram Reputo]

Recommended this plugin again today. I love it!

I tickled the donate button - hope this is making Pyrochild plenty!

[pyrochild]

Update:

- Fixed color window showing alpha = 0 when a color is opaque black

[pyrochild]

Liquify is on GitHub! Go check it out! https://github.com/bsneeze/pdn-liquify

[Rickhum]

Top plugin pyrochild. I've used it for Ebru effects (marbling) and for tricky tweaks.

Used it a lot in some of my abstracts as well.   

 

[BoltBait]

I can't believe I've never posted on this thread telling you how awesome I think this plugin is.

 

Absolutely brilliant! I love it!

 

 

[nicknack23]

Photoshop has changed the file format of .msh files created in Photoshop's Liquify. The newer .msh files are much smaller (50-300 kB) compared to the original .msh files which were often 15+ MB each. Probably Adobe is just compressing the old files, but I suspect the compression is lossy because of the massive reduction in file size. The old larger files can still be imported in Photoshop but can only be saved in the new smaller format.

 

What this means is that Paint.net's Liquify is now only partly compatible with Photoshop's. Meshes created in Paint.net can be imported into Photoshop, but not the other way around. So I'd like to know: will the plugin be updated to read Photoshop's newer format? And in any case, would anyone be willing to speculate on how the new meshes may be being compressed? That could help any reverse engineering attempts ...

[pyrochild]

I don't have Photoshop. Could you attach:

• A .msh exported from Photoshop
• Dimensions of the image it was created for
• Before and after image of the mesh's distortion

Then I can take a look... no promises

[nicknack23]

No problem. I made three PNGs of various sizes and used the "push brush" twice in Liquify to make simple test meshes. Dimensions are in the file names. The resulting zip file is too big to attach (still only 1.4 MB), but here's a link to Mega.nz:

https://mega.nz/#!We5QkARI!2-qD_qK2e8ADnYJcT578x9RxXo4uvBH0rXeDPeR-pRU

 

I understand there are no promises when trying to reverse engineer something, but thanks a lot for trying!

 

 

[nicknack23]

Hey pyrochild, I assume you didn't manage to crack this since I haven't heard anything. But I'm going to need to look into this myself, so please let me know if you made any progress at all that could give me a head start. For example, any thoughts on what kind of compression Adobe is using to get such large compression ratios (see my previous post)?

 

[Sakana Oji]

How would someone obtain Liquify for v3.36?

[pyrochild]

By time traveling 10 years into the past, then writing the Liquify plugin yourself since it didn't exist back when 3.36 was a reasonable version of Paint.NET to be using

[Ego Eram Reputo]

🤣 You crack me up pyrochild

[HyReZ]

       "Sherman, set the WABAC Machine to the summer of 2008!"

Edited March 13, 2019 by HyReZ

[Sigurd]

Not using paint.net myself (actually making competing app), but since we're all helping each other out. (Yes, it seems new mesh format isn't saving as much data, width/height are smaller than original width/height)

 

 

Last bit of my code:

 

        if (version === 2)
        {
            var width = stream.readUint32();
            var height = stream.readUint32();

            ...

        }

        else    // version === 4
        {
            var width = stream.readUint32();
            var height = stream.readUint32();

            if (width > 32768 || height > 32768) {
                throw new Error("Liquify Mesh File - width or height too large");
            }

            var _unknown0 = stream.readUint32();
            var _unknown1 = stream.readUint32();
            var _unknown2 = stream.readUint32();
            var _unknown3 = stream.readUint32();

            var width2 = stream.readUint32();
            var height2 = stream.readUint32();

            var _unknown4 = stream.readUint32();
            var _unknown5 = stream.readUint32();

            var width3 = stream.readUint32();
            var height3 = stream.readUint32();

            var data = new Float32Array(width*height * 2);

            for (var y = 0; y < height; ++y)
            {
                var x = 0;
                while (x < width)
                {
                    var skip = stream.readUint32();
                    x += skip;
                    if (x >= width) {
                        if (x !== width) {
                            throw new Error("Error in file");
                        }
                        continue;
                    }

                    var offset = (y * width + x) * 2;
                    var count = stream.readUint32();
                    for (var xend = x+count; x < xend; ++x) {
                        data[offset++] = stream.readFloat32() / width;
                        data[offset++] = stream.readFloat32() / height;
                    }
                }
            }
            assert(stream.pos === stream.length);
 

[nicknack23]

Wow, thank you so much @Sigurd!

 

So if I'm reading your code right, it seems all Adobe did in the new Liquify file format is to scale down mesh width and height by a factor 4 (each) and implemented a simple compression scheme that skips consecutive zero displacement vectors at the start and end of each line. And to compensate for the lower mesh resolution, displacements are stored as double precision floats instead of single precision. Is that correct?

 

Do you know what width2, height2, width3 and height3 represent? They seem unused in your code.

 

Would you like to share what competing app you're developing? Looks like Javascript so I'm guessing a web app.

 

Great work and thanks again for sharing!

[Daveth'st]

hey so I know it's a lil bit late but yeh tried your plugin recently and the result was way too much pixelated, so I'm asking you if I can do something to fix this or if I can just wait some update, thank you!

[CybOn]

[toe_head2001]

@CybOn, your hard drive is at capacity. You should delete or move some stuff off of it.

[CybOn]

On 8/7/2019 at 8:24 PM, toe_head2001 said:

@CybOn, your hard drive is at capacity. You should delete or move some stuff off of it.

 

i had 10 GB free now its down to 2 out of nowhere. wtf

[thesammy58]

First off, I want to say that this is by far the plugin I've used most for a few years now. Simple and easy to utilize. So thank you for that! 4 quick gripes/suggestions that you're of course welcome to take with a grain of salt:

 -Undo/redo is very slow with larger adjustments

-The entire paint.net application will crash if your brush size is too large (~700px, which is sometimes needed for high resolutions) -- I've lost work to this

-Using the effect near the edge of an image reveals a "wall" against the edge that can't be adjusted

-I frequently find myself wishing I could liquify an image while still being able to see the layers above/below it, too

 

Again, I love all of your work, having made use of it for years now. These are just the wishes/issues I've encountered the most. But hey, it's free! 😛

Edited October 20, 2019 by thesammy58

[MJW]

On 10/19/2019 at 7:48 PM, thesammy58 said:

I frequently find myself wishing I could liquify an image while still being able to see the layers above/below it, too

 

Unfortunately, that's currently not possible for plugins that operate in separate windows, as Liquefy does. Plugins don't have access to information from any layers except the active layer. However (as you may or may not already know),  by right-clicking on the image in Liquify, you can select the Clipboard as the background image. This allows you to copy the merged lower layers to the Clipboard (with Ctrl+Shift+C), then use that as the Liquify background image. Not as good as having the other layers visible, but nevertheless very useful.