Synthplayer, an explanation could be that, since the REV2 is heavily controlled by software, there might have been a glitch that would have offset the cutoff value sent to the filter via the DAC from temporary faulty data in memory ? Doing a reset would have clearly that altered wrong data, perhaps ? Without necessarily having been caused by some "hidden" parameter.
RAM memory has been known to change state, by different software/hardware glitches in the past.
;-)
I think it's a bit presumptuous to suggest an error like this without any data to support anything of the nature. In my view making such a statement only serves to alarm users when there is no cause for alarm.
That was certainly not my intention. There is no cause for alarm, since this might have been a once in a million fluke.
But memory data can become corrupt, without apparent cause, even though it's extremely rare. Either from a glitch on the power rails, an unknown obscure software bug under a very specific occurence, or even cosmic rays from the Sun.
Flash RAM is not immune to this. But that's no cause for concern, unless you have very valuable data in memory.
That's why it's always a good idea to have a backup of any important data. Not only of your patches in a synth, but with any computer device, be it smartphone or personal computer.
BTW, in DSI's own REV2 user's guide manual, on page 66, it is stated: "If you're trying to track down a problem, it's sometimes a good idea to reset the Global parameters to their defaults. This is a quick way to make sure that the Prophet REV2 returns to its factory settings".
Suggesting that some of those parameters might have been changed, either inadvertently or else.
12 Replies
4524 Views