Hi Clemens,
Thanks for the reply. I still don't understand where
the usb-midi i/o device is.
Here's my device chain Tascam DM-24 digital mixing
consol and ardour.
DM-24 (mmc) -> to Ardour, Ardour (mtc) -> DM-24
The DM-24 sends a deferred play (type =3) to Ardour
and causes the Ardour transport to play engage. Ardour
in turn replies with MTC to syncronize the location of
the DM-24 transport with itself.
I've used 'dd...' to look for incoming messages:
'dd bs=1 if=/dev/snd/midiC1D0'
There's no messages passing through /dev/snd/midiC1D0
which is the device I use with the Audiophile 2496 for
example <MIDI-port tag="midisport"
device="/dev/snd/midiC1D0" type="alsa/raw"
mode="duplex"/>.
Perhaps I'm missing the obvious.
ron
--- Clemens Ladisch <clemens@xxxxxxxxxx> wrote:
> R Parker wrote:
> >
> > I'm trying to figure out what device I should
> point
> > applications (ardour) at in order for them to see
> > incoming mmc and to send mtc. I've got what
> appears to
> > be a working USB midiman 8x8:
> > >aconnect -i
> > client 72: 'Rawmidi 1 - MidiSport 8x8'
> [type=kernel]
> > 0 'MidiSport 8x8 Port 0'
> > 1 'MidiSport 8x8 Port 1'
> > 2 'MidiSport 8x8 Port 2'
> > 3 'MidiSport 8x8 Port 3'
> > 4 'MidiSport 8x8 Port 4'
> > 5 'MidiSport 8x8 Port 5'
> > 6 'MidiSport 8x8 Port 6'
> > 7 'MidiSport 8x8 Port 7'
> > 8 'MidiSport 8x8 Port 8'
>
> If the data is from/to an external device connected
> to the 8x8, it should
> work with the appropriate port (0-7). If the data is
> for the 8x8 itself,
> you could try the ninth port ("Port 8") which is
> called "Control Port" in
> the Windows driver.
>
> I don't actually have a MidiSport, so I don't know
> if or how it has to be
> configured to do MIDI timing.
>
>
> HTH
> Clemens
>
>
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
