LIve4: sustain MIDI ctrl info causes endless sustain...
LIve4: sustain MIDI ctrl info causes endless sustain...
I am on WindowsXPsp2 using Live 4.0.1. When I record a clip which contains sustain CC info and I stop the whole track or the clip on a spot where the pedal is pressed, the sustain keeps on running endlessly. Should be a simple fix since all stop actions should at least 'push' a sustain off message.
Try it with Simpler and you will understand what I mean.
Try it with Simpler and you will understand what I mean.
Yes Yes Yes you are right,
This has been driving me mad for a week or so. So much so that I exported all my files into Sonar to finish the song. I posted on a different thread reguarding stuck notes. Yet, you said it perfectly! I can stop the notes most of the time if I just push my sustain pedal. What is funny is that I had a person I was producing a song for keep the pedal in her lap and she would push it for me every time I would push stop mid clip
Good call!!
Lance
This has been driving me mad for a week or so. So much so that I exported all my files into Sonar to finish the song. I posted on a different thread reguarding stuck notes. Yet, you said it perfectly! I can stop the notes most of the time if I just push my sustain pedal. What is funny is that I had a person I was producing a song for keep the pedal in her lap and she would push it for me every time I would push stop mid clip
Good call!!
Lance
..
I think in Cubase or Nuendo you have something like stop-all notes on stop. it should be a simple fix for Ableton I think, they just need to send sustain-off cc on all channels when the song is stopped.
Hi all,
thanks for pointing us to this problem. We will take care of this for one of the next updatereleases.
Best,
thanks for pointing us to this problem. We will take care of this for one of the next updatereleases.
Best,
eduard mueller
[email protected]
[email protected]
[/quote]_pascal_ wrote:Hi Eduard,thanks for pointing us to this problem. We will take care of this for one of the next updatereleases.
just bought my copy of live 6, but experienced this problem. Is this fixed or not ?
Regards,
Pascal.
6.0.1 here. Sustain problem exist.
- Best
- Pasha
Mac Studio M1
Live 12 Suite,Zebra ,Valhalla Plugins, MIDI Guitar (2+3),Guitar, Bass, VG99, GP10, JV1010 and some controllers
______________________________________
Music : http://alonetone.com/pasha
Live 12 Suite,Zebra ,Valhalla Plugins, MIDI Guitar (2+3),Guitar, Bass, VG99, GP10, JV1010 and some controllers
______________________________________
Music : http://alonetone.com/pasha
maybe the same bug?
Check this out.
- set up loop punch-in and punch-outs
- enable midi track
- record sequence (with or without sustain events)
- add new midi track
- disable old track and enable new track
- record new sequence with sustain events
I've found that sustain events on track 2 affect sustain on track 1 as well. Has anybody else seen this? Maybe I am doing something wrong?
found this in Live 6.0.1 (demo). I haven't bought Live yet, but as I plan to be doing a bunch of looping of concurrent midi sequences, this might make or break it for me.
- set up loop punch-in and punch-outs
- enable midi track
- record sequence (with or without sustain events)
- add new midi track
- disable old track and enable new track
- record new sequence with sustain events
I've found that sustain events on track 2 affect sustain on track 1 as well. Has anybody else seen this? Maybe I am doing something wrong?
found this in Live 6.0.1 (demo). I haven't bought Live yet, but as I plan to be doing a bunch of looping of concurrent midi sequences, this might make or break it for me.
Yes, I have been having multiple sustain related issues as well:
1. Sustain recorded during a take sometimes doesn't play back correctly. In other words, the notes don't sustain even though the sustain message was recorded.
2. Sustain gets confused. In other words, sometimes I have to hit the sustain pedal to unstick the sustain, either stuck on or stuck off.
3. Playing live on a piano, for example, while other recorded tracks are playing, and hitting the sustain on the piano track sometimes screws up sustain on the other, already recorded, tracks.
I love Live and gave up Reason 3 to focus exclusively on using Live, but the more I find issues with this software, the more frustrated I become. I don't recall having this many issues while participating in the BETA program.
1. Sustain recorded during a take sometimes doesn't play back correctly. In other words, the notes don't sustain even though the sustain message was recorded.
2. Sustain gets confused. In other words, sometimes I have to hit the sustain pedal to unstick the sustain, either stuck on or stuck off.
3. Playing live on a piano, for example, while other recorded tracks are playing, and hitting the sustain on the piano track sometimes screws up sustain on the other, already recorded, tracks.
I love Live and gave up Reason 3 to focus exclusively on using Live, but the more I find issues with this software, the more frustrated I become. I don't recall having this many issues while participating in the BETA program.
Mac OSX Leopard on Mac Pro Quad Core 2.66 with 3 GB RAM
Live 7.0.1
Live 7.0.1
I could be wrong, but here is what i found :
When you hit the stop button, Live send the Midi CC #123 (All NOTES off). This MIDI message cuts the notes of some Vsti's even if the CC #64 (hold pedal) is on 127.
But on other instruments (like my hardwares synth, operator as well), CC#123 doesn't stop the sound at all if the CC#64 is on.
There is another MIDI CC (CC#120 : all SOUND off) that cuts ALL sounds.
I mean Live should send CC#123 AND CC#120 when you hit stop button.
When you hit the stop button, Live send the Midi CC #123 (All NOTES off). This MIDI message cuts the notes of some Vsti's even if the CC #64 (hold pedal) is on 127.
But on other instruments (like my hardwares synth, operator as well), CC#123 doesn't stop the sound at all if the CC#64 is on.
There is another MIDI CC (CC#120 : all SOUND off) that cuts ALL sounds.
I mean Live should send CC#123 AND CC#120 when you hit stop button.