New build replicator td ableton loop

@Ivan @drmbt

i upgraded to the new build (31760) and something that was working in my previous build (12000) stopped working.

I have a replicator tied to a td ableton component, and when i try to use it now, it gets stuck in a loop and my fps goes down to 2.

i isolated just the necessary components, and made 2 files, one in the 12000 build that still works, and one in the 31760 build that breaks. this forum format won’t allow me to upload ableton sessions, so here is a dropbox link to that small folder as well.

thank you!!

31760 CLIP SLOT.toe (541.4 KB)

12000 CLIP SLOT.toe (417.1 KB)

Looking. FWIW, you can attach zip files in the forum.

So, the toe file is looking for tracks that don’t exist in the dropbox set… they are called pb, top, sampler+looper.

If you could do a couple things, I can be more helpful…

  1. make sure the toe and als work together, obv. Not sure what happened.

  2. reduce the toe and the als to just what is needed to reproduce the error

  3. give step by step instructions for what to look for and where to look. (e.g. where is your replicator)

thank you for info on the zip, and my apologies on one of the toe files. i’m attaching updated version here. the 12000 version was good on my end, and the 31760 i included a useless comp, that i have now deleted:

31760 CLIP SLOT v3.toe (432.7 KB)

so once you load project, dive into clip_controlSlot

there will be a replicator and 15 replicants of an abletonClipSlot comp. also two tables, the one on the right is called table_controlSlot

currently the replicator is not cooking, but if you press the x to make it cook, your fps should drop almost immediately to 2.

what it’s supposed to do (12000) build: each replicant monitors one of the tracks in ableton. when a clip is selected, the abletonClipSlot replicant will select the proper clip in the dropdown menu, so that it can send the label of that menu item, along with clip color properties, to the table on the right, called table_controlSlot

please let me know if you need more info, thank you!!

Ok, interesting bug. Turns out it is not safe to rename replicated nodes. If you redesign your component so that the replicant names remain the same, it should work fine.

We are working on a more general solution, but that should get you going for now.

ok thank you!!