top | item 14688292

Show HN: MidiPad 2 – A customizable Midi Pad Controller

47 points| thedjinn | 8 years ago |midipadapp.com

18 comments

order

goodgood|8 years ago

You shouldn't advertise your site the day you register your domain. Filters like WebSense block new domains. I've seen this happen multiple times here.

I wonder if there's a correlation between a domain name's age, and the HN rank of posts that link to them.

divenorth|8 years ago

Interesting that you use motion sensors to create midi velocity. How accurate is that?

Any reason for not adding midi sliders and knobs too? Most MIDI apps include those and are used by many composers/musicians.

thedjinn|8 years ago

The accuracy is a trade-off between latency and precision. The touch event arrives as soon as you touch the screen, but the actual force of your touch still needs a few milliseconds to actually put the device into motion. Waiting a little bit while collecting measurements gives you quite an accurate indication of the force used, but the increased latency makes it harder to play.

Sliders and knobs will be added in a future version. I wanted to put an MVP on the app store first before adding additional features.

soylentcola|8 years ago

Isn't that how all of the older iOS apps like Garage Band did drums and such? Not that it was terribly accurate there either, but I assumed it had gotten better since my last iOS device (an old iPad 2).

jamescostian|8 years ago

I'm also curious about motion sensors for MIDI. I would have thought 3d-touch would be more accurate

pampa|8 years ago

Velocity sensitive pads on a touch screen? Wow, didnt know this was possible.

mikewhy|8 years ago

Garage Band for iOS did it on release back in 2011. Using the accelerometer it's possible to simulate some sort of velocity.

jedanbik|8 years ago

The Roli app has a good implementation of this on 3D Touch enabled iOS devices.

brokenmachine|8 years ago

Only on ios.

squarefoot|8 years ago

Android has no chance of competing in the MIDI/Music field: choosing Java was an ill decision because of the huge latencies its poor performance imposes, which makes any serious Music application plain impossible. Google promised a low latency Android years ago which as predicted by many of us they didn't deliver: that would require rewriting entire layers of the OS from scratch migrating them from Java to C++ just to make some music freaks happy. Just no way.