To me, that's the most negative aspect of all this data being generated- clutter that interferes with working efficiently. It's nice to know there's a workaround.
]]>Chris
]]>Chris
]]>Just a reminder that half-pedalling is not the same as continuous damper controls.
Glenn
I stand reminded! I did, of course, mean continuous damping.
Irritatingly, Garageband, which I play Pianoteq through, responds to and records continuous damping, but shows it as an on/off switch, which means it can't be examined or edited.
]]>Michael H wrote:I haven't tried a continuous damper pedal on my netbook yet- it would probably spontaneously combust
try polyphonic aftertouch: OUCH!
Whoa! I expect that would be 'the straw that broke the camel's back'..
]]>I haven't tried a continuous damper pedal on my netbook yet- it would probably spontaneously combust
try polyphonic aftertouch: OUCH!
]]>Michael:
Your original point about cluttering up the midi stream is very valid. As I said, I usually have more Pedal Control values than notes/music.
Surely our computers have to read all the values, and there must be instances where the midi stream gets "choked". The complexity of Pianoteq has risen considerably since I started using it, and the computations required must be mind boggling.
Glenn
Hi Glenn,
Yeah, I think the amount of midi data is unfortunate, although how else they'd do it is beyond me. Since this data is so small I think modern computers can handle it just fine ~most of the time~, but my VMK188plus keyboard is extremely unreliable when continuous pedal info is sent through it- and then there's the annoyance factor during the editing of notes. I guess we're stuck with this.
]]>Surely our computers have to read all the values, and there must be instances where the midi stream gets "choked". The complexity of Pianoteq has risen considerably since I started using it, and the computations required must be mind boggling.
Glenn
Boggles my mind.
On avoiding choke, I find that I prefer a relatively short throw from 0 to 127 near the bottom of my pedal's travel; that seems closest to how it works on a real piano.
Sustain Velocity = [0, 10, 48, 125, 126, 127; 0, 0, 127, 127, 127, 127]
and it has the advantage that, although the MIDI stream won't change, Pianoteq won't need to adjust for most input values.
]]>Your original point about cluttering up the midi stream is very valid. As I said, I usually have more Pedal Control values than notes/music.
Surely our computers have to read all the values, and there must be instances where the midi stream gets "choked". The complexity of Pianoteq has risen considerably since I started using it, and the computations required must be mind boggling.
Glenn
]]>And I suppose, depending on your sequencer, you might be able to filter out specific controller messages during editing, that would make things much easier visually.
Cheers,
Michael
A midi file with half-pedalling has values of zero, 64, and 127.
A full range pedal generates all the values from zero to 127.
In my midi editor/sequencer, there is a window called the Event List. This is a screen shot of the Event List for one of my midi files:
http://www.box.net/shared/y4e9r1c9gl
The red numbers are the Pedal Control values, the blue ones are the notes.
In this particular file, there are as many Pedal Control values as there are notes.
Which is the point that Michael was making I believe.
Glenn
]]>