Pedalboard does not show inputs/outputs/connections when accessed via 192.168.51.1

Description


When accessing the web GUI at address 192.168.51.1 the pedalboard only worked in one out of five OS/browser combinations that I tested, and it took a while before I found this “magic” combination (the other 4 gave a black rectangle where I could do nothing (*))

I later discovered that the zeroconf address modduo.local/ works in all 5 cases.

                  192.168.51.1   modduo.local/
Ubuntu / FireFox      FAIL             OK
OS X / Chrome         FAIL             OK
OS X / Opera          FAIL             OK
OS X / Safari         FAIL             OK
OS X / FireFox         OK              OK

(*) When it fails, the pedalboard does not show any inputs or outputs or connections, and the plugins disappear after a short while, leaving a large black pedalboard where you can do nothing. Browser console contains loads of

Error: <path> attribute d: Expected number, "MNaN,NaNCNaN,NaN …".
    _makeNode  @ jquery.svg.js?v=1.2.0.256:820
    path       @ jquery.svg.js?v=1.2.0.256:638
    drawBezier @ pedalboard.js?v=1.2.0.256:1986

How to reproduce


Open web GUI for v1.2.0 at address 192.168.51.1

Expected/suggested solution


Web GUI should behave the same, irregardless of which http address it is accessed through.
The wiki chapter 2 instructions should be updated to reflect the new zeroconf address.
Latest version 1.2.0 should be added to http://moddevices.com/releases.html

Additional information


  • release: v1.2.0
  • system: 17020e6
  • controller: e582b18

The code is always the same for both addresses, so not sure what’s going on.
I’d suggest browser cache, but you tried different browsers…

Please post a screenshot of what it looks like when the issue happens, thanks.

1 Like

Here are screenshots for how the pedalboard loading shows up in my browser.

When accessing web gui at 192.168.51.1, notice that it never shows any inputs/outputs or cables/connections during load, and ends up “all black”:

When accessing web gui at modduo.local/ it works fine:

Clearing “Cache data” (Chrome/Opera) or “History” (Safari) effectively fixed this issue.
It now works in all browsers.

Thanks for the tip/suggestion, and amazingly fast response times :thumbsup:

hmm our caching solution is not working as desired then.
Using ?v=1.2.0.build doens’t work :frowning:

I consider/mark this bug as resolved since the “clear browser cache/history” workaround fixed it for me.

I’ll leave it to you guys to continue improving/fixing the web GUI and caching. You’re doing a great job!