- Edited
I'll look into adding a couple of steps to make the firefox process easier, without requiring the confusing manual steps.
Issue updating Gliss
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 :-)
18 days later
- Edited
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 ;-(
- Edited
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?