3 Mar
2005
3 Mar
'05
2:38 p.m.
Hi,
how boring: I simply plugged it in and all ports appeared in
aconnect.
OK, OK, I have installed all necessary software one day
before ;-) .
Anyway: That's really cool. Thanks to all developers,
especially the ALSA team, Takashi Iwai for the famous
snd-usb-driver and of course Clemens Ladisch for his work on
loading the firmware making usage of midisports a joy.
Thanks!
One question: The midisport 8x8 can be used as a programmable
patchbay in offline use. I used the windows driver panel to
set it as desired. But of course I'd like to do this using
Linux.
In ALSA, there appeared two additional control ports. Are
there any sysex commands which can be used to set up the
midisport 8x8 patchbay?
Best regards
ce
4 Mar
4 Mar
5:12 a.m.
Christoph Eckert wrote:
One question: The midisport 8x8 can be used as a
programmable
patchbay in offline use. I used the windows driver panel to
set it as desired. But of course I'd like to do this using
Linux.
In ALSA, there appeared two additional control ports.
Two? Not one?
Are there any sysex commands which can be used to set
up the
midisport 8x8 patchbay?
Yes.
(I don't know what they are, so I was lucky that you didn't ask for
them. ;-)
Regards,
Clemens
1:56 p.m.
Hi,
sorry, I meant 1 readable and one writable port:
aconnect -i
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 88: 'MidiSport 8x8' [type=kernel]
0 'MidiSport 8x8 MIDI 1'
1 'MidiSport 8x8 MIDI 2'
2 'MidiSport 8x8 MIDI 3'
3 'MidiSport 8x8 MIDI 4'
4 'MidiSport 8x8 MIDI 5'
5 'MidiSport 8x8 MIDI 6'
6 'MidiSport 8x8 MIDI 7'
7 'MidiSport 8x8 MIDI 8'
8 'MidiSport 8x8 Control'
aconnect -o
client 88: 'MidiSport 8x8' [type=kernel]
0 'MidiSport 8x8 MIDI 1'
1 'MidiSport 8x8 MIDI 2'
2 'MidiSport 8x8 MIDI 3'
3 'MidiSport 8x8 MIDI 4'
4 'MidiSport 8x8 MIDI 5'
5 'MidiSport 8x8 MIDI 6'
6 'MidiSport 8x8 MIDI 7'
7 'MidiSport 8x8 MIDI 8'
8 'MidiSport 8x8 Control'
hehe, of course I wanted to ask but I guessed that noone would
know anything.
I asked m-audio via mail, but I was told that I can only set
it up via the mac or win control panel software.
So I opened the win control panel executable in a hex editor
and searched for the m-audio sysex ID. I found some bytes,
but to be honest I fear I could damage my recent investment.
And to be honest again, I feel that it not will last long
until I'll try it out ;-) .
The panel reads the contents of the midisport at startup, so I
guess the bytes in the executable are sysex request files.
I'll sent some of them to the control input, and hopefully
the midisport will return the memory contents (which then can
be easily analysed).
Best regards
ce
In ALSA, there
appeared two additional control ports.
Two? Not one? Are there any
sysex commands which can be used to set up
the midisport 8x8 patchbay?
Yes.
(I don't know what they are, so I was lucky that you didn't
ask for them. ;-)
5 Mar
5 Mar
5:47 p.m.
Are there any
sysex commands which can be used to set up
the midisport 8x8 patchbay?
Yes.
(I don't know what they are, so I was lucky that you didn't
ask for them. ;-)
9 Mar
9 Mar
4:31 a.m.
Christoph Eckert wrote:
Should I publish the sysex info somewhere
Of course!
(any wiki?)
http://alsa.opensrc.org/
or is it intellectual property of m-audio?
Interface information like this isn't copyrightable.
Regards,
Clemens
2:30 p.m.
Hi,
the specs are now available at
http://alsa.opensrc.org/index.php?page=USBMidiDevices
Best regards
ce
10 Mar
10 Mar
3:38 p.m.
New subject: [linux-audio-user] Delta 1010/ALSA fluke
Hello. I wonder if anybody has any ideas on this one:
I'm running a gentoo 2.4 kernel with a Delta 1010 sound card, wrote an
asound.conf to route audio to various channels for multiple instances of
mplayer - very cool - but this fluke happened this morning that it'd be
awesome to understand...
I got in and it had been looping three mplayer videos (mpgs) all night.
They had gotten janky, ie: weren't really playing anymore, so I did a
killall mplayer - nice. Then I tested some play back, one at a time, of the
same movies. They routed fine, everything was great, except, on analog
outputs 3, 5 and 7 (not 1), the audio was a little garbled. Like a digital
garble type of thing almost sounding like a sample rate mismatch or
something. I tested with an .mp3 and the same happened, and I tested an mp3
with alsaplayer and it happened, and then I did the tests again, and the
second time, the .mp3 and the alsaplayer instance didn't do the weird thing,
but the .mpgs still did it.
So I rebooted it and it went away. *shrug*
Anybody have any ideas on that?
-----------------
Aaron Trumm
www.nquit.com
-----------------
4:11 p.m.
New subject: [linux-audio-user] Delta 1010/ALSA fluke
On 10 March 2005 at 11:41, "Aaron Trumm" <aaron(a)nquit.com> wrote:
So I rebooted it and it went away. *shrug*
Maybe next time, if there is one, you can just try to restart ALSA
rather than reboot. If ALSA restart doesn't work, then try some
other things, I wouldn't know what, to see if you can get it going
again. This is just a generic debugging method that I'll use in lieu
of reboots. It sure helps to isolate where the problem might be,
whereas a reboot obscures where the problem might be.
G'luck....
--
Kevin
6:15 p.m.
New subject: [linux-audio-user] Delta 1010/ALSA fluke
Maybe next time, if there is one, you can just try to
restart ALSA
rather than reboot. If ALSA restart doesn't work, then try some
other things, I wouldn't know what, to see if you can get it going
again. This is just a generic debugging method that I'll use in lieu
of reboots. It sure helps to isolate where the problem might be,
whereas a reboot obscures where the problem might be.
yes I should try that - thanks :) I'm going to try recreating the problem
tonight. I'm not sure if I'll ever see it again or not...
7200
days inactive
7207
days old
linux-audio-user@lists.linuxaudio.org
8 comments
4 participants
participants (4)
-
Aaron Trumm -
Christoph Eckert -
Clemens Ladisch -
Kevin Cosgrove