Andrew Lowell

Good to hear its working ok! As far as controller channels, I haven't implemented those, maybe version 2. They're pretty straitforward though .. once you get a curve in chops just name it c45 for instance and merge before the midi out chop.

I've made a few nodes in the past that converted a animation channel into a controller but like I said; for HMT probably 6 months off. I want the workflow to be encompassing once its there. So I recommend for now maybe just chop merge/fetch the channels already generated by the chopnet of the hmt before the midi out, merge in your controller channels, then use your own midi out. Also make sure its either visible or forced to cook (see method used in otl)

Thanks all! Glad you're excited and I hope you get some cool use from it. I've just released a new build which SESI has up-converted to master's license. Enjoy and thank you SESI

https://github.com/andrew-lowell/HMT/releases [github.com]

Also, be sure to check github for the latest HMT tutorials which I'll be releasing weekly.

lbabieno
jeskola buzz

No, I feel like a real-time application would be better suited for what I'm seeing here. The HMT is specifically for generating MIDI notes. That has a few disadvantages like Houdini's complexity and non-music specific workflows. But also has a large amount of benefits like the open architecture and the raw simulation abilities which could be applied in creative ways.

So yeah, no sound output. Just MIDI output.