That Percussia project is still set for a May 2018 release and it is always good to know what other manufacturers are up to and why. This shows that people are interested in a platform that has a way to program a unit or plugin.
Having a SDK on top of your application layer for the ER-301 is important and as I mentioned it was an idea that was good enough on your part to be included in the Percussia kick starter feature list. The ER-301 OS is already a high level graphical programming language that’s quite powerful. The vast majority of 301 owners are going to benefit most from the official Orthogonal Devices firmware development. Something developed with the plugin SDK could also be shared freely or sold, which in turn could be a benefit to 301 owners who can’t/don’t want to do any code level development.įor my two cents, the plugin SDK is where it’s at, and no rush. The plugin SDK to me is far more interesting since it would allow us to tap into the years of brilliant hard work you’ve already put into the 301, and add something small (or large) that can work alongside the rich collection of units and routing possibilities you’ve already built and continue to grow. Just speaking for myself, if you released something like this, I wouldn’t do anything with it - way too much work for me. This seems like it would benefit a incredibly small slice of ER-301 owners. Would that encourage you to dust off your ER-301? I could probably put something like that out in just a few weeks. No application layer, just the RTOS+drivers.
#Audulus muffwiggler how to#
As I agonized last night over how to respond to your post, I brainstormed about the possibility of releasing a monolithic OS-only unsupported code base that would let the intrepid users write their own firmware.
0 kommentar(er)
