Yamaha CS80 group photo

Yahoo Groups archive

Yamaha CS80

Index last updated: 2026-04-28 23:44 UTC

Message

Re: Looking for patches, establishing patch "gallary"

2005-07-21 by nicholas_kent

--- In yamahacs80@yahoogroups.com, "Max Fazio" <faxiomas@v...> wrote:
> On a CS-80 the sounds VAngelis used are A LOT easy to build....especially since he 
mainly used presets!! GUITAR1, BASS,FLUTE, STRINGS4 , BRASS2 and FUNKY1-2-3-4 are 
the most used.....you lucky guy....

true, but of course you have the performance controls overriding parts of the preset so I'd 
say the presets are a solid jumping off point rather than the instant sound he used

... and don't forget the Lexicon 224 ;-)



> M
>   ----- Original Message ----- 
>   From: h0merxxx 
>   To: yamahacs80@yahoogroups.com 
>   Sent: Thursday, July 21, 2005 11:22 AM
>   Subject: [yamahacs80] Looking for patches, establishing patch "gallary"
> 
> 
>   Hey there
> 
>   I'm looking for patches for the cs-80, especially some of the vangelis 
>   sounds from blade runner?
>   What are your methodes to store more then 4 patches?
>   I thought to take some pictures of the panael/silders when I found a 
>   nice sound which is worth to remember.
>   What do you think maybe we should try to realize some kind of patch 
>   library based on photos? 
> 
> 
> 
> 
> 
>   SPONSORED LINKS Music sampler  Synthesizer music  Yamaha synthesizer  
>         Synthesizer  Sampler  
> 
> 
> 
----------------------------------------------------------------------------
--
>   YAHOO! GROUPS LINKS 
> 
>     a..  Visit your group "yamahacs80" on the web.
>       
>     b..  To unsubscribe from this group, send an email to:
>      yamahacs80-unsubscribe@yahoogroups.com
>       
>     c..  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 
> 
> 
> 
----------------------------------------------------------------------------
--

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.