sletz
commented
3 years ago The automatically generated HTML page uses old rendering GUI code that is not really easy to tweak for your own needs. For now there is no really other solution than trying to do it anyway..., or completely remove the audio GUI and use something else (likeFaustUI : https://github.com/grame-cncm/faust-ui which is actually use din the Faust Web IDE) or design something from scratch which is obviously a bit of work.
Le 29 janv. 2021 à 04:25, Bruce Davidson notifications@github.com a écrit :
A project I’m working on is to create a guitar amplifier in the browser using the Web Audio api. It’s actually similar to the example SAM/effects/effectsForBrowser.dsp, so I’ve been playing with that, and though I’m not loving the gui, I do like the sound. So I compiled to the web platform using the webaudiowasm architecture. The problem is that then the fonts are illegible. It is fine when I just click on Run, but when I build it and run the output html, the fonts are the same color as the background, and I can’t read them. I can edit the html, and modify the css, but that seems like the wrong way to go about this. Is there a template I can tweak to make the output legible?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.
darkoverlordofdata
A project I’m working on is to create a guitar amplifier in the browser using the Web Audio api. It’s actually similar to the example SAM/effects/effectsForBrowser.dsp, so I’ve been playing with that, and though I’m not loving the gui, I do like the sound. So I compiled to the web platform using the webaudiowasm architecture. The problem is that then the fonts are illegible. It is fine when I just click on Run, but when I build it and run the output html, the fonts are the same color as the background, and I can’t read them. I can edit the html, and modify the css, but that seems like the wrong way to go about this. Is there a template I can tweak to make the output legible?