diff --git a/2006-06-06-korg-microkontrol-in-linux.html b/2006-06-06-korg-microkontrol-in-linux.html new file mode 100644 index 0000000..98a5f61 --- /dev/null +++ b/2006-06-06-korg-microkontrol-in-linux.html @@ -0,0 +1,26 @@ + + + + + +

I recently picked up a KORG MicroKontrol from that local techno-crack peddler, Guitar Center. Short specs: 37-key keyboard (velocity sensitive), 16 pads (velocity sensitive), 8 sliders, 8 knobs, and a tempo knob that generates MIDI clock.

+ +

I had expected to plug this into my MIDI interface via the MIDI outputs on the back. However, as I left my MIDI cables at the theatre, I gave the USB interface a try. Much to my amazement, ALSA detected it as a USB MIDI device. It’s a bit complicated; it acts a MIDI interface as well when plugged in via USB, so it has sub-interfaces. For example:

+ +
amidi –dump –port hw:1,0,0
+
+ +

(it’s device 1, starting from 0, on my system)

+ +

This dumps input from the MIDI-IN port on the back of the device, but not generated by the device itself. To do that:

+ +
amidi –dump –port hw:1,0,1
+
+ +

Then you spend 5 minutes or so hitting the keys really hard and watching the velocity numbers. It’s fun.

+ +

It also has a 3rd channel for an unmapped “native mode”. I expected this to be a proprietary interface that they sold to application developers who wanted to better interface with the device. Apparently, however, it’s fully documented.

+ +

Why can’t all hardware vendors be like this?

+ + diff --git a/index.html b/index.html index f2fe1eb..355e14d 100644 --- a/index.html +++ b/index.html @@ -40,6 +40,7 @@
  • 2009-Sep-11: Confusing BIND with CNAMEs
  • 2009-Feb-19: The odd case of my mugging
  • 2009-Feb-03: 5-packet TCP connection?
    • +
  • 2006-Jun-06: KORG MicroKontrol in Linux
  • 2006-Apr-07: IBM Z60m in Linux
  • 2006-Mar-21: HP ProCurve 2824 Mini-Review
  • 2006-Mar-21: Redundant Network Interfaces
    • diff --git a/markdown/2006-06-06-korg-microkontrol-in-linux.md b/markdown/2006-06-06-korg-microkontrol-in-linux.md new file mode 100644 index 0000000..9c6dd2f --- /dev/null +++ b/markdown/2006-06-06-korg-microkontrol-in-linux.md @@ -0,0 +1,24 @@ + + + + + +I recently picked up a [KORG MicroKontrol](http://www.korg.com/gear/info.asp?a_prod_no=microkontrol&category_id=8) from that local techno-crack peddler, Guitar Center. Short specs: 37-key keyboard (velocity sensitive), 16 pads (velocity sensitive), 8 sliders, 8 knobs, and a tempo knob that generates MIDI clock. + +I had expected to plug this into my MIDI interface via the MIDI outputs on the back. However, as I left my MIDI cables at the theatre, I gave the USB interface a try. Much to my amazement, ALSA detected it as a USB MIDI device. It’s a bit complicated; it acts a MIDI interface as well when plugged in via USB, so it has sub-interfaces. For example: + + amidi –dump –port hw:1,0,0 + +(it’s device 1, starting from 0, on my system) + +This dumps input from the MIDI-IN port on the back of the device, but not generated by the device itself. To do that: + + amidi –dump –port hw:1,0,1 + +Then you spend 5 minutes or so hitting the keys really hard and watching the velocity numbers. It’s fun. + +It also has a 3rd channel for an unmapped “native mode”. I expected this to be a proprietary interface that they sold to application developers who wanted to better interface with the device. Apparently, however, it’s fully documented. + +Why can’t all hardware vendors be like this? + + diff --git a/markdown/index.md b/markdown/index.md index dc07234..d4a0f49 100644 --- a/markdown/index.md +++ b/markdown/index.md @@ -39,6 +39,7 @@ 1. 2009-Sep-11: [Confusing BIND with CNAMEs](2009-09-11-confusing-bind-with-cnames.html) 1. 2009-Feb-19: [The odd case of my mugging](2019-02-19-the-odd-case-of-my-mugging.html) 1. 2009-Feb-03: [5-packet TCP connection?](2009-02-03-5-packet-tcp-connection.html) +1. 2006-Jun-06: [KORG MicroKontrol in Linux](2006-06-06-korg-microkontrol-in-linux.html) 1. 2006-Apr-07: [IBM Z60m in Linux](2006-04-07-ibm-z60m-in-linux.html) 1. 2006-Mar-21: [HP ProCurve 2824 Mini-Review](2006-03-21-hp-procurve-2824-mini-review.html) 1. 2006-Mar-21: [Redundant Network Interfaces](2006-03-21-redundant-network-interfaces.html)