如何使用 LiveAPI（Ableton Live 的）发送剪辑名称
当播放（触发）音频或 midi 剪辑时，需要使用 OSC 将其名称发送到另一个应用程序。
LiveAPI 是一个界面，允许人们探索和自动化Ableton Live 使用 python 脚本。
执行此操作的代码必须用 python 脚本编写，该脚本必须放置在 Ableton Live 可以找到它的特定文件夹中，在 Live 的首选项中选择。
有关 LiveAPI 的更多信息可以在以下网站上找到：
http://www.assembla.com/wiki/show/live-api
http://groups.google.com/group/liveapi
When an audio or midi clip is played (triggered), its name needs to be sent using OSC to another application.
LiveAPI is an interface which allows one to explore and automate Ableton Live using python scripts.
The code to do this must be written in a python script, which must be placed in a specific folder where Ableton Live can find it, selected in Live's Preferences.
More information about the LiveAPI can be found on these sites:
http://www.assembla.com/wiki/show/live-api
http://groups.google.com/group/liveapi
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
根据 LiveAPI在文档中，Clip 对象有一个“name”属性，用于保存剪辑名称。 想必这就是您想要在 OSC 数据包中发送的内容。
另外，值得一提的是，Live8 中的 Max/MSP 支持可能比 LiveAPI 更舒服，LiveAPI 几乎是一个死项目。 Max/MSP 据说有 OSC 支持，添加它是为了支持 JazzMutant Lemur，但我不确定其中有多少内容进入了 Live。 无论如何，Live8 何时发布是值得记住的。
According to the LiveAPI documentation, the Clip object has a "name" attribute which holds the clip name. Presumably that's what you want to send in your OSC packets.
Also, it's worth mentioning that the Max/MSP support in Live8 will probably be a lot more comfortable to work with than LiveAPI, which is pretty much a dead project. Max/MSP supposedly has OSC support, which was added to support the JazzMutant Lemur, but I'm not sure how much of that made it into Live. Anyways, it's worth keeping in mind for when Live8 is released.
我了解 Max 4 Live，但在我看来，它是一种不同的东西。 是的，它可能能够与 Live 接口来完成人们现在使用 LiveAPI 所做的所有事情。 有些人甚至认为M4L可能甚至不通过LiveAPI，而是使用一些内部接口来代替（因为Ableton和Cycling 74是一起开发的）。 从ableton.com网站上的宣传视频来看，我认为M4L主要是关于制作和修改声音，而不是控制/读取其他乐器、效果、剪辑等。
我不会说LiveAPI项目已经死了，因为许多硬件 MIDI 控制器依赖 LiveAPI 来执行一些自动映射魔法。 当您查看 Live 中的 MIDI Remote Scripts 文件夹时，您会发现每个控制器都有自己的文件夹，其中包含 python 脚本。 因此，我确信 LiveAPI 将继续存在，并且 Live 的大门将保持开放。 他们甚至创建了一个名为 Framework 的新文件夹，其中包含一些较新的代码，可能是新的 Akai 控制器与 Live 配合使用所必需的（这是人们理论上所相信的）。
我计划使用播放剪辑的名称的应用程序称为 vvvv，所以我不想将 Max 引入其中，因为它并不是真正需要的。
我通过某人对原始 LiveAPI 代码的修改取得了一些成功，但只有当我请求所有剪辑的名称时才有效，而当我只请求单个剪辑的名称时则无效。 后来就没时间玩了，本来准备这个的事情就过去了。 我计划最终解决这个问题，但现在已经不再那么紧急了。
I know about Max 4 Live, but as I see it, it's kind of a different thing. Yes, it will probably be able to interface with Live to do all the stuff which people do now with LiveAPI. Some even think that M4L may not even go through LiveAPI, and use some internal interface instead (since Ableton and Cycling 74 are developing it together). From the promo videos on ableton.com site I think that M4L will mostly be about making and modifying sound, and not so much about controlling/reading other instruments, effects, clips etc.
I would not say that LiveAPI project is dead, because a lot of hardware MIDI controllers rely on LiveAPI to do some auto-mapping magic. When you look at the MIDI Remote Scripts folder in Live, you'll see that each controller has it's own folder with a python script. So I definitely think that LiveAPI is going to stay, and that this door into Live will remain open. They even created a new folder called Framework which contains some newer code, probably required for the new Akai controller to work with Live (that is what people believe in theory).
The application I plan to use the playing clip's name is called vvvv, so I don't want to have to bring Max into this, because it is not really needed.
I had some success with someone's modification of the original LiveAPI code, but only worked when I request all the clips' names, not when I asked for just a single one. I didn't have time to play with it later, and the thing for which I was preparing this has passed. I plan to work that out eventually, but it's not that urgent anymore.