all I/O can be scaled/offset on the network page. (since latest update?)
wavetable oscillators generally don’t care about sample rate.
the only thing that is important is to split the data correctly into single cycles.
thats why NrWavs is vital to be correct.
lo-fi will not make any difference, however, its quite common to get aliasing if you use small wavetables.
so personally, I look for larger single cycle waves not smaller.
there is no ‘initial’ about it
it defines the number of waves in the file you have loaded.
note: the wav file format, has no means of encoding this information - this is why the user has to set it appropriately.
wavetables are prepared on a desktop/laptop. (*) often using dedicated wavetable tools, but if you are careful you can do a certain amount with normal audio editors e.g. even with audacity (free) you could combine wav files - but its pretty easy to screw it up
at the end, all a ‘wavetable’ is, is a series of single cycle waves that are exactly the same length,
and the wavetable oscillator just needs to know how many there are, so it can ‘cut up’ that file correctly.
(they could work by being told the length instead, but its easier for end-users to think in terms of number of waves)
(*) I can’t think of any hardware synth that allows prepping of wavetables on board, its too much ‘fiddling’ to do on something without a full size monitor and a mouse.
there is one thing Im a bit ‘unsure’ on, which perhaps @bert could throw some light on…
how does a non-cubed number of waves get divided by x/y/z.
e.g. 9 (3x3x3) is easy, we have 3 axis each with 3.
but how does (NrWav) 12 wave get divided? 2.289 ^ 3 ?
can fractions of a wave be divided over an axis whilst still ensuring they are cycles?
seems odd in my head - but perhaps Im just ‘overthinking it’ , perhaps the maths ‘just work’
Im just curious really, as I think id stick to x^3, just since it makes more sense to my brain!