tordo 0.1.2__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- tordo-0.1.2/.gitignore +18 -0
- tordo-0.1.2/LICENSE +158 -0
- tordo-0.1.2/PKG-INFO +235 -0
- tordo-0.1.2/README.md +214 -0
- tordo-0.1.2/pyproject.toml +59 -0
- tordo-0.1.2/remote-script/TordoBridge/__init__.py +5 -0
- tordo-0.1.2/remote-script/TordoBridge/bridge.py +2677 -0
- tordo-0.1.2/tordo/__init__.py +1 -0
- tordo-0.1.2/tordo/analysis.py +818 -0
- tordo-0.1.2/tordo/archive.py +94 -0
- tordo-0.1.2/tordo/bridge_client.py +54 -0
- tordo-0.1.2/tordo/cli.py +946 -0
- tordo-0.1.2/tordo/client.py +159 -0
- tordo-0.1.2/tordo/diff.py +346 -0
- tordo-0.1.2/tordo/doctor.py +298 -0
- tordo-0.1.2/tordo/midi_import.py +714 -0
- tordo-0.1.2/tordo/paths.py +16 -0
- tordo-0.1.2/tordo/plan_preflight.py +268 -0
- tordo-0.1.2/tordo/plans.py +765 -0
- tordo-0.1.2/tordo/project_cleanup.py +82 -0
- tordo-0.1.2/tordo/proofs.py +572 -0
- tordo-0.1.2/tordo/remote_install.py +95 -0
- tordo-0.1.2/tordo/schema.py +90 -0
- tordo-0.1.2/tordo/selectors.py +172 -0
- tordo-0.1.2/tordo/verification.py +528 -0
tordo-0.1.2/.gitignore
ADDED
tordo-0.1.2/LICENSE
ADDED
|
@@ -0,0 +1,158 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction, and
|
|
10
|
+
distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by the copyright
|
|
13
|
+
owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all other entities
|
|
16
|
+
that control, are controlled by, or are under common control with that entity.
|
|
17
|
+
For the purposes of this definition, "control" means (i) the power, direct or
|
|
18
|
+
indirect, to cause the direction or management of such entity, whether by
|
|
19
|
+
contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
20
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
21
|
+
|
|
22
|
+
"You" (or "Your") shall mean an individual or Legal Entity exercising
|
|
23
|
+
permissions granted by this License.
|
|
24
|
+
|
|
25
|
+
"Source" form shall mean the preferred form for making modifications, including
|
|
26
|
+
but not limited to software source code, documentation source, and configuration
|
|
27
|
+
files.
|
|
28
|
+
|
|
29
|
+
"Object" form shall mean any form resulting from mechanical transformation or
|
|
30
|
+
translation of a Source form, including but not limited to compiled object code,
|
|
31
|
+
generated documentation, and conversions to other media types.
|
|
32
|
+
|
|
33
|
+
"Work" shall mean the work of authorship, whether in Source or Object form,
|
|
34
|
+
made available under the License, as indicated by a copyright notice that is
|
|
35
|
+
included in or attached to the work.
|
|
36
|
+
|
|
37
|
+
"Derivative Works" shall mean any work, whether in Source or Object form, that
|
|
38
|
+
is based on (or derived from) the Work and for which the editorial revisions,
|
|
39
|
+
annotations, elaborations, or other modifications represent, as a whole, an
|
|
40
|
+
original work of authorship. For the purposes of this License, Derivative Works
|
|
41
|
+
shall not include works that remain separable from, or merely link (or bind by
|
|
42
|
+
name) to the interfaces of, the Work and Derivative Works thereof.
|
|
43
|
+
|
|
44
|
+
"Contribution" shall mean any work of authorship, including the original
|
|
45
|
+
version of the Work and any modifications or additions to that Work or
|
|
46
|
+
Derivative Works thereof, that is intentionally submitted to Licensor for
|
|
47
|
+
inclusion in the Work by the copyright owner or by an individual or Legal Entity
|
|
48
|
+
authorized to submit on behalf of the copyright owner. For the purposes of this
|
|
49
|
+
definition, "submitted" means any form of electronic, verbal, or written
|
|
50
|
+
communication sent to the Licensor or its representatives, including but not
|
|
51
|
+
limited to communication on electronic mailing lists, source code control
|
|
52
|
+
systems, and issue tracking systems that are managed by, or on behalf of, the
|
|
53
|
+
Licensor for the purpose of discussing and improving the Work, but excluding
|
|
54
|
+
communication that is conspicuously marked or otherwise designated in writing by
|
|
55
|
+
the copyright owner as "Not a Contribution."
|
|
56
|
+
|
|
57
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf
|
|
58
|
+
of whom a Contribution has been received by Licensor and subsequently
|
|
59
|
+
incorporated within the Work.
|
|
60
|
+
|
|
61
|
+
2. Grant of Copyright License. Subject to the terms and conditions of this
|
|
62
|
+
License, each Contributor hereby grants to You a perpetual, worldwide,
|
|
63
|
+
non-exclusive, no-charge, royalty-free, irrevocable copyright license to
|
|
64
|
+
reproduce, prepare Derivative Works of, publicly display, publicly perform,
|
|
65
|
+
sublicense, and distribute the Work and such Derivative Works in Source or
|
|
66
|
+
Object form.
|
|
67
|
+
|
|
68
|
+
3. Grant of Patent License. Subject to the terms and conditions of this License,
|
|
69
|
+
each Contributor hereby grants to You a perpetual, worldwide, non-exclusive,
|
|
70
|
+
no-charge, royalty-free, irrevocable (except as stated in this section) patent
|
|
71
|
+
license to make, have made, use, offer to sell, sell, import, and otherwise
|
|
72
|
+
transfer the Work, where such license applies only to those patent claims
|
|
73
|
+
licensable by such Contributor that are necessarily infringed by their
|
|
74
|
+
Contribution(s) alone or by combination of their Contribution(s) with the Work to
|
|
75
|
+
which such Contribution(s) was submitted. If You institute patent litigation
|
|
76
|
+
against any entity (including a cross-claim or counterclaim in a lawsuit)
|
|
77
|
+
alleging that the Work or a Contribution incorporated within the Work
|
|
78
|
+
constitutes direct or contributory patent infringement, then any patent licenses
|
|
79
|
+
granted to You under this License for that Work shall terminate as of the date
|
|
80
|
+
such litigation is filed.
|
|
81
|
+
|
|
82
|
+
4. Redistribution. You may reproduce and distribute copies of the Work or
|
|
83
|
+
Derivative Works thereof in any medium, with or without modifications, and in
|
|
84
|
+
Source or Object form, provided that You meet the following conditions:
|
|
85
|
+
|
|
86
|
+
(a) You must give any other recipients of the Work or Derivative Works a copy of
|
|
87
|
+
this License; and
|
|
88
|
+
|
|
89
|
+
(b) You must cause any modified files to carry prominent notices stating that
|
|
90
|
+
You changed the files; and
|
|
91
|
+
|
|
92
|
+
(c) You must retain, in the Source form of any Derivative Works that You
|
|
93
|
+
distribute, all copyright, patent, trademark, and attribution notices from the
|
|
94
|
+
Source form of the Work, excluding those notices that do not pertain to any part
|
|
95
|
+
of the Derivative Works; and
|
|
96
|
+
|
|
97
|
+
(d) If the Work includes a "NOTICE" text file as part of its distribution, then
|
|
98
|
+
any Derivative Works that You distribute must include a readable copy of the
|
|
99
|
+
attribution notices contained within such NOTICE file, excluding those notices
|
|
100
|
+
that do not pertain to any part of the Derivative Works, in at least one of the
|
|
101
|
+
following places: within a NOTICE text file distributed as part of the Derivative
|
|
102
|
+
Works; within the Source form or documentation, if provided along with the
|
|
103
|
+
Derivative Works; or, within a display generated by the Derivative Works, if and
|
|
104
|
+
wherever such third-party notices normally appear. The contents of the NOTICE
|
|
105
|
+
file are for informational purposes only and do not modify the License. You may
|
|
106
|
+
add Your own attribution notices within Derivative Works that You distribute,
|
|
107
|
+
alongside or as an addendum to the NOTICE text from the Work, provided that such
|
|
108
|
+
additional attribution notices cannot be construed as modifying the License.
|
|
109
|
+
|
|
110
|
+
You may add Your own copyright statement to Your modifications and may provide
|
|
111
|
+
additional or different license terms and conditions for use, reproduction, or
|
|
112
|
+
distribution of Your modifications, or for any such Derivative Works as a whole,
|
|
113
|
+
provided Your use, reproduction, and distribution of the Work otherwise complies
|
|
114
|
+
with the conditions stated in this License.
|
|
115
|
+
|
|
116
|
+
5. Submission of Contributions. Unless You explicitly state otherwise, any
|
|
117
|
+
Contribution intentionally submitted for inclusion in the Work by You to the
|
|
118
|
+
Licensor shall be under the terms and conditions of this License, without any
|
|
119
|
+
additional terms or conditions. Notwithstanding the above, nothing herein shall
|
|
120
|
+
supersede or modify the terms of any separate license agreement you may have
|
|
121
|
+
executed with Licensor regarding such Contributions.
|
|
122
|
+
|
|
123
|
+
6. Trademarks. This License does not grant permission to use the trade names,
|
|
124
|
+
trademarks, service marks, or product names of the Licensor, except as required
|
|
125
|
+
for reasonable and customary use in describing the origin of the Work and
|
|
126
|
+
reproducing the content of the NOTICE file.
|
|
127
|
+
|
|
128
|
+
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in
|
|
129
|
+
writing, Licensor provides the Work (and each Contributor provides its
|
|
130
|
+
Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
|
131
|
+
KIND, either express or implied, including, without limitation, any warranties or
|
|
132
|
+
conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
133
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
134
|
+
appropriateness of using or redistributing the Work and assume any risks
|
|
135
|
+
associated with Your exercise of permissions under this License.
|
|
136
|
+
|
|
137
|
+
8. Limitation of Liability. In no event and under no legal theory, whether in
|
|
138
|
+
tort (including negligence), contract, or otherwise, unless required by
|
|
139
|
+
applicable law (such as deliberate and grossly negligent acts) or agreed to in
|
|
140
|
+
writing, shall any Contributor be liable to You for damages, including any
|
|
141
|
+
direct, indirect, special, incidental, or consequential damages of any character
|
|
142
|
+
arising as a result of this License or out of the use or inability to use the
|
|
143
|
+
Work (including but not limited to damages for loss of goodwill, work stoppage,
|
|
144
|
+
computer failure or malfunction, or any and all other commercial damages or
|
|
145
|
+
losses), even if such Contributor has been advised of the possibility of such
|
|
146
|
+
damages.
|
|
147
|
+
|
|
148
|
+
9. Accepting Warranty or Additional Liability. While redistributing the Work or
|
|
149
|
+
Derivative Works thereof, You may choose to offer, and charge a fee for,
|
|
150
|
+
acceptance of support, warranty, indemnity, or other liability obligations
|
|
151
|
+
and/or rights consistent with this License. However, in accepting such
|
|
152
|
+
obligations, You may act only on Your own behalf and on Your sole
|
|
153
|
+
responsibility, not on behalf of any other Contributor, and only if You agree to
|
|
154
|
+
indemnify, defend, and hold each Contributor harmless for any liability incurred
|
|
155
|
+
by, or claims asserted against, such Contributor by reason of your accepting any
|
|
156
|
+
such warranty or additional liability.
|
|
157
|
+
|
|
158
|
+
END OF TERMS AND CONDITIONS
|
tordo-0.1.2/PKG-INFO
ADDED
|
@@ -0,0 +1,235 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: tordo
|
|
3
|
+
Version: 0.1.2
|
|
4
|
+
Summary: Agent-facing CLI toolkit for safely inspecting and controlling Ableton Live.
|
|
5
|
+
Project-URL: Homepage, https://deadjoe.github.io/tordo/
|
|
6
|
+
Project-URL: Repository, https://github.com/deadjoe/tordo
|
|
7
|
+
License-Expression: Apache-2.0
|
|
8
|
+
License-File: LICENSE
|
|
9
|
+
Keywords: ableton,ai-agent,cli,live,midi
|
|
10
|
+
Classifier: Development Status :: 3 - Alpha
|
|
11
|
+
Classifier: Environment :: Console
|
|
12
|
+
Classifier: Intended Audience :: Developers
|
|
13
|
+
Classifier: License :: OSI Approved :: Apache Software License
|
|
14
|
+
Classifier: Operating System :: MacOS
|
|
15
|
+
Classifier: Programming Language :: Python :: 3
|
|
16
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
17
|
+
Classifier: Topic :: Multimedia :: Sound/Audio :: MIDI
|
|
18
|
+
Requires-Python: >=3.11
|
|
19
|
+
Requires-Dist: mido>=1.3.3
|
|
20
|
+
Description-Content-Type: text/markdown
|
|
21
|
+
|
|
22
|
+
# tordo
|
|
23
|
+
|
|
24
|
+
<p align="center">
|
|
25
|
+
<img src="https://raw.githubusercontent.com/deadjoe/tordo/main/assets/tordo_logo.png" alt="tordo logo" width="200" height="200">
|
|
26
|
+
</p>
|
|
27
|
+
|
|
28
|
+
Tordo is an agent-facing Ableton Live control toolkit. It gives an AI agent a
|
|
29
|
+
stable CLI and JSON-plan contract for inspecting, planning, dry-running,
|
|
30
|
+
applying, and verifying safe changes inside a Live Set.
|
|
31
|
+
|
|
32
|
+
Tordo is in developer alpha.
|
|
33
|
+
|
|
34
|
+
## Features
|
|
35
|
+
|
|
36
|
+
- Inspect tracks, scenes, clips, devices, mixer state, Browser items, and MIDI notes.
|
|
37
|
+
- Create tracks, scenes, MIDI clips, and notes through explicit JSON plans.
|
|
38
|
+
- Dry-run plans before writing to Ableton Live.
|
|
39
|
+
- Resolve names against a fresh snapshot before apply to reduce stale-index mistakes.
|
|
40
|
+
- Guard writes with expected track, scene, clip, device, and parameter names.
|
|
41
|
+
- Load discovered Browser items such as racks and presets.
|
|
42
|
+
- Insert native Live devices and adjust supported mixer and device parameters.
|
|
43
|
+
- Export snapshots and note archives for offline analysis and diffing.
|
|
44
|
+
- Keep musical judgment human-ear-in-the-loop: Tordo can edit state, but it does not hear audio quality.
|
|
45
|
+
|
|
46
|
+
## Requirements
|
|
47
|
+
|
|
48
|
+
- macOS
|
|
49
|
+
- Ableton Live 12.4 Suite or newer
|
|
50
|
+
- Python 3.11+
|
|
51
|
+
- `uv`, `pipx`, or another Python CLI installer
|
|
52
|
+
|
|
53
|
+
## End-User Installation
|
|
54
|
+
|
|
55
|
+
Recommended setup is agent-led:
|
|
56
|
+
|
|
57
|
+
1. Open a skill-capable AI agent, such as Claude, Claude Code, Codex, or another
|
|
58
|
+
assistant that can install or read agent skills from a public GitHub repo.
|
|
59
|
+
2. Paste this request:
|
|
60
|
+
|
|
61
|
+
```text
|
|
62
|
+
Add the Tordo skill from https://github.com/deadjoe/tordo/tree/main/skills/tordo,
|
|
63
|
+
then set it up for Ableton Live on this Mac and check everything works.
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
3. Let the agent inspect the Skill, install or expose the `tordo` CLI with your
|
|
67
|
+
approval, run `tordo doctor`, install the Ableton Remote Script, and guide you
|
|
68
|
+
through the required Ableton Live restart and Control Surface selection.
|
|
69
|
+
|
|
70
|
+
After setup, open a Live Set and ask the agent for the musical change you want.
|
|
71
|
+
Tordo previews changes before applying them.
|
|
72
|
+
|
|
73
|
+
Skill support differs by agent. If your agent cannot install a Skill directly
|
|
74
|
+
from GitHub, clone this repository and point the agent at `skills/tordo/`.
|
|
75
|
+
|
|
76
|
+
Manual CLI setup is also available.
|
|
77
|
+
|
|
78
|
+
Install the CLI.
|
|
79
|
+
|
|
80
|
+
Published package install, after the package is available on PyPI:
|
|
81
|
+
|
|
82
|
+
```bash
|
|
83
|
+
uv tool install tordo
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
Current alpha source install:
|
|
87
|
+
|
|
88
|
+
```bash
|
|
89
|
+
uv tool install git+https://github.com/deadjoe/tordo.git
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
Install the Ableton Remote Script into your Ableton User Library:
|
|
93
|
+
|
|
94
|
+
```bash
|
|
95
|
+
tordo install-remote-script
|
|
96
|
+
```
|
|
97
|
+
|
|
98
|
+
Restart Ableton Live, then select this control surface:
|
|
99
|
+
|
|
100
|
+
```text
|
|
101
|
+
Settings -> Link, Tempo & MIDI -> Control Surface -> TordoBridge
|
|
102
|
+
```
|
|
103
|
+
|
|
104
|
+
Input and Output can stay set to `None`.
|
|
105
|
+
|
|
106
|
+
Check the setup:
|
|
107
|
+
|
|
108
|
+
```bash
|
|
109
|
+
tordo doctor
|
|
110
|
+
tordo ping
|
|
111
|
+
tordo snapshot
|
|
112
|
+
tordo schema
|
|
113
|
+
tordo capabilities
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
## Agent Skill
|
|
117
|
+
|
|
118
|
+
The first agent-facing Skill lives in `skills/tordo/`.
|
|
119
|
+
|
|
120
|
+
Give a compatible AI agent this Skill path:
|
|
121
|
+
|
|
122
|
+
```text
|
|
123
|
+
https://github.com/deadjoe/tordo/tree/main/skills/tordo
|
|
124
|
+
```
|
|
125
|
+
|
|
126
|
+
The Skill teaches the agent to:
|
|
127
|
+
|
|
128
|
+
- check whether the local `tordo` CLI is installed
|
|
129
|
+
- propose a `tordo` CLI install command and ask before running it
|
|
130
|
+
- run `tordo doctor`, `tordo schema`, and `tordo capabilities`
|
|
131
|
+
- install the `TordoBridge` Remote Script into Ableton Live
|
|
132
|
+
- discover installed Packs, User Library, and Current Project Browser resources
|
|
133
|
+
- dry-run every plan before apply
|
|
134
|
+
- verify changes after apply
|
|
135
|
+
- ask for human listening feedback when a decision depends on musical taste
|
|
136
|
+
|
|
137
|
+
## Basic Plan Flow
|
|
138
|
+
|
|
139
|
+
Plans are JSON documents applied through `apply-plan`.
|
|
140
|
+
|
|
141
|
+
Dry-run first:
|
|
142
|
+
|
|
143
|
+
```bash
|
|
144
|
+
tordo apply-plan plan.json --prepared-out prepared-dry-run.json
|
|
145
|
+
```
|
|
146
|
+
|
|
147
|
+
Apply only after inspection:
|
|
148
|
+
|
|
149
|
+
```bash
|
|
150
|
+
tordo apply-plan plan.json --apply --prepared-out prepared-apply.json --timeout 120
|
|
151
|
+
```
|
|
152
|
+
|
|
153
|
+
Example operation:
|
|
154
|
+
|
|
155
|
+
```json
|
|
156
|
+
{
|
|
157
|
+
"plan_version": 1,
|
|
158
|
+
"name": "shape-main-hook",
|
|
159
|
+
"operations": [
|
|
160
|
+
{
|
|
161
|
+
"type": "set_device_parameter",
|
|
162
|
+
"track_name": "Main Hook",
|
|
163
|
+
"device_index": 0,
|
|
164
|
+
"device_name": "Antenna Lead",
|
|
165
|
+
"parameter_index": 6,
|
|
166
|
+
"parameter_name": "Echo",
|
|
167
|
+
"value": 8.0
|
|
168
|
+
}
|
|
169
|
+
]
|
|
170
|
+
}
|
|
171
|
+
```
|
|
172
|
+
|
|
173
|
+
The CLI resolves names to current indices from a fresh snapshot, then adds
|
|
174
|
+
expected-name guards before the plan reaches Live.
|
|
175
|
+
|
|
176
|
+
## Safety Boundaries
|
|
177
|
+
|
|
178
|
+
- Never assume a previously observed track index is still correct.
|
|
179
|
+
- Resolve names from a fresh snapshot immediately before write operations.
|
|
180
|
+
- Dry-run destructive or large writes first.
|
|
181
|
+
- Do not overwrite existing clips implicitly.
|
|
182
|
+
- Do not delete tracks or scenes without explicit destructive permission.
|
|
183
|
+
- Do not delete the final regular track in a Live Set.
|
|
184
|
+
- Treat installed Packs, User Library, and Current Project Browser contents as
|
|
185
|
+
user-specific resources that must be discovered before use.
|
|
186
|
+
|
|
187
|
+
## Developer Notes
|
|
188
|
+
|
|
189
|
+
Set up a local checkout:
|
|
190
|
+
|
|
191
|
+
```bash
|
|
192
|
+
uv sync --dev --frozen
|
|
193
|
+
```
|
|
194
|
+
|
|
195
|
+
Run the local quality gates:
|
|
196
|
+
|
|
197
|
+
```bash
|
|
198
|
+
uv run ruff check .
|
|
199
|
+
uv run python tools/check_operation_registry.py
|
|
200
|
+
uv run python -m unittest discover -s tests -p 'test*.py'
|
|
201
|
+
uv run python -m py_compile tordo/*.py remote-script/TordoBridge/bridge.py tools/*.py tests/*.py skills/tordo/scripts/*.py
|
|
202
|
+
```
|
|
203
|
+
|
|
204
|
+
Build and validate package artifacts:
|
|
205
|
+
|
|
206
|
+
```bash
|
|
207
|
+
rm -rf dist
|
|
208
|
+
uv build
|
|
209
|
+
uv run python tools/check_package_artifacts.py
|
|
210
|
+
uv publish --dry-run --trusted-publishing never dist/*
|
|
211
|
+
```
|
|
212
|
+
|
|
213
|
+
The wheel contains the Python CLI plus the packaged `TordoBridge` Remote Script
|
|
214
|
+
source. The sdist is intentionally scoped to public release files and excludes
|
|
215
|
+
non-release development materials, local test material, and runtime artifacts.
|
|
216
|
+
|
|
217
|
+
## Versioning
|
|
218
|
+
|
|
219
|
+
The Python package version and Live bridge version are intentionally separate:
|
|
220
|
+
|
|
221
|
+
- The package version is the CLI and Skill distribution version shown by PyPI.
|
|
222
|
+
- The bridge version is the Live-side Remote Script compatibility version checked
|
|
223
|
+
by `tordo doctor`.
|
|
224
|
+
|
|
225
|
+
The current bridge source version is `TordoBridge 0.8.1`.
|
|
226
|
+
|
|
227
|
+
## License
|
|
228
|
+
|
|
229
|
+
Tordo is licensed under the Apache License, Version 2.0. See `LICENSE`.
|
|
230
|
+
|
|
231
|
+
## Trademark Notice
|
|
232
|
+
|
|
233
|
+
Tordo is an independent project and is not affiliated with, authorized,
|
|
234
|
+
sponsored, or endorsed by Ableton AG. Ableton and Live are trademarks of Ableton
|
|
235
|
+
AG.
|
tordo-0.1.2/README.md
ADDED
|
@@ -0,0 +1,214 @@
|
|
|
1
|
+
# tordo
|
|
2
|
+
|
|
3
|
+
<p align="center">
|
|
4
|
+
<img src="https://raw.githubusercontent.com/deadjoe/tordo/main/assets/tordo_logo.png" alt="tordo logo" width="200" height="200">
|
|
5
|
+
</p>
|
|
6
|
+
|
|
7
|
+
Tordo is an agent-facing Ableton Live control toolkit. It gives an AI agent a
|
|
8
|
+
stable CLI and JSON-plan contract for inspecting, planning, dry-running,
|
|
9
|
+
applying, and verifying safe changes inside a Live Set.
|
|
10
|
+
|
|
11
|
+
Tordo is in developer alpha.
|
|
12
|
+
|
|
13
|
+
## Features
|
|
14
|
+
|
|
15
|
+
- Inspect tracks, scenes, clips, devices, mixer state, Browser items, and MIDI notes.
|
|
16
|
+
- Create tracks, scenes, MIDI clips, and notes through explicit JSON plans.
|
|
17
|
+
- Dry-run plans before writing to Ableton Live.
|
|
18
|
+
- Resolve names against a fresh snapshot before apply to reduce stale-index mistakes.
|
|
19
|
+
- Guard writes with expected track, scene, clip, device, and parameter names.
|
|
20
|
+
- Load discovered Browser items such as racks and presets.
|
|
21
|
+
- Insert native Live devices and adjust supported mixer and device parameters.
|
|
22
|
+
- Export snapshots and note archives for offline analysis and diffing.
|
|
23
|
+
- Keep musical judgment human-ear-in-the-loop: Tordo can edit state, but it does not hear audio quality.
|
|
24
|
+
|
|
25
|
+
## Requirements
|
|
26
|
+
|
|
27
|
+
- macOS
|
|
28
|
+
- Ableton Live 12.4 Suite or newer
|
|
29
|
+
- Python 3.11+
|
|
30
|
+
- `uv`, `pipx`, or another Python CLI installer
|
|
31
|
+
|
|
32
|
+
## End-User Installation
|
|
33
|
+
|
|
34
|
+
Recommended setup is agent-led:
|
|
35
|
+
|
|
36
|
+
1. Open a skill-capable AI agent, such as Claude, Claude Code, Codex, or another
|
|
37
|
+
assistant that can install or read agent skills from a public GitHub repo.
|
|
38
|
+
2. Paste this request:
|
|
39
|
+
|
|
40
|
+
```text
|
|
41
|
+
Add the Tordo skill from https://github.com/deadjoe/tordo/tree/main/skills/tordo,
|
|
42
|
+
then set it up for Ableton Live on this Mac and check everything works.
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
3. Let the agent inspect the Skill, install or expose the `tordo` CLI with your
|
|
46
|
+
approval, run `tordo doctor`, install the Ableton Remote Script, and guide you
|
|
47
|
+
through the required Ableton Live restart and Control Surface selection.
|
|
48
|
+
|
|
49
|
+
After setup, open a Live Set and ask the agent for the musical change you want.
|
|
50
|
+
Tordo previews changes before applying them.
|
|
51
|
+
|
|
52
|
+
Skill support differs by agent. If your agent cannot install a Skill directly
|
|
53
|
+
from GitHub, clone this repository and point the agent at `skills/tordo/`.
|
|
54
|
+
|
|
55
|
+
Manual CLI setup is also available.
|
|
56
|
+
|
|
57
|
+
Install the CLI.
|
|
58
|
+
|
|
59
|
+
Published package install, after the package is available on PyPI:
|
|
60
|
+
|
|
61
|
+
```bash
|
|
62
|
+
uv tool install tordo
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
Current alpha source install:
|
|
66
|
+
|
|
67
|
+
```bash
|
|
68
|
+
uv tool install git+https://github.com/deadjoe/tordo.git
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
Install the Ableton Remote Script into your Ableton User Library:
|
|
72
|
+
|
|
73
|
+
```bash
|
|
74
|
+
tordo install-remote-script
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
Restart Ableton Live, then select this control surface:
|
|
78
|
+
|
|
79
|
+
```text
|
|
80
|
+
Settings -> Link, Tempo & MIDI -> Control Surface -> TordoBridge
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
Input and Output can stay set to `None`.
|
|
84
|
+
|
|
85
|
+
Check the setup:
|
|
86
|
+
|
|
87
|
+
```bash
|
|
88
|
+
tordo doctor
|
|
89
|
+
tordo ping
|
|
90
|
+
tordo snapshot
|
|
91
|
+
tordo schema
|
|
92
|
+
tordo capabilities
|
|
93
|
+
```
|
|
94
|
+
|
|
95
|
+
## Agent Skill
|
|
96
|
+
|
|
97
|
+
The first agent-facing Skill lives in `skills/tordo/`.
|
|
98
|
+
|
|
99
|
+
Give a compatible AI agent this Skill path:
|
|
100
|
+
|
|
101
|
+
```text
|
|
102
|
+
https://github.com/deadjoe/tordo/tree/main/skills/tordo
|
|
103
|
+
```
|
|
104
|
+
|
|
105
|
+
The Skill teaches the agent to:
|
|
106
|
+
|
|
107
|
+
- check whether the local `tordo` CLI is installed
|
|
108
|
+
- propose a `tordo` CLI install command and ask before running it
|
|
109
|
+
- run `tordo doctor`, `tordo schema`, and `tordo capabilities`
|
|
110
|
+
- install the `TordoBridge` Remote Script into Ableton Live
|
|
111
|
+
- discover installed Packs, User Library, and Current Project Browser resources
|
|
112
|
+
- dry-run every plan before apply
|
|
113
|
+
- verify changes after apply
|
|
114
|
+
- ask for human listening feedback when a decision depends on musical taste
|
|
115
|
+
|
|
116
|
+
## Basic Plan Flow
|
|
117
|
+
|
|
118
|
+
Plans are JSON documents applied through `apply-plan`.
|
|
119
|
+
|
|
120
|
+
Dry-run first:
|
|
121
|
+
|
|
122
|
+
```bash
|
|
123
|
+
tordo apply-plan plan.json --prepared-out prepared-dry-run.json
|
|
124
|
+
```
|
|
125
|
+
|
|
126
|
+
Apply only after inspection:
|
|
127
|
+
|
|
128
|
+
```bash
|
|
129
|
+
tordo apply-plan plan.json --apply --prepared-out prepared-apply.json --timeout 120
|
|
130
|
+
```
|
|
131
|
+
|
|
132
|
+
Example operation:
|
|
133
|
+
|
|
134
|
+
```json
|
|
135
|
+
{
|
|
136
|
+
"plan_version": 1,
|
|
137
|
+
"name": "shape-main-hook",
|
|
138
|
+
"operations": [
|
|
139
|
+
{
|
|
140
|
+
"type": "set_device_parameter",
|
|
141
|
+
"track_name": "Main Hook",
|
|
142
|
+
"device_index": 0,
|
|
143
|
+
"device_name": "Antenna Lead",
|
|
144
|
+
"parameter_index": 6,
|
|
145
|
+
"parameter_name": "Echo",
|
|
146
|
+
"value": 8.0
|
|
147
|
+
}
|
|
148
|
+
]
|
|
149
|
+
}
|
|
150
|
+
```
|
|
151
|
+
|
|
152
|
+
The CLI resolves names to current indices from a fresh snapshot, then adds
|
|
153
|
+
expected-name guards before the plan reaches Live.
|
|
154
|
+
|
|
155
|
+
## Safety Boundaries
|
|
156
|
+
|
|
157
|
+
- Never assume a previously observed track index is still correct.
|
|
158
|
+
- Resolve names from a fresh snapshot immediately before write operations.
|
|
159
|
+
- Dry-run destructive or large writes first.
|
|
160
|
+
- Do not overwrite existing clips implicitly.
|
|
161
|
+
- Do not delete tracks or scenes without explicit destructive permission.
|
|
162
|
+
- Do not delete the final regular track in a Live Set.
|
|
163
|
+
- Treat installed Packs, User Library, and Current Project Browser contents as
|
|
164
|
+
user-specific resources that must be discovered before use.
|
|
165
|
+
|
|
166
|
+
## Developer Notes
|
|
167
|
+
|
|
168
|
+
Set up a local checkout:
|
|
169
|
+
|
|
170
|
+
```bash
|
|
171
|
+
uv sync --dev --frozen
|
|
172
|
+
```
|
|
173
|
+
|
|
174
|
+
Run the local quality gates:
|
|
175
|
+
|
|
176
|
+
```bash
|
|
177
|
+
uv run ruff check .
|
|
178
|
+
uv run python tools/check_operation_registry.py
|
|
179
|
+
uv run python -m unittest discover -s tests -p 'test*.py'
|
|
180
|
+
uv run python -m py_compile tordo/*.py remote-script/TordoBridge/bridge.py tools/*.py tests/*.py skills/tordo/scripts/*.py
|
|
181
|
+
```
|
|
182
|
+
|
|
183
|
+
Build and validate package artifacts:
|
|
184
|
+
|
|
185
|
+
```bash
|
|
186
|
+
rm -rf dist
|
|
187
|
+
uv build
|
|
188
|
+
uv run python tools/check_package_artifacts.py
|
|
189
|
+
uv publish --dry-run --trusted-publishing never dist/*
|
|
190
|
+
```
|
|
191
|
+
|
|
192
|
+
The wheel contains the Python CLI plus the packaged `TordoBridge` Remote Script
|
|
193
|
+
source. The sdist is intentionally scoped to public release files and excludes
|
|
194
|
+
non-release development materials, local test material, and runtime artifacts.
|
|
195
|
+
|
|
196
|
+
## Versioning
|
|
197
|
+
|
|
198
|
+
The Python package version and Live bridge version are intentionally separate:
|
|
199
|
+
|
|
200
|
+
- The package version is the CLI and Skill distribution version shown by PyPI.
|
|
201
|
+
- The bridge version is the Live-side Remote Script compatibility version checked
|
|
202
|
+
by `tordo doctor`.
|
|
203
|
+
|
|
204
|
+
The current bridge source version is `TordoBridge 0.8.1`.
|
|
205
|
+
|
|
206
|
+
## License
|
|
207
|
+
|
|
208
|
+
Tordo is licensed under the Apache License, Version 2.0. See `LICENSE`.
|
|
209
|
+
|
|
210
|
+
## Trademark Notice
|
|
211
|
+
|
|
212
|
+
Tordo is an independent project and is not affiliated with, authorized,
|
|
213
|
+
sponsored, or endorsed by Ableton AG. Ableton and Live are trademarks of Ableton
|
|
214
|
+
AG.
|
|
@@ -0,0 +1,59 @@
|
|
|
1
|
+
[project]
|
|
2
|
+
name = "tordo"
|
|
3
|
+
version = "0.1.2"
|
|
4
|
+
description = "Agent-facing CLI toolkit for safely inspecting and controlling Ableton Live."
|
|
5
|
+
readme = "README.md"
|
|
6
|
+
license = "Apache-2.0"
|
|
7
|
+
requires-python = ">=3.11"
|
|
8
|
+
dependencies = [
|
|
9
|
+
"mido>=1.3.3",
|
|
10
|
+
]
|
|
11
|
+
keywords = ["ableton", "ai-agent", "cli", "live", "midi"]
|
|
12
|
+
classifiers = [
|
|
13
|
+
"Development Status :: 3 - Alpha",
|
|
14
|
+
"Environment :: Console",
|
|
15
|
+
"Intended Audience :: Developers",
|
|
16
|
+
"License :: OSI Approved :: Apache Software License",
|
|
17
|
+
"Operating System :: MacOS",
|
|
18
|
+
"Programming Language :: Python :: 3",
|
|
19
|
+
"Programming Language :: Python :: 3.11",
|
|
20
|
+
"Topic :: Multimedia :: Sound/Audio :: MIDI",
|
|
21
|
+
]
|
|
22
|
+
|
|
23
|
+
[project.scripts]
|
|
24
|
+
tordo = "tordo.cli:main"
|
|
25
|
+
|
|
26
|
+
[project.urls]
|
|
27
|
+
Homepage = "https://deadjoe.github.io/tordo/"
|
|
28
|
+
Repository = "https://github.com/deadjoe/tordo"
|
|
29
|
+
|
|
30
|
+
[build-system]
|
|
31
|
+
requires = ["hatchling"]
|
|
32
|
+
build-backend = "hatchling.build"
|
|
33
|
+
|
|
34
|
+
[tool.hatch.build.targets.wheel]
|
|
35
|
+
packages = ["tordo"]
|
|
36
|
+
|
|
37
|
+
[tool.hatch.build.targets.wheel.force-include]
|
|
38
|
+
"remote-script/TordoBridge" = "tordo/remote_assets/TordoBridge"
|
|
39
|
+
|
|
40
|
+
[tool.hatch.build.targets.sdist]
|
|
41
|
+
include = [
|
|
42
|
+
"/LICENSE",
|
|
43
|
+
"/README.md",
|
|
44
|
+
"/pyproject.toml",
|
|
45
|
+
"/remote-script/TordoBridge",
|
|
46
|
+
"/tordo",
|
|
47
|
+
]
|
|
48
|
+
|
|
49
|
+
[dependency-groups]
|
|
50
|
+
dev = [
|
|
51
|
+
"ruff>=0.14.0",
|
|
52
|
+
]
|
|
53
|
+
|
|
54
|
+
[tool.ruff]
|
|
55
|
+
line-length = 120
|
|
56
|
+
target-version = "py311"
|
|
57
|
+
|
|
58
|
+
[tool.ruff.lint]
|
|
59
|
+
select = ["E", "F", "I"]
|