ASFireWire
REAL-WORLD COMPATIBILITY

Hardware test results.

Compatibility is not always a model-by-model whitelist. It depends on the device protocol and what the device exposes to software: AV/C audio needs enough information to describe the interface to Core Audio; scanners use SCSI commands with scanning software. Host adapters and real-world tests matter too. Code support by itself is not a test.

HARDWARE COMPATIBILITY

Hardware and test results.

This table lists devices with real-hardware test reports. It is not a prediction or a complete compatibility list. An unlisted device may well work, especially if it uses a supported protocol family, but it has not been verified here yet. How compatibility works ↗ · Try yours and share what happens ↗

Tested and workingMaintainer or contributor report on real hardware.
Known blockerA documented requirement or host limitation prevents use right now.
AUDIO

Audio interfaces

Only interfaces tested on real hardware are listed here. The column gives the chipset or protocol family; exact ASIC models appear only where confirmed. If yours is absent, it may still work—try it and report the result ↗.

VendorDeviceASIC / FireWire protocolEvidence
AlesisiO|26DICE II JETIssue #211
ApogeeDuet FireWireOxford AV/CChangelog
AvidMbox Pro · 3rd generationDICEPR #162
FocusriteSaffire Pro 24 DSPTCD2210 · DICE MiniMaintainer testing
FocusriteSaffire Pro 24DICEIssue #159
FocusriteSaffire Pro 40 · TCD2220TCD2220 · DICE JuniorIssue #193
MackieOnyx 1640i · serial 204DICEGearspace report
M-AudioFireWire 1814BeBoBPR #143
M-AudioProjectMix I/OBeBoBContributor history in Issue #99
MidasVenice F24DICECommunity-reported working
MidasVenice F32DICEContributor report by @alicankaralar
MOTUUltraLite-mk3 FireWireMOTU V3Issue #192
PreSonusStudioLive 16.0.2DICEContributor report by @klochowicz
PreSonusStudioLive 32.4.2 AIDICEIssue #190
PreSonusFireStudio 2626DICEIssue #189
Prism SoundOrpheusBeBoB (BridgeCo)Gearspace report
Prism SoundADA-8XRBeBoB (BridgeCo)PR #210
RMEFireface 400RME Fireface protocolIssue #211
RMEFireface 800RME Fireface protocolCommunity report on Discord; PR #196
TerraTecPHASE 88 RackBeBoBChangelog
VENDOR CONTROL APPS

FireWire control apps such as TotalMix, DigiCheck, and MixControl were built for Apple’s IOFireWireFamily, which is no longer part of macOS. They cannot communicate with devices through ASFireWire; there is no need to test or report those apps as ASFW failures. This does not apply to Storage/SBP-2 devices: SCSI-based apps such as Hasselblad Phocus and VueScan use macOS’s SCSI path and can work with ASFireWire.

AUDIO · NOT SUPPORTED IN THE CURRENT RELEASE

M-Audio FW410, Audiophile, Solo, Ozonic and NRV10

These devices need a firmware upload before they can be used. ASFireWire does not currently perform that upload, so do not expect them to work with the current release.

VIDEO

DV camcorders

Only the listed contributor report is confirmed here. Other DV camera models remain unclassified.

CONTRIBUTOR VERIFIEDMACOS 26 · FIREWIRE 400
  • Panasonic MiniDV camcorderDV capture to raw .dv files; play / stop / rewind confirmed · @hoffmabc
    ●

Additional DV stream handling was hardened by @gdemontalivet. Reports from other models, especially NTSC cameras, are welcome.

LIMITATION

DV capture and audio receive share a resource

They both use isochronous receive context 0, so they cannot run at the same time. Starting one while the other is active returns “busy.”

STORAGE

Scanners and SCSI devices

SCSI-based applications communicate through macOS’s SCSI path. These results are separate from audio-device compatibility.

REPORTED WORKING
  • Nikon Coolscan 9000 (LS-9000)VueScan · @mhellevang
    ●
  • Nikon Coolscan 4000 (LS-4000)VueScan and Negpy (nkscan) · @mhellevang and COXOS
    ●
  • Hasselblad H4D-50MSPhocus captured and transferred the original full-resolution 1:1 image · PR #207 report. One capture using the camera’s physical shutter hung and required disconnecting power from the camera and FireWire chain. Phocus handles the capture; ASFW provides the SBP-2/SCSI data path.
    ●
CONNECTION

Macs and FireWire adapters

Compatibility depends on the host controller as well as the peripheral.

NOT COMPATIBLE

MacBook Neo cannot host FireWire

Its USB-C ports support USB 3 and USB 2, not Thunderbolt. The Apple Thunderbolt-to-FireWire adapter chain therefore cannot connect; a USB-C connector alone does not provide Thunderbolt.

Apple’s MacBook Neo accessory compatibility notes ↗
DEVELOPMENT SETUP

Apple Thunderbolt adapter chain

Maintainer's setup: Thunderbolt 3 → Thunderbolt 2 → FireWire 800, tested on a 2020 M1 MacBook Air and an M4 Mac mini.

CONTROLLER MATCHING IS LIMITED

Current main-service matching covers Agere/Lucent FireWire OHCI controllers; the SCSI HBA still matches FW643 only. Matching is not hardware verification. Other vendors require a matching review. Check the wiki and issue tracker before buying a card.

i

The wiki keeps the source reports and additional device status. Send a report if you test a device that is not listed.