![]() I strongly contributed to 5/6 of your links there, and this is the solution I highly recommend. And pyembroidery is about as good as I can do. I have a lot of experience with machine embroidery files now. That matters for visualizing it since the magic palette stops being used at that point. At version 4 they started adding some metadata in there for threads, etc. Brother just shoves a bunch of software specific stuff in between the seek offset and the PEC block, so they can add a bunch of stuff like rectangles and circles in custom blocks that the hardware will never need to see. It's backwards compatible no matter the version since the old machine hardware isn't going to change, and the new software can't make incompatible stuff. Reading PES isn't actually that hard, it gives you the PEC block offset at the beginning and you just jump there and read the stitch content. Would have you up and running no time and works for way more formats. ![]() Though again, just fork pyembroidery and use it directly. But, has a lot of the brother export files with various versions. Might need some fancier ones like with motifs clogging up the header information. I'd guess some free licensed patterned shapes with some non-color changed trimmed elements, saved out from most of the highly popular embroidery programs would scratch that itch. That said, I'll cook up some sample outputs for various formats. ![]() csd since it has encryption it runs afoul of DMCA). It's 250k and basically lets you open and write all the formats I could get my hands on (except. Inkstitch likewise just includes it as a fork without any outside updating, it's a fine way to do that. I tried to make it really readable so you can see it doesn't do anything squirrelly. Take it and plug it into your code anyway you want. ![]() It's MIT licensed, there's no demand that you need to support the code. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |