Gregory's Server@scy How has your experience with the community firmware been so far? I love the open source approach but at the same time are (without any actual indications) somewhat anxious about potential stability issues.
|
8 comments
 @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. |
@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.