In article <
3D78FD60.2050601@...>, Shayne Hardesty
<
lists@...> writes
>Ed Edwards wrote:
>> Shayne,
>[...]
>> Please go for it. I know exactly the hassle you're talking about...
>> you're looking for "that sound" but there are lots of patch banks available,
>> and you have to load and listen to each sound to see if you can find that
>> 'right one'.
>
> Yes, exactly.. They way they are organized now (by user) really
>doesn't lend itself to finding anything quickly.. You have to download
>each user's sounds then go through all of them.. If you know you're
>looking for a "brass-type" sound, this way you could search through all
>sounds classified as brass and hopefully atleast get close in a
>reasonable amount of time.
>
> The other problem I have is in only being able to have 128 patches at
>a time in my an1x, there are sounds I remember using and liking that
>I've forgotten where they are (like 'Illusion' and 'Church Bell'). This
>way you could look the sound up by name and find it.
>
> As you said classifications will be a bit tough, but we can take the
>defaults to start with and go from there. We could also allow a sound
>to fall under multiple categories if it lends itself to that.
>
>> I'm not quite sure of how to break the individual patches out
>> of the banks and group them together outside of AN1x Edit.
>
> Yeah, that was my thought.. Pull up the banks in an1x edit and save
>them out as .an1 files. Tedious, but it would only have to be done
>once. Maybe if Gary is still around he could write a quick utility to
>extract individual .an1 files from a sound bank?
I thought that there was actually a definition of the AN1x file spec. in
the sites file section.......
--
See ya,
Reggie