Skip to content

Gorilla Editor

Gorilla Editor is the visual authoring environment for the sonic portion of a Gorilla Engine instrument or effect. It is where you assemble the audio structure, configure how sound is generated and processed, and audition the result while you work.

Its output is runtime data that the application and compiler use later in the product workflow. The product interface and packaging are created outside Gorilla Editor.

The Module Editor organizes the instrument or effect as a hierarchy of modules. These building blocks include oscillators, sample groups, filters, envelopes, modulation sources, effects, buses, and output routing. You can add, configure, connect, reorder, and reuse modules to construct the required signal flow.

Gorilla Script modules extend that structure with custom behavior. Scripts can select samples, modify note events, coordinate modules, implement articulations, and expose selected parameters to the application.

For sample-based instruments, the Mapping Editor arranges samples into groups, mappings, and zones. It controls where samples play across key and velocity ranges and provides access to root notes, loops, start and end positions, tuning, level, and other zone properties.

Samples can be imported individually or in batches. Mapping tools can derive placement from audio analysis, sample metadata and filenames, fill gaps, and resolve overlapping zones.

Gorilla Editor runs the sonic core directly. You can play it from a MIDI controller or the on-screen keyboard, listen through the selected audio device, and adjust modules, mappings, modulation, routing, and effects while hearing the result.

Its transport and tempo controls also provide a working context for sequencers, arpeggiators, and other time-dependent behavior.

When the sonic core is ready for use in a product, Gorilla Editor exports .blob files. The blobs contain the instrument or effect settings, samples, scripts, mappings, routing, and other runtime data that describe the sound and behavior. It does not contain the graphical user interface.

The plugin later loads this exported data, and Gorilla Compiler combines it with the application, assets, and product configuration.

See the Gorilla Editor User Guide for installation, operation, mapping, module editing, and a complete instrument tutorial. Use the Module Reference for the parameters and behavior of individual modules.