On 24 May 2007 at 12:15, Kevin Cosgrove <kevinc@xxxxxxxxx> wrote: > On 24 May 2007 at 18:07, "Clemens Ladisch" <cladisch@xxxxxxxxxxxx> wrote: > > Kevin Cosgrove wrote: > > > > You need to connect one of these two: > > > > BCF2000:BCF2000 MIDI 1 > > > > BCF2000:BCF2000 MIDI 2 > > > > to this: > > > > ardour::mcu > > > > > > Well, I tried every combination of inputs and outputs I could > > > think of, but it didn't work. > > > > Try "aseqdump -p BCF2000:0" to see whether any data arrives. > > If it does, there is some problem with the connection to ardour. > > I just tried that, and I get > > Waiting for data. Press Ctrl+C to end. > Source_ Event_________________ Ch _Data__ > 28:0 Note on 0 108 127 > 28:0 Pitch bend 4 -8032 > 28:0 Note on 0 107 127 > 28:0 Pitch bend 3 -8016 [snip] > etc. I just thought about this a little bit more. My original problem is not that data won't come out of the BCF2000. It works fine with ardour when ardour addresses the hardware as device="/dev/snd/midiC3D0". But, when ardour relies on a MIDI patchbay to connect the ardour:mcu MIDI port to a port on the BCF2000, then the connection isn't made. At this point my supposition for testing is that ardour listens fine and the BCF2000 talks fine, but a connection between the two isn't being made. I'd like help debugging the connection issue, or confirming that it's not a connection issue. Thanks! -- Kevin _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
