Yahoo Groups archive
Thread
2009-04-05 by joeyjoejoemagee
Hey all, Just been having trouble with e-loader. I have a bi directional Midi connection, and USB to my MP-7. all the USB drivers seem to be working fine. E-loader recognizes my MP7, and the sequences. But when I try to copy them to my computer, I get a message saying "Failed" every time. I've tried using a different MIDI interface, but still the same problem. Anyone experience the same problem or have any suggestions?
2009-04-05 by dwn4tupac
Yeah i have the exact same problem with my xl-7...that's why i don't sequence with it anymore. Dunno if it is the eloader version or what, but I tried mine w/ midi instead of usb too and no dice... makes me mad because the drag and drop was half the appeal of this unit. it basically makes backing up a huge pain in the ass. If you find a workaround or other solution let us know. --- In xl7@yahoogroups.com, "joeyjoejoemagee" <joeyjoejoemagee@...> wrote:
> > Hey all, > Just been having trouble with e-loader. > I have a bi directional Midi connection, and USB to my MP-7. all the USB drivers seem to be working fine. > E-loader recognizes my MP7, and the sequences. But when I try to copy them to my computer, I get a message saying "Failed" every time. I've tried using a different MIDI interface, but still the same problem. > > Anyone experience the same problem or have any suggestions? >
2009-04-06 by joeyjoejoemagee
Has anyone got E-loader to work? Is this a common problem? Could it be the operating system or midi interface? Are there older version of e-loader that might work? This is really freakin frustrating. I have an idea, I just got ableton live 7. I was think maybe I could set all the the mp-7 midi channels to send external, arm 16 midi channels (or how ever many needed) in ableton and record all the midi tracks at once, so at least I'd still have them in some form. But yeah, that could still be pretty time consuming. I'm starting to get into the 38% range in memory left. My mp is acting funny now too, like some external tracks cut out randomly, song mode acts really sketchy when writing songs. Will i continue to experience problems the more memory I use? Or is it just in my head? (I could still be a little scarred from a MC-307 a few years back) --- In xl7@yahoogroups.com, "dwn4tupac" <dwn4tupac@...> wrote:
> > Yeah i have the exact same problem with my xl-7...that's why i don't sequence with it anymore. Dunno if it is the eloader version or what, but I tried mine w/ midi instead of usb too and no dice... > makes me mad because the drag and drop was half the appeal of this unit. > it basically makes backing up a huge pain in the ass. > > If you find a workaround or other solution let us know. > > > --- In xl7@yahoogroups.com, "joeyjoejoemagee" <joeyjoejoemagee@> wrote: > > > > Hey all, > > Just been having trouble with e-loader. > > I have a bi directional Midi connection, and USB to my MP-7. all the USB drivers seem to be working fine. > > E-loader recognizes my MP7, and the sequences. But when I try to copy them to my computer, I get a message saying "Failed" every time. I've tried using a different MIDI interface, but still the same problem. > > > > Anyone experience the same problem or have any suggestions? > > >
2009-04-06 by Bruce Manning
From: joeyjoejoemagee
Subject: [xl7] Re: E-loader Help
To: xl7@yahoogroups.com
Date: Monday, April 6, 2009, 12:46 PM
Has anyone got E-loader to work? Is this a common problem? Could it be the operating system or midi interface? Are there older version of e-loader that might work? This is really freakin frustrating.
I have an idea,
I just got ableton live 7. I was think maybe I could set all the the mp-7 midi channels to send external, arm 16 midi channels (or how ever many needed) in ableton and record all the midi tracks at once, so at least I'd still have them in some form. But yeah, that could still be pretty time consuming.
I'm starting to get into the 38% range in memory left. My mp is acting funny now too, like some external tracks cut out randomly, song mode acts really sketchy when writing songs.
Will i continue to experience problems the more memory I use? Or is it just in my head? (I could still be a little scarred from a MC-307 a few years back)
--- In xl7@yahoogroups. com, "dwn4tupac" wrote:
>;
> Yeah i have the exact same problem with my xl-7...that' s why i don't sequence with it anymore. Dunno if it is the eloader version or what, but I tried mine w/ midi instead of usb too and no dice...
> makes me mad because the drag and drop was half the appeal of this unit.
> it basically makes backing up a huge pain in the ass.
>
> If you find a workaround or other solution let us know.
>
>
> --- In xl7@yahoogroups. com, "joeyjoejoemagee" wrote:
> >
> > Hey all,
> > Just been having trouble with e-loader.
> > I have a bi directional Midi connection, and USB to my MP-7. all the USB drivers seem to be working fine.
> >; E-loader recognizes my MP7, and the sequences. But when I try to copy them to my computer, I get a message saying "Failed" every time. I've tried using a different MIDI interface, but still the same problem.
> >
> > Anyone experience the same problem or have any suggestions?
> >
>
2009-04-06 by Bob S.
----- Original Message -----From: Bruce ManningSent: Monday, April 06, 2009 10:08 AMSubject: Re: [xl7] Re: E-loader Help
Hi,I have been using E-loader for years now. You should check the MIDI device setup and make sure the MIDI in and MIDI out are identified correctly. Check that the USB interface for the MP7, XL7, PX7, 2500 is being picked up properly as a USB device. In the E-Loader, then scan for devices, you should see the MP7 or one of the other devices noted. If you see the device identified in the scan function, you should be able to get to the Bank Browser or Sequence Browser.I use all but 2-3 % of my memory in the 2500. I do notice when it gets lower than that, there can be problems. I have all the MP7, XL7, and 2500 patterns as well as MIDI songs that I uploaded from E-Loader.
--- On Mon, 4/6/09, joeyjoejoemagee yahoo.com> wrote:From: joeyjoejoemagee yahoo.com>
Subject: [xl7] Re: E-loader Help
To: xl7@yahoogroups.com
Date: Monday, April 6, 2009, 12:46 PM
Has anyone got E-loader to work? Is this a common problem? Could it be the operating system or midi interface? Are there older version of e-loader that might work? This is really freakin frustrating.
I have an idea,
I just got ableton live 7. I was think maybe I could set all the the mp-7 midi channels to send external, arm 16 midi channels (or how ever many needed) in ableton and record all the midi tracks at once, so at least I'd still have them in some form. But yeah, that could still be pretty time consuming.
I'm starting to get into the 38% range in memory left. My mp is acting funny now too, like some external tracks cut out randomly, song mode acts really sketchy when writing songs.
Will i continue to experience problems the more memory I use? Or is it just in my head? (I could still be a little scarred from a MC-307 a few years back)
--- In xl7@yahoogroups. com, "dwn4tupac" wrote:
>
> Yeah i have the exact same problem with my xl-7...that' s why i don't sequence with it anymore. Dunno if it is the eloader version or what, but I tried mine w/ midi instead of usb too and no dice...
> makes me mad because the drag and drop was half the appeal of this unit.
> it basically makes backing up a huge pain in the ass.
>
> If you find a workaround or other solution let us know.
>
>
> --- In xl7@yahoogroups. com, "joeyjoejoemagee" wrote:
> >
> > Hey all,
> > Just been having trouble with e-loader.
> > I have a bi directional Midi connection, and USB to my MP-7. all the USB drivers seem to be working fine.
> > E-loader recognizes my MP7, and the sequences. But when I try to copy them to my computer, I get a message saying "Failed" every time. I've tried using a different MIDI interface, but still the same problem.
> >
> > Anyone experience the same problem or have any suggestions?
> >
>
2009-04-06 by Bruce Manning
From: Bob S.
Subject: Re: [xl7] Re: E-loader Help
To: xl7@yahoogroups.com
Date: Monday, April 6, 2009, 1:45 PM
Hi BruceJust as a reference point, what windows version are you using?ThanksBobEl Segundo, CA----- Original Message -----From: Bruce ManningSent: Monday, April 06, 2009 10:08 AMSubject: Re: [xl7] Re: E-loader HelpHi,I have been using E-loader for years now. You should check the MIDI device setup and make sure the MIDI in and MIDI out are identified correctly. Check that the USB interface for the MP7, XL7, PX7, 2500 is being picked up properly as a USB device. In the E-Loader, then scan for devices, you should see the MP7 or one of the other devices noted. If you see the device identified in the scan function, you should be able to get to the Bank Browser or Sequence Browser.I use all but 2-3 % of my memory in the 2500. I do notice when it gets lower than that, there can be problems. I have all the MP7, XL7, and 2500 patterns as well as MIDI songs that I uploaded from E-Loader.
--- On Mon, 4/6/09, joeyjoejoemagee wrote:From: joeyjoejoemagee
Subject: [xl7] Re: E-loader Help
To: xl7@yahoogroups. com
Date: Monday, April 6, 2009, 12:46 PM
Has anyone got E-loader to work? Is this a common problem? Could it be the operating system or midi interface? Are there older version of e-loader that might work? This is really freakin frustrating.
I have an idea,
I just got ableton live 7. I was think maybe I could set all the the mp-7 midi channels to send external, arm 16 midi channels (or how ever many needed) in ableton and record all the midi tracks at once, so at least I'd still have them in some form. But yeah, that could still be pretty time consuming.
I'm starting to get into the 38% range in memory left. My mp is acting funny now too, like some external tracks cut out randomly, song mode acts really sketchy when writing songs.
Will i continue to experience problems the more memory I use? Or is it just in my head? (I could still be a little scarred from a MC-307 a few years back)
--- In xl7@yahoogroups. com, "dwn4tupac" wrote:
>
> Yeah i have the exact same problem with my xl-7...that' s why i don't sequence with it anymore. Dunno if it is the eloader version or what, but I tried mine w/ midi instead of usb too and no dice...
> makes me mad because the drag and drop was half the appeal of this unit.
> it basically makes backing up a huge pain in the ass.
>
> If you find a workaround or other solution let us know.
>
>
> --- In xl7@yahoogroups. com, "joeyjoejoemagee" wrote:
> >
> > Hey all,
> > Just been having trouble with e-loader.
> > I have a bi directional Midi connection, and USB to my MP-7. all the USB drivers seem to be working fine.
> > E-loader recognizes my MP7, and the sequences. But when I try to copy them to my computer, I get a message saying "Failed" every time. I've tried using a different MIDI interface, but still the same problem.
> >
> > Anyone experience the same problem or have any suggestions?
> >
>
2009-04-06 by steve_the_composer
I had e-loader success with both Win98SE and XP via midi and the usb with with Win98SE, but for years couldn't get the usb drivers to work with XP. However, a few months ago usb finally worked with XP. The research I did leads me to believe that Microsoft changed the way composite devices were enumerated. I know I posted messages about my new-found success. Maybe my posts will help you to locate the problem and find a solution. I know I took some screen shots from device manager to demonstrate what is now going on when my P2500 powers up and the XP goes through the usb recognition routine. I will look in the archives to see if I can find the posts. In the meantime: (1) Does e-loader find the e-mu once you set up the the midi ports (that is when you press "scan for midi devices")? If not double check your midi routings. (2) I have found that I need to power up the P2500 >>AFTER<< XP is fully booted. Otherwise, the E-Mu usb driver will not be available to e-loader. Also, some other diagnostic questions: What is giving you the "Failed" message? The Mp-7? e-loader? Is it possible something is blocking sysex between the MP7 and the computer? --Steve --- In xl7@...m, "joeyjoejoemagee" <joeyjoejoemagee@...> wrote:
> > Hey all, > Just been having trouble with e-loader. > I have a bi directional Midi connection, and USB to my MP-7. all the USB drivers seem to be working fine. > E-loader recognizes my MP7, and the sequences. But when I try to copy them to my computer, I get a message saying "Failed" every time. I've tried using a different MIDI interface, but still the same problem. > > Anyone experience the same problem or have any suggestions? >
2009-04-06 by steve_the_composer
Here are the posts. Background: Years ago, I had given up trying to get the E-Mu usb drivers to work on my XP. But when someone raised a question about getting e-loader to work, I gave it another try. For the first time I had the usb working on XP!!! So I tried to share whatever info I found and thoughts I had that >>might<< explain the success. My hope was that it might help others. In retrospect, I now think its the change in Microsoft's handling of Composite usb devices. So, kinda ignore all the other speculation. The second message has some links to some stuff about composite usb devices that are beyond my understanding, but others might find it helpful. http://launch.groups.yahoo.com/group/xl7/message/19903 http://launch.groups.yahoo.com/group/xl7/message/19904 I did not post the snapshots of device manager; I will look for them. Basically, if you successfully installed the E-Mu usb drivers, open up device manager, expand the usb listing, and then power up the MP7. At first I believe I get an unrecognized hardware info balloon on the XP as OS2.0 boots. I think there may also be either an unknown device or a composite device popping up in device manager. Around the same time that the E-Mu is fully booted [pattern 000^0] the E-Mu usb drivers get listed in device manager. Monitor device manager and see what happens at the same time your MP-7 boots. Hopefully, the drivers will show up. Hope this helps. --Steve --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@...> wrote:
> > I had e-loader success with both Win98SE and XP via midi and the usb with with Win98SE, but for years couldn't get the usb drivers to work with XP. > > However, a few months ago usb finally worked with XP. The research I did leads me to believe that Microsoft changed the way composite devices were enumerated. I know I posted messages about my new-found success. Maybe my posts will help you to locate the problem and find a solution.
2009-04-07 by steve_the_composer
Just uploaded 4 screenshots to Files --> WinXP. 1. XP's device manager before E-Mu power-up. 2. XP's device manager when E-Mu is at the Loading . . . . screen. Notice the unknown usb device. 3. XP's hardware info bubble saying there's an unrecognized usb device. This pops up on my system at the time that the E-Mu copyright notice is on the E-Mu screen display. 4. XP's device manager after the E-Mu is fully booted and ready to play pattern 000^0. Notice the Composite Device and the 2 E-Mu usb devices (0 and 1). Additonal notes: Running XP + SP3. XP must be booted before E-Mu. E-Mu usb drivers must have been installed first (carefully following the instructions that come with e-loader) --Steve --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@...> wrote:
> > I did not post the snapshots of device manager; I will look for them. Basically, if you successfully installed the E-Mu usb drivers, open up device manager, expand the usb listing, and then power up the MP7. > > At first I believe I get an unrecognized hardware info balloon on the XP as OS2.0 boots. I think there may also be either an unknown device or a composite device popping up in device manager. Around the same time that the E-Mu is fully booted [pattern 000^0] the E-Mu usb drivers get listed in device manager. > > Monitor device manager and see what happens at the same time your MP-7 boots. Hopefully, the drivers will show up. >
2009-04-07 by joeyjoejoemagee
Thanks Steve! The "Failed" message I get is from e-loader. I can see the names of my sequences. The MP-7 shows up in the scan for devices option. Both emu interface 0 and 1 show up in device manager. Still no dice. I even went out and bought 2 new midi cables, and directly connect the mp7 to my midi interface. I tried to use the straight midi connection and didn't use the USB, but the same problem persist. Thanks for all the info Steve, I'm trying again right now, not giving up yet! I'll tell you how it goes.
2009-04-07 by joeyjoejoemagee
What is really strange is that I was able to upgrade my mp-7 to os2.0 with e-loader with no problem at all. When I try to download a sequence, I get a window that says "Making Progess".... 0 of 0 bytes transferred. The computer thinks for a second then the error message shows up. The error message I get says: Error! and has a stop sign and hand. Says: "Upload of **sequence** failed", when **sequence** is the name of the sequence I'm trying to upload. My device manager looks like the one in your screenshot, the drivers are in there and recognized. Frustrating..... --- In xl7@yahoogroups.com, "joeyjoejoemagee" <joeyjoejoemagee@...> wrote:
> > Thanks Steve! > The "Failed" message I get is from e-loader, it comes with a stop sign and a hand, the entire . I can see the names of my sequences. The MP-7 shows up in the scan for devices option. Both emu interface 0 and 1 show up in device manager. Still no dice. I even went out and bought 2 new midi cables, and directly connect the mp7 to my midi interface. I tried to use the straight midi connection and didn't use the USB, but the same problem persist. > Thanks for all the info Steve, > I'm trying again right now, not giving up yet! > I'll tell you how it goes. >
2009-04-07 by steve_the_composer
Hmmm. I don't recall seeing an e-loader error like that. I think I was able to re-create it just now. Check either Files or photos for the e-loader error screenshot. Is that what youy get? I recreated it by downloading the pattern names then switching the sysex device ID on my e-mu and then trying to send a *.mid file to the sequencer. So, maybe there's a sysex device ID issue. I assume the device shows device shows up under "Scan for MIDI Devices." Check the sysex ID; I think its the 4th item there. Then check MIDI setup. Is the device ID the same? If not, that may be the problem. If they are the same, more thought is needed to try to solve this one. Hope this helps. --Steve --- In xl7@yahoogroups.com, "joeyjoejoemagee" <joeyjoejoemagee@...> wrote:
> > What is really strange is that I was able to upgrade my mp-7 to os2.0 with e-loader with no problem at all. > When I try to download a sequence, I get a window that says "Making Progess".... 0 of 0 bytes transferred. The computer thinks for a second then the error message shows up. > The error message I get says: Error! and has a stop sign and hand. Says: "Upload of **sequence** failed", when **sequence** is the name of the sequence I'm trying to upload. > > My device manager looks like the one in your screenshot, the drivers are in there and recognized. > > Frustrating..... > > --- In xl7@yahoogroups.com, "joeyjoejoemagee" <joeyjoejoemagee@> wrote: > > > > Thanks Steve! > > The "Failed" message I get is from e-loader, it comes with a stop sign and a hand, the entire . I can see the names of my sequences. The MP-7 shows up in the scan for devices option. Both emu interface 0 and 1 show up in device manager. Still no dice. I even went out and bought 2 new midi cables, and directly connect the mp7 to my midi interface. I tried to use the straight midi connection and didn't use the USB, but the same problem persist. > > Thanks for all the info Steve, > > I'm trying again right now, not giving up yet! > > I'll tell you how it goes. > > >
2009-04-07 by dc
----- Original Message -----From: steve_the_composerSent: Tuesday, April 07, 2009 7:43 AMSubject: [xl7] Re: E-loader HelpHmmm. I don't recall seeing an e-loader error like that.
I think I was able to re-create it just now. Check either Files or photos for the e-loader error screenshot. Is that what youy get?
I recreated it by downloading the pattern names then switching the sysex device ID on my e-mu and then trying to send a *.mid file to the sequencer. So, maybe there's a sysex device ID issue.
I assume the device shows device shows up under "Scan for MIDI Devices." Check the sysex ID; I think its the 4th item there. Then check MIDI setup. Is the device ID the same? If not, that may be the problem. If they are the same, more thought is needed to try to solve this one.
Hope this helps.
--Steve
--- In xl7@yahoogroups.com, "joeyjoejoemagee" ...> wrote:
>
> What is really strange is that I was able to upgrade my mp-7 to os2.0 with e-loader with no problem at all.
> When I try to download a sequence, I get a window that says "Making Progess".... 0 of 0 bytes transferred. The computer thinks for a second then the error message shows up.
> The error message I get says: Error! and has a stop sign and hand. Says: "Upload of **sequence** failed", when **sequence** is the name of the sequence I'm trying to upload.
>
> My device manager looks like the one in your screenshot, the drivers are in there and recognized.
>
> Frustrating.....
>
> --- In xl7@yahoogroups.com, "joeyjoejoemagee" > wrote:
> >
> > Thanks Steve!
> > The "Failed" message I get is from e-loader, it comes with a stop sign and a hand, the entire . I can see the names of my sequences. The MP-7 shows up in the scan for devices option. Both emu interface 0 and 1 show up in device manager. Still no dice. I even went out and bought 2 new midi cables, and directly connect the mp7 to my midi interface. I tried to use the straight midi connection and didn't use the USB, but the same problem persist.
> > Thanks for all the info Steve,
> >; I'm trying again right now, not giving up yet!
> > I'll tell you how it goes.
> >
>
2009-04-07 by Asukaya Bailey
To The XX-7 Group, SP 3 for XP is the way to go. I"ve had my MP-7 for almost 3 years now, and it's just become enabled on my Intel quad. Previously it was only possible through an older XP system that had no USB 2.0 support. It's still a fight as the E-MU drivers are loaded in the E- loader folder. So if you find yourself scoring pages to find it, look in that location. Also update your Java, and point the drivers to the install folder for correlation. Since the E-loader is enabled, other apps like Jan's Protadum become applicable, with the capabilities to check your presets, arps, and sequences. Very good stuff. My thanks and advice to the group, this has been one of the best ways to learning the machine. Now applying it to Reason, Live, and Nuendo, and all around production with both external and internal modules, and sequence - Priceless. Kayaone - Luminous Velocity ________________________________ From: steve_the_composer <smw-mail@...> To: xl7@yahoogroups.com Sent: Tuesday, April 7, 2009 7:43:48 AM Subject: [xl7] Re: E-loader Help Hmmm. I don't recall seeing an e-loader error like that. I think I was able to re-create it just now. Check either Files or photos for the e-loader error screenshot. Is that what youy get? I recreated it by downloading the pattern names then switching the sysex device ID on my e-mu and then trying to send a *.mid file to the sequencer. So, maybe there's a sysex device ID issue. I assume the device shows device shows up under "Scan for MIDI Devices." Check the sysex ID; I think its the 4th item there. Then check MIDI setup. Is the device ID the same? If not, that may be the problem. If they are the same, more thought is needed to try to solve this one. Hope this helps. --Steve --- In xl7@yahoogroups. com, "joeyjoejoemagee" <joeyjoejoemagee@ ...> wrote:
> > What is really strange is that I was able to upgrade my mp-7 to os2.0 with e-loader with no problem at all. > When I try to download a sequence, I get a window that says "Making Progess".... 0 of 0 bytes transferred. The computer thinks for a second then the error message shows up. > The error message I get says: Error! and has a stop sign and hand. Says: "Upload of **sequence** failed", when **sequence** is the name of the sequence I'm trying to upload. > > My device manager looks like the one in your screenshot, the drivers are in there and recognized. > > Frustrating. .... > > --- In xl7@yahoogroups. com, "joeyjoejoemagee" <joeyjoejoemagee@ > wrote: > > > > Thanks Steve! > > The "Failed" message I get is from e-loader, it comes with a stop sign and a hand, the entire . I can see the names of my sequences. The MP-7 shows up in the scan for devices option. Both emu interface 0 and 1 show up in device manager. Still no dice. I even went out and bought 2 new midi cables, and directly connect the mp7 to my midi interface. I tried to use the straight midi connection and didn't use the USB, but the same problem persist. > > Thanks for all the info Steve, > > I'm trying again right now, not giving up yet! > > I'll tell you how it goes. > > >
2009-04-07 by Aaron Eppolito
Hmmm. I don't recall seeing an e-loader error like that.
I think I was able to re-create it just now. Check either Files or photos for the e-loader error screenshot. Is that what youy get?
I recreated it by downloading the pattern names then switching the sysex device ID on my e-mu and then trying to send a *.mid file to the sequencer. So, maybe there's a sysex device ID issue.
I assume the device shows device shows up under "Scan for MIDI Devices." Check the sysex ID; I think its the 4th item there. Then check MIDI setup. Is the device ID the same? If not, that may be the problem. If they are the same, more thought is needed to try to solve this one.
Hope this helps..
--Steve
--- In xl7@yahoogroups. com, "joeyjoejoemagee" wrote:
>
> What is really strange is that I was able to upgrade my mp-7 to os2.0 with e-loader with no problem at all.
> When I try to download a sequence, I get a window that says "Making Progess".... 0 of 0 bytes transferred. The computer thinks for a second then the error message shows up.
> The error message I get says: Error! and has a stop sign and hand. Says: "Upload of **sequence** failed", when **sequence** is the name of the sequence I'm trying to upload.
>
> My device manager looks like the one in your screenshot, the drivers are in there and recognized.
>
> Frustrating. ....
>
> --- In xl7@yahoogroups. com, "joeyjoejoemagee" wrote:
> >
> > Thanks Steve!
> > The "Failed" message I get is from e-loader, it comes with a stop sign and a hand, the entire . I can see the names of my sequences. The MP-7 shows up in the scan for devices option. Both emu interface 0 and 1 show up in device manager. Still no dice. I even went out and bought 2 new midi cables, and directly connect the mp7 to my midi interface. I tried to use the straight midi connection and didn't use the USB, but the same problem persist.
> > Thanks for all the info Steve,
> > I'm trying again right now, not giving up yet!
> > I'll tell you how it goes.
> >
>
2009-04-08 by steve_the_composer
I wonder if there's something in the file or perhaps the file header causing the error (or the file type). If you have one of those files that produces the error consistently, I'd be willing to try it on my system (preferably a small file) and take a look at it. --Steve --- In xl7@yahoogroups.com, "dc" <carrda@...> wrote:
> > Hey Guys, > > I'm a newbie at this, but I have gotten that error when trying with some midi files. Mostly when I was trying to upload XG midi files that I had saved from a Yamaha RS7000 that I previously owned. And sometimes with midi files that I have downloaded off the net. Maybe there is something there. > > Dave
2009-04-10 by dwn4tupac
It's probably not the file. I've had this problem but only when trying to copy FROM the xl7 TO the computer...not the other way around. I"m using xp sp2 w/ eloader 1.0 (i think) --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@...> wrote:
> > I wonder if there's something in the file or perhaps the file header causing the error (or the file type). If you have one of those files that produces the error consistently, I'd be willing to try it on my system (preferably a small file) and take a look at it. --Steve > > --- In xl7@yahoogroups.com, "dc" <carrda@> wrote: > > > > Hey Guys, > > > > I'm a newbie at this, but I have gotten that error when trying with some midi files. Mostly when I was trying to upload XG midi files that I had saved from a Yamaha RS7000 that I previously owned. And sometimes with midi files that I have downloaded off the net. Maybe there is something there. > > > > Dave >
2009-04-10 by steve_the_composer
I am using e-loader 1.1. Not sure if that makes a difference. However, after testing file tranfers I am confounded. I had all kinds of problems (failures) whe the sysex device ID was anything but 000. Also, I somehow transfered some files onto the computer without the mid file type attached. This is a mystery!! --- In xl7@yahoogroups.com, "dwn4tupac" <dwn4tupac@...> wrote:
> > It's probably not the file. > I've had this problem but only when trying to copy FROM the xl7 TO the computer...not the other way around. > I"m using xp sp2 > w/ eloader 1.0 (i think) > > --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@> wrote: > > > > I wonder if there's something in the file or perhaps the file header causing the error (or the file type). If you have one of those files that produces the error consistently, I'd be willing to try it on my system (preferably a small file) and take a look at it. --Steve > > > > --- In xl7@yahoogroups.com, "dc" <carrda@> wrote: > > > > > > Hey Guys, > > > > > > I'm a newbie at this, but I have gotten that error when trying with some midi files. Mostly when I was trying to upload XG midi files that I had saved from a Yamaha RS7000 that I previously owned. And sometimes with midi files that I have downloaded off the net. Maybe there is something there. > > > > > > Dave > > >
2009-04-11 by steve_the_composer
Update of e-loader "Get sequence" [transfer from E-Mu sequencer to computer] problem. *If ID = 0, sequencer transfers. *If ID > 0, transfer fails. E-Mu sends songs packets 1 and 2 (universal system exclusive format). e-loader (java console) reports a checksum error and sends NAK. It looks like the the actual cs = the "should be" cs + sysex ID. (In snippet 1, ID was 64; in snippet 2 ID was 5; in snippet 3 ID was 1.) CONSOLE SNIPPET 1: bad checksum received. packetNum: 0 cs was: 117 should be: 53 sending NAK CONSOLE SNIPPET 2: bad checksum received. packetNum: 0 cs was: 48 should be: 53 sending NAK CONSOLE SNIPPET 3: bad checksum received. packetNum: 0 cs was: 127 should be: 126 sending NAK ------------------------------ SUGGESTION: If "Get sequence" transfer fails: (1) check sysex ID [E-Mu sequencer and e-loader] (2) check for bad checksum error in java console [e-loader] (3) if "was" cs - "should be" cs = sysex ID, change ID to 0.
2009-04-11 by Aaron Eppolito
Steve, you're awesome. Just thought I'd mention.
----- Original Message ---- From: steve_the_composer <smw-mail@...> To: xl7@yahoogroups.com Sent: Friday, April 10, 2009 7:34:34 PM Subject: [xl7] Re: E-loader Help Update of e-loader "Get sequence" [transfer from E-Mu sequencer to computer] problem. *If ID = 0, sequencer transfers. *If ID > 0, transfer fails. E-Mu sends songs packets 1 and 2 (universal system exclusive format). e-loader (java console) reports a checksum error and sends NAK. It looks like the the actual cs = the "should be" cs + sysex ID. (In snippet 1, ID was 64; in snippet 2 ID was 5; in snippet 3 ID was 1.) CONSOLE SNIPPET 1: bad checksum received. packetNum: 0 cs was: 117 should be: 53 sending NAK CONSOLE SNIPPET 2: bad checksum received. packetNum: 0 cs was: 48 should be: 53 sending NAK CONSOLE SNIPPET 3: bad checksum received. packetNum: 0 cs was: 127 should be: 126 sending NAK ------------------------------ SUGGESTION: If "Get sequence" transfer fails: (1) check sysex ID [E-Mu sequencer and e-loader] (2) check for bad checksum error in java console [e-loader] (3) if "was" cs - "should be" cs = sysex ID, change ID to 0.
2009-04-11 by joeyjoejoemagee
I second that. I just uploaded all my sequences, just had to change sysex to 000 on both the mp-7 and eloader!! Thank god! No.... Thank Steve!!!!! So much worry gone just like that. All hail Steve the Composer, king of the Emus --- In xl7@yahoogroups.com, Aaron Eppolito <synthesis77@...> wrote:
> > > Steve, you're awesome. Just thought I'd mention. > > > ----- Original Message ---- > From: steve_the_composer <smw-mail@...> > To: xl7@yahoogroups.com > Sent: Friday, April 10, 2009 7:34:34 PM > Subject: [xl7] Re: E-loader Help > > Update of e-loader "Get sequence" [transfer from E-Mu sequencer to computer] problem. > *If ID = 0, sequencer transfers. > *If ID > 0, transfer fails. > E-Mu sends songs packets 1 and 2 (universal system exclusive format). > e-loader (java console) reports a checksum error and sends NAK. > It looks like the the actual cs = the "should be" cs + sysex ID. > (In snippet 1, ID was 64; in snippet 2 ID was 5; in snippet 3 ID was 1.) > > CONSOLE SNIPPET 1: > bad checksum received. packetNum: 0 cs was: 117 should be: 53 > sending NAK > > CONSOLE SNIPPET 2: > bad checksum received. packetNum: 0 cs was: 48 should be: 53 > sending NAK > > CONSOLE SNIPPET 3: > bad checksum received. packetNum: 0 cs was: 127 should be: 126 > sending NAK > ------------------------------ > > SUGGESTION: > If "Get sequence" transfer fails: > (1) check sysex ID [E-Mu sequencer and e-loader] > (2) check for bad checksum error in java console [e-loader] > (3) if "was" cs - "should be" cs = sysex ID, change ID to 0. >
2009-04-11 by steve_the_composer
Glad to hear it solved the problem. --Steve --- In xl7@yahoogroups.com, "joeyjoejoemagee" <joeyjoejoemagee@...> wrote:
> > I second that. I just uploaded all my sequences, just had to change sysex to 000 on both the mp-7 and eloader!! Thank god! No.... Thank Steve!!!!! > So much worry gone just like that. > > All hail Steve the Composer, king of the Emus > > > --- In xl7@yahoogroups.com, Aaron Eppolito <synthesis77@> wrote: > > > > > > Steve, you're awesome. Just thought I'd mention. > > > > > > ----- Original Message ---- > > From: steve_the_composer <smw-mail@> > > To: xl7@yahoogroups.com > > Sent: Friday, April 10, 2009 7:34:34 PM > > Subject: [xl7] Re: E-loader Help > > > > Update of e-loader "Get sequence" [transfer from E-Mu sequencer to computer] problem. > > *If ID = 0, sequencer transfers. > > *If ID > 0, transfer fails. > > E-Mu sends songs packets 1 and 2 (universal system exclusive format). > > e-loader (java console) reports a checksum error and sends NAK. > > It looks like the the actual cs = the "should be" cs + sysex ID. > > (In snippet 1, ID was 64; in snippet 2 ID was 5; in snippet 3 ID was 1.) > > > > CONSOLE SNIPPET 1: > > bad checksum received. packetNum: 0 cs was: 117 should be: 53 > > sending NAK > > > > CONSOLE SNIPPET 2: > > bad checksum received. packetNum: 0 cs was: 48 should be: 53 > > sending NAK > > > > CONSOLE SNIPPET 3: > > bad checksum received. packetNum: 0 cs was: 127 should be: 126 > > sending NAK > > ------------------------------ > > > > SUGGESTION: > > If "Get sequence" transfer fails: > > (1) check sysex ID [E-Mu sequencer and e-loader] > > (2) check for bad checksum error in java console [e-loader] > > (3) if "was" cs - "should be" cs = sysex ID, change ID to 0. > > >
2010-12-12 by dutchbeats
"Make sure the sysex ID matches between E-Loader and the XL-7's MIDI menu." -Aaron eureka! the xl-7 was set to sysex id 1 when e-loader had been looking for 0. a year of frustration come to a happy ending. thanks aaron! :)
> > > > ________________________________ > From: Asukaya Bailey <luminousvelocity@...> > To: xl7@yahoogroups.com > Sent: Tuesday, April 7, 2009 9:43:42 AM > Subject: Re: [xl7] Re: E-loader Help > > > To The XX-7 Group, > SP 3 for XP is the way to go. I"ve had my MP-7 for almost 3 years now, and it's just become enabled on my Intel quad. Previously it was only possible through an older XP system that had no USB 2.0 support. It's still a fight as the E-MU drivers are loaded in the E- loader folder. So if you find yourself scoring pages to find it, look in that location. Also update your Java, and point the drivers to the install folder for correlation. Since the E-loader is enabled, other apps like Jan's Protadum become applicable, with the capabilities to check your presets, arps, and sequences. > > Very good stuff. My thanks and advice to the group, this has been one of the best ways to learning the machine. Now applying it to Reason, Live, and Nuendo, and all around production with both external and internal modules, and sequence - Priceless. > > Kayaone - Luminous Velocity > > > > > > > > ________________________________ > From: steve_the_composer <smw-mail@...> > To: xl7@yahoogroups.com > Sent: Tuesday, April 7, 2009 7:43:48 AM > Subject: [xl7] Re: E-loader Help > > > Hmmm. I don't recall seeing an e-loader error like that. > > I think I was able to re-create it just now. Check either Files or photos for the e-loader error screenshot. Is that what youy get? > > I recreated it by downloading the pattern names then switching the sysex device ID on my e-mu and then trying to send a *.mid file to the sequencer. So, maybe there's a sysex device ID issue. > > I assume the device shows device shows up under "Scan for MIDI Devices." Check the sysex ID; I think its the 4th item there. Then check MIDI setup. Is the device ID the same? If not, that may be the problem. If they are the same, more thought is needed to try to solve this one. > > Hope this helps. > > --Steve > > --- In xl7@yahoogroups. com, "joeyjoejoemagee" <joeyjoejoemagee@ ...> wrote: > > > > What is really strange is that I was able to upgrade my mp-7 to os2.0 with e-loader with no problem at all. > > When I try to download a sequence, I get a window that says "Making Progess".... 0 of 0 bytes transferred. The computer thinks for a second then the error message shows up. > > The error message I get says: Error! and has a stop sign and hand. Says: "Upload of **sequence** failed", when **sequence** is the name of the sequence I'm trying to upload. > > > > My device manager looks like the one in your screenshot, the drivers are in there and recognized. > > > > Frustrating. .... > > > > --- In xl7@yahoogroups. com, "joeyjoejoemagee" <joeyjoejoemagee@ > wrote: > > > > > > Thanks Steve! > > > The "Failed" message I get is from e-loader, it comes with a stop sign and a hand, the entire . I can see the names of my sequences. The MP-7 shows up in the scan for devices option. Both emu interface 0 and 1 show up in device manager. Still no dice. I even went out and bought 2 new midi cables, and directly connect the mp7 to my midi interface. I tried to use the straight midi connection and didn't use the USB, but the same problem persist. > > > Thanks for all the info Steve, > > > I'm trying again right now, not giving up yet! > > > I'll tell you how it goes. > > > > > >