Of course you can always save your sounds and import them into new songs but then you're likely to forget how you created a particular sound and you may fall into the trap of using them like presets. If you'd like it might even help to write down the entire contents of your tables. Perhaps you have a fast pwm at pulsetable 03 and a slow one at 2A, etc. Of course, you'll do the same for each table. For example, if you create a wavetable for a bass drum you can make a note somewhere that it starts at 0E, and that there's a that wavetable at 1F is a pulse instrument, etc. To make it easy on yourself, you might want to keep track of the various things you've put into your tables and their beginning address. If you think of these tables as little programs that you write to alter values of the SID register you wouldn't be wrong.
Each of the four tables will just be a long string of operators and arguments - commands and values for those commands to use - and your instruments will contain parameters to jump to these routines that you create.
There are four types of table in goattracker, most function sort of like an assembly routine - the speed table is a little different - but each is designed for a different purpose, to keep the interface a little cleaner. Goattracker is a pretty basic wrapper for the playback routine and therefore the way that tables work might be a bit awkward for a musician to get used to. Just like most PSG chips the key to getting any interesting sounds is with the use of tables.
0 kommentar(er)
