2026-03-28 13:00:26
One thing SEGA’s MegaDrive/Genisis and the Commodore Amiga had in common was–aside from the Motorola 68000 processor– being known for excellent music in games. As [reassembler] continues his quest to de-assemble Sonic: The Hedgehog and re-assemble the code to run on Amiga, getting the music right is a key challenge. Rather than pull MIDI info or recreate the sound by ear, [reassembler] has written a program called Sonic2MOD to automatically take the assembly file music from the MegaDrive catridge and turn it into an Amiga-style MODfile. He’s also made a video about it that you’ll find embedded below.
Of course how music gets made differs widly on the two systems. Amiga, famously has Paula, a custom ASIC designed for sampling, allowing you to play four eight-bit voices. The Sega, of course, has that glorious FM-synthesis chip from Yamaha synthesizing five channels of CD-quality sound and one channel of sample. It’s not as well known, but the Sega also has a bonus TI-compatible programmable sound chip (PSG) that can handle 3 square-wave tone channels and one noise channel. That’s ten total channels to the Amiga’s four, and CD-quality to 8-bit voices. Knowing all that, we were very curious how close to SEGA’s original music [reassembler] could get on the Amiga.
Before he could show us, [reassembler] needed to decode the SMPS files used on Sonic: The Hedgehog and many other MegaDrive games. Presumably he could have gotten a MIDI file online somewhere– there are oodles– but the goal was to reverse engineer Sonic from its cartridge for the Amiga, not download a lot of resources from the web. SMPS is a sort of programing language for sound, telling the Yamaha and PSG chips what to do.
In some ways, it’s not unlike the Amiga’s MOD format, which programmatically specifies how to play the sampled voices also stored in the file. Translating from one to another is a matter of reading the SMPS files, extracting the timing, volume, vibrato, et cetera, and translate that into a form the MOD file can use. Then [reassembler] needed to generate samples, which was an added hiccup because the Amiga can only handle 3 octaves vs the seven of the SEGA’s FM synthesizer. He’s able to solve this simply by generating multiple samples to span the Yamaha chip’s range, though, again, at only 8-bit fidelity. It doesn’t sound half bad.
What about the four-channel limit? That’s where a bit of artistry comes in; the automated tool produces MOD files with more voices, which MOD trackers can handle at increased computational load. Computational load you don’t need when trying to play a game. Scaling down the soundtrack to the Amiga’s limits is something [reassembler] already has practice with from his famous OutRun port, though, so we’re sure he’ll get it done.
All of this effort just to match the Mega Drive makes us appreciate what a capable little computer the Sega console was; why, you can even check your stocks with it! We’ve already featured [reassembler]’s Sonic port once before, but this music tool was interesting enough we couldn’t help ourselves coming back to it. The ability to play MOD files were pretty impressive when the Amiga came out, but nowadays all you need is a ten-cent microcontroller.
2026-03-28 10:00:09
Once the premium option for data transfers and remote control for high-end audiovisual and other devices, FireWire (IEEE 1394) has been dying a slow death ever since Apple and Sony switched over to USB. Recently Apple correspondingly dropped support for it in MacOS 26, and Linux will follow in 2029. The bright side of this when you’re someone like [Jeff Geerling] is that this means three more years of Linux support for one’s FireWire gear, including on the Raspberry Pi with prosumer gear from 1999.
If you’re not concerned about running the latest and greatest – and supported – software, then using an old or modern Mac or PC is of course an option, but with Linux support still available [Jeff] really wanted to get it working on Linux. Particularly on a Raspberry Pi in order to stay on brand.
Adding a FireWire port to a Raspberry Pi SBC is easy enough with an RPi 5 board as you can put a Mini PCIe HAT on it into which you slot a mini PCIe to Firewire adapter. At this point lspci shows the new device, but to use it you need to recompile the Linux kernel with Firewire support. On the Raspberry Pi you then also need to enable it in the device tree overlay, as shown in the article.
With this you now have FireWire 400 support right off the bat, but to use the FireWire 800 port you need to also connect external power to the adapter, which [Jeff]’s Canon GL1 video camera with its FW400 port does not require, so he didn’t bother with that.
Capturing the video from the GL1 via FW400 was done using the DVgrab utility, with a subsequent capture attempt successful. This means that at least until 2029 [Jeff] will be happily using his GL1 camera this way.
Meanwhile over on the Dark Side, you can still happily install FireWire drivers made for older Windows versions on Windows 10 and 11, which is great news for e.g. people who have expensive DAW gear kicking around. Perhaps the demise of FireWire is still a long while off as long as you’re not too picky about the OS you’re running.
2026-03-28 07:00:02
Recently [ETA Prime] felt a bit underwhelmed by the raw performance of his MacBook Neo when it came to running for extended periods under full load, such as when gaming. Thus the obvious solution is to mildly over-engineer a cooling solution that takes care of issues like thermal throttling.
The Apple MacBook Neo with its repurposed iPhone 16 SoC seems to have leaned hard into answering the question whether a smartphone can be a good general purpose personal computer. Ignoring the lack of I/O, it’s overall not a bad SoC for a laptop, but like when you try to push the CPU and GPU on a smartphone, they do get pretty toasty. Due to the minimalistic cooling solution in the MacBook Neo it’ll easily hit the 105°C thermal throttle limit.
Technically the ‘heatsink’ for this laptop is the aluminium case, as the SoC is coupled via a thermal pad to the case. This doesn’t leave a lot of space and the case will heat soak pretty fast, while also making retrofitting a cooling solution a challenge.
Amusingly, replacing the existing thermal pad with a thin copper plate already massively reduced the thermal throttling of the A18 Pro SoC by about 20 degrees. In Geekbench 6 this bumped multi-core scores up by 9.7% and single-core by 15.2%. Definitely a promising glimpse at how much performance could still be extracted from this SoC.
For the next step a thermo-electric cooler (TEC) with built-in water cooling loop was used, which happened to be one of those overkill smartphone cooling systems that you’d stick to the back of the phone. Here the cooler was attached similarly, directly to the bottom aluminium of the case.
With this solution in place Geekbench 6 results mostly showed a solid bump for single-core results, while multi-core results showed diminishing returns. For Cinebench results this gave a 19% increase over stock cooling in multi-core and 23.5% for single-core.
Perhaps most interesting of all was that playing a video game for a while without thermal throttling meant framerates of over 80 FPS instead of hitting that thermal wall with 30 FPS. This shows just how much performance is left on the table due to the cooling choices for the system, even with this still rather inefficient cooling solution.
That said, this probably isn’t some kind of nefarious scheme by Apple, but rather the result of designing the thermal solution to not heat the case up to temperatures that are deemed to be unsafe or uncomfortable for the user. After all, if the case if the heatsink, then you don’t want to feel like you’re literally handling one. This is sadly the compromise when venting out hot air is deemed to be an unacceptable solution.
2026-03-28 04:00:10
Laser Welding is apparently the new hotness, in part because these sci-fi rayguns masquerading as tools are really cool. They cut! They weld! They Julienne Fry! Well, maybe not that last one. In any case, perhaps feeling the need to cancel out that coolness as quickly as he possibly could, YouTuber [Wesley Treat] decided to make a giant version of his own head.
[Wesely] had previously been 3D scanned as part of the maker scans project, which you can find over on Printables. Those of you who really hate YouTubers, take note: finally you have something to take your frustrations out on. [Wesely] takes that model into Blender to decimate and decapitate– fans of the band Tyr may wonder if the model questioned his sword–before feeding that head through an online papercraft tool called PaperMaker to generate cut files for his CNC. There are also a lot of welding montages interspersed there as he practices with the new tool. [Wesely] did first try out his new raygun on steel in a previous video, but even knowing that, he makes the learning curve on these lasers look quite scalable.
While we’re not likely to follow in [Wesely]’s footsteps and create our own low-poly Zardoz– Zardozes? Zardii?– using a papercraft toolchain and CNC equipment with sheet aluminum is absolutely a great idea worth stealing. It’s very similar to what another hacker did with PCBs— though that project was perhaps more reasonable in scale and ego.
We are no strangers to papercrafts that use actual paper here, either, having featured everything from model retrocomputers to fully-mobile strandbeasts.
2026-03-28 02:30:23
Embedding fasteners or other hardware into 3D prints is a useful technique, but it can bring challenges when applied to large or non-flat objects. The solution? Use a gap-cap.
The gap-cap technique is essentially a 3D printed lid. One pauses a print, inserts hardware, then covers it with a lid before resuming the print. The lid — or gap-cap — does three things. It seals in the part, it fills in empty space left above the component, and it provides a nice flat surface for subsequent layers which makes the whole process much cleaner and more reliable.
This whole technique is a bit reminiscent of the idea of manual supports, except that the inserted piece is intended to be sealed into the print along with the embedded hardware under it.
If you have never inserted anything larger than a nut or small magnet into a 3D print, you may wonder why one needs to bother with a gap-cap at all. The short version is that what works for printing over small bits doesn’t reliably carry over to big, odd-shaped bits.
For one thing, filament generally doesn’t like to stick to embedded hardware. As the size of the inserted object increases, especially if it isn’t flat, it increasingly complicates the printer’s ability to seal it in cleanly. Because most nuts are small, even if the printer gets a little messy it probably doesn’t matter much. But what works for small nuts won’t work for something like an LED strip mounted on its side, as shown here.
In cases like these a gap-cap is ideal. By pre-printing a form-fitting cap that covers the inserted hardware, one provides a smooth and flat surface that both seals the component in snugly while providing an ideal surface upon which to resume printing.
If needed, a bit of glue can help ensure a gap-cap doesn’t shift and cause trouble when printing resumes, but we can’t help but recall the pause-and-attach technique of embedding printed elements with the help of a LEGO-like connection. Perhaps a gap-cap designed in such a way would avoid needing any kind of adhesive at all.
2026-03-28 02:00:21
What did Elliot Williams and Al Williams read on Hackaday last week? Tune in and find out. After a bit of news, [Vik Oliver] chimes in with some deep PLA knowledge. Then the topic changed to pressure advance measurements, SDRs, making super-resolution PCBs with a fiber laser, and more.
Want to 3D print wire strippers? A robot arm? Or just make your own Z-80? Those hacks are in there, too.
For the long articles, we talked about old tech, including the :CueCat and the Iomega Zip Drive. Let us know if you had either one in the comments.
What do you think? Leave us a comment or record something and send it to our mailbag.
Download a copy of the podcast with no corporate trackers in the clean MP3.
