13
0
livetrax/libs/midi++2
David Robillard 08fffeffec 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.
2016-12-03 15:18:21 -05:00
..
macosx
midi++ Remove Evoral::MIDIEvent 2016-12-03 15:18:21 -05:00
MSVCmidi++
test
channel.cc more corrections for libmidi++ (N)RPN API 2015-11-23 12:27:51 -05:00
COPYING
ipmidi_port.cc add explanatory comment regarding IP_MULTICAST_LOOP, remove cout debug msg 2016-01-18 18:36:11 -05:00
libmidi++.pc.in
libmidi++.spec.in
midi.cc
miditrace.cc
midnam_patch.cc Remove Evoral::MIDIEvent 2016-12-03 15:18:21 -05:00
mmc.cc
mmctest.cc
mtc.cc
parser.cc Spelling correction patch from Debian 2016-02-22 15:13:01 -05:00
port.cc
run-tests.sh netbsd: Fix unportable shell construct 2015-12-03 12:19:34 +01:00
wscript