Adobe Premiere Pro Crashes Corrected on an M3 MacBook Air with a Cache Reset
Adobe Premiere Pro 24.5 kept quitting roughly every twenty minutes on an M3 MacBook Air while I scrubbed ProRes 422 timelines from a Blackmagic recorder. Clearing both the Media Cache Database and the per-user Media Cache Files folder killed the crash, and relocating the cache to an external SSD stopped it coming back. That afternoon of troubleshooting bled into a few other repairs sitting on the same desk.
Premiere Pro 24.5 on an M3 MacBook Air with 16 GB of unified memory quit during timeline scrubbing about every twenty minutes. The pattern only showed up with ProRes 422 clips brought in from a Blackmagic recorder. H.264 footage shot on a phone kept playing fine. macOS 14 Sonoma logged each event as a normal quit rather than a kernel panic, which told me the machine itself was staying up and the failure was living inside the application layer.
My first guess was a corrupt project file, so I rebuilt the timeline in a fresh project. That did nothing. The crashes came back at the same cadence. Only after that did I go looking at the cache, which is where the real problem turned out to be.
The path Premiere Pro, Settings, Media Cache opens a panel with two relevant buttons. One deletes the Media Cache Database. The other, added in the 23.x line, purges the Media Cache Files. I cleared both with no project open, because Premiere holds file handles on cache material during an active session and a partial delete can leave orphaned peak files behind.
Where the cache was filling the Air
On macOS, Premiere defaults its cache into the user Library, then Application Support, Adobe, Common. When I opened that location the Media Cache Files folder held 41 GB of .cfa peak files and .pek waveform data from projects going back several months. The Media Cache Database sat beside it as a single index file.
Quitting Premiere and deleting the folder contents through Finder gave me the same result as the in-app buttons, and it freed the space faster. That speed matters on the base M3 Air, where the internal drive is the tight part of the setup.
That base machine has a 256 GB SSD. macOS reserves room for swap and snapshots, and this Air also carried a system install plus a Criterion Collection rip library. Stack a 41 GB cache on top of all that and free space dropped low enough that Premiere started failing when it tried to write new peak files during playback. The crash was following that failed write while I scrubbed.
Moving the cache stopped the repeat failure. The same Media Cache panel has a Browse button, and pointing it at an external SSD kept the ProRes projects from rebuilding another oversized cache on the internal drive. I did have to remember to keep that SSD plugged in before opening Premiere, because a missing cache path just sends it back to the Library default without much warning.
The soundbar on the same desk
That same M3 Air also feeds a Dolby Atmos soundbar over HDMI-eARC through a USB-C to HDMI adapter. Atmos needs the source to send a bitstream, so macOS Sound output had to be set to the HDMI device and the playback app had to be allowed to pass encoded audio through.
The soundbar showed PCM instead of Atmos with the first adapter I tried. It took me a while to work out why, since the audio path looked correct on the Mac side. Swapping to an adapter rated for HDMI 2.0 bandwidth fixed it: the earlier adapter negotiated only 1080p60 and stripped the object metadata.
Atmos calibration on most consumer soundbars runs an automatic room-correction sweep from the unit. With the soundbar sitting on a desk, that sweep measured reflections off the monitor and the wall behind the laptop, which flattened the height channels. Disabling the room-correction profile and setting the height level by hand to a low positive offset gave a more accurate overhead image than the automatic pass, which had assumed a couch-distance listening position of two to three metres.
The Stratocaster neck repair
Cache work and soundbar tuning are the kind of jobs where you sit at a desk waiting for a file to rebuild, and while a peak-file pass ran I turned to something that had been on the bench for weeks: a 1990s Fender Stratocaster with a maple neck. Fret sprout had made the edges feel sharp and the fingerboard had gone dry and grey. Fret sprout is the sensation of fret ends sticking past the board edge after the wood contracts in low humidity.
The repair was fret-end dressing with a fret-end file held at roughly 35 degrees. After that I made a light pass with 0000-grade steel wool along the frets only. I taped the pickups over first, so the steel wool fibres would not cling to the magnets.
The maple board mattered here. Vintage-style Strat maple boards have a nitrocellulose or poly finish, and they do not absorb lemon oil the way unfinished rosewood does. Oil on a sealed maple board leaves a film that attracts grime, so I cleaned this one with a barely damp cloth and dried it immediately.
I reset neck relief to about 0.010 inches at the eighth fret, measured with a feeler gauge, a capo at the first fret and the string fretted at the last. The truss rod moved in quarter-turn adjustments, and I overshot on the first turn and had to walk it back before it settled.
String height at the twelfth fret ended up at 1.6 mm on the treble side and 2.0 mm on the bass side, measured from the top of the fret to the bottom of the string. Intonation went in at the bridge saddles against a tuner, checking the twelfth-fret harmonic against the fretted note. The fingerboard did not need replacement, which is the expensive route a shop can quote when fret sprout gets misread as board failure.
Steam Deck storage before the OLED
The guitar work left me thinking about storage that fills up quietly, the same way the Premiere cache had, so the next thing I picked at was the Steam Deck on the shelf above the bench. The LCD Steam Deck ships with a microSD slot that takes UHS-I cards. A 512 GB Samsung EVO Select card, formatted to ext4 through Steam Deck settings under System and Format SD Card, held around a dozen large titles.
The card read slower than the internal NVMe drive, so open-world games took noticeably longer to load. Shader compilation and save writes were unaffected.
Cleaning records without a machine
A manual vinyl cleaning kit with a carbon-fibre brush and alcohol-free fluid handled surface dust and light static between plays. I drew the brush across the rotating record at a slight angle so the bristles lifted particles into the pile instead of dragging them along the groove.
For pressings with visible fingerprints or mould-release residue, the fluid went onto a microfibre pad. I worked it in the direction of the groove and left the record to air-dry on a rack before returning it to an anti-static inner sleeve.
Isopropyl alcohol above about 70 percent can haze some older pressings and can attack the lacquer on shellac 78s, which is why the kit fluid was alcohol-free. Cleaning helps when surface noise comes from dust, residue, or fingerprints. When the clicks and pops are cut into the groove by wear or physical damage, fluid leaves those sounds exactly where they are, and one record in the batch stayed noisy no matter how many passes I gave it.
Headphones for podcast editing and balance checks
Closed-back headphones for podcast editing serve a different role from open-back monitors. The Audio-Technica ATH-M50x isolates well enough to edit in a room with the soundbar running, and it exposes mouth clicks, plosives, and low-frequency rumble that laptop speakers hide entirely.
Its trade-off is bass emphasis. A mix that feels balanced on the M50x can come across bass-shy on other systems, so it is a weak final-balance reference.
For podcast work, the isolation is the reason to reach for it. Editing decisions are mainly about finding artefacts. Plosives that survive a pop filter show up as broadband thumps under 100 Hz, and a high-pass filter set around 80 Hz on a voice track removes them without thinning the voice. What I still catch myself doing is second-guessing a bass level on the M50x, then pulling the audio up on a phone speaker and a car stereo to hear where the low end actually sits before I lock anything down.