Starless unofficial Dwarf image - ALABS

Ok, I have a working branch with all the Mod Master branch changes: GitHub - AndrewCapon/mod-host at midi_cc_out_nrpn_merged_from_master · GitHub

This is working on linux, I will attach up the Mod Dwarf later today and get a build for that as well…

3 Likes

Hi Andrea,

here’s the log:

desktop.js?v=1.13.5.3315-alabs9:1049 show bindings
hardware.js?v=1.13.5.3315-alabs9:1063 Uncaught TypeError: Cannot read properties of undefined (reading 'find')
    at HardwareManager.buildCCTable (hardware.js?v=1.13.5.3315-alabs9:1063:43)
    at _open (hardware.js?v=1.13.5.3315-alabs9:1476:16)
    at HardwareManager.open_overview (hardware.js?v=1.13.5.3315-alabs9:1805:7)
    at HTMLButtonElement.<anonymous> (desktop.js?v=1.13.5.3315-alabs9:1059:30)
    at HTMLButtonElement.dispatch (jquery-1.9.1.min.js?v=1.13.5.3315-alabs9:2:28337)
    at v.handle (jquery-1.9.1.min.js?v=1.13.5.3315-alabs9:2:25042)
    at _super.bugsnag (buy-button-storefront.js?v=1.13.5.3315-alabs9:7433:30)
HardwareManager.buildCCTable @ hardware.js?v=1.13.5.3315-alabs9:1063
_open @ hardware.js?v=1.13.5.3315-alabs9:1476
HardwareManager.open_overview @ hardware.js?v=1.13.5.3315-alabs9:1805
(anonymous) @ desktop.js?v=1.13.5.3315-alabs9:1059
dispatch @ jquery-1.9.1.min.js?v=1.13.5.3315-alabs9:2
v.handle @ jquery-1.9.1.min.js?v=1.13.5.3315-alabs9:2
_super.bugsnag @ buy-button-storefront.js?v=1.13.5.3315-alabs9:7433

Thanks!

2 Likes

If anyone is brave enough to want to try the midi feedback stuff you can look here: Release mod-host with midi feedback and nrpn support · AndrewCapon/mod-host · GitHub

@AndreaDelSignore I’m not sure if you want to grab this into your image, maybe there is an easier way to install it then?

2 Likes

That’s really a good news, I’m interested for sure, someone can test it a little?

Can I use the branch you linked to try to compile it myself?

@Abotte thanks for the stack trace, it helps but it will be very difficult to make it work without any HW, if you have the patience to give me feedback I’ll try to fix it, just be patient :slight_smile:

2 Likes

Sure! :grinning: Just let me know how I can help (should you decide to compile a firmware version with extra debug logs, I’ll gladly install it and perform any test you’ll need).

Thanks again for this release and for the super handy on-board buffer size switch!

Hi Andrea, thanks a lot for your new release!
The preset bindings selection looks very useful. I played today a little with it… looks there is some index problem when assigning the preset to a knob or foot switch. After changing pages, it shows the next preset, not the selected (except the last). And sometimes I got a Dwarf freezes(audio and web was ok, and no crash screen). Still I didn’t catch when it exactly happens…
EDIT: I did the test just with an empty pedalboard with the GAIN plugin

1 Like

Absolutely you can take that branch and compile it yourself.

I’m not sure of the difference between that and the stuff you have been doing.

To build for the dwarf I had to use the mod-plugin-builder setup, if you need any help let me know as I went through the pain of it today :wink:

2 Likes

Sorry about that — this wasn’t a very easy feature to implement, so some bugs were expected.

Please try the following: change the preset checkboxes and, before using the Dwarf footswitches, open the addressing dialog and save the settings.

Hi Andrea, no worries, I understand is not easy. It is really great :wink:

I try with your procedure, and still some errors. What I found:

  • when all presets selected works fine
  • if you only deselect the first or last preset also ok.
  • if you only select 3 preset it works fine

But as soon as you have more than 3 preset selected. For example 4 and you select the 3rd. After you change page and you come back to the page with the control, the preset that is shown in the control is the 4th, although internally the plugin is working with the right preset.

1 Like

Yes, that makes sense. I’ll try to replicate it when I get back home.

Thanks!

And a little wish, an unselect all preset button. Considering the tight space, probably a select all is not needed, as you can insert again the plugin and all is selected.

I have the NAM plugin with more than 30 presets and to select only 3 for a pedalboard is too long sometimes….

Good news, I think that I reproduced and fixed the bug

Quick question: can anyone running the stock firmware confirm if preset assignment to an encoder is working?

It doesn’t seem to work with the Starless firmware, and I can’t identify any change on my side that could have caused a regression.

Hi Andrea, not recently but I ve used stock 1.13 firmware with preset assigned to knobs without problems. More recently with your 7b firmware there was also no problem. I didn’t try 8b

EDIT: In the device Settings I have always the CLICK mode for the list behavior selected

1 Like

Hello @AndreaDelSignore,

Thanks for the great work!
I tested your new version, particularly on the bug that I previously mentioned and it’s sort of there still.
So, when I access the plugin editor view on the AIDA-X and then move the presets, all is good (it was not before) as long as I keep in the middle of the preset list. As soon as I scroll all the way up, after the first preset, it “throws me” back to the view of what I have assigned to that control on the first page. Not even getting out and coming back to the plugin editor will help.
Would a video help you?

It’s working fine here.

1 Like

How does the standard firmware behave in the following case?

  1. Controller list behavior set to CLICK (in settings)
  2. The encoder is rotated to select a different preset, but the selection is not confirmed with a click

umm that’s a good question. I’m not 100% sure (long time ago…), but I think it remains in this position till the HMI is updated. For this you need to change subpage or page and come back to that page. Somehow after so many firmwares, I’m used to do this to double check very often.

PD: with the very useful plugin Companion plugin for external MIDI control buttons, where you assign an action to a dwarf control and also to CV or midi. The Dwarf is also not updated till you change page/subpage. Only the leds on the footswitches I think are updated cyclically.

1 Like

With the standard firmware and it set to CLICK it seems glitchy here:

  1. Rotate knob and value changes on the dwarf screen, wait until timeout goes back to previous screen, value on display and value in the plugin are now different. Clicking makes no difference.

  2. Rotate knob and value changes on the dwarf screen, before timeout goes back to previous screen click. this works.

I’ll put the old mod-host back and see if that makes a difference…

Edit: It still seems pretty buggy with CLICK turned on, sometimes it works, sometimes it doesn’t.

Basically:

  1. If you don’t confirm with a click the Dwarf display changes but the plugins preset doesn’t. So they are out of sync.

  2. If you try to confirm with a click after the display has gone back from the list, then the list re-appears and even clicking again will not change the preset.

  3. If you now try to change to the next preset this also fails, you need to choose the one after that or the one before to get it unstuck.

So the initial error condition seems to be caused by the list timing out and the one that was selected but not clicked can become what the Dwarf thinks is the current preset even though it isn’t (this can also randomly take on a different value)

It’s pretty bust I would say!

3 Likes

Thanks, both you and @fer confirm that there isn’t a regression, it’s just the standard behaviour (or perhaps an old bug :slight_smile: )

1 Like