ASFireWireTest a device
INDEPENDENT ENGINEERING · SUPPORT DEVELOPMENT

Why I’m asking for support.

I started ASFireWire because I love audio and wanted good FireWire gear to stay useful instead of becoming e-waste. Keeping it working takes more than writing code.

Free to use · Open source · Apache-2.0Explore the project ↗
WHY SUPPORT HELPS

Keeping the project going takes time and money.

I’m Aleksandr Shabelnikov (@mrmidi), the creator and maintainer. I’ve spent more than a year building the driver. New device reports mean investigation, fixes, and testing, often with hardware I have to buy myself.

There are recurring costs too: Apple’s Developer Program, which I need to sign distributable builds, development tools, and hardware for testing.

For now, public signed downloads are paused at ASFW 0.6.0 build 33. I’ll share future signed tester builds with Buy Me a Coffee members. ASFireWire remains free and open source; support helps cover these costs and gives me more time to work on it. It can’t guarantee a specific fix or date, but it makes it much more likely that I can take a closer look at your problem sooner.

Thank you to everyone who has supported the project.

Have a question, a press inquiry, or an idea for a partnership? You can reach me directly at me@mrmidi.net.

FINANCIAL SUPPORTERS

Thank you for helping keep ASFireWire going.

  • David Voss
  • Luis Murillo
  • @holmsius
  • CN70
  • Joey
  • Mike Music Maker
  • @caso.grave

If you’ve supported ASFireWire and would like to be listed, write to me with the name or handle you’d like me to use.

WHAT THE WORK INVOLVES

More than writing code.

Rebuilding FireWire support requires methodical research: understanding IOMMU mappings and DMA ownership, programming OHCI controllers, tracing FireWire protocols, and finding the device-specific behavior that keeps real-time audio and video working.

A functioning architecture also needs maintenance. That means profiling and performance optimization, keeping layer boundaries clear, preventing regressions across device families, testing changes against real hardware, and reviewing contributions carefully enough to understand their consequences.

Some work ends in a smaller implementation or a better test rather than a new feature. That work matters just as much when one shared change can affect every device on the bus.

PUBLIC ENGINEERING

DriverKit in practice.

ASFireWire has also grown into a substantial open-source example of Apple's DriverKit ecosystem in practice. The project brings together DriverKit, PCIDriverKit, AudioDriverKit, and SCSIControllerDriverKit in a single hardware stack.

It's not just a collection of API examples. The implementation covers real controller initialization, DMA, interrupts, device discovery, protocol handling, audio and SCSI integration, and the interactions between these layers.

The source code is publicly available for anyone researching low-level driver development on modern macOS.

HARDWARE OWNERS AND CONTRIBUTORS

Good evidence helps too.

Hardware testers help cover devices I do not own. A reproducible failure with startup logs and relevant device reports can reveal a problem that would otherwise stay invisible. A successful physical playback, capture, or scan test helps establish exactly what works.

Share a hardware result ↗ · Read the contribution policy ↗

ASFireWire remains free and open source. Financial support does not create paid features or a promise about delivery dates.

PROFESSIONAL OPPORTUNITIES

Working together.

I'm also open to employment or contract opportunities in systems programming, C/C++, driver and low-level hardware development, macOS and DriverKit, embedded systems, and real-time audio/video software.

The public repository is an example of my engineering work. Reach me at me@mrmidi.net or through LinkedIn.

TRY ASFW

Keep useful hardware running.

Check the installation guide and device evidence before testing.

Downloads and installation