24 May
2007
24 May
'07
5:15 p.m.
On 24 May 2007 at 18:07, "Clemens Ladisch" <cladisch(a)fastmail.net> wrote:
Kevin Cosgrove wrote:
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
28:0 Pitch bend 3 -7744
28:0 Pitch bend 4 -7664
28:0 Pitch bend 3 -7568
28:0 Pitch bend 4 -7584
28:0 Pitch bend 3 -7472
28:0 Pitch bend 4 -7552
28:0 Pitch bend 3 -7440
28:0 Pitch bend 4 -7536
28:0 Pitch bend 3 -7456
28:0 Note on 0 108 0
28:0 Note on 0 108 127
28:0 Pitch bend 4 -7488
28:0 Note on 0 107 0
28:0 Pitch bend 4 -7440
28:0 Pitch bend 4 -7392
28:0 Pitch bend 4 -7312
28:0 Pitch bend 4 -7216
28:0 Pitch bend 4 -7072
28:0 Pitch bend 4 -6912
28:0 Pitch bend 4 -6736
28:0 Pitch bend 4 -6528
28:0 Pitch bend 4 -6272
28:0 Pitch bend 4 -6160
28:0 Pitch bend 4 -6096
28:0 Pitch bend 4 -6064
28:0 Note on 0 108 0
28:0 Note on 0 107 127
28:0 Pitch bend 3 -7248
28:0 Pitch bend 3 -6944
28:0 Note on 0 108 127
28:0 Pitch bend 3 -6592
28:0 Pitch bend 4 -6032
28:0 Pitch bend 3 -6224
28:0 Pitch bend 4 -6000
28:0 Pitch bend 3 -5856
28:0 Pitch bend 4 -5904
28:0 Pitch bend 3 -5536
28:0 Pitch bend 4 -5728
28:0 Pitch bend 3 -5264
28:0 Pitch bend 4 -5504
28:0 Pitch bend 3 -5120
28:0 Pitch bend 4 -5264
28:0 Pitch bend 3 -5072
28:0 Pitch bend 4 -5136
28:0 Pitch bend 3 -5056
28:0 Pitch bend 4 -5088
28:0 Pitch bend 4 -5072
28:0 Note on 0 107 0
28:0 Note on 0 108 0
28:0 Note on 0 104 127
28:0 Pitch bend 0 -7728
28:0 Pitch bend 0 -7200
28:0 Note on 0 105 127
28:0 Pitch bend 0 -6816
28:0 Pitch bend 1 -8128
28:0 Pitch bend 0 -6592
28:0 Pitch bend 1 -7872
28:0 Pitch bend 0 -6528
28:0 Pitch bend 1 -7600
28:0 Pitch bend 0 -6496
28:0 Pitch bend 1 -7312
28:0 Pitch bend 1 -7088
28:0 Pitch bend 1 -6944
28:0 Pitch bend 1 -6880
28:0 Pitch bend 1 -6864
28:0 Note on 0 104 0
28:0 Pitch bend 1 -6896
28:0 Note on 0 104 127
28:0 Pitch bend 0 -6432
28:0 Pitch bend 0 -6304
28:0 Pitch bend 0 -6144
28:0 Note on 0 105 0
28:0 Pitch bend 0 -5792
28:0 Note on 0 107 127
28:0 Pitch bend 0 -5680
28:0 Pitch bend 3 -5200
28:0 Pitch bend 0 -5600
etc.
So, I'll take this info back to the ardour list. Thanks much Clemens!
--
Kevin
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.
24 May
24 May
5:26 p.m.
New subject: MIDI connections (BCF2000 <--> ardour)
On 24 May 2007 at 12:15, Kevin Cosgrove <kevinc(a)doink.com> wrote:
On 24 May 2007 at 18:07, "Clemens Ladisch"
<cladisch(a)fastmail.net> wrote:
[snip]
Kevin Cosgrove wrote:
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 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. 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
6:01 p.m.
New subject: MIDI connections (BCF2000 <--> ardour)
On 24 May 2007 at 12:25, Kevin Cosgrove <kevinc(a)doink.com> wrote:
On 24 May 2007 at 12:15, Kevin Cosgrove
<kevinc(a)doink.com> wrote:
I tried ardour 2.0.2 again with "28:BCF2000"'s "0:BCF2000 MIDI 1"
output connected to "129:ardour"'s "1:mcu" input and this time I
get one line of input traced:
mcu input: Channel 3 Pitch Bend 6147
At that point things seem to hang. If I try to quit ardour I
get the dialog about saving first or just quitting. But, after
selecting to just quit ardour doesn't quit, and I have to ctrl-c.
Again, communication seems to be hung somewhere, but where?
Any more thoughts folks?
Thanks...
--
Kevin
On 24 May 2007 at 18:07, "Clemens
Ladisch" <cladisch(a)fastmail.net> wrote:
[snip]
Kevin Cosgrove wrote:
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 > 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. 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. 
25 May
25 May
2 p.m.
New subject: MIDI connections (BCF2000 <--> ardour)
Kevin Cosgrove wrote:
On 24 May 2007 at 12:25, Kevin Cosgrove
<kevinc(a)doink.com> wrote:
I experienced similar issues with my BCF2000 in mcu mode. I didn't (and
don't) have the time to do a decent bug report though.
What I remember is that connecting the bcf to arours mcu port caused
ardour UI to freeze for a while. The audio keeps on playing though.
Ardour's response to the BCF was rather unpredictable (sometimes the
faders worked, sometimes they didn't), although everything comes in fine
at aseqdump.
My 2 cents,
Pieter
On 24 May 2007 at 12:15, Kevin Cosgrove
<kevinc(a)doink.com> wrote:
I tried ardour 2.0.2 again with "28:BCF2000"'s "0:BCF2000 MIDI 1"
output connected to "129:ardour"'s "1:mcu" input and this time I
get one line of input traced:
mcu input: Channel 3 Pitch Bend 6147
At that point things seem to hang. If I try to quit ardour I
get the dialog about saving first or just quitting. But, after
selecting to just quit ardour doesn't quit, and I have to ctrl-c.
Again, communication seems to be hung somewhere, but where?
On 24 May 2007 at 18:07, "Clemens
Ladisch" <cladisch(a)fastmail.net> wrote:
[snip]
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 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.
6573
days inactive
6574
days old
linux-audio-user@lists.linuxaudio.org
3 comments
2 participants
participants (2)
-
Kevin Cosgrove -
Pieter Palmers