5 May
2010
5 May
'10
9:45 a.m.
Hello. I'd like to take a stab at spying the protocol between the
Mackie C4 and the Mackie "C4 Commander" control software.
The plan is to put my Linux laptop between a Winmac running C4
Commander and the C4, start a MIDI capture and try to upload a
known .c4i layout to the C4.
____________ _______________ ________
| | | | | |
| OUT |--->| IN1----> OUT1 |--->| IN |
| Winmac | | Linux | | C4 |
| IN |<---| OUT2 <--- IN2 |<---| OUT |
|____________| |_______________| |________|
I need a small, light, 2-input, 2-output MIDI USB interface. Does
anyone have experience with the ESI RoMI/O II ?
--
André Majorel http://www.teaser.fr/~amajorel/
5 May
5 May
10:04 a.m.
On 05/05/10 11:45, Andre Majorel wrote:
Hello. I'd like to take a stab at spying the
protocol between the
Mackie C4 and the Mackie "C4 Commander" control software.
You don't have to. Check out the contrOSC source:
http://controsc.sourceforge.net/
Flo
--
Machines can do the work, so people have time to think.
public key DA43FEF4 x-hkp://wwwkeys.eu.pgp.net
2:34 p.m.
On 2010-05-05 12:04 +0200, Florian Faber wrote:
On 05/05/10 11:45, Andre Majorel wrote:
Thank you I don't think it's the same thing. The idea behind
contrOSC, as I understand it, is to leave the C4 in its default
configuration and translate the messages it sends to whatever the
synth expects.
I'm under the impression that, with C4 Commander, you can
reconfigure the C4 to send the right MIDI messages for the synth.
After that, the C4 can talk to your synth without a computer in
between. Or so I hope !
--
André Majorel http://www.teaser.fr/~amajorel/
Hello. I'd like to take a stab at spying the
protocol between the
Mackie C4 and the Mackie "C4 Commander" control software.
You don't have to. Check out the contrOSC source:
http://controsc.sourceforge.net/ 
3:06 p.m.
Andre Majorel wrote:
Hello. I'd like to take a stab at spying the
protocol between the
Mackie C4 and the Mackie "C4 Commander" control software.
The plan is to put my Linux laptop between a Winmac running C4
Commander and the C4, start a MIDI capture and try to upload a
known .c4i layout to the C4.
I need a small, light, 2-input, 2-output MIDI USB interface.
Any USB MIDI interface that works in Windows or OS X without separate
drivers also works in Linux.
Does anyone have experience with the ESI RoMI/O II ?
The non-II model works fine, although several ESI devices have design or
firmware bugs that must to be worked around in the driver.
The ESI website says:
| * Windows XP and Mac OS X compatible (Hardware Revision A and B)
| * Windows Vista and Windows 7 compatible (Hardware Revision B only)
It seems ESI finally found a reason to fix some of those bugs. :-)
Regards,
Clemens
17 May
17 May
6:47 a.m.
On 2010-05-05 17:06 +0200, Clemens Ladisch wrote:
Andre Majorel wrote:
Thanks. The ESI RoMI/O II works to some extent although the driver
only seems to see one interface, as far as I understand how MIDI
on Linux works these days :
$ find /dev/ -iname "*midi*"
/dev/dmmidi1
/dev/midi1
/dev/snd/midiC1D0
/dev/.udev/db/sound:midiC1D0
/dev/.udev/db/sound:dmmidi1
/dev/.udev/db/sound:midi1
Got to look into that.
--
André Majorel http://www.teaser.fr/~amajorel/
I need a small, light, 2-input, 2-output MIDI USB
interface.
Any USB MIDI interface that works in Windows or OS X without separate
drivers also works in Linux.
Does anyone have experience with the ESI RoMI/O
II ?
The non-II model works fine, although several ESI devices have design or
firmware bugs that must to be worked around in the driver.
7:47 a.m.
Andre Majorel wrote:
...
Thanks. The ESI RoMI/O II works to some extent although the driver
only seems to see one interface, as far as I understand how MIDI
on Linux works these days :
$ find /dev/ -iname "*midi*"
/dev/dmmidi1
/dev/midi1
/dev/snd/midiC1D0
Try "amidi -l" or "aplaymidi -l".
Regards,
Clemens
8:43 p.m.
On 2010-05-17 09:46 +0200, Clemens Ladisch wrote:
Andre Majorel wrote:
$ amidi -l
Dir Device Name
IO hw:1,0,0 RoMIO II MIDI 1
IO hw:1,0,1 RoMIO II MIDI 2
$ aplaymidi -l
Port Client name Port name
14:0 Midi Through Midi Through Port-0
20:0 RoMIO II RoMIO II MIDI 1
20:1 RoMIO II RoMIO II MIDI 2
That's better, thanks.
Now why are there 6 files ? What are they for ? Why don't any of
them seem to deal with the second interface ? This is exactly the
kind of information I was hoping to find in the MIDI howto but
didn't.
--
André Majorel http://www.teaser.fr/~amajorel/
...
Thanks. The ESI RoMI/O II works to some extent although the driver
only seems to see one interface, as far as I understand how MIDI
on Linux works these days :
$ find /dev/ -iname "*midi*"
/dev/dmmidi1
/dev/midi1
/dev/snd/midiC1D0
Try "amidi -l" or "aplaymidi -l".
18 May
18 May
7:52 a.m.
Andre Majorel wrote:
/dev/snd/midiC1D0 is the ALSA node for card 0, device 0.
/dev/midi1 is the OSS node for compatibility with old applications.
/dev/dmmidi1 is the same as /dev/midi1.
The .udev files are for internal bookkeeping of the udev daemon.
Andre Majorel
wrote:
> $ find /dev/ -iname "*midi*"
> /dev/dmmidi1
> /dev/midi1
> /dev/snd/midiC1D0
Now why are there 6 files ? What are they for ? Why don't any of them seem to deal with the second
interface ?
The ports are multiplexed through one device file as subdevices because
there is a limit of four MIDI devices per card in some circumstances.
Regards,
Clemens
5124
days inactive
5137
days old
linux-audio-user@lists.linuxaudio.org
7 comments
3 participants
participants (3)
-
Andre Majorel -
Clemens Ladisch -
Florian Faber