Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /storage/content/49/145849/famitracker.com/public_html/forum/classes/dbHandler.php on line 29
Basically, you use custom samples. There is no popping of changing samples. So, famitracker employs multiple samples an instrument, and the ability to change them like the duty settings on the pulse channels. Also, from what I gather, it can only play one sample from each of the 4 buffers at a time. All channels playing instruments on the same buffer will use the sample of the highest-numbered channel using samples in that buffer. You can also change the amount of samples in the sample, in increments of 4 up to 32. In famitracker, anything NOT 4/8/16/32 will will be off. And that is what I know so far, if it helps you.
[quote=kinkinkijkin]I will help you in your learning.[/quote]
Let's see what you got.
[quote=kinkinkijkin]Basically, you use custom samples.[/quote]
Well, they're called waveforms, but I'll give you that. ("Sample" is the term usually given to each "step" in the waveform, if you will.)
[quote=kinkinkijkin]There is no popping of changing samples. So, famitracker employs multiple samples an instrument, and the ability to change them like the duty settings on the pulse channels.[/quote]
That bit's right. Also, you can use Vxx within the tracker itself.
[quote=kinkinkijkin]Also, from what I gather, it can only play one sample from each of the 4 buffers at a time.[/quote]
They're actually "memory positions", though they do act a bit as ppMCK's buffers do. In FT, you choose exactly where to put your waveform in the memory, whereas ppMCK's "buffer" system handles that automatically (and is therefore less reliable and less accurate, and more prone to errors).
[quote=kinkinkijkin]All channels playing instruments on the same buffer will use the sample of the highest-numbered channel using samples in that buffer.[/quote]
That's half true, actually. It is the case when two instruments attempt to read the exact same memory location (the longer wave always gains precedence), but not if your second wave tries to read after the beginning of the longer wave, in which case the first portion will be read from the other wave, and then the portion of the wave that doesn't overlap will play.
For instance, if you have a wave going from 0 to 31, and you're trying to play another 32 sample wave from position 16, it'll play the last 16 samples of the first waveform, and THEN the last 16 samples of the current instrument's waveform.
[quote=kinkinkijkin]You can also change the amount of [b]samples[/b] in the [b]sample[/b][/quote]
Ah yes, very clear...
What you meant, I'm guessing, was "you can set the length of an instrument's waveforms to any number between 4 and 32, in increments of four".
[quote=kinkinkijkin]In famitracker, anything NOT 4/8/16/32 will will be off.[/quote]
Correct, only the powers of two are accurately tuned. Those that aren't in tune can be approximately corrected using Pxx (or just an arp macro if you want to save yourself the trouble - but the notes will still be a few cents off).
[quote=kinkinkijkin]And that is what I know so far, if it helps you.[/quote]
Looks like you did your homework then!
I haven't messed around with n163 on famitracker much, yet, but I think the number of channels you have depends on how large the wavetable is for the instrument you're using.
Basically, with higher quality instruments that have larger tables, you really only have 4 channels.
Not true! The N163 has 128 bits for waves + channels, but 2 steps in a waveform = 1 bit, so even with 8 channels (64 bits) enabled, you can still have 4 32-sample waves at once!
Ah! right, I was getting number of maxed out(32) sample waves confused with active channels...or something. Man, I haven't touched that chip in a while...forgot exactly how the buffer works.
I wonder how accurately FT produces realtime buffer abuse...