Yes. I’m aware. I think that’s the reason why it never went through. We were always a small team and that would require quite some time from development and from the documentation people.
My idea here is that you keep it to a minimum possible and for more info you use the clichê “for more on bla bla check this link” that would led you to the wiki respective page.
Hey @AndreaDelSignore, I have a question for you:
The great feature of allowing to download of the pedalboards was something that you added or was some heritage from the stuff already in the official image, but not released?
I’m asking, because I miss a (somehow obvious) feature to allow the upload of pedalboards 
I only added it to make debugging easier at the beginning.
BTW, I’ll try to push out a new version this weekend — I didn’t have much development time in this cycle.
Yes, there isn’t was just a debugging feature, perhaps I should hide for now…
Gotcha!
Personally, I like it.
This helps you back up stuff and keep it somewhat organized.
I give a practical example: let’s say you are recording a new track and you have created a pedalboard for that. You can easily store the pedalboard file in the same folder that you store all audio recordings, DAW sessions, etc., so you can easily track everything. And if you have a problem in your MOD Dwarf and you may lose some data, you play on the safe side and you don’t lose the most important one.
My suggestion: survey the community 
That sounds cool I’m excited about it.
New small release! Even though I didn’t have much time for this cycle, Starless has still made good progress.
For this round I managed to complete the MIDI tab in the binding overview and fix a critical bug in the performance view. I also submitted the final pull request to the standard firmware to add support for port groups.
Once it’s accepted, we can start improving the plugin definition files to include port group data and get a cleaner, more consistent interface overall.
Thanks to the community for the support and to @jon for the input and all the advice!
Download: Release aLabs version 8 (beta) · sejerpz/alabs-mod-custom-images · GitHub
MIDI in bindings is great!
Performance view on the laptop & Plugin Edit on the Dwarf is so good, I just found out how good…
Great news @AndreaDelSignore
And thank you for everything that you are providing to the community! This is really awesome!
I’m here for that and I’m happy on doing it. I will try to keep it flowing as much as possible and give you all the tools that you need to keep what you are doing.
I actually may have found a bug on the plug-in editor just the other day. But I want to try on this new version before reporting it.
I can tell you that on the weekend I was with a guitarist friend that is considering to get a MOD Dwarf to a synth setup that now he requires on a fairly big project he plays and the plugin editor was one of the features that most excited him. And thats 100% yours
So I’m back to report the bug…in the meantime, I found another that is more visual than anything else: on the Cabinet Loader plugin editor, it seems to be a glitch that creates a funny spot under the plugin title, it also makes somtimes either the header for “Presets” or the preset name itself a bit “funky”
Now the bug I wanted to report: When changing presets on AIDA-X it freezes the full UI. Audio still goes through, but you can’t interact with the device anymore. You can also still access the WebGUI while the device interface is frozen.
It actually seems to have something more on the behaviour. First, I access the Plugin Editor for AIDA-X and try to change the preset and on the screen, I get another control being changed (always from the LP1 that I also have on this pedalboard). Then I go back to the plugins list and go back to the AIDA-X and it freezes.
Check the video. (Actually, while recording the video, I managed to go a step further than I ever got before, but I believe it was only because I was fast).
EDIT: I guess it interacts with that parameter of the LP1 because it’s what I have assigned for that very same encoder on the first page and first subpage.
Thank for the report.
The UI glitch was already reported by Abotte IIRC, but I didn’t manage to find the root cause and fix. Anyway it’s just a cosmetic bug.
The freeze is instead a major bug, I’ll take a look ASAP and report back when I found a fix or if I need some more testing.
Ah sorry, forgot about that. Yes, it’s a bug that “doesn’t bug me” 
Cool. Let me know if you need some extra info from my side.
And thanks a lot!
Hi Andrea,
I have a small bug to report, nothing to worry about since it’s quite a remote use case: I noticed that the binding assignment is not working if you have the onboard plug-in editor open. It seems to really assign the control to a footswitch (the icon of the assigned parameter turns purple), but on the device, the binding is not acquired. I didn’t try, but I guess that assigning an encoder would be the same.
I’m reporting this because I assume you’d find any feedback valuable, but I’m not sure it’s worth fixing. This bug requires using the on-board plugin parameter editor and the web GUI simultaneously, which is quite a nonsense imho
Hi, yes I find any feedback valuable.
Yes, but we can do better, there are some places in the firmware that display a message when attached to the web gui, may be I should do the same and don’t allow on device editing while connected with the GUI.
Ehm, please don’t
I find it very handy to use both the web GUI and the on board editor at the same time, and I remember a post of another user who tweaked the software to bypass that nag screen.
If you think you really need to solve the issue, maybe you should prevent the web GUI from saving a binding if the onboard editor it’s opened.
Don’t get me wrong… But you can’t take that hiatus. lol… Looking forward to more updates. This project is sensational! Congratulations!
Hello,
as expected development slowed down during december and january, too busy at work, but I’m near a new release.
I hope to finish the last things in the next weeks 
@jon I didn’t manage to reproduce your bug would mind to send me the pedalboard?
Sure! I’m really happy that you are getting back on this
Little note, not sure why, but I was not able to share the pedalboard via the share pedalboard feature over the pedalboard feed. I was always getting an error both with your MOD OS version as with the original. So I took it over ssh.
Here is a zip file of it: https://drive.google.com/file/d/1hFIIzDIyY53oWH0Kg_COsFkyu8AbHVP8/view?usp=sharing
I have another thing to add on this: the controls that actually show up is what I have assigned on the normal assignments system. First page, first sub-page.
Thank you so much for creating this great addition to the ModDwarf! I understand that it`s a lot of work and possibly extra work with bugfixes and so on.
Anyway, I still dare to wish for implementation of two way midi. Maybe this would still work? Midi cc out nrpn by AndrewCapon · Pull Request #62 · mod-audio/mod-host · GitHub
I will also try to report if I discover some bug.
That would be great !
@AndyCap (Andrew Cap already made the code but was never merged with the MOD OS.
I can’t find it…
Here is a thread talking about it this some Guthub links
