17 Oct
2009
17 Oct
'09
8:22 p.m.
i've followed the online ardour manual section 10.2, but it isn't working.
manual page shows the bcf showing up under MIDI in qjackctl Connect window,
but for me it comes up under ALSA. i tried various combinations conncections
to/from ardour from qjackctl but to no avail.
i'm using debian lenny on amd64 with ardour compiled from source (since it's
not in the debian distribution).
i have the bcf2000 connected through usb and it's showing up fine
in /proc/asound/cards.
any help would be greatly appreciated.
17 Oct
17 Oct
11:31 p.m.
the good news is that this will definitely work with linux, but it took me a
little bit of effort.
I recently got my BCR2000 to work with jack, and after some hacking, i've
been using it as my midi interface to the rest of my gear. There are some
internal settings on the BCR that I am sure also apply to the BCF (they've
got the same manual pretty much), which has to deal with modes. You
definitely want to be in usb mode (modes U1-4).
what alsa midi modules do you have? im on gentoo, and I compile everything
alsa as modules, as in-kernel never worked.
i did a few things while i was getting this going. 1) ran usbmon on the
usbport and manipulated things until i was sniffing the usb traffic. 2) ran
pd (puredata) and got midi working through that, 3) figured out which midi
ports were usb and which are actually midi ports.
You'll also want to check your midi channels.
On Sat, Oct 17, 2009 at 3:29 PM, uhoh <uhoh(a)cox.net> wrote:
i've followed the online ardour manual section
10.2, but it isn't working.
manual page shows the bcf showing up under MIDI in qjackctl Connect window,
but for me it comes up under ALSA. i tried various combinations
conncections
to/from ardour from qjackctl but to no avail.
i'm using debian lenny on amd64 with ardour compiled from source (since
it's
not in the debian distribution).
i have the bcf2000 connected through usb and it's showing up fine
in /proc/asound/cards.
any help would be greatly appreciated.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
--
godspeed you black cats
18 Oct
18 Oct
2:04 a.m.
On Sun, Oct 18, 2009 at 12:29 AM, uhoh <uhoh(a)cox.net> wrote:
i've followed the online ardour manual section
10.2, but it isn't working.
manual page shows the bcf showing up under MIDI in qjackctl Connect window,
but for me it comes up under ALSA. i tried various combinations conncections
to/from ardour from qjackctl but to no avail.
i'm using debian lenny on amd64 with ardour compiled from source (since it's
not in the debian distribution).
i have the bcf2000 connected through usb and it's showing up fine
in /proc/asound/cards.
any help would be greatly appreciated.
In qjackctls setup window, select 'seq' as Midi driver in the drop-down
menu at the bottom left. Then all Alsa-Midi ports should appear under
Alsa as well as under Midi.
Not exactly sure, but I expect lennys qjackctl to be sufficiently up
to date to have that feature.
Some explanation of the two Midi systems:
http://wiki.linuxaudio.org/faq/start#qwhat_is_the_difference_between_jack-m…
best,
d
19 Oct
19 Oct
11:45 a.m.
On Sunday 18 October 2009 12:04:14 am David Adler wrote:
On Sun, Oct 18, 2009 at 12:29 AM, uhoh
<uhoh(a)cox.net> wrote:
okay, now i have extra ports under the MIDI tab conveniently labeled
midi_capture_3 ... midi_playback_8 (presumably for the BCF2000 and ardour) in
addition to my soundcard ports. i tried some random connections here, but it
didn't do anything.
i've followed the online ardour manual
section 10.2, but it isn't
working. manual page shows the bcf showing up under MIDI in qjackctl
Connect window, but for me it comes up under ALSA. i tried various
combinations conncections to/from ardour from qjackctl but to no avail.
i'm using debian lenny on amd64 with ardour compiled from source (since
it's not in the debian distribution).
i have the bcf2000 connected through usb and it's showing up fine
in /proc/asound/cards.
any help would be greatly appreciated.
In qjackctls setup window, select 'seq' as Midi driver in the drop-down
menu at the bottom left. Then all Alsa-Midi ports should appear under
Alsa as well as under Midi. Some explanation of the two Midi systems:
http://wiki.linuxaudio.org/faq/start#qwhat_is_the_difference_between_jack-m
idi_and_alsa-midi
thanks for the link. it doesn't solve my problem, but any info on how the
underlying software works is good to know.
under the ALSA tab i have the following out ports (in addition to my sound
card): MIDI 1 & 2 under the BCF2000 and control, mcu, & seq under ardour. the
in ports are the same for ardour, but i have MIDI 1, 2, & 3 for the BCF2000.
which outs connect to which ins?
12:40 p.m.
On Mon, Oct 19, 2009 at 3:52 PM, uhoh <uhoh(a)cox.net> wrote:
On Sunday 18 October 2009 12:04:14 am David Adler
wrote:
AFAIK there is no disadvantage if the connections are done
in the Alsa tab, since both, the BCF and Ardour, don't use
Jack-Midi anyhow. The Midi tab shown in the Manual is
presumably the same as the Alsa tab today, the picture is
rather outdated.
In Ardour I had to check 'Generic MIDI' (options menu ->
control surfaces -> ...) before I could successfully
ctrl-middle-click the faders to assign them. Probably also
check 'feedback' for driving the motor faders.
I can't tell you which of the ports to use, trial and error
should work. If the Ardour settings don't do the magic a
simple Midi monitor (any of gmidimon, kmidimon or ams
or (if you like) puredata can do it) might be helpful to
trace down the problem.
best,
d
On Sun, Oct 18, 2009 at 12:29 AM, uhoh
<uhoh(a)cox.net> wrote:
okay, now i have extra ports under the MIDI tab conveniently labeled
midi_capture_3 ... midi_playback_8 (presumably for the BCF2000 and ardour) in
addition to my soundcard ports. i tried some random connections here, but it
didn't do anything.
i've followed the online ardour manual
section 10.2, but it isn't
working. manual page shows the bcf showing up under MIDI in qjackctl
Connect window, but for me it comes up under ALSA. i tried various
combinations conncections to/from ardour from qjackctl but to no avail.
i'm using debian lenny on amd64 with ardour compiled from source (since
it's not in the debian distribution).
i have the bcf2000 connected through usb and it's showing up fine
in /proc/asound/cards.
any help would be greatly appreciated.
In qjackctls setup window, select 'seq' as Midi driver in the drop-down
menu at the bottom left. Then all Alsa-Midi ports should appear under
Alsa as well as under Midi. Some explanation of the two Midi systems:
http://wiki.linuxaudio.org/faq/start#qwhat_is_the_difference_between_jack-m
idi_and_alsa-midi
thanks for the link. it doesn't solve my problem, but any info on how the
underlying software works is good to know.
under the ALSA tab i have the following out ports (in addition to my sound
card): MIDI 1 & 2 under the BCF2000 and control, mcu, & seq under ardour. the
in ports are the same for ardour, but i have MIDI 1, 2, & 3 for the BCF2000.
which outs connect to which ins?
5:17 p.m.
On Monday 19 October 2009 10:40:57 am David Adler wrote:
i'm using the ALSA tab with the default connections
under the ALSA
tab i have the following out ports (in addition to my
sound card): MIDI 1 & 2 under the BCF2000 and control, mcu, & seq under
ardour. the in ports are the same for ardour, but i have MIDI 1, 2, & 3
for the BCF2000. which outs connect to which ins?
AFAIK there is no disadvantage if the connections are done
in the Alsa tab, since both, the BCF and Ardour, don't use
Jack-Midi anyhow. The Midi tab shown in the Manual is
presumably the same as the Alsa tab today, the picture is
rather outdated. In Ardour I had to check 'Generic MIDI'
(options menu ->
control surfaces -> ...) before I could successfully
ctrl-middle-click the faders to assign them. Probably also
check 'feedback' for driving the motor faders.
yep, that did it. i got the faders and the panning knobs to work. i'm pretty
sure i know what to do now to get the rest going. thanks!
the other thing was to make sure MTC, MMC, and MIDI param control radio
buttons were set to the control port in preferences->MIDI. the ardour manual
seems to imply using the seq port, which didn't work. i'm not sure if all
need to be set to the control port, but at least one of them does. (the setup
that works is the default for new projects on version 2.8)
8:15 p.m.
On Mon, 19 Oct 2009, uhoh wrote:
On Monday 19 October 2009 10:40:57 am David Adler
wrote:
i'm using the ALSA tab with the default connections
For what it's worth, I was unable to get Ardour to slave to MTC/MMC from
an Akai MPC2000 going through QJackCtl's regular Alsa Midi tab (in 'seq'
mode, not 'raw'). Don't know if 'raw' would have helped or not, but
going to JackMidi *did*. It now works using JackMidi (from the QJackCtl
Jack Midi tab) and 'seq' ports in Ardour.
--
+ Brent A. Busby + "We've all heard that a million monkeys
+ UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ Physical Sciences Div. + Shakespeare. Now, thanks to the Internet,
+ James Franck Institute + we know this is not true." -Robert Wilensky
under the
ALSA tab i have the following out ports (in addition to my
sound card): MIDI 1 & 2 under the BCF2000 and control, mcu, & seq under
ardour. the in ports are the same for ardour, but i have MIDI 1, 2, & 3
for the BCF2000. which outs connect to which ins?
AFAIK there is no disadvantage if the connections are done
in the Alsa tab, since both, the BCF and Ardour, don't use
Jack-Midi anyhow. The Midi tab shown in the Manual is
presumably the same as the Alsa tab today, the picture is
rather outdated. In Ardour I had to check 'Generic MIDI'
(options menu ->
control surfaces -> ...) before I could successfully
ctrl-middle-click the faders to assign them. Probably also
check 'feedback' for driving the motor faders.
yep, that did it. i got the faders and the panning knobs to work. i'm pretty
sure i know what to do now to get the rest going. thanks!
the other thing was to make sure MTC, MMC, and MIDI param control radio
buttons were set to the control port in preferences->MIDI. the ardour manual
seems to imply using the seq port, which didn't work. i'm not sure if all
need to be set to the control port, but at least one of them does. (the setup
that works is the default for new projects on version 2.8) 
3:29 p.m.
Hi uhoh,
On Mon, Oct 19, 2009 at 1:52 PM, uhoh <uhoh(a)cox.net> wrote:
<snip>
under the ALSA tab i have the following out ports (in addition to my sound
card): MIDI 1 & 2 under the BCF2000 and control, mcu, & seq under ardour.
the
in ports are the same for ardour, but i have MIDI 1, 2, & 3 for the
BCF2000.
which outs connect to which ins?
Here's how it works for me and my BCR:
In QJackctl, my connections are like this:
Alsa tab:
BCR2000 MIDI 1 -> Ardour control
Ardour control -> BCR2000 MIDI 1
Ardour has Options>Control Surfaces> Generic Midi
&
Options>Control Surfaces>Controls> Feedback
both selected.
To assign a knob:
Ctrl+MidMouseClick on any parameter in the mixer or effect-edit & move a
BCR2000 knob.
Of course you have to use a preset on the BCR/BCF where knobs/faders send
out cc messages. :)
I think BCF's and BCR's both work the same...
Good luck ;-)
Peter
4:32 p.m.
On Mon, Oct 19, 2009 at 7:28 PM, Peter Geirnaert
<peter.geirnaert(a)gmail.com> wrote:
Here's how it works for me and my BCR:
In QJackctl, my connections are like this:
Alsa tab:
BCR2000 MIDI 1 -> Ardour control
btw, i have a question:
the BCF doesn't have touch sensitivity, so i can write automations,
and i can play back automations (with midi feedback). but "touch" mode
don't works (just a missing BCF functionality)
how i can send "touch signal" ? it' s a standard midi message? any
workarounds?
can i use my bcf in play mode, and then send this message to switch
from "play" to "touch", and then again from "touch" to
"play"?
thanks!
4:54 p.m.
On Mon, Oct 19, 2009 at 6:32 PM, becks <becks(a)msound.org> wrote:
On Mon, Oct 19, 2009 at 7:28 PM, Peter Geirnaert
<peter.geirnaert(a)gmail.com> wrote:
Is it AfterTouch (At)you're looking for? I use the BCMan program with wine
(http://home.hetnet.nl/~f2hmjvandenberg281/bcman.html) to edit mine, and
it's just setting up the type to "At" so using the edit button is just as
easy. Turn the Upper Left knob (TYPE) until you get At (after pressing
"edit" and moving the slider/knob you want to use for sending aftertouch).
Here it sends channel AfterTouch messages, on the channel set with the CH
knob.
Here's how it works for me and my BCR:
In QJackctl, my connections are like this:
Alsa tab:
BCR2000 MIDI 1 -> Ardour control
btw, i have a question:
the BCF doesn't have touch sensitivity, so i can write automations,
and i can play back automations (with midi feedback). but "touch" mode
don't works (just a missing BCF functionality)
how i can send "touch signal" ? it' s a standard midi message? any
workarounds?
can i use my bcf in play mode, and then send this message to switch
from "play" to "touch", and then again from "touch" to
"play"?
What do you mean by "touch" and "play"?
thanks!
Have a nice day :)
5:01 p.m.
On Mon, Oct 19, 2009 at 8:54 PM, Peter Geirnaert
<peter.geirnaert(a)gmail.com> wrote:
Is it AfterTouch (At)you're looking for?
i don't know if Aftertouch is the same "touch" midi message needed by
ardour
What do you mean by "touch" and
"play"?
the ardour automation modes
http://ardour.org/files/manual/ch-mixing.html
automation mode : off, play, write and touch
thanks!
ciao
5560
days inactive
5562
days old
linux-audio-user@lists.linuxaudio.org
10 comments
6 participants
participants (6)
-
becks -
Brent Busby -
David Adler -
munkeyfreenix batcat -
Peter Geirnaert -
uhoh