Didn't realize they were so broad in scope. The only thing I had heard of was "SMPTE codes" used in audio recording to sync up multiple multi-track recording machines, so that e.g. you could record 30 tracks using two 16-track recorders (with one track on each machine used for the sync). I never bothered to look up what SMPTE meant.
You’re likely referring to SMPTE timecode, a method of conveying timing information about a video signal (eg. HH:MM:SS:FF), which is SMPTE 12M. There are various ways that timecode is conveyed in media such as LTC (linear timecode, usually carried as an audio signal), VITC (vertical interval timecode, in the vertical blanking interval of a video signal), and others.
I'm old enough and lucky enough to have had my first computing experiences (1978-80) be on a teletype in our elementary school which was connected to a minicomputer that the town owned. The connection was an acoustically coupled modem/analog phone line that ran at 300 baud. The exciting thing was to write very basic BASIC programs and see results on the printout. There was no CRT, everything was via the literal teletype - a keyboard and a clunky printer.
I've been using the Codex app for a while (a few months) for a few types of coding projects, and then slowly using it for random organizational/productivity things with local folders on my Mac. Most of that has been successful and very satisfying, however...
Codex is still far from ready for regular people. Simply moving a folder that Codex has been working on confuses the hell out of it. I can't figure out how to fix "Current working directory missing. This chat's working directory no longer exists". I've tried asking it to fix the problem and it tries lots of terminal commands and screws around with SQLite. Something this brittle is not for non-developers.
Moving the folder you’re in out from under yourself is okay if you know you did it - but if you don’t, you’re gonna get confused :) And so is an agent!
I'm very used to tools which keep track of connections to documents based on internal IDs, not folder structure. It seems primitive to be so brittle.
It seems even more stupid that it was so hard to get Codex to fix this for me. I managed to get it to solve the problem, but not before it got itself in this crazy loop of restarting the app, wanting to quit, quitting even if I canceled the quit dialog, and restarting over and over. I was able to reboot my machine and it had sorted out the missing references to most of the projects, but wow.
This is an amazing deep dive into color difference measurements and how sensitive the math is. The idea that we really need to save characters - bytes - in CSS when we have so many web sites chewing through 49 MB with the enshitification of the web is hard to reconcile.
I've been using Codex (GPT-5.4 extra high) to code custom FeatureScript in Onshape (3D mechanical CAD software). It's challenging to get it to do TDD that involves any visual reasoning. At the moment I've got tooling through Google Chrome Devtools MCP and Playwright to extract things and control the browser and I use some custom features which help with formatting and controlling debugging outputs (text and visual overlays). Mostly the text debugging outputs are very helpful to Codex. It will often add debugging payloads when we're focused on a particular issue. I do occasionally take screenshots and paste them into Codex and explain the issue that I'm seeing. It seems to understand a certain amount, especially if the issue can be seen in orthogonal views.
Might as well be 3862 grams considering how much they hurt to wear for any length of time. I was also hoping this update would improve the ergonomics, but no. Still too heavy and no mention of any improvements to the headband.
I have a pair of the first generation AirPods Max. They leave dents in my scalp if I wear them for any real amount of time. I've been an Apple person since the 1980s. This is one of the most disappointing Apple products for me ever, and I really don't want to know how much $$$$$ lifetime customer value I've contributed to Apple's bottom line.
I had the same reaction to the originals. They just hurt! One of my kids swiped them and I never used them again: I wanted to like them but they were almost as uncomfortable as my Vision Pro
reply