Thread with 12 posts
jump to expanded postwell you see, a โpianoโ has 1 polyphonic channel with 88-note range, velocity, and 3 controllers, whereas a โguitarโ has 6 monophonic channels each with its own circa 24-note range (staggered and overlapping), velocity, pitch bend, polyphonic aftertouch, and uhhh many controllers
oops i meant channel aftertouch, polyphonic aftertouch is meaningless in this context
but you know what has 16 polyphonic channels with 128-note range, velocity, pitch bend, channel aftertouch, five controllers, and 128 different programs?
that's right: a General MIDI System Level 1 compliant tone generator.
but this is a shitpost, this is unfair to guitars
i think part of my wonder at the guitar is it is just impossible to model as a midi instrument. i mean, you can try. midi guitar controller systems exist. midi guitar synthesisers exist. but every single one is but a shadow of a real guitar, the inescapably physical instrument
hell, even a piano can only be modelled by midi by assuming you play it โcorrectlyโ. if you open the lid and directly play with the strings, that's considered cheating or something
@hikari MIDI is more about digitally recreating a score, rather than a performance, I feel. There are a lot of subtleties when it comes to playing an instrument, any instrument, which are not really part of the composition, but are important during performance.
That said, the piano played in a normal way must be one of the least expressive mainstream instruments we have. And therefore also one of the easier ones to model in software.
@Tijn unfortunately i can't agree with this, MIDI is a radically different thing from sheet music and has always been designed and used to capture and reproduce performances, not to replace scores; it is fundamentally unsuited to the latter
@Tijn what is colloquially called a โMIDI fileโ has many names, a notable one that occurs again and again โMIDI performance dataโ
@hikari I get what you mean, but don't you agree that when it comes to what data MIDI records, it's more in line with what's in a score than what is going on between the player and the instrument?
Like, when a violinist plays a piece, the score just says which notes to play in what tempo, at what volume. MIDI does offer a bit more possible parameters, as do scores btw, but it remains a very coarse description of what's it actually like to play the piece.
@hikari What a violinist is concerned with is the angle of the bow, how tight the grip is, how much pressure is applied with the left hand, etc. Tons and tons of details and subtleties that the performer is conscious of and are crucial to how the end result sounds, none of which are typically part of a MIDI file or a score.
@Tijn MIDI data for a synthesiser would precisely recreate every detail of a performance. this is also the case for MIDI data from a player piano.
for a violin, well, a sufficiently advanced performance capture system ought to capture the details you describe. it's just hard
@Tijn even in the simplest case a MIDI file is still a performance and not a score. timing and expression are conveyed precisely, there is no room for interpretation. trying to turn a score into a MIDI performance requires interpretation, as does the reverse. now, you can make a very spartan and uninspiring MIDI for a beautiful idea, but that also exists for audio recordings, we call those sketches or demos