[Ardour-Users] MIDI Tracer input not matching aseqdump

Paul Davis paul at linuxaudiosystems.com
Tue Apr 30 16:18:56 PDT 2013

ardour's output is in hexadecimal, aseqdump is in decimal. you can change
ardour's trace window to be decimal too.

On Tue, Apr 30, 2013 at 7:13 PM, will cunningham <willpanther at gmail.com>wrote:

> Hello,
> I am trying to write a mapping file for Ardour 3, and I'm having some
> problems.  I'm breaking my problem down into smaller issues as I have
> good examples from other mappings.
> For MIDI mapping in another app I used aseqdump -p which I think gives
> the same output as kmidimon, or at least worked for what I was doing
> before.  In the Ardour 3 docs, it says that you can also use their
> MIDI Tracer with the Port connected to MIDI control in.  This is
> working, but I get different output than I got from aseqdump.
> Below are nine faders I move on my controller and the different output:
> For aseqdump all are said to be channel 0 with data controller-
> 7,84,5,72,73,93,91,71,74 for each of the nine.
> In the Midi Tracer, I get channel 0 with data controller-
> 07,54,05,48,49,5d,5b,47,4a
> My question is which set of numbers to use for the controller numbers
> in the mapping, or am I doing/configuring/looking wrong here?
> thanks,
> Will
> _______________________________________________
> Ardour-Users mailing list
> ardour-users at lists.ardour.org
> http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ardour.org/pipermail/ardour-users-ardour.org/attachments/20130430/f09c3549/attachment-0001.htm>

More information about the Ardour-Users mailing list