[A6] Who's getting busy with their Andromeda

Chris Pickett chris.pickett at mail.mcgill.ca
Wed Sep 17 06:50:30 PDT 2003


scd wrote:

>on 17-09-2003 15:17, Chris Pickett at chris.pickett at mail.mcgill.ca wrote:
>
>  
>
>>>­ An agreed list of categories
>>>
>>>      
>>>
>>Yes ... but ...
>>
>>For me the list of categories you had was good enough, if anything else
>>comes up when you listen to the sounds, feel free to add extras or
>>delete some.  If some categories have 200 sounds while others have 15,
>>you might want to do some splitting and merging ... but you won't know
>>until it's all done, right?
>>
>>Anybody differ on this one?  It's Boele doing the work here, he knows
>>best what categories to make.
>>    
>>
>
>OK, I understand. When I get the freedom to choose the categories I will
>find my way through the sounds :-)
>I'll check the Waldorf Q sets as well, the Q offers a user definable
>categoryname to be stored with every sound. I am not gonna invent the wheel
>again :-))
>  
>
>>>­ Approved sounds choosen by the listmembers to put into the bank(s).
>>>
>>>      
>>>
>>I would say this comes *after* we have all the user patches and
>>alternate banks in -- we want a *complete* list before we start
>>analyzing / selecting / voting, right?
>>    
>>
>
>Good one.
>
>But should I make banks of 127 sounds (first on alfabethic order I should
>say), or one sysex file for every single sound (MUCHOS work)? I'de rather do
>that later, when all choices have been made.
>
>I can also create a Word or PDF document with all the sounds listed in
>alfabethic order. Easy to have at hand when analyzing/selecting/voting.
>

I think there's a bit of a misunderstanding.

I was thinking about the following process:

1)  Acquire patches (either in existing banks or from individual user 
patches such as those posted on code404.com)
2)  Extract patches to individual SysEx files.
3)  Categorize patches.
4)  Repeat steps 1) - 3) until no more patches are being added to the 
collection! :)

at this point you can stop, it's already a lot of work! Now we should 
have, (for example):

57 bass patches
40 string patches
90 pad patches

5) Combine categories into banks for voting.  Given the above example 
list, that means 57 bass + 40 string go into Bank 1, and 90 pad go into 
Bank 2.
6) Everyone downloads the Category Banks and selects their favourite 
patches.
7) New uber-banks are created from the most popular patches.

--------

This way, after step (4) is finished, we have a complete resource of all 
existing patches sorted according to category before voting starts.

Maybe it's too much work, but this way we don't "lose" any information.  
If you don't need step (2) because it is too much work, that is fine ... 
I just thought it would make the sorting job easier, and was necessary 
because some of the patches acquired in step (1) are not in user banks 
but individual sysex files.

Cheers,
Chris




More information about the a6 mailing list