![]() ![]() the Waldorf idea of putting a single cycle saw, square, and sine in the last three positions of the table is a handy way of including these basic waves in a synth, but don't do it unless the synth you are going to use has a handy way of excluding these positions when scanning the table with a slow CV (other than requiring you to carefully trim your CV signal level, which can be hard to do if it's something like a slow random signal), so you can avoid having sudden blasts & blips of these basic waves occurring as the table is scanned. ![]() For example, if you are making a wavetable of vocal timbres, maybe don't put sharp consonant sounds scattered in between resonant vowel sounds. wavetables that make a sudden timbre change in the wave at some point in the table, rather than a continuous smooth transition across the entire table. Tweak the levels of the individual sample as needed to avoid this. wavetables that have sudden jumps in overall level when they reach a particular wave in the table. Of course it's partly a matter of personal taste and of how you want to use the wavetable, but I have noticed a few things that IMO should be avoided. I haven't built my own wavetables but I've used them quite a bit and have noticed things that seem to work well and some things that don't. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |