From 08fffeffec10beb708610fd35eb9e7c35365d446 Mon Sep 17 00:00:00 2001 From: David Robillard Date: Sun, 6 Nov 2016 22:04:35 -0500 Subject: 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. --- libs/ardour/audio_unit.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'libs/ardour/audio_unit.cc') diff --git a/libs/ardour/audio_unit.cc b/libs/ardour/audio_unit.cc index 95a66800c8..4bc8cdaf3b 100644 --- a/libs/ardour/audio_unit.cc +++ b/libs/ardour/audio_unit.cc @@ -1686,7 +1686,7 @@ AUPlugin::connect_and_run (BufferSet& bufs, /* one MIDI port/buffer only */ MidiBuffer& m = bufs.get_midi (i); for (MidiBuffer::iterator i = m.begin(); i != m.end(); ++i) { - Evoral::MIDIEvent ev (*i); + Evoral::Event ev (*i); if (ev.is_channel_event()) { const uint8_t* b = ev.buffer(); DEBUG_TRACE (DEBUG::AudioUnits, string_compose ("%1: MIDI event %2\n", name(), ev)); -- cgit v1.2.3