On Tuesday, September 4, 2001, at 09:29 PM, deephousesouldier@...
wrote:
> The eloader software is my problem. i am trying to export my smf
> from cubase to the MP-7
> the problem is it never recognizes my Program or bank changes.
> so I export the file again back into cubase so i can see what
> happened and the data is no where to be found. in fact there is
> new CC data. CC 79 and CC80 on every track. I am not sure
> what this is
> so i fix it and export it back in to the MP. no luck. it keeps
> corrupting my data.
> For the techs on this page... I spoke with dave lees from Emu
> and he said you guys were unaware of a bug and that there
> should be a work around. he suggested a few things but thye did
> not work.
> So 1 this is a eloader problem
> or 2 this is a cubase conflicting with the eloader problem.
> could you get some ideas and help me work this out please.
> I will speak more with Dave and will be attending a seminar on
> the 17th in nashville
E-Loader does not (at least should not be) changing the data that exists
in the MP-7. It simply moves a copy of the data across the MIDI wire in
what should be a very secure manner. It handshakes and validates each
packet transferred, so it is highly unlikely that the data itself is
getting corrupted by the transfer performed by E-Loader.
Can you send me (off the list) an SMF file that is purportedly being
corrupted? What would be best is to send me a file that starts out on
the host with the program changes and controller messages the way you
want them and then another file that is the result of the original file
after being transferred into the MP-7 and then back to the host computer
and has lost some data in the process.
It is more likely that your problem is in something that the MP-7 is
unexpectedly doing with the data that is being imported into it. Like I
said, E-Loader should just be transferring the data back to the host as
it exactly exists in the MP-7. The unexpected changes could be because
of some MP-7 setting or some other 'feature' that you are unaware of, or
possibly its a bug in MP-7 code itself.
Scott