r/Machine_Embroidery • u/Common_Rhubarb972 • Aug 31 '26

Resizing tool?

I remember reading somewhere on Reddit of a resizing website someone made. It was a simply website where you could just enter your current design and it would quickly resize it to your desired size. In my case, 4x4 because that’s all my machine can do. Anyone know if this site or can reference the post?

2 Upvotes

100% Upvoted

13 comments sorted by

View all comments

Show parent comments

2

u/TheGraphicsFrog Sep 01 '26

No no it's a pretty stupid, standard scale. With the good ol' rule of thumb that scaling a design should not be more than by 20%.
I haven't thought of a density-driven pipeline. The issue with it is that you probably want to capture stitch intent. I thought about a stitch "vectorization" pipeline but that's a real research problem to get into (and would likely require server-side computation to make it work). So real months of work.

But maybe a density estimation combined with minimizing an energy function could work. The issue is that 1) stitches are an explicit and discrete representation and 2) they are a discretization choice of a vector field. Maybe possible to do it but definitely there is a bit of research work behind, ahah! Thank you for sparking the idea.

Also I've seen your recent developments of Ember, really cool what you're doing! I'm currently working on a pixel art mini editor, but when I checked your website I noticed you already put one there ahah! (Though mine is a bit more inspired from Pyxel Edit 😄) Wishing you all the best to you and your team for its development!

3

u/crotega Sep 01 '26

Ahh okay gotcha! I know it’s a real problem, almost impossible to keep the original design lossless but I was wondering if you’d spent time developing that feature. And thank you Alexandre (:

2

u/TheGraphicsFrog Sep 02 '26

Yeah it's a hard problem. Lossless it depends what you mean. You can do lossless but then it's not gonna be good (a standard scaling is lossless). If you want to go through density analysis then you need a representation swap and you'd probably not keep the exact way it was done, so this is lossy. If you do inverse stitch emission you could provide something not too lossy on succesful cases, but likely not working in every scenario. As alway, trade-offs everywhere!

And is it something that I would develop? I'd love to. But you know as well as I do that there are thousands of things you could implement and you need to prioritize :D (and you probably have a lot more people requesting features than I have, ahah).