diff options
author | David Robillard <d@drobilla.net> | 2016-11-06 22:04:35 -0500 |
---|---|---|
committer | David Robillard <d@drobilla.net> | 2016-12-03 15:18:21 -0500 |
commit | 08fffeffec10beb708610fd35eb9e7c35365d446 (patch) | |
tree | ce9c8c77e6a926b4d8be90052c32945b7718bb4b /libs/ardour/midi_track.cc | |
parent | 875b1367b2c4750ecd861424c57ed4bcc9c642d2 (diff) |
Remove Evoral::MIDIEvent
It is slightly questionable whether type specific methods like
velocity() belong on Event at all, these may be better off as free
functions. However the code currently uses them as methods in many
places, and it seems like a step in the right direction, since, for
example, we might some day have events that have a velocity but aren't
stored as MIDI messages (e.g. if Ardour uses an internal musical model
that is more expressive).
In any case, the former inheritance and plethora of sloppy casts is
definitely not the right thing.
Diffstat (limited to 'libs/ardour/midi_track.cc')
-rw-r--r-- | libs/ardour/midi_track.cc | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/libs/ardour/midi_track.cc b/libs/ardour/midi_track.cc index f1344e7697..69291f1cce 100644 --- a/libs/ardour/midi_track.cc +++ b/libs/ardour/midi_track.cc @@ -339,7 +339,7 @@ MidiTrack::update_controls(const BufferSet& bufs) { const MidiBuffer& buf = bufs.get_midi(0); for (MidiBuffer::const_iterator e = buf.begin(); e != buf.end(); ++e) { - const Evoral::MIDIEvent<framepos_t>& ev = *e; + const Evoral::Event<framepos_t>& ev = *e; const Evoral::Parameter param = midi_parameter(ev.buffer(), ev.size()); const boost::shared_ptr<Evoral::Control> control = this->control(param); if (control) { @@ -549,7 +549,7 @@ MidiTrack::push_midi_input_to_step_edit_ringbuffer (framecnt_t nframes) for (MidiBuffer::const_iterator e = mb->begin(); e != mb->end(); ++e) { - const Evoral::MIDIEvent<framepos_t> ev(*e, false); + const Evoral::Event<framepos_t> ev(*e, false); /* note on, since for step edit, note length is determined elsewhere |