Lspatch Modules Top |link| Guide
lspatch modules — overview and practical guide
lspatch is a lightweight, modular patching framework for audio and software synthesis environments that follows a small-patch, modular philosophy: encapsulated modules (oscillators, filters, envelopes, utilities) connected via signal/control patching to build instruments, effects, and patches. This article explains the architecture, common module types, topological considerations, module design patterns, implementation tips, and example patch designs to help you design robust, reusable lspatch modules.
Note: this article assumes a modular patching environment named lspatch (conceptually similar to modular synth frameworks and patch-based programming). Adapt names and APIs to your specific lspatch implementation.
Example modules (detailed designs)
-
Bandlimited Saw Oscillator
- Inputs: freq (Hz audio-rate), phase reset (trigger)
- Outputs: out (audio)
- Parameters: amp (0–1), waveform aliasing mode
- Implementation: BLEP correction at discontinuities; phase accumulator with 64-bit phase for low jitter; anti-alias oversampling optional.
-
SVF Multi-mode Filter
- Inputs: audio in, cutoff (Hz), Q (resonance), mode CV
- Outputs: low, band, high
- Parameters: cutoff knob, Q knob, mode selector
- Implementation: TPT (Topology-preserving transform) integrator for parameter stability; per-sample coefficient smoothing; prevent self-oscillation by clamping resonance.
-
ADSR Envelope (sample-accurate)
- Inputs: gate (trigger), retrig, curve CV
- Outputs: env (control)
- Parameters: attack, decay, sustain, release, curve shape
- Implementation: per-sample state machine, exponential segments implemented via one-pole filters with time-constant conversion; sample-offset handling for immediate retrigger.
-
Tempo-synced Multi-tap Delay
- Inputs: audio in, tempo BPM (control), sync gate
- Outputs: wet, dry
- Parameters: feedback, mix, tap times (musical divisions), diffusion
- Implementation: circular buffer with fractional-delay interpolation; tempo-to-sample calculation; smooth parameter changes and feedback clamping.
Typical module structure (conceptual)
- metadata (name, description, version)
- targets (file patterns or offsets)
- operations (ordered list of replace/insert/remove/func)
- preconditions (e.g., required signature bytes)
- postchecks (validate expected bytes/checksum)
8. Fuck-Location (Location Spoofer)
Best for: Dating apps (Tinder, Bumble) & Geo-locked games (Pokémon Go).
This is the most stable non-root spoofing module. Unlike fake GPS apps that get detected easily, Fuck-Location hooks directly into the app’s location manager via LSPatch. lspatch modules top
- Warning: Use on social media only. Dating apps have anti-spoofing algorithms that may shadowban you.
5. XAuth (Authentication Forwarding)
Best for: WebView debugging and SSO.
XAuth allows you to forward login tokens from third-party apps into WebView browsers. If you constantly have to log into Google/Apple within an app every time you open it, XAuth solves that.
- Why it’s top tier: Reduces login fatigue dramatically.
Implementation patterns
- Single-process audio graph: process nodes in topological order computed per-graph; detect cycles and insert delays.
- Block-based processing: operate on audio blocks (e.g., 64 samples) to amortize overhead; handle sample-accurate events with offset within block.
- Multi-rate processing: separate control-rate (lower frequency) and audio-rate, updating control parameters every N samples.
- Voice allocator: preallocate voice objects, maintain free list, implement note-on/note-off routing and polyphony limits.
- Message/event routing: use typed message buses with timestamps and sample offsets for accurate scheduling.
- Plugin wrapper: expose modules as VST/AU/CLAP or host them in a standalone lspatch runtime by providing consistent parameter/state serialization.
1. Essential Management Modules
These modules are necessary to manage other modules or the LSPatch environment itself. lspatch modules — overview and practical guide lspatch
- LSPosed Manager
- Why it's top: While LSPatch has a built-in manager interface, installing the actual LSPosed Manager app gives you a more robust dashboard to view logs, check module compatibility, and manage scope (which apps use which modules).
- Note: You often don't "patch" the manager itself; you use it to control the framework. However, in a non-root LSPatch environment, you mostly manage scopes directly inside the LSPatch app.