NASTY MIDI LOOP IN LIVE

Discuss music production with Ableton Live.
Post Reply
Farr
Posts: 14
Joined: Wed Jan 26, 2005 10:20 pm
Contact:

NASTY MIDI LOOP IN LIVE

Post by Farr » Sat Jan 28, 2006 1:32 pm

Hi all

Has anyone experienced problems with unwanted MIDI loop in Live?

Any suggestions to avoid it.

Thanks in advance.
Farr
iBook 1GHz, 40 Gig HD, 768MB RAM, M-AUDIO Firewire 410, Remote25, Trigger Finger, Live 4, Rickenbacker 330, 1962 VOX AC-30.

sqook
Posts: 2430
Joined: Mon Oct 04, 2004 8:14 pm
Location: Sweden
Contact:

Post by sqook » Sat Jan 28, 2006 1:36 pm

Care to be a bit more specific?

hacktheplanet
Posts: 2846
Joined: Sat Sep 25, 2004 6:37 am
Location: Chicago, IL
Contact:

Post by hacktheplanet » Sat Jan 28, 2006 2:12 pm

Aah, those nasty MIDI loops. I get those from time to time, but I usually just hit "stop" and delete the loop.

:P

If you're talking about feedback loops, you just have to be careful. I've created a few audio feedback loops since I've been working with music, and they really suck. Now I'm ultra-paranoid about it.
I guess it just takes practice to get in the habit of double checking everything.
Image

sqook
Posts: 2430
Joined: Mon Oct 04, 2004 8:14 pm
Location: Sweden
Contact:

Post by sqook » Sat Jan 28, 2006 2:13 pm

How on earth would you get feedback from a midi loop?

hacktheplanet
Posts: 2846
Joined: Sat Sep 25, 2004 6:37 am
Location: Chicago, IL
Contact:

Post by hacktheplanet » Sat Jan 28, 2006 2:26 pm

sqook wrote:How on earth would you get feedback from a midi loop?
It's not like really bad audio feedback, it's just MIDI feedback... So it does weird things, like double the signal, or other things depending on the patch.

I haven't done this with VST's though, cos they go straight to audio. Only with hardware. You set it to retransmit MIDI data on the same channel it's receiving the data on.
Image

Farr
Posts: 14
Joined: Wed Jan 26, 2005 10:20 pm
Contact:

Post by Farr » Sat Jan 28, 2006 2:48 pm

Sorry for the vague terminology - yes 'feedback' loop is what I'm talking about.

So basically the problem is in the MIDI file itself, and not the software or hardware?
Farr
iBook 1GHz, 40 Gig HD, 768MB RAM, M-AUDIO Firewire 410, Remote25, Trigger Finger, Live 4, Rickenbacker 330, 1962 VOX AC-30.

ILTK
Posts: 800
Joined: Fri Dec 02, 2005 6:41 pm
Location: Denmark, land of the awesome

Post by ILTK » Sat Jan 28, 2006 3:30 pm

If I understand this correctly, all you need to do is turn local control on your hardware synth off.

hacktheplanet
Posts: 2846
Joined: Sat Sep 25, 2004 6:37 am
Location: Chicago, IL
Contact:

Post by hacktheplanet » Sun Jan 29, 2006 1:24 am

Switching local control off will just disable the synth from being played by the user, not by the MIDI control.
What are the settings in the MIDI channels? Also, what are your settings in the routing setup (i think) in Live preferences?
Image

mr-e
Posts: 344
Joined: Thu Dec 30, 2004 7:43 am

Post by mr-e » Sun Jan 29, 2006 10:25 am

always select the proper input on each miditrack instead of using 'all' , so you don't record your synths automation/notes on another miditrack while jamming

Needs2Know
Posts: 111
Joined: Tue Jul 12, 2005 11:16 pm
Contact:

Post by Needs2Know » Sun Jan 29, 2006 8:02 pm

Just a thought from a new guy but I was reading from MOTU that some midi interfaces dont single out other midi channels very well so some of the signal goes into an unwanted channel you might be recording on at the same time. Consult your midi controllers manual but I think they referred to it as "timestamping." Hence the name of the midi interface I bought:MOTU's "timepeice".

Post Reply