Problems with MIDI Sustain Pedal while recording

[jeremyroberts]

I have no such issues.

PT 8.0.1cs2
HD2
MIDI I/O
OS 10.5.8
PPC

plugins include Ivory, VSL, VEPRO and many, many VIs

Yes, I get annoyed when punching in piano pats with sustain pedal -- but that's the nature of the beast. It's either on or off. So we work around it. BUT NEVER experienced the other behaviors. I would guess there is something unique to your config that is causing this.

[jeremyroberts]

PS -- there are situations that may cause the sustain to turn itself off. Such as REC ENABLING a track while the transport is rolling.

Is this what you are referring to?

[Steve@ZooWest]

For me, it is rarely an issue when I have a session using only Ivory - but it has happened. Generally it's more of an issue when there are more virtual instruments happening. The sustain pedal info is recorded though and seems to be fine on playback.

At times I had thought my sustain pedal was dying. (I always love it when I'm doing an orchestra date in the studio or playing live and the sustain pedal actually does cease to work).

Mac OSX 10.5.4
PT 7.4.2

[ChrisSimon]

It really has nothing to do with one special virtual instrument...cause it also appears on Hardware Synths....

Yeah, I thought about my sustain pedal, too, but no... While playing along, everything´s fine, just at the recording.... The sustain events are also recorded fine, but MIDI Thru seems to cut off sustain pedal "ons" sometimes...

I have the impression, the more you play, the higher the tempo, the more you get this bugs...

And it´s not just me... The forum is full of guys, complaining about it...

[Sean Halley]

I used to see this all the time when I ran a G5 on Tiger and Leopard.

It went away when I switched to a big new Nehalem Macpro a few months ago. I think it may be linked to cpu-managed USB overhead...

S..

[ChrisSimon]

...hmmm, I think I got something...

When I deactivate "MIDI Merge", the problem disappears...no sustain problems - like it looks now...please check it out.... so we could Avid a feedback... but it looks as this is the problem here...

[tonwurm]

Originally Posted by ChrisSimon

...hmmm, I think I got something...

When I deactivate "MIDI Merge", the problem disappears...no sustain problems - like it looks now...please check it out.... so we could Avid a feedback... but it looks as this is the problem here...

very interesting...

I´ll try that and report back later


thanks

[Hanswurstlsepp]

Originally Posted by ChrisSimon

...hmmm, I think I got something...

When I deactivate "MIDI Merge", the problem disappears...no sustain problems - like it looks now...please check it out.... so we could Avid a feedback... but it looks as this is the problem here...

Will do so, too and report.

[tonwurm]

Originally Posted by ChrisSimon

...hmmm, I think I got something...

When I deactivate "MIDI Merge", the problem disappears...no sustain problems - like it looks now...please check it out.... so we could Avid a feedback... but it looks as this is the problem here...

confirmed ... same here

very good to know, thanks simon !!! since there´ll never be any updates for ppc users - it´s a workaround I can live with

[jeremyroberts]

Originally Posted by ChrisSimon

When I deactivate "MIDI Merge", the problem disappears.

And since I work almost exclusively with midimerge disabled, I have never experienced this.

I only use midimerge mode when actually doing something that requires the function, such as a true merged overdub, or adding keyswitches or controller data. Then [9] right away.

IS IT REMOTELY POSSIBLE that a track you were recording had a #64 on at some point, and since you wee in [9] mode, the new #64 on was zapped by the old #64 off? Is there the slightest remote possibility of an operator error?

Considering that I have NEVER EVER experienced this, even when [9] is enabled, the fact that others had [9] enabled by default leads me to the possibility that a #64 off could have ben in the track, and since [9] mode doesn't overwrite, you get what you get.

Just thinking out loud, since random midi events simply make no logical sense.