Update: Korg Prologue SDK

[vc_row][vc_column][vc_column_text]

One of the most intriguing and unique features of the Korg Prologue is its MULTI ENGINE topology. Up until this point, the way in which users were able to create and install Multi Engine effects and oscillators has remained a mystery. However, Korg have recently updated their webpage with some extra info and provided answers to some common questions regarding the Prologue SDK.

[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]

Downloading & Installing Custom Oscillators/Effects

How do i obtain custom oscillators/effects?

Custom oscillators/effects created by, or in collaboration with, KORG will be featured on this website. 3rd party developers will also be free to distribute their custom oscillators/effects through alternative channels such as community websites, forums, GitHub etc and in some cases featured here.

How do i load oscillators/effects?

In addition to the usual program management functionalities, the librarian application can be used to load and remove custom oscillators and effects via USB MIDI. The Librarian is a user-friendly software that allows you to manage the sound programs, the custom oscillators and effects on the prologue.

Will there be a patch editor to customize internal parameters of the on-board effects?

There are no editors planned for customization of on-board effects.

Will the librarian be implemented as a VST/AU plug-in to facilitate automation of prologue and storage of patches with DAW projects via Snapshots?

No, not for this version of the Librarian.

Creating Custom Oscillators/Effects

Do I need programming experience to create my own content?

Yes. Please note that as opposed to the prologue Librarian application that will be released in June, the Developer kit is a standard development kit meant for programmers, and not a neophyte-friendly high-level editor. We expect that oscillators and effects will be programmed and distributed by pro and hobbyist software developers. It will be an open development kit aimed at experienced users so we will not be offering technical support beyond the provided documentation.

What programming language can I use?

Custom oscillators and effects can be written in C, with support for a subset of C++. What limitations are imposed in terms of available RAM? (it would have to be reasonably finite). For oscillators, both code and variables must fit in 32KB of RAM. Custom effects will have additional RAM for delay lines, up to 2MB.

For the multi-engine, will the LFO be able to modulate its parameters?

The LFO can modulate the shape parameter of the multi-engine. Custom oscillators will be able to take advantage of this.

How many editable internal parameters can a custom oscillator have?

Parameters for custom oscillators are limited to 6. This is a deliberate limitation to keep custom oscillators straightforward and simple.

This information is taken from Korg.com.au.[/vc_column_text][vc_single_image image=”3748″ img_size=”large” add_caption=”yes” alignment=”center” onclick=”link_image”][vc_single_image image=”3749″ img_size=”large” add_caption=”yes” alignment=”center” onclick=”link_image”][vc_column_text css=”.vc_custom_1550790256678{padding-top: 0px ;padding-right: 0px ;padding-bottom: 0px ;padding-left: 0px ;}”]

Release Dates:

Korg have advised that the SDK code, tools, and  documentation will be made available via  GitHub at the beginning of May 2018. Custom oscillators and effects features will be enabled via a prologue firmware update, and the Librarian application release, in June 2018.[/vc_column_text][/vc_column][/vc_row]