My A4 is 10 years old and started to have some memory lapses - it looses the sound settings. After power off and power on again the next day, the sounds that I’ve created are different, like some data controlling the setting is corrupted. It happens also when there is no MIDI or USB connected (so I exclude some MIDI messages to be a reason for that).
Initially I thought it’d be the internal battery issue, but… there is no battery as far as I understood from this topic: A4 teardown (and infrared pics)
What else could be the reason?
Have you reached Elektron support directly?
I don’t see much we can do but other might have some answers…
Can you describe exactly what happens? “Sound setting” is pretty vague.
Do you save your Kits? Or/and Projects?
Do you observe the same thing with other/new projects?
I would save the Project, backup everything (Projects and Sounds) and do a factory reset.
Thanks for response (not that my flagging was a provocation - I seriously thought it’d better to clean it up
).
“Sound setting” - I mean the sound preset, for example I did some short bass, and the day after filter and envelope settings differ and the bass sounds totally different - and it’s not a nuance drift typical for analog synthesis, but a total difference comparing to how it sounds before power off. The sound is stored in the kit and the kit is used in only one pattern. I’ll probably do the factory reset as you suggest, but just wondered what sort of hardware issue it may be, since the memory is the one with battery backup.
Yes indeed, it always works like this, unless you use Sound locks.
But what I meant was… did you save?
The Kit? The Project?
Yes, kit saved. Project not.
Try saving the projects, normally everything gets saved.
Use Transfer to backup everything.
Load another project, the load this one again.
See if it changes anything.
Ah, I forgot to mention - problem is not reproducible each time, is quite random. But I’ll try to transfer backup after each day session - at least this will help to reduce my frustration in case if problem strikes back one day 
This are two opposite sentences.
I give you precise advices to help understand where your problem is from.
Do as I say and tell me if your problem arise again.
- Save your project
- Backup at least once
- Load another project then reopen this one.
- Let’s see from here what happens.
By doing this, we potentially get rid of some corrupt memory artefact.
And try saving your project before switching off, so that your work doesn’t depend on the memory.
Oh, and what’s your OS?
(edited my sentence ^^^, sorry)
OK. I did steps 1-3 now, I’ll see for a couple of next days what will be happening.
OS is 1.50.
1 Like