Skip to content

[wip] support delete track/clip - #23

Draft
zzstoatzz wants to merge 15 commits into
ahujasid:mainfrom
zzstoatzz:main
Draft

[wip] support delete track/clip#23
zzstoatzz wants to merge 15 commits into
ahujasid:mainfrom
zzstoatzz:main

Conversation

@zzstoatzz

@zzstoatzz zzstoatzz commented Apr 26, 2025

Copy link
Copy Markdown

also fixes minor typing issues and adds a script to automate copying the remote script. i don't have experience scripting with ableton but the only way i got it to show in the control surface dropdown was copying it into the app bundle, which felt wrong / like itd be overwritten on update etc

happy to trim out changes if you want to keep them focused

other thoughts

testing it out i noticed several places it might be nice to add tools, but noticed server.py is already quite large/flat - maybe we could modularize things a bit here by using fastmcp 2.0 "hubs"

@coderabbitai

coderabbitai Bot commented Apr 26, 2025

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

zzstoatzz and others added 4 commits April 26, 2025 05:15
…e_device

extends both the remote script and MCP server with the capabilities that
kept requiring socket side-channels in practice:

- get_clip_notes: read a clip's MIDI before editing it
- get/set_device_param: real audio engineering (EQ, reverb, envelopes) with
  display-value feedback
- get_device_chains / set_chain_volume: per-pad drum rack mixing
- set_track_volume / set_send_level / set_master_volume: gain staging
- delete_device: swap instruments (loading always appends)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…p_envelope (step write)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@ahujasid
ahujasid force-pushed the main branch 2 times, most recently from 46f3be4 to babc39d Compare August 16, 2026 13:19
…routing

- introspect(path): dir() any LOM object relative to the song
- get_set_overview: tracks/returns/master, mixer, routing, devices recursing
  into rack chains; every node carries a LOM path
- get_params/set_param/set_routing by path: reaches master, returns and
  rack-nested devices; set_routing changes compressor sidechain source
- get_routing(track, device?)
- scripts/abl.py: direct socket client for iterating without the MCP server
all commands move to handlers.py as cmd_<name>(params) methods with a
MAIN_THREAD_COMMANDS set; __init__.py keeps the socket server and
main-thread scheduling and gains a 'reload' command that importlib.reloads
handlers.py, so iterating no longer requires restarting Live.

drop the two dispatch entries (get_browser_categories, get_browser_items)
whose handlers never existed. scripts/install.sh copies + reloads;
replaces the sudo app-bundle installer.
handlers v3. reports peak/mean per track + master, loudest first, with
optional play/start_time. raw 0-1 meter values (no documented dB mapping).
send_command gains a timeout kwarg; abl.py scales its timeout with seconds.
handlers v4. the blocking sample_meters tied measurement duration to the
socket timeout and mixed transport control into a read. capture now
accumulates on a thread inside Live until stopped; playback is driven
separately (start_playback / set_current_song_time tool added).
handlers v5. v3 drove transport from the socket thread, which is the likely
cause of a Live crash; v4 still read the LOM from a background thread. the
capture now re-arms itself via schedule_message so all LOM access stays on
the main thread. the blocking sample_meters variant would stall the UI
there, so it is removed — one mechanism: start/get/stop_meter_capture.
v6. drops the MAIN_THREAD_COMMANDS allowlist; the LOM is not thread-safe and
reads from the socket thread are not worth the risk.
handlers v9. get_automated_params scans every device (recursing racks) and
mixer param for automation_state; capture records their values each main
thread tick alongside meters, reported as [beat, value] series bucketed at a
chosen resolution. get_arrangement_envelope reads clip envelopes and
documents that track-lane arrangement automation is not exposed by the LOM.
start/get/stop_meter_capture become start/get/stop_capture.
MCP_Server/als.py indexes every AutomationTarget by enclosing track/device/
parameter and joins the AutomationEnvelopes to it: exact breakpoints (with
bezier handles) per lane, no playback needed — the LOM does not expose
lane automation. get_automation (json) and get_automation_grid (one char
per bar per lane) tools; get_song_file remote command supplies the path.
handlers v10: capture meters only accumulate while playing.
handlers v13. the LOM cannot write lane automation (create_automation_envelope
refuses arrangement clips: 'Not a session clip'), but Live records a lane when
a parameter moves during playback with record_mode on. record_automation seeks,
records, applies interpolated points each main-thread tick, restores record
mode / playhead / arms, all in one undo step. verified: ramp written, read
back via capture, undone cleanly.

also: play_from (start then seek — start_playing ignores a prior seek),
call/set_attr low-level LOM primitives, get_song_file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant