Why not - alternatively - from left-to-right or vice versa? *scratches head*
See the well known scanning we're used to:

Now ... would it be impossible to scan from left to right or right to left here - meaning implement such a readout alternative?

Because this way the shape of the individual waveforms are clearly shown .elassi wrote: Sun Sep 08, 2024 3:14 pm Wondering if scanning of a wavetable has to be always from bottom-to-top or vice versa when we look at a 3D-representation of a table like shown in numerous WT-synths.
Why not - alternatively - from left-to-right or vice versa? *scratches head*
See the well known scanning we're used to:
Now ... would it be impossible to scan from left to right or right to left here - meaning implement such a readout alternative?![]()
Interesting.Funky40 wrote: Sun Sep 08, 2024 3:53 pm This VCO does it in an arrangement of 3 axis.
http://www.industrialmusicelectronics.com/products/21
Honestly, no.GruvSyco wrote: Sun Sep 08, 2024 4:02 pm I think it would be hard without converting the entire table to something else.
Yes, but its basically one index into a linear array of single-cycle waves, (which are themselves a linear array of single sample values). Basically its already a 2-dimensional array. The actual code could even be treating it as such...Current wave-tables are literally that. It's a linear group of single cycle waves.
Not necessarily, though I may be misinterpreting you. Its entirely possible that the full single cycle is read in its entirety, and the wavetable index is only updated once per read through that whole single cycle.You are talking about reading a bit from each wave in the table at a time.
You cant scan a linear table 'up and down' and 'left and right' as well. Its either/or. For the table to be scannable in two dimensions it needs to be a two-dimension table in the first place.elassi wrote: Mon Sep 09, 2024 2:47 pm I'm not talking about the visualization but indeed about the resulting audio readout of the waveform. It's defo another result when you scan the table from left to right instead of top to bottom (and each vice versa).
Therefore I suspected that the table has to be a square in that case to provide the same specs (i.e. 2048 samples).
Without some fancy interpolation, I think you'd probably wind up just getting noise or DC by scanning in the orthogonal direction, unless you do something akin to what Ensoniq did with transwaves to make sure their wavetables were always nicely behaved. You might get somewhere with a sinc(x,y) waveform for example but once it gets a bit more arbitrary, none of your waves line up nicely.elassi wrote: Mon Sep 09, 2024 2:47 pm I'm not talking about the visualization but indeed about the resulting audio readout of the waveform. It's defo another result when you scan the table from left to right instead of top to bottom (and each vice versa).
Therefore I suspected that the table has to be a square in that case to provide the same specs (i.e. 2048 samples).
I must be missing something but almost every wavetable can be read in the opposite directionelassi wrote: Mon Sep 09, 2024 2:47 pm I'm not talking about the visualization but indeed about the resulting audio readout of the waveform. It's defo another result when you scan the table from left to right instead of top to bottom (and each vice versa).
Therefore I suspected that the table has to be a square in that case to provide the same specs (i.e. 2048 samples).
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026