Yahoo Groups archive

Emu XL-7 & MP-7 User's Group

Index last updated: 2026-04-29 00:09 UTC

Message

Re: Problem: Weird wheel!

2002-04-23 by emufreak1

Nifflas,

It's called the encoder.  The same thing happened on my P2K if the 
wheel was turned too quickly.  Here is my reply to a user on the P2K 
group with what I do to avoid sending it away....


> Subject: [p2k] Re: Problems with TurnWheel???
> 
> 
> Unfortunately there is nothing you can do aside from sending it 
away 
> to a service center. There is a device called an encoder which is 
> soldered in to the front panel(you can see it if you pull the knob 
> off), the is what's going bad. I have the same problem but I find 
> that if I apply pressure to the knob(inward)while turning it(I 
> usually put my thumb near the top-center and rotate either 
clockwise 
> or counter clockwise depending on which value I need), it will 
scroll 
> normally but if I try to spin quickly without pressure, that's when 
> it jumps.
> 
> Hope this helps.
> 
> Later,
> 
> M2
> 
> http://groups.yahoo.com/group/orbit3/
> 

--- In xl7@y..., "nifflas" <nifflas@m...> wrote:
> I have problems with the data wheel. I sent back my last XL-7 
because 
> the data wheel was buggy. When I turned it sometimes it did strange 
> things. When trying to change pattern or anything, it would 
> suddenly "jump" to a completley different value (And I know I 
didn't 
> turn the wheel that fast).
> 
> I got a new XL-7 and had no problem with it. The data wheel was 
> acting nice 'n smooth, no unexpected "jumps". Until now. A while 
ago 
> I noticed the data wheel on the new XL-7 started to act a little 
bit 
> weird. And now it's quite bad again, like the last XL-7.
> 
> Must be quite low quality components or something? This never 
> happends to my other synthesizers.
> 
> I just want to know how the data wheel is for the others of you?
> 
> //Nifflas

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.