This has me stumped. What OS are you using? If its Vista, maybe that's the problem. Did you try the e-mu 1x1 driver that someone suggested in that thread?
If e-loader works properly to transfer patterns (or even just to get the names or reports a valid midi connection), it would seem that you do indeed have 2-way midi communication set up. (No need to test with midi-ox.)
If your device is properly registered in the OS, it would show up as a device in your software--which evidently it does.
So what could be left as the cause of the problem? (That's the mystery.) I am out of suggestions--other than trying a different interface. Hope that works.
Footenote: years ago I picked up a bunch of midiman sound card cables (unopened). (I was going to network a bunch of old Windows 98 machines as midi devices.) This cable should work if you already had a sound card with a joystick sound card and a couple of standard male-male 5-pin din midi cables. But, it seems like getting a new interface would be a better route, unless you can borrow one from someone.
Steve
--- In xl7@yahoogroups.com, "lutherblisset63" <lutherblisset63@...> wrote:
>
> I think it might a driver or compatibility issue. A quick search revealed people using the exact cable have had issues:
>
> http://www.thewinforums.com/threads/17054-Help!-My-USB-MIDI-Cable-won%27t-work-anymore
>
> If I load the xl-7 normally (not holding enter) I can do a midi can e-loader and the xl-7 shows up, and it seems to be receiving and sending. If I then restart and try to load the prep file I it says no midi device is connected. At any rate, I think I'll probably just try another interface / computer from here on in. I have no idea what's going on.
>
> "Do you have sequencing software that captures and sends sysex?"
>
> I think I have a midi-ox or something similar, not too familiar with it. I also have a kenton hardware controller that is capable of sending sysex. Are you asking to see if I could test if the cable was transmiting sysex?
>
>
>
> --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@> wrote:
> >
> > I have seen those usb/midi cables for sale, but I never ordered one.
> >
> > Yes, if you have an old sound card you would need a joystick port to midi cable. If you don't already have an old sound card, you might be better off using the money towards a higher end usb to midi solution.
> >
> > Another option might be to find someone in your area that has a PC-midi setup that can handle sysex and bring your e-mu there.
> >
> > It sounds like you have things set up correctly and I cannot understand why the midi interface would handle sysex only in one direction.
> >
> > Do you have sequencing software that captures and sends sysex?
> >
>
>
>
>
>
> > Steve
> >
> >
> > --- In xl7@yahoogroups.com, "lutherblisset63" <lutherblisset63@> wrote:
> > >
> > >
> > > Thanks for all the suggestions. I'll get there eventually :)
> > >
> > > Theoretically I have the proper connections. I using one of these:
> > > http://www.9mart.com/9dollar/Budget/EG1504-2-USB-to-MIDI-Cable.jpg
> > >
> > > Tried all combinations of ins and outs. No go.
> > >
> > > "Probably the cheapest way to go is if you have a soundcard with a joystick/midi port, all you would need is a joystick/midi cable."
> > >
> > > Is this likely to be more reliable then a cheap usb midi cable? From what I understand you would need a 15 pin to midi in /out as well anyhow. I see usb midi cables go for anything from $4 to $100 (mine was $10.) Maybe if go from a better cable I'll have more luck.
> > >
> > >
> > > "Do you have 1.16 or lower already installed on your CS; you will have to refer to the prereadme.txt below."
> > >
> > > Yeah I'm following that. I've been trying to load the commandprep file.
> > >
> > >
> > >
> > >
> > > --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@> wrote:
> > > >
> > > > Good point. Midi is one way (from Device 1 Out to Device 2 In). So, in order to have a complete midi loop you need the following:
> > > >
> > > > (1) Computer Midi Out --> E-Mu Midi In
> > > > (2) E-Mu Midi Out --> Computer Midi In
> > > >
> > > > I am not sure if you need to use Port A Out on your E-Mu, but that's how my P2500 is set up.
> > > >
> > > > Also, it doesn't hurt to try different midi cables, in case that's a source of the problem. And if the usb interface is configurable, check that as well.
> > > >
> > > > Steve
> > > >
> > > > --- In xl7@yahoogroups.com, "jbgange" <jbgange@> wrote:
> > > > >
> > > > >
> > > > > Don't know if I'm too late for this but I just updated my OS to ver. 2 and initially had a problem. The computer didn't see the MP-7. I was using a usb to midi cable and had the out midi cable connected to the out of the MP-7, the in cable to the in socket. Nothing happened so I switch the out cable to the in midi socket and vice versa. I rescanned for midi devices and there it was. 5 minutes later it was done. Maybe your cables are backwards like mine were.
> > > > > Cheers
> > > > > Jim
> > > > > --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@> wrote:
> > > > > >
> > > > > > Ooops--typo.
> > > > > > It should read: ". . . I'd say perhaps your >>PC<< is not receiving sysex."
> > > > > >
> > > > > >
> > > > > > --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@> wrote:
> > > > > > >
> > > > > > > Yeah--OS2.0 is much better.
> > > > > > >
> > > > > > > If e-loader's midi monitor is receiving sysex, but (1) nothing shows up when you "scan for midi device" and (2) you cannot download the names of patterns into e-loader, then I'd say perhaps your CS is not receiving sysex.
> > > > > > >
> > > > > > > Do you have software that can capture sysex (such as midiox or a sequencer like cakewalk)? If so try to send a data dump (e.g., a single preset) from the CS to the software. Does your PC capture the sysex data?
> > > > > > >
> > > > > > > Just making sure:
> > > > > > > (1) you have a complete midi circuit, right? (both PC -> CS and CS -> PC)
> > > > > > > (2) both the CS and e-loader are using sysex id = 000, right?
> > > > > > >
> > > > > > > Probably the cheapest way to go is if you have a soundcard with a joystick/midi port, all you would need is a joystick/midi cable.
> > > > > > >
> > > > > > > BTW, what are you using for a midi interface (maybe I missed it)? also, is the MPU-401 a card? If so, that should work.
> > > > > > >
> > > > > > > Steve
> > > > > > >
> > > > > > >
> > > > > > > --- In xl7@yahoogroups.com, "lutherblisset63" <lutherblisset63@> wrote:
> > > > > > > >
> > > > > > > > Thanks for the replies.
> > > > > > > >
> > > > > > > > Nothing shows up in scan for midi device and I'm also unable to see any patches etc. In 'midi monitor', however, it appears to be receiving sysex. Trying again today I was able to get the downloader to say the request had been received but when I click on download file, it says that no midi device is attached.
> > > > > > > >
> > > > > > > > Can anyone recommend a cable or interface (cheap) that is known to work? Some of the features in 2.0 look handy.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@> wrote:
> > > > > > > > >
> > > > > > > > > PS: A while ago, I diagnosed a problem relating to sysex ID and sequences not transferring with e-loader. I am not sure if any of this will help with the OS issue, but it might.
> > > > > > > > >
> > > > > > > > > See the last two items in http://launch.groups.yahoo.com/group/xl7/files/e-loader%20issues/ .
> > > > > > > > >
> > > > > > > > > Or, for the full discussion of the issue, see:
> > > > > > > > > http://launch.groups.yahoo.com/group/xl7/message/19949
> > > > > > > > >
> > > > > > > > > The analysis/solution is at:
> > > > > > > > > http://launch.groups.yahoo.com/group/xl7/message/19972
> > > > > > > > >
> > > > > > > > > Steve
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@> wrote:
> > > > > > > > > >
> > > > > > > > > > In e-loader, does "Scan Midi Device" show that your E-Mu is successfully connected with 2 way communication and has the right sysex id (probably 0).
> > > > > > > > > >
> > > > > > > > > > You cannot use the usb connection on the E-Mu to upgrade OS and it does not function as a general usb device other than working with E-Mu's drivers and e-loader for transferring patterns and songs.
> > > > > > > > > >
> > > > > > > > > > As mibrilane mentions, I have heard that some interfaces can be problematic with sysex. I wonder if they filter out sysex by default. But if that were the case you, I would think that e-loader wouldn't work at all to transfer patterns. Can you get pattern names and download patterns with e-loader? Since it uses sysex to do those things, that should tell you whether or not the usb device is filtering out sysex.
> > > > > > > > > >
> > > > > > > > > > Hope this helps.
> > > > > > > > > >
> > > > > > > > > > Steve
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --- In xl7@yahoogroups.com, "lutherblisset63" <lutherblisset63@> wrote:
> > > > > > > > > > >
> > > > > > > > > > > I have both input and output set to usb device which appears when I plug usb/midi cable in. The only other option is mpu-401.
> > > > > > > > > > >
> > > > > > > > > > > Under the download button it always reads:
> > > > > > > > > > > "status: waiting for download request"
> > > > > > > > > > >
> > > > > > > > > > > Channel is set to 0 on both the command station and e-loader. Are there any other settings I'm not aware of.
> > > > > > > > > > >
> > > > > > > > > > > I have no other interface at present and would like to make sure its not the settings before I buy a new one.
> > > > > > > > > > >
> > > > > > > > > > > How would I attempt the usb only direct connection?
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > --- In xl7@yahoogroups.com, Mibrilane <mibrilane@> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Probably the first thing to check is that E-Loader is set to output to that interface. Step 1 before blaming equipment is to make sure the settings are correct.
> > > > > > > > > > > >
> > > > > > > > > > > > I assume you have checked this and also that you can get regular MIDI (notes, CCs) working fine with OS 1.x. I know I had to try several MIDI interfaces (MOTU FastLane, then my Korg padKONTROL, and finally the Novation ReMote SL Mk II) before E-Loader decided that it could do the OS 2 upgrade for my XL-7, and all three of those interfaces work just fine sending regular MIDI data, so at that point I'd wager it's your interface and either trying another one or even the USB direct connection (Windows only) will be your best bet.
> > > > > > > > > > > >
> > > > > > > > > > > > Beyond that, what is E-Loader saying - does it start doing the OS send, or does it say it can't communicate?
> > > > > > > > > > > >
> > > > > > > > > > > > On May 12, 2011, at 9:31 PM, lutherblisset63 wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > I'm having trouble upgrading to os 2.0 from 1.0. I downloaded the e-loader program and the prep file but when trying to upload the file I get no response. It seems the CS is sending midi but not receiving it (the midi out light blinks but no in and there is some data in the midi monitor ). It remains on "waiting for download request".
> > > > > > > > > > > > >
> > > > > > > > > > > > > Not sure what else to try. I'm using a generic usb to midi in/out cable, so it might be the cable but I have no way of testing it.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Any ideas appreciated. Thanks!
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Michael Brien Lane
> > > > > > > > > > > > mibrilane@
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>