PER|FORMER

Introduction

DISCLAIMER: Building the PER|FORMER sequencer is not recommended for beginners.

This page is based on the original Westlicht build guide and kept here as a local reference for the Vinx Scorza fork.

Sourcing Parts

To build the sequencer you first need to source all the required parts. The original build guide references the complete BOM, Octopart BOM, and assembly resources for the hardware project.

For the hardware build process and sourcing details, the original upstream guide remains the main reference: Westlicht Build Guide

Setup on macOS and Linux

Clone this repository:

git clone --recursive https://github.com/VinxScorza/performer.git
cd performer

Make sure you have a recent version of CMake installed. On Debian-based systems you may also need:

sudo apt-get install libtool autoconf cmake libusb-1.0.0-dev libftdi-dev pkg-config

To compile for hardware and allow flashing firmware:

make tools_install

Then set up the build directories:

make setup_stm32
make setup_sim

Setup on Windows

There is currently no native Windows build flow. The standard workaround is the Vagrant virtual machine, as in the original Westlicht documentation.

git clone --recursive https://github.com/VinxScorza/performer.git
cd performer
vagrant up
vagrant ssh

Build directories

After setup, build directories are available under build/[stm32|sim]/[release|debug]. Use release for hardware builds and debug for the simulator.

Build for hardware

cd build/stm32/release
make -j

The sequencer build generates an UPDATE.DAT file suitable for firmware updates through the bootloader.

For full hardware assembly, flashing, and sourcing notes, refer to the original build guide: Westlicht Build Guide

Build for simulator

cd build/sim/debug
make -j
./src/apps/sequencer/sequencer

Upstream reference

This page is intentionally close to the original Westlicht build documentation and will be diversified only where the Vinx fork requires different build or release behavior.