Re: Midi entry

[Mojca Miklavec]

On 26 July 2016 at 17:01, Richard Shann wrote:
> On Tue, 2016-07-26 at 15:45 +0200, Mojca Miklavec wrote:
>
> I think the first track is just being used to vary the tempo. Whether
> that is because it originated in a human performance (it would be a
> sophisticated program that generated this in that case)

Yes, I agree :)
I suspect computers ...

> or some sort of
> human-modified MIDI performance (you could easily "conduct" a MIDI
> performance causing the tempo to vary throughout and record the modified
> MIDI by adding a track with the tempo changes that you conducted).
>
>> In any case, I got reasonable output for at least some midi files with
>>
>>     midi2ly -a --duration-quant=16 --key=-1 --start-quant=16 file.midi
>
> Interestingly, Denemo creates reasonable output straight out of the box
> - in many ways a measure of its crudity - it ignores all those tempo
> changes and so you get one empty staff and then the four parts. If that
> was a hard as it got, you could write a script to output the parts into
> your own templates quite easily.

I realized that Denemo comes as a binary for Mac, so I tested it now,
but it doesn't seem to like the original MIDI file. Not being familiar
with its GUI interface, I'm completely confused, but after importing
the MIDI and pressing play, I get some semi-nonsense out of it. It
doesn't seem to be able to handle chords at all (it just ignores the
upper pitch), it linearizes stuff, so I get weird alterations between
the basses and the main melody (with durations of 8. instead of 4 and
2), but the timings are all wrong. Not wrong in the sense of wrong
quantisation, but there is something horribly wrong with the import.

By picking a guided import it does something completely different, but
still completely useless.

Mojca