-
|
Hello, first of all thanks for the work on this project. It looks very promising! Unfortunately I cannot get it to work on my system (Ableton Live 10 on Mac OS 13 running on an M1 Max MacBook Pro). I copied the Also, I forked the project and tried to run I got several messages like I tried copying the Finally, I don`t really understand where I should run the TS code for interacting with Ableton from. Can I just start a Node project somewhere, add ableton-js as dependency, create a file where I import the class, run the whole thing and it and it should just work? I would really appreciate any help with this! Best regards, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
Hey @Sejmou, thanks for your report! That was indeed a bug I accidentally introduced with the last version. Could you try updating to the latest version and see if that fixes the issue? The
Yes, if the AbletonJS plugin is loaded in Live, the Node library should automatically connect to it, no matter where you run it from. I hope this helps and look forward to your reply! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! I managed to run the code from the example in the repo :) I have a follow-up question though: is it somehow possible to arm a specific track via AbletonJS? Or is there maybe even some way to just arm the next or previous track? My goal is to program a footswitch to automatically switch to the next or previous track and arm it on the press of a button. Is this achievable with the help of AbletonJS? Or do you happen to know any alternative way to do this? I did a quick search through the API with the help of IntelliSense in VS Code, but couldn't find a solution. I tried await ableton.song.set('exclusive_arm', 3);in the hope that it would select and arm the third track, but I got an error: |
Beta Was this translation helpful? Give feedback.
-
|
This should arm the first track: const tracks = await ableton.song.get("tracks");
await tracks[0].set("arm", true);Currently, there's no way to quickly check which tracks are armed but if you only use your controller to move the arm state between tracks, you could keep track internally: let currentArmIndex = 0;
async function armNext() {
const tracks = await ableton.song.get("tracks");
await tracks[currentArmIndex].set("arm", false);
await tracks[currentArmIndex + 1].set("arm", true);
currentArmIndex++;
}
async function armPrevious() {
const tracks = await ableton.song.get("tracks");
await tracks[currentArmIndex].set("arm", false);
await tracks[currentArmIndex - 1].set("arm", true);
currentArmIndex--;
}Hope this helps! |
Beta Was this translation helpful? Give feedback.
-
|
Awesome! I managed to achieve what I wanted by using this code together with the Thanks <3 In case someone happens to stumble over this and wants to implement something similar, you can find the code here. |
Beta Was this translation helpful? Give feedback.
-
|
Awesome, glad I could help! I just found a little bug in your code, on line 13 you're not awaiting the result of let currentArmIndex = 0;
for (let i = 0; i < tracks.length; i++) {
if (await tracks[i].get("arm")) {
currentArmIndex = i;
break;
}
}This doesn't look as nice as the |
Beta Was this translation helpful? Give feedback.
-
|
thanks, I already fixed this with this exact approach a few moments before reading this haha |
Beta Was this translation helpful? Give feedback.
Hey @Sejmou, thanks for your report!
That was indeed a bug I accidentally introduced with the last version. Could you try updating to the latest version and see if that fixes the issue? The
yarn ableton:copy-scriptsshould now work as expected as well. Let me know if that works on your end now!Yes, if the AbletonJS plugin is loaded in Live, the Node library should automatically connect to it, no matter where you run it from.
I hope this helps and look forward to your reply!