Hello!
I've been writing few remote scripts for Ableton, and something I've struggled quite a bit was debugging them.

Open Ableton In Terminal 2

It's a personal thing, usually when I code, especially in an environment that I don't know, I need to debug it to understand what's behind the curtain.

To use any version of Live you need an Ableton account. It takes less than a minute to create one, and even less to log in if you already have one. ASD Files are audio analysis files that are auto-created by Ableton each time you use an audio clip in a project for the first time. It stores data on the audio file such as tempo, warp marks, pitch, etc. So the software will not need to re-analyze the audio clip the next time it’s being used. Channelite wrote: Live won't allow you to have two sessions open at the same time. JHJaime2014 wrote: yes u can have 2 live projects at once here's how. Go to Prefferences/Look and Feel. Then Click Multipe instances then exit preferences and there u go. PC: One can open multiple instances of Live. MAC: One cannot open multiple instances of Live. Dec 01, 2020 The Akai Network Driver will allow your MPC X or MPC Live to seamlessly communicate with and control Ableton Live. Download the Network MIDI Driver for your OS from the MPC X/Live product page. After the download completes, click the file to open the setup application. Follow the prompts to complete the installation.

Anyway, how?
I've used remote pdb, here's what you have to do in order to use it [Windows]:

• Pip install remote_pdb in Ableton Remote Scripts folder

create any virtual environment with python 2.7, or use your system interpreter and run the following command: The target folder is your Midi Remote Scripts folder.
This will install remote_pdb and make it accessible in your remote scripts.

• Enable telnet in Windows.

Open your control panel, click Programs, click Turn WIndows Features On/Off.
Look for Telnet, enable it. This will allow you to connect to the pdb process in Ableton.

• The following point is my own pattern, you can do this differently. I created a singleton class which runs the connection listener. This has to be done ONCE, or the process will get stuck and you'll have to use a different terminal each time you run the connection listener creation. The singleton pattern creates the listener just once time in a Debugger singleton class, that you can later on access quickly.

Code: Select all

• Set your breakpoints.

In your code, set your breakpoints in the following way:Remember, Debugger is the singleton class we created in the previous point, so you'll have to import it from wherever you created it.

• Run Ableton, and open a terminal window.

Once Ableton loads, if you select your remote midi script, as soon as it hits the breakpoint the Ableton process should freeze.
This is normal, as the process is awaiting on the python debugger connection.

Open Ableton In Terminal 8

Open Ableton In Terminal 2

In your terminal, run the following command:

Code: Select all

Check pdb page for the commands, few of them quickly:

• n: Next line of code

• s: Step inside code

• c: continue to next breakpoint.

• w: shows a traceback around the current line of code.

Open Ableton In Terminal 6

Hopefully this helped someone.

Open Ableton In Terminal 7

Iacopo