From: Al Kossow <aek@bitsavers.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Monitoring by loudspeaker
Date: Sun, 12 Jul 2020 09:09:56 -0700 [thread overview]
Message-ID: <8cf76d2d-c598-9c5c-3bcc-8b3e0518e313@bitsavers.org> (raw)
In-Reply-To: <20200712145822.GA72854@fuz.su>
On 7/12/20 7:58 AM, Robert Clausecker wrote:
> That's how you know that the machine is stuck in an endless loop: if it
> was doing something useful, the values would change every iteration and
> you would get white noise again.
Computers are capable of generating PWM speech with a single bit output
https://www.youtube.com/watch?v=IIejqWEV_8w
is an example on the Apple II
or multi-voice music using multiple bits
https://www.youtube.com/watch?v=dTaVffknxEY
the sound is not 'white noise' which implies totally random output
any loop in the code will produce a unique sound when it is running
next prev parent reply other threads:[~2020-07-12 16:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 1:08 [TUHS] AT&T Research John P. Linderman
2020-07-11 1:32 ` Larry McVoy
2020-07-11 1:51 ` John P. Linderman
2020-07-11 15:36 ` Clem Cole
2020-07-11 20:30 ` Warren Toomey
2020-07-11 20:36 ` Jon Steinhart
2020-07-11 21:58 ` Rob Pike
2020-07-11 22:29 ` Larry McVoy
2020-07-12 7:55 ` Ed Bradford
2020-07-12 2:22 ` [TUHS] BTL pranks [was AT&T Research] Doug McIlroy
2020-07-12 11:58 ` [TUHS] Monitoring by loudspeaker (was: BTL pranks) Michael Kjörling
2020-07-12 13:25 ` Dan Cross
2020-07-12 14:58 ` Robert Clausecker
2020-07-12 16:09 ` Al Kossow [this message]
2020-07-12 20:10 ` [TUHS] Fwd: Monitoring by loudspeaker Rich Morin
2020-08-23 8:58 ` [TUHS] " Tom Ivar Helbekkmo via TUHS
2020-07-23 4:13 ` [TUHS] AT&T Research scj
2020-07-23 6:02 ` [TUHS] Technical decisions based on political considerations [was Re: AT&T Research] arnold
2020-07-23 14:42 ` Larry McVoy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8cf76d2d-c598-9c5c-3bcc-8b3e0518e313@bitsavers.org \
--to=aek@bitsavers.org \
--cc=tuhs@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).