I don't understand cars either LOL. But I drive one, and can put gas and oil in it, and discern when something sounds off.
I do have a very basic understanding that computers run on commands that are all basically yes or no.
So people write programs that allow us to do things by telling the program yes or no to something that
is already written in. I may have expressed that wrong. Image files allowed on this web site must have
the extension of being a jpg, a gif, or a png. Those are the allowed file types. Anything else will be an
error and rejected by the site's programming. Same thing with videos allowed: only from youtube, I think.
So if someone wants to post a video from somewhere else, they can only link to it, because the site
program prohibits (does not allow) other media of that type. Videos often come with sound. So that
would be a specific file type, MP3 or MP4, or a wav file, or maybe something else. How our devices
actually decipher those files I do not comprehend beyond it being through some program with all
those yeses and nos turned on or off so we can see and hear what is being presented. I mentioned
designing web pages using a template... that was all text. So I had to learn to read long sequences
seemingly incomprehensible text to look for what was familiar within the code. That text told the
website what to display, just as this site does, and we can change the colour and size and style of text
because the program allows for that and gives us an easy way to do it. Anyways, these text to speech
and speech to text apps operate on the same premise, and create a file you can save to your device and
then add to something else, just like I design an image in photoshop, make it a specific file type so
I can post it here, and then it is displayed because the program knows what to do with what is given.