Once I got the hang of Inkscape, making the SVG became kind of relaxing, like crochet or knitting lol

Thank you! Next I'm gonna try to get colors closer to the common themes, tweak the settings, and then try other devices.

I managed to convert Utility from a raster screenshot to SVG by hand in Inkscape, then adjust in a slicer and print. That's close to credit card size.

and eventually I will add actual volume bars lol

so we'll see how it goes as is. I made that print in January so I've learned a bit more since then; it needs to be optimized heavily to reduce waste and print time.

This is a 3D version I was able to make by scaling the Ableton UI as big as it could go, taking a screenshot, then loading that into some BambuLab software to help separate the objects, emboss them, then sliced it. 1st attempt was AWFUL because the 0.4mm nozzle was too big. But now I've got a 0.2mm

I thought maybe Ableton was using Qt/QML based on files I found, so I was looking for those objects in memory, but no dice. Now I'm learning that Qt might only be for Push, not Ableton itself. Hope you can shed some light here, but if not due to proprietary reasons, I totally understand.

Are the Ableton device images/elements stored somewhere in a more raw format that is accessible to the end-user (without breaking any License Agreement)? I've tried the forensic approach with debugging tools and memory-extraction techniques but that's very difficult obviously.

Hey Linus, random UI/dev question for you. I'm trying to make 3D printed versions of Ableton devices as a personal creative project (not for sale). I've tried using screenshots of the devices, converting them to SVG then CAD, but the results are not great. Manual tracing is an option, but laborious.