Image 1 — Polyend Tracker Studio — free web-based pattern & instrument editor
Image 2 — Polyend Tracker Studio — free web-based pattern & instrument editor
▲ 48 r/Polyend+1 crossposts

Polyend Tracker Studio — free web-based pattern & instrument editor

Hey everyone! I wanted to share a project I've been working on: Polyend Tracker Studio, a free, open-source web editor for the Polyend Tracker.
Try it live https://simoianni.github.io/polyend-tracker-studio/

WHAT IS IT?
A browser-based tool that lets you create, edit, and play Polyend Tracker patterns and instruments — no hardware needed. It runs entirely in your browser (Chrome or Edge recommended for Web MIDI + Web Audio). Nothing gets uploaded anywhere: your samples and instruments stay on your machine, and work-in-progress is auto-saved locally so it survives page reloads.

WHAT CAN IT DO?
Pattern Editor:
- Full step sequencer with Note, Instrument, FX1, and FX2 lanes
- Live playback with adjustable BPM
- Record mode: input notes directly from your QWERTY keyboard
- Import original Tracker project folders (project.mt + patterns + instruments)
- Export to .mtp (pattern), .mid (MIDI), or Ableton Live 12 project

Instrument Editor:
- 8 playmodes: OneShot, Forward/Backward/Pingpong Loop, Slice, Beat Slice, Wavetable, Granular
- Sample editor: Cut, Fade, Normalize, Compress, 3-band EQ
- Sample recorder with MIDI-triggered auto-sampling
- Full parameter control: Filter (LP/HP/BP), Tuning, Volume, Pan, Overdrive, Bitcrush, Delay/Reverb
- 6 automation lanes (ADSR envelope + LFO) for Volume, Pan, Cutoff, Wavetable Pos, Granular Pos, Finetune
- Waveform visualizer with zoom, drag-to-seek, and interactive slice markers
- QWERTY keyboard note input + MIDI controller support
Beat Slice mode: each slice is triggered by a different keyboard note — Z=slice1, S=slice2, X=slice3, D=slice4, etc. (standard tracker keyboard layout).

HOW TO USE
Just open https://simoianni.github.io/polyend-tracker-studio/ and you're good to go. There's a built-in help guide (click the ? button) with all keyboard shortcuts.

CREDITS
This is a fork of the original Polyend Tracker Instrument Editor by Sandro "Sandroid" Ducceschi u/SerpentineDex. Huge thanks to Sandro for the initial codebase and for creating and open-sourcing tracker-lib, the library that makes reading and writing .pti/.mtp/.mt files possible.

LINKS
Live app: https://simoianni.github.io/polyend-tracker-studio/
GitHub: https://github.com/simoianni/polyend-tracker-studio
tracker-lib: https://github.com/polyend/tracker-lib

Let me know what you think! Feedback and contributions are welcome.

u/HelicopterBig3975 — 17 hours ago
▲ 43 r/ableton

Running the original Ableton Move firmware on Raspberry Pi 4 + web GUI

Hi everyone,

I've managed to get the original Ableton Move software running outside the original hardware shell. In simple terms: this is like taking the "brain" of Ableton Move and running it in different environments.

Right now there are two working paths:

  • Raspberry Pi 4: running the Move software natively on Pi hardware
  • Docker / Linux ARM64 container: running the Move software in a container for experimentation and development

I also built a web interface around it, so you can open a browser and interact with it instead of using the physical Move buttons, pads and display.

screen GUI https://ibb.co/W4TB7bRN

From the browser you can see and control things like:

  • the Move display
  • buttons and controls
  • pads and steps
  • LED feedback
  • audio streamed to the browser

What works today:

  • Original Move software running on Raspberry Pi 4
  • Original Move software running in a Docker / Linux ARM64 container
  • Browser-based interface
  • Display visible in the browser
  • Controls from the browser
  • LED feedback
  • Pad/step state
  • Browser audio streaming
  • Raspberry Pi 4 build flow
  • Docker/container setup for experiments and development

Important note:

I'm not distributing Ableton's proprietary firmware, binaries or images. The GitHub repo contains only the open tooling, scripts, web interface, shim source and documentation. To try it, you download the official Move recovery image from Ableton and build everything locally.

Official Move recovery image: https://www.ableton.com/download/hardware/latest/move/recovery/

GitHub repo: https://github.com/simoianni/ableton-move-lab

Why this is exciting:

It means Move is not just a closed box. It can potentially become a platform for experiments, custom hardware, alternative interfaces, mods, preservation work, and maybe even completely new DIY devices based around the Move software.

