Alesis Andromeda A6 group photo

Yahoo Groups archive

Alesis Andromeda A6

Index last updated: 2026-04-28 22:41 UTC

Message

Re: -- no more A6 ? --

2008-07-10 by joostdenhertog

Hi Andrea Toni,


I was at Rush too,
great show. Now i have an Andromeda too!!
but i have replaced the OB12 by a xpander :-)

regards

Joost




--- In Andromeda_A6-ION@yahoogroups.com, "bob Weeks" <bob.weeks@...>
wrote:
>
> I have never had an issue with my A6. It's been gigged heavily,
dropped, and
> had beer spilt on the Case. It's never let me down. Ok the knobs are
very
> wobbly but they all work well. It's a great keyboard. 
> 
> Ok apart from a small tuning issue which goes after 3 auto tunes. 
> 
> 
> Bob
> 
> 
> -----Original Message-----
> From: Andromeda_A6-ION@yahoogroups.com
> [mailto:Andromeda_A6-ION@yahoogroups.com] On Behalf Of Andrea TONI
> Sent: 17 October 2007 14:22
> To: Andromeda_A6-ION@yahoogroups.com
> Subject: [Andromeda_A6-ION] -- no more A6 ? --
> 
> Hello,
> 
> i have been to see RUSH in Rotterdam yesterday night 
> ... fantastic gig as usual ... 
> 
> however i remember that in the RIO DVD they had an A6 on stage 
> i also remember a pvc protection case all over it
> maybe to protect from humidity and condense 
> 
> Last night however they replaced the A6 with a Roland X8 
> and a little phatty on top for the solos.
> 
> In general they are not very "endorsing-gear-oriented" so i wander 
> why they give it up ? reliability issues or what ?
> 
> 
> Regards
>
--------------------------------------------------Env1-----Env2--Env3-------
> ----
> Andrea.TONI@...                               Vco1 \    |     |  \
> Solar System Missions Sci-SM
> Vco2-->--Vcf-->Vca-->Ducati996 
> www.rssd.esa.int                                  Vco3 /    |     |  /
>
--------------------------------------------------Lfo1-----Lfo2--Lfo3-------
> ----
> 
> 
> 
>  
> Yahoo! Groups Links
>

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.