I can't load configs 1 and 2 into MCT anymore

[kimouette]

This reminds me of MCT's incompatibility symptoms with my Mac!

I've rencently noticed that I can no longer send individual pads into MCT once I load config 1 or 2 on MD.
I currently have the latest MD firmware and thought maybe that was causing the problem, so I tried to go back to megadrum32_16_32_20090517 version, but that doesn't change anything.

In other words, if i simply plug my MD change some values directly in MD, open MCT and load individual pads from MD it works fine. The problem only occurs when I plug my MD, load config 1 or 2, open MCT and try to load individual pads from MD.

Is it possible to have corrupted configs in MD?
The thing thats really pissing me off is that I cant just try to reset MD's setting without losing both of my configs. They are close to be perfect and changing them manually in MCT (while going left and right on MD to show each setting one at a time) is gonna take forever!

Anything else than downgrading the firmware I could try to maybe solve the problem?

Thanks for your help!
Kim

[dmitri]

It looks like a Mac specific problem. On Windows I can send/load individual pads even after loading config 1 or 2.

[kimouette]

Sorry for the misunderstood, but we're not talking about a Mac here!
I now own a PC (that I bought especially for MCT and BFD2). Running Windows XP SP2 with the latest version of Java.
Sending/receiving settings from/to MCT worked just fine... until about 2 weeks ago.

That's why i thought maybe it was related to upgrading the firmware. But it isnt.


EDIT : Euh... The subject of this thread is now incorrect. I only said that the actual problem REMINDED ME of the incompatibility between MCT and Mac, which is a Java problem. This time it CANT be a Java problem, it's something else!

[gabriel1712]

Try this:

Start up MD
Start MCT (no OX or BFD for now)
Config MCT to USB in/out

Can you send and recieve to and from MD now?

PS.
You can edit thread headline by entering your first post and edit the subject

[dmitri]

Are you trying to load a config saved with an old version of firmware into MegaDrum with a newer version of firmware? If there were changes to the config format between these two version, doing so will most likely lead to problems.

[kimouette]

Try this:

Start up MD
Start MCT (no OX or BFD for now)
Config MCT to USB in/out

Yes it works.

if i simply plug my MD change some values directly in MD, open MCT and load individual pads from MD it works fine. The problem only occurs when I plug my MD, load config 1 or 2, open MCT and try to load individual pads from MD.

So like i said the problem only appears in MCT after I load configs in MD

Are you trying to load a config saved with an old version of firmware into MegaDrum with a newer version of firmware?

Call me stupid if you want, YES I thought i could load my configs whenever I wanted even after I update the firmware.

I cant do it right now, but I'll just manually enter my configs in MCT, save as a .sys file, reinstall the latest MD firmwarem, load the default settings and will start to think twice before updating MD's firmware in the futur.

I remember someone asking if when updating the firmware we were losing our saved settings, I guess the answer should have been "yes" (cuz even though these configs remain accessible, it will "most likely lead to problem")

If reinstalling the firmware and loading the defaut settings doesnt work, I'll come back with as many details as possible. But if i dont, just consider the problem is solved.

[gabriel1712]

Call me stupid if you want, YES I thought i could load my configs whenever I wanted even after I update the firmware.

I cant do it right now, but I'll just manually enter my configs in MCT, save as a .sys file, reinstall the latest MD firmwarem, load the default settings and will start to think twice before updating MD's firmware in the futur.

I remember someone asking if when updating the firmware we were losing our saved settings, I guess the answer should have been "yes" (cuz even though these configs remain accessible, it will "most likely lead to problem")

If reinstalling the firmware and loading the defaut settings doesnt work, I'll come back with as many details as possible. But if i dont, just consider the problem is solved.

MD will automatically attemp to load old settings after the installation of new firmware. If the new firmware is compatible with the old settings all is fine.
However Dmitri occational adds new features to the MD settings and thus making old settings obsolete FOR THE CHANGED INPUT/PAD.

If you force old settings into a new firmware, chance are you'll corrupt the firmware. SOooo, if your old settings aren't automatically carried over, after upgrading firmware, DON'T USE SEND ALL TO MD! from MCT or Load Config from MD.

Read the version history to see which input/pad has changed. Set that pad manually in MD. The rest you can transfer from MCT, pad for pad.

There has been some change to HHpedal recently.

[Ken Forgettable]

If you force old settings into a new firmware, chance are you'll corrupt the firmware.

Can't have this idea floating around - it's not true!
You should have said - chances are you'll make the settings in the EEPROM memory incompatable with your current firmware.

[gabriel1712]

If you force old settings into a new firmware, chance are you'll corrupt the firmware.

Can't have this idea floating around - it's not true!
You should have said - chances are you'll make the settings in the EEPROM memory incompatable with your current firmware.

I don't know what EEPROM memory is. Can I refrase to:
"...instead of numbers, MD will spam a creative selection of funky symbols?"

[Rubis]

That is where the configs are saved. If you hold the right button on startup it is reset to defaults.