Mod Archive Forums

Music Production => MilkyTracker => Tracking => MilkyTracker Support => Topic started by: radian on April 03, 2009, 16:55:04

Title: 9xx Sample offset docs, stupid question
Post by: radian on April 03, 2009, 16:55:04
This part of the manual is pretty confusingly phrased, using both meanings of sample in the same bit. Anyway, as far as this part goes:

Quote
Tips:    Resampling a loop to exactly (0x10000=) 65536 bytes gives you the highest possible level of control over the sample.

How many samples or milliseconds does this translate to? I assume it different in 8 or 16 bit samples?
Title: Re: 9xx Sample offset docs, stupid question
Post by: raina on April 03, 2009, 18:39:52
Feel free to suggest a clarification, it's a little hard to stay away from the word. :)

Byte is a sample and it doesn't translate to milliseconds because that would depend on the playback speed. MilkyTracker makes the conversion (in display) so that there's no difference to the user between 8 and 16-bit samples.
Title: Re: 9xx Sample offset docs, stupid question
Post by: radian on April 03, 2009, 19:06:38
So timestretching a 1 bar drumbeat .wav to a multiple of 65536 samples long makes 9 80 exactly halfway through the bar?
Title: Re: 9xx Sample offset docs, stupid question
Post by: raina on April 03, 2009, 19:46:45
Well, not a multiple (unless you count 16-bit), but exactly 65536 bytes. But yes, 980 offsets the playback by 32768 (0x8000) samples, which is exactly half of 65536.