The Docker/container path also makes it easier for people to experiment, debug and improve things without constantly flashing SD cards or working directly on hardware.

What's next:

  • Better audio interface support
  • Better pad and step behavior
  • More hardware experiments
  • More UI polish
  • Easier setup

I'd love help from anyone into reverse engineering, Linux audio, embedded systems, Docker/Linux, hardware hacking, custom controllers, UI work, or just curious Move experimentation.

Huge respect to the Ableton team. Move is already a brilliant piece of hardware, and the fact that it runs on Raspberry Pi-class Linux hardware makes it feel much more hackable, future-proof, and fun to explore.

This opens the door to a lot of interesting things: mods, experiments, custom interfaces, new hardware ideas, and maybe keeping this device alive for a very long time..

u/HelicopterBig3975 — 3 days ago

Running the original Ableton Move firmware on Raspberry Pi 4 + web GUI

Hi everyone,

I've managed to get the original Ableton Move software running outside the original hardware shell. In simple terms: this is like taking the "brain" of Ableton Move and running it in different environments.

Right now there are two working paths:

  • Raspberry Pi 4: running the Move software natively on Pi hardware
  • Docker / Linux ARM64 container: running the Move software in a container for experimentation and development

I also built a web interface around it, so you can open a browser and interact with it instead of using the physical Move buttons, pads and display.

From the browser you can see and control things like:

  • the Move display
  • buttons and controls
  • pads and steps
  • LED feedback
  • audio streamed to the browser

What works today:

  • Original Move software running on Raspberry Pi 4
  • Original Move software running in a Docker / Linux ARM64 container
  • Browser-based interface
  • Display visible in the browser
  • Controls from the browser
  • LED feedback
  • Pad/step state
  • Browser audio streaming
  • Raspberry Pi 4 build flow
  • Docker/container setup for experiments and development

Important note:

I'm not distributing Ableton's proprietary firmware, binaries or images. The GitHub repo contains only the open tooling, scripts, web interface, shim source and documentation. To try it, you download the official Move recovery image from Ableton and build everything locally.

Official Move recovery image: https://www.ableton.com/download/hardware/latest/move/recovery/

GitHub repo: https://github.com/simoianni/ableton-move-lab

Why this is exciting:

It means Move is not just a closed box. It can potentially become a platform for experiments, custom hardware, alternative interfaces, mods, preservation work, and maybe even completely new DIY devices based around the Move software.

The Docker/container path also makes it easier for people to experiment, debug and improve things without constantly flashing SD cards or working directly on hardware.

What's next:

  • Better audio interface support
  • Better pad and step behavior
  • More hardware experiments
  • More UI polish
  • Easier setup

I'd love help from anyone into reverse engineering, Linux audio, embedded systems, Docker/Linux, hardware hacking, custom controllers, UI work, or just curious Move experimentation.

Huge respect to the Ableton team. Move is already a brilliant piece of hardware, and the fact that it runs on Raspberry Pi-class Linux hardware makes it feel much more hackable, future-proof, and fun to explore.

This opens the door to a lot of interesting things: mods, experiments, custom interfaces, new hardware ideas, and maybe keeping this device alive for a very long time.

u/HelicopterBig3975 — 3 days ago

118d M Sport perfetta ma vorrei cambiare: cosa comprereste con 20–22k?

Ciao a tutti, ho una BMW 118d M Sport del 2017, mappa 185 CV, 155mila km, impianto frenante maggiorato Msport (pinze blu)

Per me l'auto va benissimo: fa 17 km/l, è divertente, ha trazione posteriore e motore longitudinale, gestisce i pesi molto bene. È divertente, comoda e consuma poco.

Ma ogni tanto avrei voglia di cambiare. Il punto è che ora le auto costano troppo. Vorrei qualcosa sportivo, divertente, con consumi accettabili. Cosa propone il mercato?

Non voglio spendere cifre folli, volevo stare sui 20–22k prendendo un usato. Ma ripeto, cosa comprereste?

Ci penso ogni tanto, ma poi mi dico "mi tengo la mia".

reddit.com
u/HelicopterBig3975 — 23 days ago

I built a local DeepSeek api gateway for Claude Desktop

Hey everyone, I built a small local proxy that lets Claude Desktop run through DeepSeek instead of Anthropic’s API. It handles HTTPS (using local CA certs), maps Claude model IDs to DeepSeek models, and works with Claude Desktop’s gateway setup out of the box. I couldn’t find anything like this already available, so I made it myself, hopefully it’s useful community

Repo: https://github.com/iannuz92/claude-deepseek-proxy

u/HelicopterBig3975 — 2 months ago