Audio drop-outs with more than 2 midi-remote-outs active

UHE is now closed. For Technical Support from Ableton, please go here: http://www.ableton.com/support
Locked
Nicken
Posts: 18
Joined: Mon May 11, 2009 7:08 pm
Location: Leipzig, Germany
Contact:

Audio drop-outs with more than 2 midi-remote-outs active

Post by Nicken » Sat Sep 12, 2009 4:57 pm

Hello.

I thought i found my perferct looping setup, but then encountered audio drop-outs when doing usual tasks. (such as selecting tracks and devices). even when cpu-load is under 10%.
I searched a lot and now found the problem. it occurs, when I have more than 1 midi-remote-output active. Pretty strange in my opinion.
I read, that people had similar problems, but hadn't boiled it down to that reason yet. Don't know really what to do now.
Is this a topic that is worked on over at Ableton?

My setup:

Nocturn (with Automap Server: this is one Midi-Out)
Padkontrol (with farmpad: the other Midi_Out)
MacbookPro 2,5 Ghz, 4 GB ram,
Live 8.04
Bomes MT running

5 tracks with one Looper each
3 tracks with one instrument rack each
routings...

i know that's a lot of stuff.
just for the sake of it i changed the midi-output of my nocturn control surface to an IAC-bus and monitored 343 (sic) midicontrol changes being sent right in that moment i select another device. regarding this mass of data i can understand why i have dropouts. the question is how to avoid it? ;)

anyone else having these problems?

thanks for your help,
nicken

Nicken
Posts: 18
Joined: Mon May 11, 2009 7:08 pm
Location: Leipzig, Germany
Contact:

Re: Audio drop-outs with more than 2 midi-remote-outs active

Post by Nicken » Thu Sep 24, 2009 8:22 am

Okay, the problem went away as I took out the self-hacked Stepsequencer out of the equation.

It is this one:

http://forum.ableton.com/viewtopic.php? ... psequencer

made with farmpad and the padkontrol. seems like the massive amount of midi-assignments does not go along with multiple midi-outs.
now you know :)

Locked