exactly.
the loop() is called continuously from (hidden) main. Every direct call to set the volume can generate a glitch. So, put all one-time settings into setup().
If you need to modify volume during replay, you...
Are you sure? It is easy to verify.
AFAIK, I2S input allocates 4 blocks for input and you have only 5. You need IMO at least 6 to allow allocation of new blocks while data are still written to USB.
Keep in mind that...
If you have access to GND (e.g. battery) then behind the hole needs to be only a contact that is connected to program pin. A grounded needle / wire will put teensy into programming mode.
or have two nails (GND and...
Even without button, you still have the Program Pin, you can use to start programming by touching GND.
It is fairly common for systems that are enclosed to have program pin accessible.
No, connect I2S MEMS directly to Teensy replacing the Audio shield.
Run the following program
#include <Audio.h>
#include <Wire.h>
#include <SPI.h>
#include <SD.h>
#include <SerialFlash.h>
// GUItool: begin...
Similar to @StefanPetrick delivery can take long time (in my case > 3 weeks) for delivery from UK to Germany (standard shipping).
In addition to VAT I had also to pay custom handling.
Can someone explain in two sentences:
Apart from replacing "void (*funct)()" by "callback funct" is there any other advantage, and what is different to "typedef void (*callback)() ;" that I used in the past?
and why...
The standard procedure is to access microSD card within the loop() function and to sample the sensors on interrupt level (say running a timer)
on a T4.1 a sample easily 6 sensors at 96 kHz and write to disk.
these high latencies are quite normal and within the specs and a couple of times discussed on this forum.
They are due to microSD card internal activities (bad block handling, wear levelling). In case you do not know,...
Find latest posts