[A6] Soundbanks etc.
Chris Pickett
chris.pickett at mail.mcgill.ca
Mon Sep 29 01:19:28 PDT 2003
scd wrote:
>on 26-09-2003 20:34, Oliver at vivalamarcha at web.de wrote:
>
>Uhhhrrrrr... Patience please :-) !
>
>I almost have the devided banks ready. Didn't intergrate Cyrils stuff yet,
>because I noticed that that bank contains a lot of doubles.
>I am not in the mood to go through 1400 sounds again, just to remove those.
>So Cyril, could you tell me (or even better send me) the sounds you added,
>beside the ones I already had?
>I downloaded everything from Alesis site plus the ones on code404.com
>
>Now then, when I have the SoundDiver banks ready, what to do next?
>
>This was a lot of work and I want to be sure we are heading in the right
>direction with this project :)
>
>So to summarize what I have done:
>- Created one big bank with all available sounds
>- Removed the doubles
>- Categorised every sound (here is some discussion possible I am sure :-))
>into pads, drums, fx, leads, keys, arps, basses, acoustic and misc.
>- Created separated banks listed like above
>- Changed some volumes from sounds in these banks that where a bit too loud.
>
>We're talking about 1090 sounds at the moment.
>
>Now what? Input please! :-))
>
Nice progress!
Here's what I would say comes next ... we still aren't done gathering
patches
1) Locate all the copies of the preset sound banks -- these have some
different patches depending on when you purchased your A6, and a few of
them are worth having (e.g. my sought-after strawberry flutes patch).
These are gonna have to come from list members. I'll send you my preset
banks and you can tell me if you already have all of those sounds. It
might be worthwhile posting lists of patches in the preset banks so that
list members can check before uploading.
2) Get list members to send in *all* of their half-decent or better
patches for inclusion in the library.
3) Take Cyril's patch library and eliminate doubles -- can you do a
compare (i.e. a "diff") on a patch-by-patch basis? This would be the
easiest way to eliminate doubles.
Then ... we wait until the patch influx has slowed down to only the new
patches, and start distributing / voting on your work.
I know this is a pretty anal approach, but I really think it's better to
try and get *everything* -- and we can sort of then close the book on
the A6's past history of patches and move forward.
Cheers,
Chris
More information about the a6
mailing list