Print

[bentendo]

I am running V0.4 from supercard lite with transflash micro SD, having got barni's DLDI.

Pan - initial value 64, does not work, can scroll to values of 0 and 127 but has no effect on audio output. Ihave tried loading mono and stereo files but it has no effect.

rel - initital value c-4 when sample bank empty, but when sample is loaded it jumps to a random value (different each time?). It should remain at default of c-4 after loading sample. Also upon scolling through the possible values i have noticed that going upward after a#4 it goes to h-4, this should read b-4.

tune - initial value 0 when sample bank empty, but when sample is loaded it jumps to a random value (different each time?). It should remain at default 0 after loading sample.

[andars]

The h-4 thing is a European thing i guess, where B is written as H

[bentendo]

pan issue resolved , it was my soundcard mixer doh! I have audio in 1 an 2 which appear on my soundcard mixer with a pan knob and both were panned centrally so could not hear the panning from nitro. Also had a response from tob regarding the rel and tune issues:
"
OK, this is a bit unintuitive: In the XM format, samples are all saved
with the same base frequency which is 8363 Hz. You cannot have samples
at other frequencies, which sucks, but that's how they designed XM.  So,
all frequency adjustments are done via the "relative note" and
"finetune" settings. Now if you load a sample at some arbitrary sampling
frequency intro NitroTracker, it calculates the relative note and
finetune settings such that it is played back at the original frequency
even though internally it gets stored at 8386 Hz. This is confusing.
"

[pailes]

Well in FT2 there simply is no C4 speed value like in other trackers. Instead there is relative note number and fine tune. Actually it's pretty much the same, you can convert from one into the other and vice versa.

[zoikkis]

Haven't seen random values, rel is always e-6 and tune is 100 when a new sample has been loaded.

Having either 'b' or 'h' is a matter of taste methinks('h' commonly used in a classical notation), but maybe 'b' is more common with trackers so should that be changed? I didn't port this to the issue tracker at this point.