When our products 'forgets' the registration it usually has to do with an access problem to the registry (Windows) or preference file (Mac). Please check if If you make any changes to the preference dialog in MicroTonic, is that information kept if you restart? If not, then for some reason, you do not have access rights to write to the registry as needed. If you are running under a restricted account, you could try to relax the restrictions temporarily until you registered MicroTonic (like setting your self as administrator).

If you want to look into the problem in more detail, here is the path to the registry key: HKEY_CURRENT_USER Software NuEdge Development SonicCharge. Hi Fredrik, although I'm on Win7 I always run anything with admin rights. I also disabled the UAC on my machine. The registry key you mentioned is set and has two binary values, 'Data' and 'ssc2salt' and I guess one is supposed to contain the encoded registration. I just opened µTonic again after looking in the registry and it was in demo mode again. I entered the reg details and the 'Data' value changed. I will keep track of it the next few weeks.

Sonic Charge certainly knows how to produce high-quality plug-ins, but it doesn't release that many of them. We were pleasantly surprised, therefore, to discover that not only has it updated the excellent MicroTonic drum machine, but it's also released a completely new vocal processing effect in the shape of Bitspeek.

The odd thing is that it doesn't loose the reg always, for a few weeks everything is fine and one day it's gone out of the blue. I'm an IT professional and know my computer well;) - µTonic is the only VST that does this, even Synplant doesn't seem to have that problem. I would prefer if the reg data and config was written to a file anyway - though I'm on Win, I really hate the registry stuff.;). Well, this is odd. Today I once again had to enter the reg info. And this time twice in a row. I was working in Ableton, inserted the µTonic Drum Rack which uses the multi-out version and was asked for the reg again.

I just didn't enter them but closed Ableton. Then I fired up energyXT (with admin rights, context menu run as admin), opened the single out version, entered the reg, restarted energyXT and tried multi and single out versions and everything was fine. Then I started Ableton again and inserted the drum rack and I was asked for the reg again???!! I entered the reg, this time right away in Ableton and now it seems to work. Well, at last for a few days. Is there any problem when using the single and multi out versions in turns?

Windows Vista and Windows 7 • Press the Windows Key + E. • In the window that appears, click Organize in the top-left corner. How do i open hidden files on vista windows. • From the, select Folder and search options.

Btw.: I exported the registry entries before and after entering the reg data. If that helps I can email that to you. [edit]OK, it seems it has something to do with using different DAWs. In Ableton everything was fine first, then I tested energyXT and it was in demo again.

As if the reg just counts for one DAW at a time. I can reproduce that everytime now. Regging in eXT->MT doesn't work in Ableton and the other way around[/edit]. Would love to see the registry entries thanks. Send them to support@soniccharge.com.

The only incompatibility that we know of which erases the registration data was between version 1 and version 2 of MicroTonic. But version 3 uses a totally separate 'chunk' for its registration data. Just for safety measure, could you please double-check that you only have version 3.0.1 installed and no other MicroTonic*.dll on your entire hard-drive.

Haven't you beta-tested for us by the way? Mizuno mp 630 fast track driver settings. I recognize your handle. I can't rule out that a beta-version of MicroTonic could corrupt the registration data even if it is just scanned and never launched. Wrote: Anything? It's been over 2 months now. I am really sorry.

Time flies amazingly fast. I did check your registry data, but it didn't shed any new light on the matter. The only thing I could see was that the 'demo dump' was unregistered and the 'full dump' was registered.

Apart from that all registry data was identical. It looks like MicroTonic has just unregistered itself, and the only occasion where that can happen is when it fails to validate the registration key. Either because the key data is invalid or because the 'system identifier' has changed. Neither of which makes much sense to me under the circumstances you describe. My plan was to finish a MicroTonic 3.0.2 beta that you could try. As far as I remember I haven't changed anything concerning registration codes but the betas include traces that are helpful. However, as MT 3.0.2 was put on hold for some more urgent work, the only thing I can offer you right now is the beta of MT 3.0.1 that will send us the trace logs.