[LAU] OT: hardware problem Behringer FCB1010 and edirol USB midi adaptors.

Devin Anderson surfacepatterns at gmail.com
Tue Jan 29 05:50:42 UTC 2013


Hi Bill,

On Mon, Jan 28, 2013 at 5:55 PM, Bill Allen <bill at k2bea.org> wrote:

> My problem is that I've got 4 edirol usb midi interfaces of various types:
> UA-20, 2 UM-2, UM-30. They all work fine for passing a signal from a
> controller (keyboard, wind synth, FCB1010) to the computer via USB. On my
> desktop machine I've got a venerable MAudio 2496 with midi in/out and I've
> always had my FCB1010 hooked to it for programming (which unfortunately is a
> windows only program). Last week I decided to load a copy of winxp in a
> virtual machine on Ubuntu so I could get rid of my windows partition for
> good. The virtual windows doesn't seem to see my 2496 at all, so I thought
> I'd use one of the edirol interfaces for programming the FCB1010. I found
> that when I hooked the FCB1010 midi in to the UM-2 midi out, the FCB1010
> goes into error mode. This happens with every one of the edirol devices. The
> 2496 works fine with it, but not the edirol usb interfaces. It seems really
> far fetched that out of 4 devices the midi out is broken on all of them, but
> that's what the evidence is telling me unless I'm missing something. I'm
> pretty certain this isn't related to linux or its driver because I get the
> same response when booted to native windows.

I suggest using a MIDI monitor to check each step of the process to
make sure that each component involved in outputting MIDI messages is
outputting the correct bytes.  Possible monitoring points include:

* MIDI produced by the application that communicates with the FCB1010
(if this isn't possible inside the virtual machine, then try running
the application in `wine`)
* MIDI output by the virtual machine (I'm not sure if you can create a
virtual sound card for a VM or not)
* MIDI output by the MIDI interface (use a MIDI split device, or,
possibly, the MIDI thru port of the FCB1010)

I'd be interested in knowing if the problem goes away if you run the
program via `wine`.

-- 
Devin Anderson
surfacepatterns (at) gmail (dot) com

blog - http://surfacepatterns.blogspot.com/
midisnoop - http://midisnoop.googlecode.com/
psinsights - http://psinsights.googlecode.com/
synthclone - http://synthclone.googlecode.com/


More information about the Linux-audio-user mailing list