Now, this was interesting. I started up the Dwarf and went straight to the plugin store. All plugins I wanted to remove I was able to remove.
On three previous occasions, I got the “could not remove” message. I achieved my goal of housekeeping, but I don’t know what to make of this. At least it does not seem to be related to Starless in any way.
Well…eventually, some weird bug happened.
Just keep a close eye to check if it happens again.
I finally took the time to update to v10 (from b8), It’s flawless !
Thanks again !
5 Likes
I did the update as welll
great work. really good. Its so easy now toedit parameters with the encoders.
thank you
4 Likes
I have yet to try this OS as I’ve hardly touched my device. So I’m assuming this OS is way better than the stock OS?
We are way beyond assumptions now 
The stock firmware is great, but the Starless revamp provided lots of amazing improvements, turning something already solid into a jewel. Highly recommended.
5 Likes
Haha, ok cool. Thanks for the feedback.
New release - aLabs version 11
Another bug-fix release — this should hopefully be the last one. The image should now be stable enough.
If no major issues come up, I’ll soon release version 12a with bidirectional MIDI merged, along with the new VU meter UI.
Please test it and report back here, or open an issue in the GitHub repository.
Download: Release aLabs version 11 · sejerpz/alabs-mod-custom-images · GitHub
12 Likes
this is great… thanks again, @AndreaDelSignore !
v11 is solid for me so far.
i’ve noticed one thing - not specific to v11, but a suggestion: the MIDI page of the bindings display shows original plugin names, rather than edited ones. this makes parsing that list confusing. i suggest showing edited plugin names there.
github issue: Bindings Overview - MIDI - Plugin Names · Issue #43 · sejerpz/alabs-mod-custom-images · GitHub
1 Like
really great indeed, I’m using v11 and it’s running nicely… Thanks!
I just saw a small topic, when you have a tempo parameter with the option Translate value to musical tempo (1/4, 1/8,…) in the device edit it shows a Hz value… which could be fine, but when the value is changed it shows a different number than mod-ui. I’m not sure if this was ok in v10…