Ableton Forum

hello,
this behaviour is reproducible, for me, live 6.0.3, os x 10.4.8, dual 800Mhz g4ppc, 2MB L3 cache per processor, 768 MB SDRAM, sndcard=built in audio.

1. load sample into single audio slot in audio track in session.
2. select region, crop sample.
3. drag clip to browser (save it)
4. drag same clip to audio track.
5. open midimap editor
6. set clip launch to a midi note on (in my case, a single supercollider3 statement, MIDIOut.noteOn(chan, num, vel))
7. exit midi map editor
8. set clip to warp->loop
9. play the clip by triggering the midi note over IAC bus 1
10. when the clip is at it's end, and starts to loop, there is very bad anomaly, sometimes looping the sample start (say, 0.75 bars), or just then sample distortion, like playing extremely small amount of samples. the live processor usage on Activity Monitor shoots past 100%, then the sample plays, then when you get to the loop point again, the same thing happens. only happens when a midi note is set to launch the clip, and the clip is looping. i've just clearedthe decoding cache/Live Recordings flder (10GB btw), restarted live, and the behaviour persists. i guess that this doesn't happen to anyone but can anyone please offer any ideas, ..

this behaviourr isn't exhibited in live 5.2.2, btw, exact same setup (execpt the sample isn't cropped - can I do that in live 5??).

Hi Leonard,

I was able to reproduce this. You probably have a MIDI feedback loop with IAC (you can see this when opening the Console system.log):
Your IAC In and Out have Remote enabled. When you trigger the MIDI-mapped clip, Live sends a Note out to IAC, and simultaneously receiving the Remote Note, creating a loop.

For now please disable "Remote" in the Output IAC Bus in Live Preferences:MIDI

This behavior seems independant from the cropping and the other described steps.

If you use IAC to create dummy automation clips, the settings in Live 6 should look like this to avoid a feedback loop:

Input IAC: Track OFF Sync OFF Remote ON
Output IAC: Track ON Sync OFF Remote OFF


Daniel

thanks for your reply daniel, i shall try this this afternoon when I get home.

hi daniel, that seems to fix it. i turned all the other midi channels for the other devices off also, it seemed to not like it (i.e. the same behaviour).

FIANLLY!!!

a solution to this problem!

so you say disable remote "for now". will i ever need to turn it back on?

i'm just wondering, with remote out disabled, will we not be able to receive feedback from mapped parameters over IAC? reading the manual, it would seem as though we can't. i may be wrong, and ia m not in a position to try at the moment, but maybe there is a way to receive from IAC bus 1 and send via IAC bus 2 (this is for audio tracks mapped directly, I know we can specify send/receive busses over midi tracks). any ideas? abes??

Use a midi track to route IAC 1 to IAC 2.
Everything will be hardwired to channel 1 though.

i thought about using a extra midi track a a 'proxy' of sorts, but i wanted to keep the track count down though as my old computer just isn't up to the task of having a midi track for each audio track which is what i guess i'll need. i guess i'll have to for the time being thogh. also, my live 5 has exactly the same midi configuration as 6 had (i.e. IAC Bus 1 output=on/on/on, inpute=on/on/on), but it functions normally, so I guess i is a problem with six and if it is i really hope they get it sorted in the next bugfix.