Hi,
--- Chris Cannam <[EMAIL PROTECTED]> wrote:
> R Parker wrote:
> > However, it appears that Rosegarden writes its
> output
> > to alsa-midi-device:outputs when it should be
> writing
> > to alsa-midi-device:inputs.
>
> I'm not entirely clear on your terminology here.
Sorry about that, it was late and these are new
interfaces and describing them is a learned talent.
> Can you perhaps
> send a list of the ALSA clients and ports (say, as
> reported by
> rosegardensequencer when you start it up -- or
> whatever) and
> indicate which ones you're referring to?
We'll try to describe what we're doing and how it
works and based on that, how we'd expect rosegarden to
participate in the alsa midi environment.
>aconnect -lio
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
Connecting To: 128:0, 129:0
client 72: 'Rawmidi 1 - MidiSport 8x8' [type=kernel]
0 'MidiSport 8x8 Port 0'
1 'MidiSport 8x8 Port 1'
2 'MidiSport 8x8 Port 2'
3 'MidiSport 8x8 Port 3'
4 'MidiSport 8x8 Port 4'
5 'MidiSport 8x8 Port 5'
6 'MidiSport 8x8 Port 6'
7 'MidiSport 8x8 Port 7'
8 'MidiSport 8x8 Port 8'
client 80: 'Virtual Raw MIDI 2-0' [type=kernel]
0 'VirMIDI 2-0 '
client 81: 'Virtual Raw MIDI 2-1' [type=kernel]
0 'VirMIDI 2-1 '
client 82: 'Virtual Raw MIDI 2-2' [type=kernel]
0 'VirMIDI 2-2 '
client 83: 'Virtual Raw MIDI 2-3' [type=kernel]
0 'VirMIDI 2-3 '
We have a Tascam DM-24 digital mixing consol from
which we send mmc transport instructions. The DM-24
midi-out is connected to the midisport 8x8 input:2
--as seen by aconnect this is the input side of "1
'MidiSport 8x8 Port 1'". With this connection, when
DM-24 Play is engaged the 8x8 green (input) lite will
flash when that data passes through.
In our studio, we route the DM-24 mmc instruction to
Ardour via /dev/snd/midiC2D0 file. We're sending
deferred play. The following is that route created
using alsa-patch-bay
DM-24 MMC Route
Subscription 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 1' -> 'Virtual Raw MIDI 2-0::VirMIDI 2-0'
succeeded
When the Ardour transport engages play, it generates
and transmits MTC. Here's the route used to return MTC
to the DM-24:
Ardour MTC Route
'Virtual Raw MIDI 2-0::VirMIDI 2-0' -> 'Rawmidi 1 -
MidiSport 8x8::MidiSport 8x8 Port 1'
The MTC is used to sync the Ardour and DM-24
transports.
Of course we create the VirMIDI devices in alsa.conf
using:
alias snd-card-2 snd-virmidi
alias sound-slot-2 snd-card-2
options snd-virmidi index=2
In Ardour we've got the ardour.rc file. Here's the
line that tells ardour which file to read and write
to:
<MIDI-port tag="midisport" device="/dev/snd/midiC2D0"
type="alsa/raw" mode="duplex"/>
So, a concise method for routing midi incoming and
outgoing instructions is created. This is vital
because the instructions can be routed to any inputs
and outputs.
Consider RoseGarden with MTC slave capabilities.
Ardour transmits MTC the DM-24 via 'Virtual Raw MIDI
2-0::VirMIDI 2-0' -> 'Rawmidi 1 - MidiSport
8x8::MidiSport 8x8 Port 1' but Ardour's MTC can also
be routed to RoseGarden via 'Virtual Raw MIDI
2-0::VirMIDI 2-0' -> 'Virtual Raw MIDI 2-1::VirMIDI
2-1'
If RoseGarden were able to participate in the routing
environment as demonstrated above, then users could
configure its messages to go anywhere and only where
they require.
Know what I mean?
ron, dana
I have a
> midisport 2x2
> myself but I rarely use it at the moment and I can't
> remember how
> its ports are configured or what they're called.
>
> This is more Rich's area than mine, but I'd like to
> be clear on
> what's required here too.
>
> (Glancing at the RG code, it appears that system
> messages like
> MIDI clock ones are sent to every duplex ALSA port.
> I'm not quite
> sure why only duplex ones and not write-only ones
> too.)
>
>
> Chris
>
>
>
>
-------------------------------------------------------
> This SF.net email is sponsored by: eBay
> Get office equipment for less on eBay!
> http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
> _______________________________________________
> Rosegarden-devel mailing list
> [EMAIL PROTECTED] - use the
> link below to unsubscribe
>
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
Rosegarden-devel mailing list
[EMAIL PROTECTED] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
