[HN Gopher] Midihum: An ML-Based MIDI Humanizing Tool
___________________________________________________________________
Midihum: An ML-Based MIDI Humanizing Tool
Author : erwald
Score : 46 points
Date : 2023-12-30 11:30 UTC (1 days ago)
(HTM) web link (www.erichgrunewald.com)
(TXT) w3m dump (www.erichgrunewald.com)
| CrypticShift wrote:
| 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/
| BriggyDwiggs42 wrote:
| Why couldn't you use this on drawn in midi data? I figured that
| was the point.
| erwald wrote:
| Yes, that is indeed the main use case.
| lancesells wrote:
| 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.
| adzm wrote:
| 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.
| cammikebrown wrote:
| 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.
| steve1977 wrote:
| > 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.
| lancesells wrote:
| In Logic Pro it's called Humanize.
| NikkiA wrote:
| 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)
| a-dub wrote:
| 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.
| DrSiemer wrote:
| 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.
| brudgers wrote:
| Why not use an existing file?
|
| https://archive.org/details/themagicofmidiv1
| DrSiemer wrote:
| 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.
| brudgers wrote:
| For me, the less I winge the more time I have to just try
| things out.
|
| YMMV.
| palemoonale wrote:
| Hint: One can get "MIDI" hum only when using MIDI over USB.
|
| (stupid name btw)
| BriggyDwiggs42 wrote:
| Okay palemoonale
| cmiller1 wrote:
| > 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?
___________________________________________________________________
(page generated 2023-12-31 23:02 UTC)