10 Sep
2012
10 Sep
'12
8:56 p.m.
Hiya,
A few years back I was using my BCF2000 with ardour. After upgrades
to my computer hardware and Linux distribution the combination no
longer works.
The BCF shows up in /proc/asound fine. I can send and receive data
with the BCF using amidi.
The test of tracing communication between the BCF and ardour fails.
I think this is because the mcu (port?) of ardour isn't connected to
the BCF. But, qjackctl won't let me connect those. They don't
show up in the MIDI tab of qjackctl. They only show up in the ALSA
tab of qjackctl. A long time ago there was an issue with my
distribution where qjackctl wasn't linked against libasound. But,
that's not the problem this time around.
I know people would need more info from me to help me troubleshoot
this. But, I'd rather not spew 5-6 pages of stuff to the list.
What would be useful here?
Thanks....
--
Kevin
10 Sep
10 Sep
9:14 p.m.
On Mon, Sep 10, 2012 at 2:56 PM, Kevin Cosgrove <kevinc(a)cosgroves.us> wrote:
Hiya,
A few years back I was using my BCF2000 with ardour. After upgrades
to my computer hardware and Linux distribution the combination no
longer works.
The BCF shows up in /proc/asound fine. I can send and receive data
with the BCF using amidi.
The test of tracing communication between the BCF and ardour fails.
I think this is because the mcu (port?) of ardour isn't connected to
the BCF. But, qjackctl won't let me connect those. They don't
show up in the MIDI tab of qjackctl. They only show up in the ALSA
tab of qjackctl.
run a2jmidid -e
if you want a second rate solution, use JACK's "builtin" ALSA MIDI support
via the "MIDI Driver" selector at teh bottom left of the setup dialog.
11 Sep
11 Sep
2:57 a.m.
On 10 September 2012 at 15:14, Paul Davis <paul(a)linuxaudiosystems.com> wrote:
Now that I've got that installed, I see something that could point at
my problem:
JACK MIDI <-> ALSA sequencer MIDI bridge, version 6
(a500771941cd42419a2418ee28259cde718a82bb) built on Wed Dec 31 16:00:00 1969
Copyright 2006,2007 Dmitry S. Baikov
Copyright 2007,2008,2009 Nedko Arnaudov
Bridge starting...
Using JACK server 'default'
Hardware ports will be exported.
Cannot lock down memory area (Cannot allocate memory)
Bridge started
Press ctrl-c to stop the bridge
port created: Midi Through [14] (capture): Midi Through Port-0
port created: Midi Through [14] (playback): Midi Through Port-0
ERROR: a2j_alsa_connect_from: can't subscribe to 20:0 - Resource temporarily
unavailable
port skipped: M Audio Delta 1010 [20] (capture): M Audio Delta 1010 MIDI
port skipped: M Audio Delta 1010 [20] (playback): M Audio Delta 1010 MIDI
ERROR: a2j_alsa_connect_from: can't subscribe to 24:0 - Resource temporarily
unavailable
port skipped: BCF2000 [24] (capture): BCF2000 MIDI 1
port skipped: BCF2000 [24] (playback): BCF2000 MIDI 1
ERROR: a2j_alsa_connect_from: can't subscribe to 24:1 - Resource temporarily
unavailable
port skipped: BCF2000 [24] (capture): BCF2000 MIDI 2
port skipped: BCF2000 [24] (playback): BCF2000 MIDI 2
port created: ardour [130] (capture): control
port created: ardour [130] (playback): control
port created: ardour [130] (capture): mcu
port created: ardour [130] (playback): mcu
port created: ardour [130] (capture): seq
port created: ardour [130] (playback): seq
Skipping the BCF2000 doesn't seem right.
A few years
back I was using my BCF2000 with ardour. After upgrades
to my computer hardware and Linux distribution the combination no
longer works.
The BCF shows up in /proc/asound fine. I can send and receive data
with the BCF using amidi.
The test of tracing communication between the BCF and ardour fails.
I think this is because the mcu (port?) of ardour isn't connected to
the BCF. But, qjackctl won't let me connect those. They don't
show up in the MIDI tab of qjackctl. They only show up in the ALSA
tab of qjackctl.
run a2jmidid -e if you want a second rate solution, use JACK's
"builtin" ALSA
MIDI support via the "MIDI Driver" selector at the bottom left
of the setup dialog.
Right now MIDI Driver is set to "raw". I'm not sure when or if
I set that, or whether it might be the default.
Thanks...
--
Kevin
4:30 a.m.
On 10 September 2012 at 15:14, Paul Davis <paul(a)linuxaudiosystems.com> wrote:
run a2jmidid -e
if you want a second rate solution, use JACK's "builtin" ALSA MIDI support
via the "MIDI Driver" selector at the bottom left of the setup dialog.
I've got it half working, thanks to the advice of those who
responded. Half working means that the sliders on the BCF move
when I move the sliders in ardour. The slider to slider track
assignments look right too.
Tracing the MIDI traffic of mcu I get "input" when I move the BCF
slider, and I get "output" when I move the ardour slider.
My setup is currently running MIDI Driver of qjackctl as "none"
in combination with running "a2jmidid -e". In the MIDI tab
of qjackctl's Connections window I have ardour's output ports
(control, mcu, and seq) all connected to the BCF MIDI 1 input
port. I also have the BCF MIDI 1 output port connected to all of
ardour's input ports.
Now all I need to do is to figure out how to get the BCF sliders
to move the ardour sliders. The way I've got it leaves me
hopeful. But, it's not yet useful.
Cheerio...
--
Kevin
5:41 a.m.
On Mon, Sep 10, 2012 at 10:30 PM, Kevin Cosgrove <kevinc(a)cosgroves.us>wrote;wrote:
Now all I need to do is to figure out how to get the BCF sliders
to move the ardour sliders. The way I've got it leaves me
hopeful. But, it's not yet useful.
although it does sort-of-kind-of-work, i cannot recommend ardour 2.X's
support for the mackie control protocol.
the entire thing was reimplemented for 3.0 and works vastly better.
6:05 a.m.
On 10 September 2012 at 23:41, Paul Davis <paul(a)linuxaudiosystems.com> wrote:
On Mon, Sep 10, 2012 at 10:30 PM, Kevin Cosgrove
<kevinc(a)cosgroves.us>wrote;wrote:
OK. I should give beta 5 a whirl, and follow the development news
to see when the release candidates come out.
Thanks again....
--
Kevin
Now all I need to do is to figure out how to get the BCF sliders
to move the ardour sliders. The way I've got it leaves me
hopeful. But, it's not yet useful.
although it does sort-of-kind-of-work, i cannot recommend ardour 2.X's
support for the mackie control protocol.
the entire thing was reimplemented for 3.0 and works vastly better. 
9:06 a.m.
On 09/11/2012 05:41 AM, Paul Davis wrote:
although it does sort-of-kind-of-work, i cannot recommend ardour 2.X's
support for the mackie control protocol.
With 2.8x it works very well if in ardour the raw device is used instead
of the jack device.
From ~/.ardour2/ardour.rc:
<MIDI-port tag="mcu" device="/dev/midi-bcf2000"
mode="duplex"
type="alsa/raw"/>
...
<Option name="mackie-emulation" value="bcf"/>
And in /etc/udev/rules.d/60-symlink.rules I have:
KERNEL=="midiC[0-9]D0", ATTRS{product}=="BCF2000",
SYMLINK+="midi-bcf2000"
Unfortunately ardour removes/rewrites the entry in ardour.rc whenever
the device can not be found.
-- Giso
the entire thing was reimplemented for 3.0 and works vastly better.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
6:13 p.m.
On 11 September 2012 at 9:06, Giso Grimm <gg3137(a)vegri.net> wrote:
On 09/11/2012 05:41 AM, Paul Davis wrote:
That was my previous experience as well. Now that I've changed
computer hardware and Linux distribution version I haven't been able
to recreate that experience.
although it does sort-of-kind-of-work, i cannot
recommend ardour 2.X's
support for the mackie control protocol.
With 2.8x it works very well if in ardour the raw device is used instead
of the jack device.
From ~/.ardour2/ardour.rc:
<MIDI-port tag="mcu" device="/dev/midi-bcf2000"
mode="duplex" type="alsa/raw"/>
...
<Option name="mackie-emulation" value="bcf"/>
I might give that one more whirl. But, I won't spend a lot of time
on it.
And in /etc/udev/rules.d/60-symlink.rules I have:
KERNEL=="midiC[0-9]D0", ATTRS{product}=="BCF2000",
SYMLINK+="midi-bcf2000"
Excellent! I never did figure that out. I've used "midiC3D0", as
that's where my BCF2000 ends up.
Unfortunately ardour removes/rewrites the entry in
ardour.rc whenever
the device can not be found.
I've noticed. But, if I turn on all the outboard gear, then start
jack, then start ardour, then it worked very nicely in the past.
Thanks much....
--
Kevin
4255
days inactive
4256
days old
linux-audio-user@lists.linuxaudio.org
7 comments
3 participants
participants (3)
-
Giso Grimm -
Kevin Cosgrove -
Paul Davis