I know, I know.. limitations.. my tempest doesn't make my coffee.. ;P
but luckily I have some C/C++ understanding, and yes - I'm aware from the compression issue. since ca. 4 or 5 years
building blocks..
well.. yes. I thought about it. And I still do. but in slightly different manner.
My idea is to randomize existing beat patterns with existing sounds. so you get a complete new project with beats that uses preprogrammed "building blocks" from other projects. the idea is from a nice winXP tool for the KORG MS2000 i had(still have
)
for the randomizer I don't really see much reason to do it. I want to layout sounds
really fast and start playing.
for this, the option to choose with the build in/ saved sounds in the machine is too slow.
so I want this workflow:
select a pad, press randomize, select next pad, press randomize etc.. then play/record.
this way you create a whole sound pack in seconds! the only thing you do (and you do it anyway the whole time since social-media) is to curate.
and during the programming I had the whole parameters as layout and grouped in front of me. I never ever had the intention to tweak the knobs in the UI from the app. It was just to be sure, that my compression/uncompression is done right.
so I really don't get it why do you need an sound editor for the tempest..
tempest IS a sound editor by itself. a pretty good one, btw.
but without an randomizer
so right now I'm coding the UI. but the business logic is done and I made sure that it scales. So if i decide to implement something like the project randomizer, f.e. I can build on top of the code I already have..
so chears, take it easy! limitations are one of the most important building blocks of creativity