Differences

This shows you the differences between two versions of the page.

--- tonegen_design [2022/03/17 02:34]
dpisuperadmin [Minimal Tone Generator with Volume Control]
+++ tonegen_design [2022/03/20 03:51] (current)
dpisuperadmin
@@ Line 11: / Line 11: @@
 The FPGA never sees the note C0 or the frequency.  All it sees is the phase offset per sample and this is set by a look-up table in the host. Feeding the MSB of the phase accumulator to an output pin is a minimal tone generator.
-==== Minimal Tone Generator with Volume Control ====
+==== A Minimal Tone Generator with Volume Control ====
-A full synthesizer, as described below, may take more that its fair share of FPGA logic.  This is fine if the goal of the project is a synthesizer but is not fine if the user wants something that just beeps.  This section describes something that beeps but includes volume control.
+A full synthesizer may take more that its fair share of FPGA logic.  This is fine if the goal of the project is a synthesizer but is not fine if the user wants something that just beeps.  This section describes something that beeps but includes a volume control.
 The API for a simple tone generator might specify the musical note to play, the volume in the range of 0 to 100, and the number of milliseconds to play the note.  We might also want to play a file of notes where each line the the file has the note, volume, and duration.  For example:
-    dpset tonegen tone b4 30 200
+    dpset tonegen note b4 30 200
-    dpset tonegen play mymelody.txt
+    dpset tonegen melody mymelody.txt
 {{ wiki:audiotaper.png?200|}} Square waves are easy to generate and have a pleasing sound since they have lots of higher harmonics.  A more difficult question for a simple tone generator is how to control the volume.  Human hearing perceives audio volume on a logarithmic scale.  Electronics manufactures use what is called a 'audio taper' for potentiometers in audio applications. The diagram to the right shows an audio taper and we want our gain control to follow the same curve.
@@ Line 39: / Line 39: @@
 a 24 bit phase offset set by the host,
 four 4 bit PDM counters,
-four 4 bit gain settings set by the host,
+four 4 bit gain settings set by the host, and
-an 8 bit duration counter (to count milliseconds), and
+an 8 bit duration counter (to count milliseconds),
-an 8 bit duration set by the host,
 (The diagrams in this section were generated using Octave.  The sources are attached to this section in a wiki comment.  Edit the page or contact the author to get the sources for the diagrams.)
@@ Line 155: / Line 154: @@
 grid on;
 print -dpng '/tmp/r2-2.png';
-% Generate 100 points on an log curve and map the gain
-% to setting in pwm - nonlinear DAC scheme.  This gives
-% the actual table to use in the API driver modules.
-% Manually add {0,0,0,0} and {15,15,15,15}.
-% Get the target gains
-x = 1:1:100;
-out = exp((5 .* x) ./ 100) ./ 150;
-target_idx = 1;
-% loop past all possible gains recording the first to pass out(target_idx)
-idx = 0;
- for i3 = 0:15;
-  for i2 = 0:15;
-   for i1 = 0:15;
-    for i0 = 0:15;
-     idx = idx +1;
-     outval = ((i3 .* .73203) + (i2 .* .19608) + (i1 .* 0.05229) + (i0 .* 0.01307)) ./ 16;
-     if outval > out(target_idx),
-         %printf("%d %f {%d, %d, %d, %d},\n", target_idx, outval, i3, i2, i1, i0);
-         printf("{%d, %d, %d, %d},\n", i3, i2, i1, i0);
-         target_idx = target_idx + 1;
-     end
-    end
-   end
-  end
- end
 */
-==== Wave Tables ====
-{{ wiki:wavetable.png?300|}}A wave table captures a waveform by dividing it into slices and recording the output value for each slice.  If the address decoder has N bits then the length of the table is 2^N.  A wave table is usually driven by the N high bits of a phase accumulator.
-The number of bits in each word determine the audio fidelity of the output.  The values in the table are often the sign and the log of the desired value.  Human hearing is such that perceived volume follows a logarithmic scale, and using log value makes subsequent gain and modulations easier since multiplication in a linear scale is just addition in a log scale.  You can get the best fidelity from the least number of bits by making the waveform span the full range of M bits.  The log function can be log-base-2, natural logarithm, or one of the standard u-law or a-law functions.
-There are often more than one wave table and while each may have a default, all can be set from the host.  The API is to be determined but might appear something like:
-    dpset tonegen table_id 3      # select the table to download
-    dpset tonegen table_addr 0    # point to first address in table
-    dpset tonegen table_val 00 12 34 56 78 9a 87 56 78 88 99 aa bb cc dd ee
-    dpset tonegen table_val ff ee ff ee ff ee ff ee ff ee ff ee ff ee ff ee
-    (... for all 2^N values ...)
-==== Gain Blocks ====
-{{ wiki:gain.png?150|}}  As mentioned above, gain is just addition when using log amplitude values.  You have a few choices when dealing with the issue of overflow.  One approach is to increase the sample size at each addition.  This is shown in the diagram at the right.  This approach maintains the greatest fidelity through the system at the expense of consuming more FPGA fabric.  Another approach is to use //saturating arithmetic//.  Saturating addition prevent overflow by clipping the output to a maximum value.  For example, in 8 bits the value of ''FF+1'' would not be zero but remain at ''FF''.
-Another consideration is the meaning of gain.  If the values in the wave tables represent the smallest signal then gain means amplification.  It the value represent the loudest samples possible then gain means attenuation and the gain block is actually subtraction.

Demand Peripherals

User Tools

Site Tools

Differences

Page Tools