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: EchoplexDP Plus: "tick-tick-tick" noise problem




Now that I can hear this, it isn't "clock noise" at all.
It sounds very much like you bumped the cable or connector
while you were in record mode. Perhaps one of you plugs
doesn't fit quite correctly or is extra loose or some such thing.
This doesn't sound like an EDP problem (unless it is a bad
or dirty jack on the EDP).

On Jan 26, 2005, at 11:43 AM, Cox wrote:

> ak butler said:"because it's recorded in the loop?"
>
> Yes, it is. The noise always appear after a recording or overdubbing. I
> record, press record (or overdub or multiply) again to launch the  
> loop, and
> sometimes the noise is played too. But if it does not appear  
> immediately
> after the recording, it will not appear later during play back...
>
> I've recorded the noise. I recorded silence, with the input knob at its
> minimum. My loop lasted 29seconds, ans this noise appeared at around  
> the 9th
> second.  It was just as you can hear it: four serials of four ticks in  
> a
> row, and then nothing untill the end of the loop...
> It's here :
> http://www.familoo.com/familoo/RepFiles/9042563465/tick-Echoplex.mp3
>
> Thanks again to everyone who is trying to help ;-)
>
> ----------------------------------------------------------------------- 
> -----
> ---------------------------------------------------------------------
>
>
>> At 15:22 26/01/05, you wrote:
>>>     When I use the half speed function, it affects the noise: it is
> played
>>> half-speed as well.
>>
>> because it's recorded in the loop?
>>
>> what happens if the noise appears while you're in halfspeed?
>>
>>
>>>     I changed the power cable, and tried to plug nothing to the EDP:  
>>> so
> I
>>> looped silence; but the noise still appears in this case.
>>>     I must specify that if the noise seems to appear in a random way,
> once
>>> it's here it's recorded in the loop: it comes back regularly within  
>>> the
>>> loop.
>>>
>>> I guess no outside factor causes this problem, right?
>>> Is it serious, doctor?
>>
>>
>> Could be the memory playing up,
>> try MoreLoops=16 and see if the problem only occurs on some loops.
>> if so, then it's the memory at fault.
>>
>> Could still be external though, you won't totally rule that out by  
>> just
>> changing rooms.
>> (could be a mains spike caused by heating, or your neighbours'  
>> overused
>> washing machine).
>>
>>
>>
>> andy butler
>>
>>
>>
>>
>>
>>
>
>
--
| Michael A. Firman
| maf@mlswebworks.com
| http://www.mlswebworks.com