|
Top-level
 Each of the colored blocks of 4×8 LEDs represents a 32-bit address in the firmware, while the 2×8 section at the right is displaying the first 4 hex digits of the Git commit hash that's running. The colors represent different types of stack frames, if I understood it correctly. Devs then translate these addresses into the actual functions and lines in the code and can start to reason about it. 13 comments
 @dezwo I had my Deluge crash three times. Once with the stock firmware, twice with the community. I don't think that means anything. If I was performing live, I'd be hesitant. But I'm not, and the community firmware comes with _so_ many improvements big and small that I'd be missing out if I didn't use it. I don't regret upgrading. That being said, I'd love an "auto-save" feature, but saving manually every few minutes doesn't really hurt either. Let me know if you have any more questions. @dezwo Also, the community firmware definitely is the future. It has made lots of refactorings, which means that merging single features back to the Synthstrom firmware is hard or even impossible. I expect (and the community devs do, too, afaict) that the Synthstrom firmware won't see much development in the future. Instead, the community one is where features & bugfixes are going to be. It's already so much better than stock, and the stock firmware was already pretty good.  @dezwo @scy Dude, open source firmware has become a major factor for hardware purchase decisions. My linnstrument is open source, my norms shield, my axoloti synths. The m8 was promised open source when I pulled the trigger, but the maker seems to be too lazy to release openly. Some of the major innovations in synth hardware were all open source (mutable instruments, for example). I am saving up for a deluge. @tekknovator @scy I don't doubt that folks care. But forking and maintaining a proprietary code base is no small feat, so I was interested in @scy's experience (especially since he started the thread with an experience report or a crash and subsequent debugging). Anyhow, thanks for sharing your perspectives. RIP my notifications I guess :) If you're interested in the Deluge, I highly recommend it. The official website is https://synthstrom.com/product/deluge/ and https://youtu.be/aBeeDwukpTs has a detailed introduction. #Synthstrom is a small company with a great attitude. When they introduced the OLED screen to the Deluge instead of the 7-segment display it had before, they offered retrofit upgrades to all existing customers instead of trying to sell you new devices like pretty much the rest of the industry would. |
Gregory's Server
Of course I had to ask whether that bot is open source. And it is! It's a few Python scripts to interact with Discord, fetch all the images posted to the channel, and use OpenCV to try and detect a crash pattern in it. If that succeeds, the result is posted back to Discord.
https://github.com/0beron/delugeqr/
(Don't get confused by the "QR" in the name, these are not QR codes at all.)
And the code that generates these patterns is here in the firmware:
https://github.com/SynthstromAudible/DelugeFirmware/blob/community/src/fault_handler.c
Of course I had to ask whether that bot is open source. And it is! It's a few Python scripts to interact with Discord, fetch all the images posted to the channel, and use OpenCV to try and detect a crash pattern in it. If that succeeds, the result is posted back to Discord.
https://github.com/0beron/delugeqr/