Anything pinball on HN is a good day :)
624 karma · joined October 18, 2021
Anything pinball on HN is a good day :)
https://www.fcc.gov/media/radio/low-power-radio-general-info...
I sold the game years ago as it is rather large. I also worked with a few ex-Cinematronics engineers back in the day. They claimed it was a "hack shop" but a lot of fun at times.
https://youtu.be/1LDlOmKtfeQ?t=60
This is a 20 yr old vid shot at Pearl Harbor on the deck of USS Missouri with a low-end consumer Hi-8 camera using built-in mics. Notice flags and clothes rippling in the wind. This filter works pretty well in this case. Maybe it was trained on a New York accent? Mixing in the enhanced track as needed works well. Using only the enhanced track may sound artificial at times.
Here's another vid shot at a brewery where this filter helped clarify the brewmaster's voice over a noisy restaurant and outdoor machinery (again, built-in mic):
I found this filter useful.
Co-produced “Pinball 101”, helping thousands of pinball players up their game: https://youtu.be/_RroLKc4wEQ
Created “Le Dominoux” for a 555 timer contest. Now popular electronics project. https://youtu.be/PQOjkuJtBfM
1) Burn and crash embedded development – burn EPROMs, run until your system reset. Use serial output for debugging. Later, demand your dev board contains EEPROM to speed up this cycle.
2) Tools cost $$$. Cross-compilers weren’t cheap. ICE (in-circuit emulation) for projects with a decent budget.
3) DOS 5.0 was boss! Command line everything with Brief text editor with text windows.
4) Upgrading to a 486dx, with S3 VGA – Wolfenstein 3D never looked so good!
5) The S3 API was easy for 1 person to understand. With a DOS C compiler you could roll your own graphics with decent performance.
6) ThinkPad was the best travel laptop.
7) Sharing the single AMPs cellphone with your travel mates. Service was expensive back then!
8) Simple GANTT charts scheduled everything, +/- 2 weeks.
9) You could understand the new Intel processors – i860 and i960 – with just the manuals Intel provided.
10) C Users Group, Dr Dobbs, Byte, Embedded Systems Journal and other mags kept you informed.
11) Pay wasn’t great as a software dev. No stock options, bonus, or overtime. If your project ran late you worked late! A few years later the dot com boom raised everyone’s wages.
12) Design principles could be as simple as a 1-page spec, or many pages, depending on the customer. Military customers warranted a full waterfall with pseudo-code, and they paid for it.
13) Dev is much easier today as most tools are free, and free info is everywhere. However, system complexity quickly explodes as even “simple” devices support wireless interfaces and web connectivity. In the old days “full-stack” meant an Ethernet port.
https://www.sdmts.com/inside-mts/current-projects/uc-san-die...
I also tested with wind noise (outdoor speaker) and the audio "recovery" is amazing. It rescues bad field recordings that you normally can't use. I'm impressed!
1) I'm thankful my elderly parents and in-laws are healthy and survived the worst of the pandemic.
2) I'm thankful new relatives are healthy and thriving (who doesn't adore babies?)
3) I'm thankful my immediate family is OK. Zoom-schooling and masking is not ideal but we adjusted and adapted.
4) I'm in awe of the medical professionals who withstood the brunt of the pandemic and continue to provide for our well-being.
5) And the technologists that support the medical professionals -- the those who build the tools, design the scientific instruments, operate the equipment, push the tech to incrementally do more -- all this seems like magic but is comprised of late night debugging, inspired insight, that blood-sweat-beers workpersonship that keeps society chugging along.