On Wed, May 05, 2010 at 09:19:05PM +0200, Jona Joachim wrote: > On Wed, May 05, 2010 at 09:17:15PM +0200, Alexandre Ratchov wrote: > > On Wed, May 05, 2010 at 08:20:38PM +0200, Jona Joachim wrote: > > > On Wed, May 05, 2010 at 07:57:31PM +0200, Alexandre Ratchov wrote: > > > > On Wed, May 05, 2010 at 06:13:20PM +0200, Jona Joachim wrote: > > > [snip] > > > > > I recently bought a Korg NanoKONTROL[1] midi controller and the volume > > > > > control in aucat just works using the sliders. However I'm not quite > > > > > savvy in the whole MIDI business and I was wondering if it was > > > > > possible > > > > > to personalize the use of it. For example there is a "scene" selection > > > > > button on the bottom left and to be able to use it with aucat I need > > > > > to > > > > > select scene 4, how come it's scene 4 and not 1? > > > > > > > > I guess sliders of different scenes are mapped to different > > > > controllers. And it happens that scene 4 contains a slider > > > > that maps to the appropriate volume control of aucat. > > > > > > > > To control the volume, the simpler is to configure the > > > > nanokontrol as follows: first slider to (channel 0, > > > > controller 7), next slider to (channel 1, controller 7), and > > > > so on. > > > > > > > > This way you get one slider per application. > > > > > > That works as-is, if I select scene 4 I get 1 slider per application > > > mapped correctly. > > > > excellent, this way you escape the windows ``editor'' ;) > > > > > > > > > > The controller also has start/stop etc. buttons. These probably send > > > > > MMC > > > > > messages and I was wondering whether it would be possible to use these > > > > > to control aucat -t slave? > > > > > > > > yes exactly. This is to start multiple applications > > > > synchronously (ex. play a track with one program while you > > > > record another track with another program..) > > > > > > Yes but I don't know how to make it work, at least it doesn't work if I > > > do the following: > > > aucat -l -t slave -q midithru:0 > > > > > > The applications don't start when I hit the start button. > > > > > > > oh, you have to use ``-q rmidi:<nanokontrol_number>'', as > > you probably did for the volume. > > > > Except if you have started the following before you start > > aucat: > > > > midicat -l -q rmidi:<nanokontrol_number> > > I actually have midicat running. I also tried with rmidi:n without > midicat with the same result. volume control works but start/stop > doesn't.
hmmm... could you send a hexdump of what message the start button sends? For instance with my setup I'd do: $ midicat -o - -q rmidi:2 | hexdump -ve '1/1 "%02x\n"' f0 7f 7f 06 02 f7 there are multiple MMC start messages. BTW any MIDI device is supposed to come with a ``MIDI implementation chart'' that gives the list of messages the device transmits and receives, this is often the last pages of the manual. Did you get one ? -- Alexandre
