lilypalooza

KO | EN

gitlite — search

#javascript #python #ai #typescript #llm #go #machine-learning #linux #docker #java #kubernetes #security #ios #openai

(★ 16)

LilyPond DAW and IDE

lilypalooza 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Lilypalooza

**Lilypalooza** is a desktop LilyPond IDE with DAW-style playback, editing,
score preview, plugin hosting, and project persistence.

![Screenshot 1](https://raw.githubusercontent.com/ales-tsurko/lilypalooza/main/assets/screenshots/screenshot_1.png)
![Screenshot 2](https://raw.githubusercontent.com/ales-tsurko/lilypalooza/main/assets/screenshots/screenshot_2.png)
![Screenshot 3](https://raw.githubusercontent.com/ales-tsurko/lilypalooza/main/assets/screenshots/screenshot_3.png)
![Screenshot 4](https://raw.githubusercontent.com/ales-tsurko/lilypalooza/main/assets/screenshots/screenshot_4.png)

## Features

- multi-tab LilyPond editor with tree-sitter highlighting
- watched LilyPond sources with automatic recompilation on save/external change
- score preview with point-and-click navigation back to source
- MIDI playback with transport, piano roll and feature-full DAW-grade mixer
- DAW-style processor slots for built-in, AUv2, CLAP, and VST3
  instruments/effects
- built-in SoundFont sampler
- plugin editor windows with preset controls and native embedded plugin views
- non-blocking AUv2/CLAP/VST3 scanning with isolated validation and persistent
  cache
- mixer buses, output routing, sends, pre/post fader sends, feedback prevention,
  effect bypass, effect reordering, and plugin delay compensation
- dockable multi-pane workspace with editor, score, piano roll, mixer, logs, and
  project state persistence

## Run

Use `make run` for development. It builds the plugin validator helper first and
then starts the app.

```bash
make run
```

Pass app arguments after `--`:

```bash
make run -- --soundfont assets/soundfonts/FluidR3_GM.sf2 --score path/to/score.ly
```

Useful direct environment overrides:

```bash
LILYPALOOZA_SOUNDFONT=assets/soundfonts/FluidR3_GM.sf2 cargo run
LILYPALOOZA_SCORE=path/to/score.ly cargo run
```

Trace plugin/editor hosting:

```bash
RUST_LOG=lilypalooza_vst3=trace,editor_host=trace,lilypalooza::editor_windows=trace make run
```

## Settings

Settings are stored in the platform config directory:

```text
lilypalooza/settings.toml
```

The file is generated with documented defaults. Important sections include:

- `au_search_paths`, `clap_search_paths`, and `vst3_search_paths`
- editor view and theme settings
- shortcut overrides
- playback SoundFonts and audio output device

Default plugin search paths are created for the current platform. On macOS this
includes:

```text
/Library/Audio/Plug-Ins/CLAP
~/Library/Audio/Plug-Ins/CLAP
/Library/Audio/Plug-Ins/Components
~/Library/Audio/Plug-Ins/Components
/Library/Audio/Plug-Ins/VST3
~/Library/Audio/Plug-Ins/VST3
```

Plugin scanning runs in the background. The UI and log/status line report scan
progress while the app is not blocked and the picker may still be filling.

## Projects

When a score belongs to a saved project, project state is stored under:

```text
.lilypalooza/project.ron
```

Project/global state preserves editor tabs, mixer state, plugin choices,
routing, and user processor presets.

## Workspace Crates

- `lilypalooza-audio`: engine, mixer, routing, processor interfaces, PDC
- `lilypalooza-au`: macOS-only AUv2 discovery, runtime, state, audio, and
  generic controls
- `lilypalooza-builtins`: built-in processors such as SF-01 and Gain
- `lilypalooza-clap`: CLAP discovery, runtime, state, audio, and editor adapter
- `lilypalooza-vst3`: VST3 discovery, runtime, audio, and editor adapter
- `lilypalooza-plugin-scan`: reusable background scanner and cache
- `lilypalooza-plugin-validator`: subprocess validator for plugin candidates
- `editor-host`: cross-format embedded plugin editor window/frame host
- `lilypalooza-egui-baseview`: egui/baseview frame rendering support
- `crates/vendor/*`: vendored UI/editor/parser dependencies

## Development Commands

Install local quality tools:

```bash
rustup toolchain install nightly --component miri --component rust-src --component rustfmt
cargo install cargo-binstall
cargo binstall cargo-llvm-cov cargo-crap similarity-rs cargo-machete --no-confirm
```

Linux system dependencies:

```bash
sudo apt-get update
sudo apt-get install -y \
  libasound2-dev \
  libdbus-1-dev \
  libegl1-mesa-dev \
  libfontconfig1-dev \
  libfreetype6-dev \
  libgtk-3-dev \
  libwayland-dev \
  libx11-xcb-dev \
  libxkbcommon-dev \
  pkg-config
```

```bash
make fmt       # nightly rustfmt, using rustfmt.toml
make check     # stable cargo check for first-party crates
make lint      # clippy and first-party rustfmt check
make fmt-vendor-check # vendored crates with upstream/default rustfmt
make test-all  # stable workspace tests
make code-health # Miri, duplicated code, unused deps, llvm-cov, CRAP
```

`make fmt` and `make lint` format first-party crates with the repository
`rustfmt.toml`. Vendored crates are checked separately with their own
`rustfmt.toml` when present, otherwise default rustfmt settings.

`make code-health` runs `similarity-rs` on Rust functions. It compares
structural similarity, not behavior; treat the report as refactoring leads. The
same target also runs `cargo machete`, coverage, CRAP, and package-scoped Miri.

`make code-health` writes `target/lilypalooza-lcov.info` and
`target/lilypalooza-crap.md`. CRAP analysis includes coverage-reported test
modules and excludes build scripts, examples, benches, vendored crates, and
external test module roots that llvm-cov does not emit as LCOV source files.

Miri is intentionally package-scoped. The current gate covers
`lilypalooza-clap`, `lilypalooza-plugin-scan`, and
`lilypalooza-plugin-validator`; audio, VST3, editor-host, and GUI-heavy crates
need targeted Miri-compatible tests before they should be added.

Build only the validator helper:

```bash
make validator
```

## Built-in Debugging

Open the SF-01 editor directly:

```bash
cargo run -p lilypalooza-builtins --example open_soundfont_synth
```

Other useful built-in examples:

```bash
cargo run -p lilypalooza-builtins --example play_soundfont_midi
cargo run -p lilypalooza-builtins --example profile_engine
```

## Status

The app is under active development. macOS is the primary tested platform right
now. AUv2, CLAP, and VST3 hosting are implemented; Windows and X11 paths are
kept in the architecture but mostly placeholders yet. Wayland plugin editor
hosting is not a current target.

lilypalooza

lilypalooza 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

lilypalooza

lilypalooza 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README