Page 1 of 1

strange control surface problem

Posted: Thu Nov 03, 2011 9:09 pm
by shig
Okay this is a weird one.. about an hour and a half ago everything was working fine and now not only is my control surface (m-audio keyreg 25) playing up in Ableton, but the setting to use your laptop keyboard as a controls surface is acting up as well?

Basically if I hit a note on the MIDI keyboard, it sends the signal to Ableton (I can see the yellow icon in the top right flashing) but it doesn't do anything at all, but the knobs still work? and if I try to use the laptop keyboard as my surface, say if I push the 'A' button to get whatever note, and I push it 10 times, it will only actually play the note maybe one or two times out of those ten. and if it does play the note, if I take my finger off the key the note continues until I play the whole track and stop it again. what the feck is this about? It's making synth programming extremely irritating. I've never encountered this problem before. Any ideas?

Re: strange control surface problem

Posted: Thu Nov 03, 2011 9:26 pm
by shig
it's now playing random notes without me even touching it. I think my keyboard is haunted :|

Re: strange control surface problem

Posted: Thu Nov 03, 2011 9:45 pm
by oWLinDaylight
Whats the cpu and memory usage at while this is going on?

Re: strange control surface problem

Posted: Thu Nov 03, 2011 9:49 pm
by shig
never seen it jump above 45%. the keyboard works fine in reason, so I know it's something to do with ableton. I just re-installed and it's still doing it, so it could be some disagreement between the keyboard and ableton, which then tricks it out for the laptop keyboard as well.

Re: strange control surface problem

Posted: Thu Nov 03, 2011 9:55 pm
by oWLinDaylight
It sort of sounds like a lot of MIDI packets are being dropped or delayed from a bottle neck. I've had ableton will pick up the key on message but then the key off message gets dropped so the note will stick on. And then the random notes could be midi notes that were stuck in a bottle neck and came through late. I dont know what in ableton would cause that though. Did you check the memory usage as well as the cpu meter. Sometimes the cpu can be fine when the memory is maxed out which could cause something like this.