Looper's Delight Archive Top (Search)
Date Index
Thread Index
Author Index
Looper's Delight Home
Mailing List Info

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Date Index][Thread Index][Author Index]

Re: JamMan memory problems, Part 2

At 6:20 PM 8/18/97, Mikell D. Nelson wrote:
>  There is a very rational reason for this behavior: stuck bits. After
>power up the bits should all be at zero yielding silence on playback,
>but one or more of the memory modules has some bits stuck at 1. The
>change in noise with module location probably occurs because of the
>following. Each module is responsible for storing 4 bits of each 16 bit
>sample. If the bad module is in the "most significant" position then it
>represents a huge number and you hear a pop. If the bad module is in the
>"least significant" position, then the flaw may be completely
>inaudible.  In between locations for the bad module should create in
>between noise levels. Because you found a very quiet positioning, I'd
>say your vendor sold you only one defective module.
I thought so! I bounced this theory off of the tech at VisionSoft, and he
said it was unlikely, but what do you expect from a phone support guy
anyway. So, per Mikell and Robbin's suggestions, I'm going to try to get a
new chip out of VisionSoft, and see if this solves it for good...

Thanks for the advice!

Dave Trenkel : improv@peak.org  : www.peak.org/~improv/

"...there will come a day when you won't have to use
gasoline. You'd simply take a cassette and put it in
your car, let it run. You'd have to have the proper
type of music. Like you take two sticks, put 'em
together, make fire. You take some notes and rub 'em
together - dum, dum, dum, dum - fire, cosmic fire."
                                            -Sun Ra