Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: add humanization data to exported midi #1160

Open
github-wlk opened this issue Feb 4, 2021 · 1 comment
Open

Feature request: add humanization data to exported midi #1160

github-wlk opened this issue Feb 4, 2021 · 1 comment

Comments

@github-wlk
Copy link

github-wlk commented Feb 4, 2021

Hydrogen version * : Future
Operating system + version : all
Audio driver + version : n/a


Hi, I would like the option of having any humanization data optionally applied to exported midi data. I know that this is not the default, so to make it optional, one could either:
a) provide a pop-up with a checkbox when you export, asking if you want the humanization data "printed", or
b) have an option in the preferences to export humanization data, with the default being "no" to honor legacy users

My use case: I use H2 with Ardour, and as I like H2's humanization, I prefer to do my drum programming all in H2, and then print the audio output from H2 to Ardour. I would like the option of being able to export the H2 midi data into Ardour. I know I can route the midi data from H2 to Ardour, but I've found that less than ideal.

Thanks!

@notsmoothsteve
Copy link

+1

My use case is using H2 to program drum parts which I then export as MIDI files to be played on my keyboard. It would be nice to be able to have some modest amount of humanization in the MIDI file, via either of the methods suggested above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants