They're useful if you've got an instrument sampled at different pitches (eg: a piano), but for drums it's easier to just have different instruments than try and do it the midi way
For chip I sometimes use it for different PWM loops across the pitch range, saves having to change them manually in the pattern.
Load your first sample as normal so it creates an instrument. (instrument0) Now move to the next 'box' in the sample window of the instrument. (see I've got sample0.wav and sample1.wav below it) Click on Disk Op, Select Load Sample and load the wav. It'll appear in the sample box. Click on Instrument Editor. (which is the window at the bottom of the screenshot) Select which sample you want to map on the keyboard, then click on the relevant keys on the keyboard at the bottom. They're all by default mapped to 0, but you can see I've mapped the top half of the keyboard with 1. Obviously the higher you go the higher the deafult sample pitch is going to be, so you need to compensate by setting the relative note lower in the instrument editor.
MSSIAH/SynthCart etc are never going to sound as good as a dedicated demoscene tracker. (or GoatTracker) Those guys know the chips inside and out. If you really need Midi I guess there's no other option (well, except for the latest SDI ) , but in every other case the cutting edge for SID work comes from the demoscene, not anywhere else. SDI/JCH/SidWizard/John Player, even the old ones like Music Assembler sound 2000% better than the cart devices.
If you're releasing streaming files (which 99% of the chip scene are) you might as well master them. There's hardly anybody doing music disks outside the demo scene.
Do you have a tracker on there already? You could load program files into it as samples and use those for loops. (we used to use bits of Workbench back in the day)
I'd go Milkytracker, it's portable, fairly coherent to use and if people don't want to do pure chip they can just load a bunch of samples in. lgpt is the least friendly tool to start anybody off with ever.
Ok, I'll bite. Is it because of the joypad interface? Other than the fact that the "reflexes" you build using a joypad to track won't translate to really anything except LSDJ, piggy is the most clearly laid out and approachable tracker I've found.
well, how the heck is anyone going to relate to that? It's just horrible to look at, it's horrible for me and I know what I'm doing with it. Eugh. At least with pc trackers related things are either on the same screen or can be split onto the same screen. It's really difficult to associate one thing with another in this (and LSDJ's) interface, and it's the association between one part of a tracker and another that's really important for learning. I know a lot of c64 trackers have the same problem too.
Actually, thinking about it at a chip music workshop what hardware are people going to best relate to? I'd imagine it'd be gameboy, so perhaps that is the route to go.
I'd go Milkytracker, it's portable, fairly coherent to use and if people don't want to do pure chip they can just load a bunch of samples in. lgpt is the least friendly tool to start anybody off with ever.