[ardour-users] Ardour 2.0 and BCF2000
Kevin Cosgrove
kevinc at doink.com
Wed May 16 11:28:40 PDT 2007
On Tue, 2007-05-01 at 12:30 +0200, Thomas Desbarats wrote:
> I'm using Ardour 2.0 beta and rc for a while and I have to say
> that MCU mode changed my life. My point is, since the 2.0rc2 I
> can't use the MCU (with a BCF2000).
On 1 May 2007 at 7:04, Paul Davis <paul at linuxaudiosystems.com> wrote:
> the default port name "mcu" is now an ALSA sequencer port and
> will need to be explicitly connected to the hardware port where
> your BCF2000 is plugged in. you can use qjackctl's MIDI tab in
> its connect dialog to do this.
On 5/15/07, Kevin Cosgrove <kevinc at doink.com> wrote:
> The recent chatter about the BCF2000 (my new one is in a box
> ready to hook up to ardour 2.0.2) got me thinking about this
> again. I just fired up qjackctl and found that my MIDI tab is
> all grayed out. Is this the right place to ask why that is or
> how to fix it?
On 15 May 2007 at 12:13, "Jesse Chappell" <jesse at essej.net> wrote:
> Assuming you are on linux,
> make sure that the snd_seq alsa kernel module is loaded
On 15 May 2007 at 9:26, Kevin Cosgrove <kevinc at doink.com> wrote:
> Mandriva 2007.0, 2.6.17-13mdv #1 SMP Fri Mar 23 13:07:21 MDT 2007
> i686 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ GNU/Linux
>
> lsmod | grep snd_seq
>
> snd_seq_midi 7264 0
> snd_seq_dummy 3620 0
> snd_seq_oss 31392 0
> snd_seq_midi_event 7072 2 snd_seq_midi,snd_seq_oss
> snd_seq 49488 6 snd_seq_midi,snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
> snd_rawmidi 19936 3 snd_seq_midi,snd_mpu401_uart,snd_ens1371
> snd_seq_device 7212 5 snd_seq_midi,snd_seq_dummy,snd_seq_oss,snd_seq,snd_rawmidi
> snd_timer 19620 2 snd_seq,snd_pcm
> snd 46500 22 snd_seq_oss,snd_seq,snd_via82xx,snd_ice1712,snd_ak4xxx_adda,snd_cs8427,snd_i2c,snd_mpu401_uart,snd_pcm_oss,snd_mixer_oss,snd_ens1371,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm,snd_timer
Last night I plugged in my BCF2000 for the first time, and via USB.
I changed it's emulation mode to "Logic Control" per instructions on
the ardour website. Then I did a little more digging.
'aconnect -o' reports:
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 16: 'Ensoniq AudioPCI' [type=kernel]
0 'ES1371 '
client 20: 'M Audio Delta 1010' [type=kernel]
0 'M Audio Delta 1010 MIDI'
client 28: 'BCF2000' [type=kernel]
0 'BCF2000 MIDI 1 '
1 'BCF2000 MIDI 2 '
2 'BCF2000 MIDI 3 '
'aconnect -i' reports:
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 16: 'Ensoniq AudioPCI' [type=kernel]
0 'ES1371 '
client 20: 'M Audio Delta 1010' [type=kernel]
0 'M Audio Delta 1010 MIDI'
client 28: 'BCF2000' [type=kernel]
0 'BCF2000 MIDI 1 '
1 'BCF2000 MIDI 2 '
ardour2 (2.0.2) reports:
WARNING: Your system has a limit for maximum amount of locked memory!
This might cause Ardour to run out of memory before your system runs out of memory. You can view the memo
ry limit with 'ulimit -l', and it is normally controlled by /etc/security/limits.conf
Ardour/GTK 2.0.2
(built using 1810 and GCC version 4.1.1 20060724 (prerelease) (4.1.1-3mdk))
Copyright (C) 1999-2007 Paul Davis
Some portions Copyright (C) Steve Harris, Ari Johnson, Brett Viren, Joel Baker
Ardour comes with ABSOLUTELY NO WARRANTY
not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This is free software, and you are welcome to redistribute it
under certain conditions; see the source for copying conditions.
Loading ui configuration file /etc/ardour2/ardour2_ui.rc
theme_init() called from internal clearlooks engine
loading system configuration file /etc/ardour2/ardour_system.rc
loading user configuration file /home/kevinc/.ardour2/ardour.rc
ardour: [INFO]: Using SSE optimized routines
ardour: [INFO]: looking for control protocols in /home/kevinc/.ardour2/surfaces/:/usr/lib/ardour2/surface
s/
ardour: [INFO]: Control surface protocol discovered: "Generic MIDI"
ardour: [INFO]: Control protocol Tranzport not usable
ardour: [INFO]: Control surface protocol discovered: "Mackie"
loading bindings from /etc/ardour2/ardour.bindings
Loading session /home/kevinc/Music/Test/delta1010test using snapshot delta1010test (1)
Loading history from '/home/kevinc/Music/Test/delta1010test/delta1010test.history'.
ardour2 also added this line to my ardour.rc file
<MIDI-port tag="mcu" device="ardour" type="alsa/sequencer" mode="duplex"/>
But, qjackctl still has it's MIDI tab grayed out, and I don't
know of any way to connect the ALSA sequencer port name "mcu" to
the hardware port where my BCF2000 is plugged in, which is card 3
port 0 (I think).
I wondered if I could fire up a MIDI app and see if anything would
show up in qjackctl's MIDI tab. I started rosegarden (before the
BCF2000 was turned on) and rosegarden reported:
Rosegarden 1.5.1 - AlsaDriver - alsa-lib version 1.0.12
JackDriver::initialiseAudio - JACK sample rate = 44100Hz, buffer size = 256
JackDriver::initialiseAudio - creating disk thread
JackDriver::initialiseAudio - found 10 JACK physical outputs
JackDriver::initialiseAudio - connecting from "rosegarden:master out L" to "alsa_pcm:playback_1"
JackDriver::initialiseAudio - connecting from "rosegarden:master out R" to "alsa_pcm:playback_2"
JackDriver::initialiseAudio - found 12 JACK physical inputs
JackDriver::initialiseAudio - connecting from "alsa_pcm:capture_1" to "rosegarden:record in 1 L"
JackDriver::initialiseAudio - connecting from "alsa_pcm:capture_2" to "rosegarden:record in 1 R"
JackDriver::initialiseAudio - initialised JACK audio subsystem
ALSA Client information:
14,0 - (Midi Through, Midi Through Port-0) (DUPLEX) [ctype 2, ptype 655362, cap 99]
16,0 - (Ensoniq AudioPCI, ES1371) (DUPLEX) [ctype 2, ptype 589826, cap 127]
20,0 - (M Audio Delta 1010, M Audio Delta 1010 MIDI) (DUPLEX) [ctype 2, ptype 589826, cap 127]
Creating device 0 in Play mode for connection 16:0 Ensoniq AudioPCI: ES1371 (duplex)
Default device name for this device is MIDI external device
Creating device 1 in Record mode for connection 16:0 Ensoniq AudioPCI: ES1371 (duplex)
Default device name for this device is MIDI hardware input device
Creating device 2 in Play mode for connection 20:0 M Audio Delta 1010 MIDI (duplex)
Default device name for this device is MIDI external device 2
Creating device 3 in Record mode for connection 20:0 M Audio Delta 1010 MIDI (duplex)
Default device name for this device is MIDI hardware input device 2
Creating device 4 in Play mode for connection 14:0 Midi Through Port-0 (duplex) (not connecting)
Default device name for this device is MIDI output system device
Creating device 5 in Record mode for connection 14:0 Midi Through Port-0 (duplex) (not connecting)
Default device name for this device is MIDI input system device
System timer is only 250Hz, sending a warning
Current timer set to "system timer" with timer checks
WARNING: using system timer with only 250Hz resolution!
AlsaDriver::initialiseMidi - initialised MIDI subsystem
System timer is only 250Hz, sending a warning
Current timer set to "system timer" with timer checks
WARNING: using system timer with only 250Hz resolution!
ALSA Client information:
14,0 - (Midi Through, Midi Through Port-0) (DUPLEX) [ctype 2, ptype 655362, cap 99]
16,0 - (Ensoniq AudioPCI, ES1371) (DUPLEX) [ctype 2, ptype 589826, cap 127]
20,0 - (M Audio Delta 1010, M Audio Delta 1010 MIDI) (DUPLEX) [ctype 2, ptype 589826, cap 127]
I'm starting to wonder if qjackctl is getting confused by my having 4
sound "cards", if one counts the BCF2000 as a card; it showed up as
/proc/asound/card3
Anyone have ideas as to how I could debug this further? If I know
that the BCF2000 is midi C3D0, does anyone know how to connect it to
ALSA's mcu, maybe with aconnect? Should I be asking this on LAU
in addition to here? Right now I'm completely stuck as far as the
BCF2000 goes.
Thanks....
--
Kevin
More information about the Ardour-Users
mailing list