Re: JamMan memory problems, Part 2

[robin bussell <robin.b2@ukonline.co.uk>]

> On the second permutation, I got the desired effect: 32 seconds of
> glorious, distortion-free looping.
> 
> So, now I'm really curious about how this can work this way. I've talked 
>to

Well it sound to me like you *have* got a duff chip there but it's now
in a position to cause distortion that's inaudible. Say you had the most
significant bit of your sixteen stuck on (or random) you'd have either a
massive DC offset on your signal (half the full swing ) or large amounts
of noise. Move this duff chip to the least significant bit and all of a 
sudden your noise of offset is only 1/65535th of the total output swing
possible... hardly noticable, in fact there are some intersting
techniques for hiding encrypted data (which looks like a random
bitstream) in digital audio this way.. simply string out all the bits in
you data bytes and use them as the least significant bit in your WAV
file or whatever... similar things are done to hide digital copyright
data in CD's etc but I digress!

All the above is rendered a bit invalid if the jamman runs a memory test
on powerup as it should spot this and complain... though it might not
spot an error knocked out  address bits, this would mean that data got
replicated inblocks throughout the RAM and in it's least noticeable form
would be like halfing the sample rate...hmmm some jamman inside knowlege
needed here! Bob?

Anyway the long and the short of it is that there are plenty of possible
explanations for a faulty chip making your unit behave as it does so I'd
say ask them for one more, swap the ram back to a noisy config, then
swap the replacement in  one at a time until you find the culprit.

Hope this helps a bit,
                    Robin.