Skip to content
Gorilla Engine SDK Documentation

Gorilla Tester User Guide

Gorilla Tester is an optional developer utility for loading .blob files exported from Gorilla Editor. Use it to audition or debug a sound core in a DAW before a product interface is available.

Gorilla Tester is not a plugin-development environment. Do not use it to build or fine-tune a production interface. New products should use Gorilla Engine React and should be compiled, installed, and tested as real plugins from the beginning of development.

What Gorilla Tester is useful for

Section titled “What Gorilla Tester is useful for”
  • Confirming that an exported blob loads in a plugin host
  • Auditioning exposed parameters through a temporary generated interface
  • Checking instrument or effect behavior in a DAW before application work begins
  • Isolating whether a problem belongs to the sound core or the compiled application

The generated controls are diagnostic. Their layout and appearance do not represent the finished product.

Load blob files

Section titled “Load blob files”

  1. Remove all running Gorilla Tester instances from the host.

  2. Export the blob parts from Gorilla Editor.

  3. Rename them Gorilla Tester_part1.blob, Gorilla Tester_part2.blob, and so on.

  4. Remove the existing contents of the Gorilla Tester data directory:

    • Windows: C:\ProgramData\UJAM\Gorilla Tester\
    • macOS: /Library/Application Support/UJAM/Gorilla Tester/

  5. Copy the renamed blob files into that directory.

  6. Ensure the directory does not contain a .js application entry point when you want the generated diagnostic interface.

  7. Load Gorilla Tester in the DAW.

The generated interface exposes at most the first 1,000 parameters. Use a compiled plugin to validate the complete product.

Continue with the compiled product

Section titled “Continue with the compiled product”

After the sound core can be loaded, continue with Gorilla Engine React. Build and install the example or product project with:

Terminal window
npm run buildAndInstall

Use npm start for a standalone-capable project or npm run deploy for a project that must run in a DAW. Those workflows exercise the real application, assets, plugin formats, state, and host integration.

Historical JavaScript-based custom interfaces are deprecated and no longer supported. See the Legacy Examples section when maintaining an existing product that uses this workflow.