Thanks for the report. Immediately I had a lot of trouble with this library trying to get its faceplate and backplate to show up, they have a transparent faceplate overlaid on the backplate.
Does the MM support syntax like this?
Similarly, panel->addLayer doesn’t seem to work
I had to write a workaround for the above just to get one of the layers to load:
Re: aestus, looks like working as intended. It has this knob that’s labeled Module model but it only has two discrete states which get shown in that view.
I’ll look at the addLayer thing. It looks like the workaround you used is just using addChild instead of addChildBelow? And also explicitly setting the box.pos to Vec(0,0) (which is probably important to do)
Update: I see now, your workaround calls addChild() to the ModuleWidget, and the original code calls it to the SvgPanel FrameBufferWidget.
OK, I see what’s happening. There are three PNGs it’s trying to overlay with transparency. What we need to do is make the background one the panel (since that’s always the first/lowest layer), and then make the other two SvgWidget children of the ModuleWidget.
I tested it out, seems to work? (just in the simulator I didn’t bother fixing the font):
It would faster to load and less memory consumed to combine those three images into a single PNG. Not a huge deal, but something like imagemagick could be scripted to do all the modules in one command.
I’ll push how I did it.
Update: pushed to branch faceplate-fix
Updated again today - I reduced some of FFT/window size for MM on the Spectral modes for Fluctus and Etesia. So now the “STRETCH” and “SPECTRAL” modes can run on 48khz 256 buffer size.