Can you load https://arachsys.github.io/webmidi/sysex ? See if you can see the device lists and select Gliss as both input and output. Then send
f0 00 21 3e 00 05 06 f7and verify that you get this response:
f0 00 21 3e 00 05 07 02 47 6c 69 73 73 2d 76 32 2e 30 2e 31 00 f7As an alternative, I assume most Chromium-based browsers that are not sandboxed would work. We tested Brave,for instance, with success, see if you have something installed that works.
PS: Also Firefox works on some platforms. On Linux it doesn't because it doesn't re-detect the device after it resets it, but if when it hangs the first time you close it and restart it without unplugging the device it may get you to the end of the process.
Thanks, I will try the verify. EDIT: it does not work ("Web MIDI not supported or port access refused") although I basically allowed anything in the config menu of chromium. Brave browser install alas not possible at the moment (do not have the resources to meet its system requirements).
Updating via firefox (having read your modwiggler-post) does start, but fails at "reboot to application". The whole module is now steadily lit red (apprently only the flasher has been written on it). EDIT: it still drops out at "reeboot to application", but having done the procedure overagain once more, it seems to have witten the 2.0 and is blinking green-red (button) and red-orange(strip). Can I disconnect it, or will it be bricked?
When it blinks yellow-red it is correctly flashed, but it is in factory test mode.
Enter the menu by pressing the button and placing two fingers on the touch strip, press the green selector and you'll be in control.mode
Press the button to exit the menu.
crowhurst EDIT: it does not work ("Web MIDI not supported or port access refused")
Well this should mean that webmidi doesn't work on this browser - in its current configuration and with the current system permissions - so that's at odd with your earlier statement
crowhurst I was a bit puzzled about webMIDI not working in this case as it had worked flawlessly in numerous other cases before.
That may have happened with a different system/browser/config? If you go back to those flawless earlier cases, I am pretty sure they won't work with the current system/browser/config.
although I basically allowed anything in the config menu of chromium.
I know nothing about snap and almost nothing about sandboxing in general, but it makes sense that any permissions you may set in the software won't affect its system-wide capabilities: it's about the OS giving permissions to the software besides anything you may set in the software itself. It may be hell though and one may be better off using a browser with system access instead.
@crowhurst I think we were able to reproduce your issue and that it is related to your browser being a sandboxed snap. We pushed an update that detects that and warns the user. The easiest solution is to get another browser that is not sandboxed. It may be possible to work around the limitation some other way but it's a system specific hell
hey giuliomoro,
thanks a lot for looking into this! I understand that snap-related chromium won't be sufficient.
However, with firefox I managed to get through the procedure until button blinks red-green and strip blinks red-orange. That is the state it is in now, when powered up via USB.
Twofingers-on-strip plus Button-pressing enters several states one can cycle through by pressing the button again and again. For example a white dot wandering upwards, a yellow-lit strip, a red-blinking lower part of the strip, a yellow upper part of the strip and some more cycles, until it goes back to that green-red (button) orange-red (strip) blinking-state.
I wonder, what state this is.. has Gliss been updated successfully and if so, how can it be set to working order?
Thanks again!
crowhurst Twofingers-on-strip plus Button-pressing enters several states one can cycle through by pressing the button again and again.
Once it's flashed in firefox the module is in factory test mode. A description for that is available in the manual. Here you have to enter the menu as usual by pressing the button and placing two fingers on the touch strip (start with the button then add the fingers, the order is important). The menu in this case only has the green selector for changing mode. Tap that and it will take you to control mode. Press the button to exit menu as usual. You may still want to perform the calibration, see the manual for instructions on calibration mode.
The v2 manual is available here https://github.com/BelaPlatform/Gliss/blob/main/GLISS_user_manual-2.pdf
Thanks - did as you said: leaving factory test mode manually after firmware upload via firefox and applying calibration afterwards.
As Slider&Touch is now accessible option on both updated Gliss units, I think it's fair to say the 2.0 upload can be considered successful!
Thank you for your support!. In hindsight the "work-around process" was solid and easy. Please understand my temporary anxiousness. Since Gliss is a most valuable module for me, I'd have been gutted having it bricked by user error.
Thank you for 2.0! Super valuable upgrade whilst not cluttering up the UI with hundreds of additional features - great effort!
If the firefox-bug only means that one has to do the web-udate twice leaving the module connected and manually exit factory test mode at the end, I think it would be fair to claim that it basically works as well. With help of a little demo-video I think any firefox user could be enabled to do this update. Maybe that would be less hassle than getting the mozilla-crew to finally fix that auto-reconnecting-bug of firefox.
Can't shoot such a video at the moment but if it helps I can report back over at modwiggler that firefox did the job in my case, illustrating the procedure.
Cheers and thanks again!
I'll look into adding a couple of steps to make the firefox process easier, without requiring the confusing manual steps.
Hi, i have 4 GLISS Modules. On the 3 newe ones the update worked flawlwss on the one which is the oldest, it was recogniced as GLISS, but wenn i press button update, i got an error, that this is not a GLISS Module, and cannot be updatet! The name on the usb and the midi-channels are GLISS-CS! I hope somebody can help. I never updatet this module!
Hmm GLISS-CS should be a preproduction unit ... weird that it's in your hands at all ... maybe you bought it a trade show?
Anyhow, you should use this procedure for the first update of your module: https://files.bela.io/gliss-update-dfu.html
Hi, thanks! Worked flawless! I bought it Online, was one of the first! Used it long time alone, but now i put my moog mavis in a moog case and had place for 4! So i upgraded! But now i understand why it had sometimes a little bit strange behaviors :-)
hi, had some trouble updating this on linux (arch). tried with latest standard-chrome and ungoogled-chromium.
got the following error and a red button:
write error {"slice":{"0":51,"1":177,"2":2,"3":35,"4":35,"5":113,"6":0,"7":32,"8":32,"9":97,"10":1,"11":35,"12":35,"13":113,"14":16,"15":189,"16":67,"17":113,"18":254,"19":247,"20":209,"21":254,"22":244,"23":231,"24":1,"25":32,"26":112,"27":71,"28":112,"29":181,"30":4,"31":70,"32":13,"33":70,"34":17,"35":70,"36":4,"37":154,"38":64,"39":121,"40":1,"41":40,"42":107,"43":208,"44":1,"45":32,"46":96,"47":113,"48":2,"49":32,"50":32,"51":113,"52":0,"53":45,"54":49,"55":209},"seq":345}
after powering off/on my module was detected as
Gliss MIDI 1 (Gliss-flasher-v1.1) �����������������������
tried updating to v1.1 and v2.0.1 with different error messages:
write error {"slice":{"0":27,"1":81,"2":38,"3":25,"4":0,"5":192,"6":13,"7":83,"8":38,"9":81,"10":28,"11":20,"12":40,"13":81,"14":27,"15":28,"16":39,"17":118,"18":36,"19":122,"20":48,"21":191,"22":215,"23":80,"24":255,"25":60,"26":33,"27":128,"28":192,"29":17,"30":52,"31":36,"32":118,"33":36,"34":52,"35":35,"36":14,"37":35,"38":0,"39":52,"40":34,"41":14,"42":34,"43":0,"44":52,"45":33,"46":127,"47":80,"48":0,"49":83,"50":37,"51":83,"52":38,"53":1,"54":16,"55":83},"seq":38}
write error {"slice":{"0":23,"1":75,"2":195,"3":98,"4":0,"5":35,"6":3,"7":99,"8":32,"9":34,"10":128,"11":248,"12":65,"13":32,"14":128,"15":248,"16":66,"17":48,"18":67,"19":99,"20":17,"21":240,"22":4,"23":15,"24":19,"25":208,"26":3,"27":104,"28":90,"29":106,"30":67,"31":106,"32":26,"33":112,"34":67,"35":106,"36":1,"37":51,"38":67,"39":98,"40":3,"41":141,"42":83,"43":177,"44":1,"45":59,"46":3,"47":133,"48":67,"49":141,"50":155,"51":178,"52":1,"53":59,"54":155,"55":178},"seq":470}
then switched to a windows machine with latest chrome and there it worked fine.
quite depressing to be dependent on microsoft and google here ;-(
journalctl -f
kernel: usb 1-5.1.2: new full-speed USB device number 13 using xhci_hcd
kernel: usb 1-5.1.2: New USB device found, idVendor=be1a, idProduct=eee3, bcdDevice= 2.00
kernel: usb 1-5.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: usb 1-5.1.2: Product: Gliss-v2.0.1
kernel: usb 1-5.1.2: Manufacturer: AIL
kernel: usb 1-5.1.2: SerialNumber: 207230824856
mtp-probe[12855]: checking bus 1, device 13: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.1/1-5.1.2"
mtp-probe[12855]: bus: 1, device: 13 was not an MTP device
mtp-probe[12892]: checking bus 1, device 13: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.1/1-5.1.2"
mtp-probe[12892]: bus: 1, device: 13 was not an MTP device@x_x sorry you had troubles, we are not able to reproduce your issue. It seems like it failed at some random point while sending one of thousands of payload messages. It's unclear why it would fail there and even more why it would work for all the previous ones ...
Were you using a USB hub or had otherwise high USB traffic on your system?