Hello V-P. Have you checked the ROM version of your X5? Mine is version 12, but I know, from mail by james_sajeva@xxxxxxxxxxx, august 1997, that there has been updates to the firmware...(quote): - The current ROM is 14 ... - A newer ROM can be installed by taking it to any of your local Korg authorized service centers.... Bu I never did that, maybe there is some bugs in the older versions... I do not use the soud editor much, have just replaced some strings sounds, then never changed them. My 2 cnts.... cheers, Thomas On 13 Jan 2002 at 18:35, Veli-Pekka Tätilä wrote: > > Hi=20 > > I have had my x5 for around four years now. It has been working properly = > most of the time. well, apart from few minor repairs (pitch bender and = > few keys that gave no sound, but other than that no probs until = > recently.=20 > > The problem I am having is quite strange. At first, let me say that the = > factory reset works as it should, that is all patches are initialized to = > their factory defaults. The problems begin when I try to dump an X5/05r = > file from the X5/05 sound editor. The factory patches of the x5 are = > replaced by the patches I chose to transmit as far as around patch 70. = > The patches after about number 70 (don't remember the exact patch = > number, but it's always the same) remain unchanged, they are stuck the = > the factory sounds and will not be replaced. If I try to request the = > data I dumped to the x5, the sound editor gives me a "data receive error = > " and nothing is received.=20 > > But if I double-click a patch in the editor, who's number is greater = > than about 70, it's copied to the temporary patch area and sounds as it = > should. However when I change patches and reselect the patch I played = > (in the editor window showing all the patch names), the factory default = > sound is heard. > > I am wondering is this strange behavior a hardware-related problem = > (something wrong with the memory of the X5?) or a software problem? I = > have tested dumping stuff with other software (Cakewalk and Dumpster) in = > sysex format but, still the factory patches are not replaced.=20 > > In addition, I keep getting "cannot open MIDI output device" errors from = > the X5/05 sound editor. This happens particularly often when switching = > rapidly between patches or tweaking the X5 parameters in the editor. I = > have to restart the editor in order to get the MIDI output working = > again. If I don't restart but select the same MIDI output, the program = > doesn't find the X5 (gives me a "check cabless and bla bla bla..." = > error).=20 > > The MIDI transmition of a bank from the editor to X5 doesn't fail = > always. Seldom it happens that all the patches are succesfully dumped = > including those who's number is greater than 70. But If I try to dump = > another bank the patches of the succesfully dumped bank who's number is = > greater than 70 wil not be replaced.=20 > > Could it be possible that the memory of my X5 is somehow damaged and = > causes this strange behavior? How about the battery of the x5, how long = > does it last? and what happens when it's dead?=20 > > Another theory is that there's something wrong with my MIDI interface. = > Here are the specs of my machine:=20 > CPU: AMD T-bird 1.4 GHz > Mother Board: Asus mother board (don't remember the model) > Memory: 512 MB DDR RAM=20 > OS: Win 98se (Directx8) > Graphics card: GeForce 2 based card with 32 MB of video memory=20 > Devices: Smartmedia reader, virtual USB LAN adapter (Logitech), USB PC = > link (for transfering audio from the computer to Minidisc), Terratec = > EWS88 MT soundcard, USB MIDIsport 4x4 MIDI interface and all the usual = > stuff like keyboard and of course a mouse. > > My MIDI sport is working fine in other applications and I never get any = > MIDI errors in Cakewalk, for instance. Sysex dumps for my Roland JP-8080 = > and JV-1010 work fine (no data is lost on the way. So I don't quite = > think it could be my MIDI interface, but you never no.=20 > > It may be also that the editor software is too old for my machine. I = > mean it's written for the Win 3x and I am running Win 98SE. Besides I = > have around 10 MIDI outputs listed (4 Hubi's loopback ports, 4 MIDIsport = > ports, Terratec port, MIDI mapper, Microsoft GS wave synthesizer). I = > heard there were some problems if running Win 95 with ten or more MIDI = > ports, maybe this applies to Win 3x software as well.By the way, does = > anybody know why the Microsoft MIDI driver is listed? I thought it was = > only used by direct music and besides it doesn't give any sound if = > selected as a MIDI out. And some MIDI software, like Sound Diver and = > Logic, complain about not being able to open the Microsoft GS MIDI out = > device. Could the Microsoft MIDI port be the "trouble maker"? > > What should I do to see what's the problem? What do you think of all of = > this, is it a software or hardware problem? Has anybody else been = > experiencing errors in the x5/05 sound editor? How about errors dumping = > sysex and stuck patches as in my case? I would really need help on this = > one. It's been doing it long (half a year, more? I don't remember). I = > have recently updated my machine and my MIDI sport is also quite new. = > Unfortunately I don't remember whether I had the problem with my old = > machine, too.=20 > > Sorry for this long post but I wanted to provide you with as much = > information as possible. > > P.S.=20 > Korgy Park is a great site. I downloaded the N364 patches for my X5 and = > they are great. It felt almost as I was playing a different synth (I = > used the arpeggiator of my JP to control the X5 and a drum pattern from = > Korg's ES-1 and the x5 sounded almost as it could have been the Triton, = > OK, almost). The sounds were very thick and bassy, the factory sounds = > seemed thin in comparison. The effects are also used cleverly.=20 > > > > > > > ---------------------------------------------------------------- > This message was sent through the Korgy Park mailing list. > Mailing list info page: //www.freelists.org/list/korgypark. > ---------------------------------------------------------------- This message was sent through the Korgy Park mailing list. Mailing list info page: //www.freelists.org/list/korgypark.