I’ve been working on porting over my SignalFunctionSet plugin and I’m finding that while most of my modules render correctly, two have glitched out faceplates. Fugue, posted below, shows the issue. I’ve converted the PNG a few times and had no result. Note that some parts of the device controls are obscured as well (sliders and pots).
Has anybody encountered this issue before?
[edit: I’ve tried conversion with Inskape, Photoshop and the script in the SDK, all similar results]
These look cool, I’m glad you’re porting them!
I did once have a similar issue converting an svg panel from a VCV module to a png for MetaModule, but using the SvgToPng.py script fixed it, and you said you’ve tried that …
I can’t quite make out what it’s supposed to look like, so it’s hard to say. Is it a scaling issue? Or is it that part of the panel is transparent? If you can share the SVG and PNG, that would help.
First though I would run the SvgToPng.py script with the --white and the --height 240 flags. That will remove the two most common issues I came across when porting hundreds of VCV SVGs to MM PNGs: transparency issues, and scaling issues.
metamodule-plugin-sdk/scripts/SvgToPng.py --input res/Fugue.svg --output assets/ --white --height 240
The other thing to check is to see if you have any layers in the SVG that are supposed to be hidden but are showing up in the PNG, or vice-versa. You can use the --layer option to specify a layer by name, but you might also want to open the SVG, make all objects and sub-objects visible and then delete anything that you don’t want to be visible in the PNG.
Thanks Dan, appreciate it! I think I have it sorted out, will test again and reach out with more detail if my fix doesn’t address it.
Just to close the books, I was able to get rid of these issues, things are working well now. For one module, it turned out to be component sizing doing some weird stuff. Thanks again for the help.