-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection from Webflasher, not always. #66
Comments
I think i got it working, After running reinstalling my Presonus Studio 192 driver and doing "sfc /scannow" in windows 11, the mebmidi tool writes this: Now, "Squares&Circles" has the same number for input(0) and output port (0). and I can use the Webflasher tool - also with my USB audio interface connected. Webmidi tester: https://studiocode.dev/webmidi-tester/ |
thank you for the detailed report. As you can see in your first posting, the second screenshot does not show "no midi device detected". This means that "Squares&Circles" was found in the WebMidi devices. I suspect it could be a timeout in further communication. Could you please open the Developer Console in the browser (press F12) and see if red error messages are displayed there? |
Is it possible to download the firmware .hex file? I can't get webflasher to work for me. I have tried different computers, cables, USB connections and I always get the same error: ReferenceError: delay is not defined- please try again. On the other hand, if I load the phazerville firmware with teensy.exe I have no problems. thank you. |
@jpnielsen - I have just updated WebMidi.js from 1.3.5 to 1.3.8 - maybe this will solve the issue. I think I will introduce a MessagePopup in the firmware with the next update, so that you can safely track and verify whether the commands from the PC arrive at the Teensy, or the response is lost for some reason. @Pepebotika1980 - Possible this information will help you in some way #43 (comment) Otherwise, it would help me if you could provide more details, such as which browser and operating system you are using. Screenshots of the error message would also help. |
Unfotuunately, I see no change. I can still only connect to the teensy firmware from the webflasher, when i turn off my Presonus Studio 192. I don't think i'm going to use the midi on the presonus - but it doesn't help when i turn it off in the device manager, and the available settings in the Presonus Universal control don't seem to make a difference. I was thinking you maybe could give us the possibility to change the name for the input and output midi devices - that would be usefull too if we have more O-C/s connected. I would probably call mine "OC1 IN", "OC1 OUT", "OC2 IN", "OC2 OUT", "OC3 IN", "OC3 OUT", "OC4 IN", "OC4 OUT" and "OC4 IN", "OC4 OUT". Or do we have some other unique identifier going on that i'm not aware of ? |
@jpnielsen - I took a close look at the webmidi tester - Thanks for that, we can actually use this for debugging
@Pepebotika1980 thanks for the infos - I have fixed a small bug (which actually only occurred after flashing a bare-teensy). I hope we're not mixing two different issues here - but I think it could be the same issue: Before I make any further adjustments, we have to ensure the following cases are working.
Goto https://studiocode.dev/webmidi-tester/
Thank you for your patience. |
yeah!! I already have the module working correctly, thanks to you for your patience and for the great work you do! |
In addition to the O_C, the webflasher supports another module based on the Daisy Patch Submodule which a few people have. But back to the issue. Let me summarize briefly: The issue only only occurs when the "Presonus Studio 192" is turned on. Regarding the timeout - it occurs if there is no response 5 seconds after sending. I don't think it makes sense increasing it. I think the "device names" are different since I'm on Linux and you're probably on Windows. |
I tried several combination of midi devices now - the result is, that i can only get your WebFlasher config tool to work, If there are no other midi devices connected. It's not just "Presonus Studio 192" - also Behringer Neutron, Behringer Model D. Your assumption with regards to my operating system is correct. Windows 11 pro build 22631.3085 (23H2) |
I wanted to reflash the latest firmware But the flasher finishes very fast, and nothing is flashed to the teensy. |
Hi @jpnielsen, Today I connected two teensys to a Windows PC and tested the Webflasher. I think I was able to reproduce the issue you described. It looked like I got into the state when I unplugged one of the teensys while the WebFlasher was open. It seems to me that WebMidi generally is not supporting multiple devices that have the same name. I also had the case that the browser didn't recognize any MIDI devices at all - after I closed it and reopened it, it worked again. The next days (maybe tomorrow) I would introduce that every S&C device has a unique MIDI name, I hope that this will fix this issue. |
I have only connected one teensy so far. Unique S&C MIDI names sounds promising. |
I will continue to test this with multiple devices for a while and thinking about to add the option to select one S&C device if several are connected in the WebFlasher . |
After updating to the latest firmware (main_9cd30a1), and rebooting. |
thanks for testing and reporting. I've found a minor issue after some testing and have just pushed another update. In the current Webflasher multiple devices are supported, you can select the midi device in the top right combo box. If no Midi device is recognised, you propable have a bare teensy and have to flash the "Loader" first (I have added a short explanation in Webflasher today - hope that it is understandable so far). The reason for this is that I plan to support different Squares&Sircles devices and everything that happens after the loader will be the same for all devices. My goal is that it will only take one click to install an firmware update. Regarding your last message: |
I only flashed the loader, because i didn't get the option to Flash/update. I let it stand on the screen, and unplugged usb midi devices. I did the update, and after the first reboot, i got the "ready to update" again. I flashed the loader from pjrc's teensy.exe, and tried flashing - again, no flash/update in the webflasher - until i plugged in the unrelated midi-device... and the screen appears.. like the midi devices enumeration happens again, or something . . I''m not a programmer. Then followed the slowest MCU flash I have experienced for some time. Seems to run now. Thank you. |
You can actually increase the flashing speed. I have recently reduced this because a few users have reported issues. If you want to have it faster, you can change the following parameters in the Webflasher URL (I am using the following parameters without issues)
|
Hy. If someone can help me.... |
thanks for reporting. I have just tested the firmware flashing (even with french translater). It works for me. Please try the following:
|
Thanks, I will try it when come back home. |
Hy, I try your solutions but it does not function, it's always the same message. |
thanks for trying again and for your patience. I think I have fixed a possible bug in webflasher.
Unfortunately, there are currently no freely available complete hex files. There will probably soon be a closed area where registered users (registered devices) can download the full hex files, among other things. |
When I try to upload the latest firmware with the S&C Teensy Loader in it (ready to update flashing), it's always the same message: But now if I try to install without the teensy loader, I can use the Reset and Flash option but at the end it's the same message again. The same if I press the teensy button... I also try another COM port, another browser, another version of the firmware, with loader, without loader... I don't understand why I can use calibration function,flip,dac,display, format, ect... but not the Flash/update of the same page... Thanks again for your time. |
I found the old .HEX firmware at this address: |
Let me summarise.
In my case it looks like this (with a small browser window, otherwise I can still see the image of the module):
If I click on I have added more tracing to the console output, can you please tell me exactly what appears in the line ‘memMap...’ before you get the "Uncaucht TypeError" ... To be on the safe side, try disable caching and press ‘CTRL+F5’ a few times. Thanks for the hint with the hex file (It is a very old ‘unstable’ version). |
Hi. When I press ‘CTRL+F5’ I've got this message: And when I click on Flash/Upgrade, with disable caching, I've got this: Without refresh or ‘CTRL+F5’ I've got this: Excuse me with my English if I don't answer correctly to your solutions. |
Thanks again for the reply. I think you are using an outdated version of chrome. The Please paste |
I can't update Chrome since a long time because of my version of Windows, until today I've got no problems because I'm using teensyloader or Arduino IDE, STM32CubeProgramer, Thonny, ect ect... It's my first time with WebFlasher. Sorry for my incompetence, I will trying to borrow a better computer and see if it's ok. Thanks |
Noob noob noob, I'm an old Noob !!!! Everything is alright with a recent computer. Thanks for everything, S&C is my best Eurorack Audio Module. |
That's good, btw. I also learned something and was able to improve a few things. Otherwise, you can also do updates from your smartphone (testet with chrome - if you have a suitable cable/adapter). |
Hi, first of all thanks for your amazing work on S&C, I use it literally in every patch! But unfortunately I have the exact same problem as [OvErDrIvEwItHdIsTo]("toArray"-function error), because of audio interface/FW driver it's complicated to update my OS with the result that I can't update Chrome for the moment. Hence, I can't flash my S&C anymore... Currently i'm on Chrome version 116. Isn't there a work around for now so at least I can get my S&C back up and running? |
I do not success with my smartphone, even if I got the good version of chrome and the good cable. |
I have recently removed the toArray call. Please refresh the webflaher with CTRL-F5 and try again. As long as its in my code, I can try adjust something. If it doesn't work, please send a screenshot with a detailed error description. As far as testing is concerned, it works on all my devices :-( |
Yes, that did the trick, that was easy!! :) Thanks again for your great work and super fast help! |
Hi @eh2k I went to update my O&C today and similar issues to others, the web flasher isn't working for me. It finds the teensy (with bootloader, old firmware wiped in the process), but just gets stuck in a loop of being able to only upload the bootloader, not the firmware, with the only button being "Calibration", which works, as does midi and I can send and parse bytes like 0xF3 0x4C to open and close the machine engine. ![]() ![]() I'm running the latest version of Chrome, with web midi enabled on MacOS 11.7 on ARM64. Attached are some screenshots. I think there is. bug in the code and have attached the screenshot for the JSON error. ![]() A friend (with forewarning it might wipe his unit) tried to update on a Windows machine and ended up in the same place I am with a unit that's stuck waiting for an update, that can't update. Any idea on how I/we can resolve this? Thanks in advance! |
Hi @eh2k, |
Please try again with a refresh (CTRL+F5) In general, I recommend updating as often as possible and always using the latest version. |
@eh2k thank you! This has resolved whatever was causing the issue. I'm now running the latest firmware, calibrated and ready to make some music. Thank you not only for resolving my issues, but your wonderful Firmware! |
Case image 1:
![image](https://private-user-images.githubusercontent.com/27916597/303246788-662b73c3-6621-433e-8ab0-4967a242a6f0.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjYwOTg1OTksIm5iZiI6MTcyNjA5ODI5OSwicGF0aCI6Ii8yNzkxNjU5Ny8zMDMyNDY3ODgtNjYyYjczYzMtNjYyMS00MzNlLThhYjAtNDk2N2EyNDJhNmYwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTExVDIzNDQ1OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTJhMzViYWRiOGU2MWE5NzliNTk5YTM4N2JiNzQwODQyY2VhN2ZhMGZiZmE4MDM4OTI1N2YyZWFmMzMxODI4MWMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.eN3ZBjuD8PUM7mCxdj29bcGs0nuqXfZsLH8XDfLo4HM)
![image](https://private-user-images.githubusercontent.com/27916597/303246851-adaa20a1-e858-4005-95bd-5c2912939d2b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjYwOTg1OTksIm5iZiI6MTcyNjA5ODI5OSwicGF0aCI6Ii8yNzkxNjU5Ny8zMDMyNDY4NTEtYWRhYTIwYTEtZTg1OC00MDA1LTk1YmQtNWMyOTEyOTM5ZDJiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTExVDIzNDQ1OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWIzMWEwZjIwMDdhYzZiYjY5M2U1YWQyZTNjZDUzNmMyZmZhNTFiMTM1YzdiNmU0ZGIyMzc1MDIzMGZkMjRkZmQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.AQZd8Xnfytibt4HTwJv-D4zVHOcIbzf_CrC7au_djz0)
Connection to teensy seems OK
case image 2:
![image](https://private-user-images.githubusercontent.com/27916597/303247005-af9870e7-dd3b-4d28-b10f-5117e70157d2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjYwOTg1OTksIm5iZiI6MTcyNjA5ODI5OSwicGF0aCI6Ii8yNzkxNjU5Ny8zMDMyNDcwMDUtYWY5ODcwZTctZGQzYi00ZDI4LWIxMGYtNTExN2U3MDE1N2QyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTExVDIzNDQ1OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWZkMmUxMTg0MTk1MjJhOWE5MzkyYTQ2MTdmYTljMmFkNWZjMzQzMzZhMzI4YjQzZGE2NjA2OGZiMjIzYTg5MDcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.nv1xSYyBEkPVVjZExDYEyyP1kFFef5RVri_BZXedmJw)
my audio interface is turned on, and the webmidi tester is reloaded:
refreshing Webflasher page doesn't show the options&engines page:
![image](https://private-user-images.githubusercontent.com/27916597/303247150-e8023e8e-6120-42e3-88c2-dcb1dc1dcfa3.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjYwOTg1OTksIm5iZiI6MTcyNjA5ODI5OSwicGF0aCI6Ii8yNzkxNjU5Ny8zMDMyNDcxNTAtZTgwMjNlOGUtNjEyMC00MmUzLTg4YzItZGNiMWRjMWRjZmEzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTExVDIzNDQ1OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTBmZDI2YzNhZDU1NzhkMzVhMmUwNDY0YzllNjg3MTg3YjM1M2MyMGI0ZmIzMmYwYTgyMmI3OGViMDZkZTJmZTUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.F3LuAGQohIFlrkzAaNtnssosKvtiGGaUymJDG2hGoCY)
The text was updated successfully, but these errors were encountered: