Fiddlingβ¦
I'm working on a new knob for #Beast, with bidirectional and unidirectional modes.
The updates may only use "transform:rotate(angle)" #CSS to utilize #GPU acceleration during automation.
Sadly, Chrome cannot compose *inside* and SVG, so I have some nasty splitting and layering of the #SVG elements going on...
Last Tuesday #Beast 0.15.0 was released.
This is most probably the last release that supports the #Gtk+ Beast UI. We have most of the bits and pieces together to move towards the new EBeast UI and a new synthesis core in the upcoming months and will get rid of a lot of legacy code along the way...
https://testbit.eu/2019/rewriting-beast
#electron #linuxaudio
So I've been working on "upgrading" the Font Awesome package used by the new #Beast UI from 4.7.0 to 5.9.0.
Just β in the end I found that the icons look way more crispy and professional in the 4.7.0 version.
Is it just me, or did anyone else experience this with #fontawesome ?
DSP + DAW developer, Free Software author + advocate, contributor to ALSA/GNOME/procps/LibreOffice/etc.