I use a simple, solid setup that has never had any real troubles...
G3 iBook 700mhz 640MB OS 10.2.8
Edirol PCR-A30 usb audio/midi interface
OWC Mercury Elite 120GB firewire hard drive
Live 4
This is not regarding recording or sequencing, and it is not a latency issue.
With NO quantization activated, I should be able to trigger/play a short, percussive audio clip freely.....fast successions of notes, like sixteenths.....and indeed I can do this easily from my midi keyboard. But if I play the SAME clip from either my mouse or my computer keyboard, there seems to be something preventing me from playing anything faster than, say, eighth notes.
The sounds don't respond as I play them. If I play ten quick notes, any fast rhythm my hand happens to play, all ten come out in succession, but more slowly, as straight eighth notes, finishing after I've already stopped playing.
If I open the SAME clip with the SAME settings in Live 3, this problem does not occur.
Actually, it happens even from just playing the sounds of, say, a drumkit in the Impulse instrument........no clips, no set, no looping, no recording, no quantization. Just playing the sounds.
Again, my midi keyboard does fine, perfectly triggering quick successions of fast notes as I play them.....
But when I play from either my mouse or my computer keyboard, I am not able to trigger the notes freely..........as if there is some kind of quantization enabled.
Any suggestions?
Ableton support says they can't help because they can't find a problem.
But there is a problem, and on my system, it doesn't occur in Live 3?
Has anyone experienced this?
Triggering issue with mouse/computer keyboard
I see now that on the second page of these topics, some other people with varying iBooks are having the same problem........triggering sounds from the Impulse instrument with the computer keyboard.
Well it's not only with Impulse, but with triggering any clip in general.
AND THIS PROBLEM DOES NOT OCCUR IN LIVE 3.
Again, Ableton support told me they can't help. They don't see a problem.
I like Ableton, and I appreciate their timely responses to my first emails,
but just dropping the issue like that doesn't seem like very good business. I hope that someone there is looking into the problem.
Any suggestions, anyone?
Well it's not only with Impulse, but with triggering any clip in general.
AND THIS PROBLEM DOES NOT OCCUR IN LIVE 3.
Again, Ableton support told me they can't help. They don't see a problem.
I like Ableton, and I appreciate their timely responses to my first emails,
but just dropping the issue like that doesn't seem like very good business. I hope that someone there is looking into the problem.
Any suggestions, anyone?