7 Jun
2005
7 Jun
'05
1:06 p.m.
Hi
Whats the best midi/usb interface for Linux.
I have seen a few midiman 2's on ebay.
I have to now get into Midi for my Linux studio, I have a cheap yamaha
keyboard with Midi out and would like to try out Rosegarden
with this.
Cheers
Bob
7 Jun
7 Jun
2:57 p.m.
Whats the best midi/usb interface for Linux.
This depends ;-) .
I have seen a few midiman 2's on ebay.
At least the m-audio midispocht 8x8 needs a firmware loaded,
and AFAIK this is also valid for the 4x4 and 2x2s.
Works fine with the loader from Clemens Ladisch (see
sourceforge.net), but it is an extra step to install.
I also run an Edirol UM-1S which works very well without any
firmware loading. AFAIK it is meanwhile sold out. But Edirol
has successors, I guess these should work fine.
Best regards
ce
3:28 p.m.
At least the m-audio midispocht 8x8 needs a firmware
loaded,
and AFAIK this is also valid for the 4x4 and 2x2s.
.. as the 1x1 does. It works very well.
Works fine with the loader from Clemens Ladisch (see
sourceforge.net), but it is an extra step to install.
The installation works as discribed, perfectly. The firmware can be
extracted with wine :)
Regards,
Georg.
4:02 p.m.
I'm running a Midisport 2x2 with seq24 on Ubuntu (Pentium II 333
laptop) and the MIDI timing is rock solid! I could not even achieve
such reliable MIDI timing with the latest driver for the device
running a new version of Cubase on Windows (and a significantly more
powerful computer!). Highly recommended!
On 6/7/05, Christoph Eckert <mchristoph.eckert(a)t-online.de> wrote:
The installation works as discribed, perfectly.
The
firmware can be extracted with wine :)
Yeah, I have to agree: Well prepared and the installation
script run *very* fine on my gentoo box. Well done.
Best regards
ce
4:04 p.m.
Hi,
I'm not sure why, but just plugging the midisport 2x2 on my planetCCRMA
FC2 setup makes it work. No extracting firmware or anything....
Andres
On Tue, 2005-06-07 at 12:30, Georg Rudolph wrote:
At least the
m-audio midispocht 8x8 needs a firmware loaded,
and AFAIK this is also valid for the 4x4 and 2x2s.
.. as the 1x1 does. It works very well.
Works fine with the loader from Clemens Ladisch
(see
sourceforge.net), but it is an extra step to install.
The installation works as discribed, perfectly. The firmware can be
extracted with wine :)
Regards,
Georg.
4:32 p.m.
My experience too.
Nice to see the maturity of Gnu/Linux, esp. with regards to drivers. I've
got a BestData USB modem that simply works in Linux, and I can't even get
it to install under Windows XP Pro. SP2, and believe me I've tried all the
tricks I know.
Frank
Hi,
I'm not sure why, but just plugging the midisport 2x2 on my planetCCRMA
FC2 setup makes it work. No extracting firmware or anything....
Andres
On Tue, 2005-06-07 at 12:30, Georg Rudolph wrote:
> >At least the m-audio midispocht 8x8 needs a firmware loaded,
> >and AFAIK this is also valid for the 4x4 and 2x2s.
> >
> >
> .. as the 1x1 does. It works very well.
> >Works fine with the loader from Clemens Ladisch (see
> >sourceforge.net), but it is an extra step to install.
> >
> >
> The installation works as discribed, perfectly. The firmware can be
> extracted with wine :)
>
> Regards,
> Georg.
>
>
5:51 p.m.
I successfully use ESI RoMIO (2x1 $49). Actually I wanted to buy ESI
M4U (4x4 $99), but they are out of stock here for now :(
All ESI interfaces are class-compliant and are seen by the standard
usb-audio driver.
IMHO Midisport is expensive, bulky and needs firmware to be loaded.
6:25 p.m.
IMHO Midisport is expensive, bulky and needs firmware
to be
loaded.
Maybe. But the 8x8 has a true patchbay which can be connected
in any way you like.
The Edirol 880 seems to be the same, but it isn't. It can
actually do connections as you like, but it can only do 1
merging connection per patch. It's a hard limitation as soon
as you want to independent from your computer. And it is more
expensive than the Midisport.
Best regards
ce
6:11 p.m.
HI
Now that I like.
If that works ok I can concentrate on getting midi working,
seems a bit of a black art to me at the moment.
Thanks for all the advice
Bob
On Tue, 2005-06-07 at 13:06 -0500, Andres Cabrera wrote:
Hi,
I'm not sure why, but just plugging the midisport 2x2 on my
planetCCRMA
FC2 setup makes it work. No extracting firmware or anything....
Andres
8 Jun
8 Jun
12:04 p.m.
At 19:30 +0200 7/6/05, Georg Rudolph wrote:
>At least the m-audio midispocht 8x8 needs a
firmware loaded,
>and AFAIK this is also valid for the 4x4 and 2x2s.
i have a midisport 2x2, it requires a firmware loader (no problems),
but it only ends up providing -one- MIDI port for some reason, not
two.. dunno why, but just thought i'd give you a headsup.
--
;
Jay Vaughan
12:16 p.m.
Jay Vaughan wrote:
i have a midisport 2x2, it requires a firmware loader
(no problems),
but it only ends up providing -one- MIDI port for some reason, not
two.. dunno why, but just thought i'd give you a headsup.
Hardware/firmware version problem, maybe ? My 2x2 performs as
advertised, no problems at all.
Best,
dp
10 Jun
10 Jun
9:16 a.m.
At 17:33 +0200 8/6/05, Clemens Ladisch wrote:
Jay Vaughan wrote:
the midisport_firmware-0.5 loader, with the 'extractfirmware.c'
approach (off USB22LDR.SYS) ...
i have a midisport 2x2, it requires a firmware
loader (no problems),
Which loader?
What's the output of "amidi -l" and
"playmidi -l"?
amidi -l:
Device Name
hw:1,0,0 MidiSort 2x2 MIDI 1
hw:1,0,1 MidiSort 2x2 MIDI 2
ls -l /dev/midi
crw-rw---- 1 root audio 14,18 Jun 10 13:05 /dev/midi1
i think udev is only creating one dev node, when it should be
creating two .. i'll try the ez-usb-midi loader next and see if that
helps ..
--
;
Jay Vaughan
1:12 p.m.
Jay Vaughan wrote:
amidi -l:
Device Name
hw:1,0,0 MidiSort 2x2 MIDI 1
hw:1,0,1 MidiSort 2x2 MIDI 2
Does it really say "MidiSort" without "p"? :-)
ls -l /dev/midi
crw-rw---- 1 root audio 14,18 Jun 10 13:05 /dev/midi1
i think udev is only creating one dev node, when it should be
creating two ..
There is a limit of eight MIDI devices per card, so the snd-usb-audio
driver makes multiple ports available as subdevices that are
multiplexed through one device node. This works fine when using the
ALSA API, but the OSS API is too simple for that. (Using /dev/midi01
will open the first free subdevice.)
You can load the snd-virmidi driver and connect its ports to the
MidiSport ports. (This works for any sequencer ports that you want to
access as an OSS /dev/midi* file).
i'll try the ez-usb-midi loader next and see if
that helps ..
This isn't a firmware issue.
HTH
Clemens
8 Jun
8 Jun
5:50 a.m.
Frank smith wrote:
Whats the best midi/usb interface for Linux.
All interfaces from Edirol, ESI, Yamaha, and M-Audio, and the
Audiotrak XP MIDI Mate work. With the latest ALSA 1.0.9, Emagic
interfaces and the MOTU Fastlane work, too.
All M-Audio interfaces except the 2x4 need the firmware loader from
<http://usb-midi-fw.sf.net/> (which seems to be included with
PlanetCCRMA).
HTH
Clemens
9:44 a.m.
Greetings:
Since my desktop machine is down for a while I'm really digging into
what's possible on my laptop. I have a MidiSport 2x2 on the USB port, it
works like a champ when I want to drive the external rack gear.
Configuring the 2x2 is easy-easy, I wrote a little shell script to load
the firmware after I start an X session, it works fine. And like many
others on this list I must also thank Clemens Ladisch for his valuable
assistance.
However, all is not joy and rapture here in Linux MIDIland. There are
some annoyances I'd like to resolve, perhaps some of you can suggest
some resolutions to these problems:
1. I put the USB driver on the blacklist in /etc/hotplug/blacklist
to force a particular ordering of my cards. I load the driver and
firmware with this script:
echo "Loading MidiSport firmware..."
modprobe snd-usb-audio
fxload -I /usr/share/usb/ezusbmidi/ezusbmidi2x2.ihx -D
/proc/bus/usb/001/003
echo "Done !"
Can I automate this so I don't have to use the script ? It's not a
big deal, but it would eliminate a small step in setting up my system.
2. The firmware script requires a USB ID. Is there some way to have
the script find that number, instead of me having to look it up via 'cat
/proc/bus/usb' ?
3. More of a seq24 problem, but: When I start seq24 and load a
previous session I *must* have my synths loaded in their original order,
else I have to reassign every sequence port/channel to the new ordering,
which can be a real pain. Is there anyone else who would like to see
more flexibility in relocating device numbers ? I'm thinking that it's
much easier to redefine one device's ID than to redefine potentially
hundreds of sequence patterns.
So it's back to the hack, and I hope everyone else has as much fun as
I'm having with contemporary Linux MIDI.
Best,
dp
Clemens Ladisch wrote:
Frank smith wrote:
Whats the best midi/usb interface for Linux.
All interfaces from Edirol, ESI, Yamaha, and M-Audio, and the
Audiotrak XP MIDI Mate work. With the latest ALSA 1.0.9, Emagic
interfaces and the MOTU Fastlane work, too.
All M-Audio interfaces except the 2x4 need the firmware loader from
<http://usb-midi-fw.sf.net/> (which seems to be included with
PlanetCCRMA).
HTH
Clemens
11:29 a.m.
Dave Phillips wrote:
1. I put the USB driver on the blacklist in
/etc/hotplug/blacklist
to force a particular ordering of my cards.
You don't need to put the driver into the blacklist to force a
particular ordering. Just make sure that all driver modules have
correct "index" parameters in /etc/modprobe.conf (or whatever module
configuration file your distribution uses):
options snd-whatever index=0
options snd-usb-audio index=1
I load the driver and firmware with this script:
modprobe snd-usb-audio
fxload -I /.../ezusbmidi2x2.ihx -D /proc/bus/usb/001/003
In theory, snd-usb-audio should be loaded after the firmware.
Can I automate this so I don't have to use the
script ?
Put the script into /etc/hotplug/usb, and create another file named
scriptname.usermap containing the vendor/product IDs of the device.
The files I'm using in the loader for M-Audio's closed source firmware
are available here:
<http://cvs.sourceforge.net/viewcvs.py/usb-midi-fw/midisport-firmware/>
2. The firmware script requires a USB ID. Is there
some way to have
the script find that number, instead of me having to look it up via 'cat
/proc/bus/usb' ?
The kernel passes the usbfs file name to the hotplug script in the
environment variable DEVICE. (fxload will use this variable by
default.)
3. More of a seq24 problem, but: When I start
seq24 and load a
previous session I *must* have my synths loaded in their original order,
else I have to reassign every sequence port/channel to the new ordering,
which can be a real pain. Is there anyone else who would like to see
more flexibility in relocating device numbers ?
You could try "modprobe snd-seq-dummy ports=10" and connect those
ports by hand to your synths, but then you'd have quite unintuitive
port names.
I'm thinking that it's much easier to redefine
one device's ID
Currently, ALSA doesn't allow to choose/change the client number of
software synthesizers.
than to redefine potentially hundreds of sequence
patterns.
It would be nice if sequencers would support assigning ports by name.
The MMA has defined a meta event for this, but AFAIK nobody uses it.
Regards,
Clemens
1:42 p.m.
Hi,
Sorry to hijack on this thread but I gotta ask. Could
someone explain how they are extracting the midiman
8x8 firmware?
I don't own a windows machine. I could probably
arrange to borrow one but I prefer not to.
Anyway, I installed wine-20050524-1fc3winehq and then
ran 'wine MS8x8_1010_web.exe', as root and normal
user, which both result in a window that momentarily
pops up and seems to say "initializing ...".
Unfortunately USB88LDR.SYS isn't extracted.
I also tried using wineconsol because I thought there
might be some error reporting or something but no luck
with that.
ron
__________________________________
Discover Yahoo!
Get on-the-go sports scores, stock quotes, news and more. Check it out!
http://discover.yahoo.com/mobile.html
3:24 p.m.
Hi,
Sorry to hijack on this thread but I gotta ask. Could
someone explain how they are extracting the midiman
8x8 firmware?
if you tell me which files (filename) you need I'll send you
mine and you're done.
I once installed Win 98 only to extract the FW and want
prevent you from doing the same, but I do not remember which
files have been the FW.
Best regards
ce
7:02 p.m.
Hi Christoph,
--- Christoph Eckert <mchristoph.eckert(a)t-online.de>
wrote:
Hi,
Someone else hooked me up. It saved me a bunch of
time. Thank you!
ron
Sorry to hijack on this thread but I gotta ask.
Could
someone explain how they are extracting the
midiman
8x8 firmware?
if you tell me which files (filename) you need I'll
send you
mine and you're done.
I once installed Win 98 only to extract the FW and
want
prevent you from doing the same, but I do not
remember which
files have been the FW. Best regards
ce
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
8:31 p.m.
New subject: [linux-audio-user] Extracting midiman 8x8 firmware
>Sorry to hijack on this thread but I gotta ask.
>
>
>Could someone explain how they are extracting the
>
>
>midiman 8x8 firmware?
>
>
I actually just typed the filename USB88LDR.SYS into google, in case
this speeds up anyone finding a solution to this in future. :-)
--
Darren
NZ
8:47 p.m.
New subject: [linux-audio-user] Extracting midiman 8x8 firmware
On Thu, Jun 09, 2005 at 10:37:06AM +1200, Darren Inwood wrote:
run the installer in vmware or wine, or try unrarring the installer exe..
>Sorry to hijack on this thread but I gotta
ask.
>
>
>Could someone explain how they are extracting the
>
>
>midiman 8x8 firmware?
>
>
I actually just typed the filename USB88LDR.SYS into google, in case
this speeds up anyone finding a solution to this in future. :-)
--
Darren
NZ
7108
days inactive
7111
days old
linux-audio-user@lists.linuxaudio.org
24 comments
13 participants
participants (13)
-
Andres Cabrera -
Christoph Eckert -
Clemens Ladisch -
Darren Inwood -
Dave Phillips -
Dmitry Baikov -
Frank smith -
Georg Rudolph -
ix＠replic.net -
Jay Vaughan -
pirrone＠localnet.com -
R Parker -
Stephen Ceresia