IAC issues with Live 7

metajack · Post by **metajack** » Tue Dec 11, 2007 6:17 am

I set up an IAC port to send MIDI from Puredata to Live. Everything works fine in live until I send a midi note to Live from Puredata. After that happens, live stops accepting midi input from everywhere. Ie, computer keyboard input works fine when the midi input of the track is set to All Inputs/All Channels. After the first midi note from puredata, keyboard input only works if it is specifically selected. The IAC input causes the midi traffic light to flash, but Live never plays any notes, even if the input is specifically selected in the track.

Any ideas?

kleine · Post by **kleine** » Tue Dec 11, 2007 1:56 pm

Hello,

I can´t reproduce this here. (Midi notes from Max via IAC to Live 7.01).

Best,
Christian
[email protected]

metajack · Post by **metajack** » Tue Dec 11, 2007 3:22 pm

This is very strange. If I close live and open Reason 3, set Reason's Bus A to the IAC port, everything works fine. Reason starts making sounds from the midi notes in Puredata. Close reason, open Live, I get nothing.

Even stranger is that if I go into MIDI map mode and click on the power button of Analog or Electric or whatever, it will map it to the note on that I'm sending from Puredata. It's just that live cannot see these in the tracks.

posssu · Post by **posssu** » Wed Dec 12, 2007 5:23 pm

Hey!

I have the same problem. It doesn't include Puredata, but the result is the same.

I don't know what causes Live to change like this.. I'm using Overture 4 to send midi data to Live 7 through an IAC bus. It works well, but then after some while when I come back to using those programs (I keep them open at the background), I Live suddenly doesn't receive anything anymore.

I can see the indicator blink, but it doesn't reach Live's tracks. Only reboot fixes it. But everything works fine with Live 6.

Christian, I'll send you my log file asap, but my laptop got broken few days ago, so I'll send it when I get it fixed.

metajack · Post by **metajack** » Wed Dec 12, 2007 5:25 pm

I can confirm that a reboot made it suddenly work for me as well. So at least there is a work around. I'm on OS X 10.5 if that helps.