Python Developer — Validate & Debug Existing Ableton Live Integration (Fixed-Price Trial)

Description: I have a working but not-yet-validated Python integration with Ableton Live's scripting API — a third-party bridge communicating over JSON-RPC/stdio. I need an experienced Python developer to test it against a real Ableton Live 12 installation, confirm it behaves reliably, and report back on what's solid and what isn't. This is a private project. This posting covers the first, self-contained validation stage only. If it goes well, there's significant follow-on work — this stage is as much about confirming fit as it is about the validation itself. Required: Strong Python, specifically asyncio, subprocess management, and threading/callback debugging Comfortable diagnosing timing, cancellation, and reconnect-handling issues in async code Windows 10 or 11 available for testing Ableton Live 12 Suite available for testing (or willing to acquire it) Able to work independently in an unfamiliar codebase from written documentation Preferred, not required: Ableton MIDI Remote Scripts / Live Object Model experience Prior DAW or music-software integration work Experience with Python WebSockets, JSON-RPC, or similar IPC protocols Scope of this stage — five validation gates, all must pass, repeated reliably several times in a row without manual intervention: Read Ableton's current state (track names, mute/solo status, tempo) via the bridge. Perform the correct action based on that state (e.g., mute the correct track by name). Undo that action cleanly via the bridge. Recover from a deliberate failure — kill the bridge process, or close/restart Ableton mid-session — and confirm the connection recovers rather than hanging or leaving things in a bad state. Repeat the full sequence multiple times back to back with no manual intervention. Required safety step: Test only against a disposable, backed-up Live Set. This is an unofficial, community-maintained bridge, and its own author documents that it can directly edit — and potentially corrupt — a Live Set. Deliverables: Written pass/fail report against each of the five gates, with logs for any failure Any bugs found, reported with enough detail to reproduce A small, obvious fix is welcome if one falls out naturally, but isn't required for this stage — flag anything larger and we'll scope it separately Out of scope for this stage: Anything audio/microphone-related; new feature development beyond what's needed to pass the five gates. Screening question (required): Are you looking to validate and report on this code, or are you also interested in actively debugging and fixing issues you find? Please answer directly — this affects how we scope the next stage.