Some keyboard commands stop responding...

UHE is now closed. For Technical Support from Ableton, please go here: http://www.ableton.com/support
Locked
krushing
Posts: 70
Joined: Fri Jul 23, 2004 7:58 am
Location: Helsinki / Finland
Contact:

Some keyboard commands stop responding...

Post by krushing » Wed Sep 01, 2004 6:07 pm

Hi,

I'm having a seemingly random problem with Live 4.0.1. After a while of doing stuff, at least the space bar (toggle play/stop) and tab (toggle views) sometimes simply cease to work anymore, and I haven't gotten around this any other way than restarting Live. Some commands still work, but I didn't do a thorough test with which keys work and which don't.

I could understand this if there was a lot of load on the CPU, but in this case the meter was around 35% or so. Bug? My stupidity? Something else?

krushing
Posts: 70
Joined: Fri Jul 23, 2004 7:58 am
Location: Helsinki / Finland
Contact:

Post by krushing » Wed Sep 01, 2004 7:20 pm

Ok, I (think) I found the problem - rgc:Audio's z3ta+ seems to be the culprit. I was able to replicate the problem by simply inserting one z3ta+ on a MIDI track, opening it's own interface and then closing it - blam. All keyboard action stops there, and all the functions have to be accessed via mouse & menus.

anti-banausic
Posts: 1609
Joined: Fri Jun 11, 2004 9:15 pm
Location: NYC

Post by anti-banausic » Wed Sep 01, 2004 7:31 pm

You might also check to see if you have the computer keyboard set up as your MIDI input device...I have found that when this is the case (and especially when opening a saved set), that you will not be able to use the keyboard for anything but MIDI.....So go into preferences and disable it as your MIDI device...

Hope this helps.
AB
Macbook c2d 2.0, 2G RAM, 160G HD 5400 RPM, OSX(10.5.5), XP Home, LIVE6, BCR 2000, UC33e, Yamaha P-200, Logic Studio, KRK V6 II

krushing
Posts: 70
Joined: Fri Jul 23, 2004 7:58 am
Location: Helsinki / Finland
Contact:

Post by krushing » Thu Sep 02, 2004 9:58 pm

That's good to remember, thanks. However in this case it was clearly the plugin (z3ta+) causing the problem...as others have reported the same problem happening, I'm pretty sure who's to blame here :)

Locked