Korg has announced that the Prologue Software Development Kit (SDK) is now available.
The SDK, along with the Prologue’s open architecture, means that developers will be able to add new types of oscillators and effects, and users will have a keyboard with features that grow over time.
Here’s what they have to say about it:
prologue introduces an open development API (Application Programming Interface) that allows users to extend the possibilities of the hardware via an SDK (Software Development Kit) and dedicated development tools.
Via this SDK, custom digital oscillators can be created for the MULTI ENGINE, and custom modulation effects can be added to the existing modulation effects.
Users can then load these new custom oscillators and modulation effects into their prologue via the prologue Librarian application (Mac and Win).
Here’s an intro to the SDK, the Prologue Developer Kit and what the open development system means for both users and developers:
Release Schedule:
- The SDK code, tools and documentation are now available on GitHub
- Custom oscillators and effects features will be enabled via a prologue firmware update, and the Librarian application release, in June 2018.
One of the most awesome features of the KORG Prologue, I hope some really good stuff comes of it.
That said, the synth has a real problem with the tuning of the analogue oscillators and some nasty aliasing in the digital oscillator.
I’ll be really interested to see how this develops. Also – they should make a ‘Monologue Pro’ that’s full-size and incorporates the Prologue oscillator. That open up the audience for this by a huge factor, which would be good for Korg, the developers and end users.
That’s a great idea, anf make it $500
I’m not sure how a developer is supposed to test their creations unless they have a development board. They need to get the support added to the Prologue ASAP. Then anybody with a Prologue, the SDK and the knowhow can start developing.
Let everyone who wants to buy one, able to be purchased.
Buying a new synth with a wellknown problem…how is that…it shouldnt left the manufactory…or at least a shop after solving that problem…