Midihum: An ML-Based MIDI Humanizing Tool | Hacker News Reader

Midihum: An ML-Based MIDI Humanizing Tool

erichgrunewald.com

55 pointserwald18 comments

A before and after demo would help. I don't even have time to actually make music anymore, I'm not going through the trouble of installing this and then finding or creating a suitable midi file just to test it.

Why not use an existing file?

https://archive.org/details/themagicofmidiv1

Because I assume this works on single track compositions and not full compositions, which would increase the time I'd need to spend finding a suitable midi file. I did check if one was included in the repository, but there isn't.

If you work on something for 5 years, adding a quick demo isn't too much to ask for, is it? I'm sure I'm not the only one who has negative time to spare.

For me, the less I winge the more time I have to just try things out.

YMMV.

Ad hominem is not a great way to reply to valid criticism on something that is easy to fix and greatly affects the potential reach of a project like this.

https://github.com/erwald/midihum

Have at it.

> Using midihum is easy. First clone the repository, navigate to the midihum/ directory, and install dependencies:

> pip install -r requirements.txt

Why not just upload it to pypi so you can do all this with one pip command?

cool! might be able to improve substantially with low effort using a simple approach to capturing dynamics like adding a few lags of the existing features.

I mean, you are already "performing"; it's not as if it is computer-generated (or drawn with the mouse), so it should already be "humanized." I believe the real issue lies with subpar MIDI keyboards that lack sufficient responsiveness. This is rarely a problem for me with guitars, where I can always dial in velocities with exactly the precision I have in mind (and I'm an amateur).

FYI Another way MIDI is humanized in DAWs is in the temporal domain (i.e., rhythm/timing). This was popularized by Ableton's Groove Pool [1].

[1] https://www.ableton.com/en/manual/using-grooves/

Why couldn’t you use this on drawn in midi data? I figured that was the point.

Yes, that is indeed the main use case.

That's what I assumed this was for as well. Take a composition from something like Hookpad and run it through this before importing into a DAW.

Groove is such an amazing feature in Ableton. It's so surprising how much just slight adjustments to the rhythm can make something feel laid back.

It’s a lot easier for me to play with proper dynamics on an actual piano versus a keyboard. Maybe if it’s an extremely fancy weighted one, it’d be okay, but I generally don’t have access to one of those.

> This was popularized by Ableton's Groove Pool

This was a feature in Cubase on Atari years before Ableton even existed. Most likely also in Logic Pro’s precursor Notator.

In Logic Pro it's called Humanize.

Also 'groove pool' as a term comes from acid pro, which predates ableton (and has always been able to extract groove timing from audio as well as midi)

Reply on news.ycombinator.com