![]() ![]() Haha, I probably spent more time looking at the keyboard shortcut summary screen than the tracker itself the last time I tried it. And if they can be optimized in some or share tables in any way let the code do the magic before pushing out the SID code.Īlso while some people are still comfortable with VI on unix/linux, I cant help but think that adding a few buttons here and there to use a mouse on would help immensely unless you use the tracker every day to memorize the gazillion keyboard shortcuts. I dont know if Bordeaux also is struggling here or not, but I usually just try random numbers in goattracker for where to start the pulse (high,low byte), and then I just increase and decrease the pulse randomly without actually understanding how it works from a overall sound perspective. Haha, just kidding, well, I guess I am kinda used to the idea of having all parameters and settings for one instrument in one screen/area, and not glued together like a sticky sandwitch. Well, its probably something you get used to, heck, people even learn to play the bagpipe so why not learn Goattracker. But its rather counter-intuitive in the way that it has "jumps" that gets messed up if you start shifting stuff in those tables. I perfectly understand though that in a C64 every byte counts so its wise to have some control over this and reuse tables whenever possible. ![]() I use this tool so frequently that i decided to make a tutorial on how to use it. One thing I never could get used to was the tables in Goattracker. Alternatives listed Popular alternatives 1 Bosca Ceoil 2 GoatTracker 3. ![]()
0 Comments
Leave a Reply. |