Skip to content

rewindDV 0.1.23 (Beta)

Pre-release
Pre-release

Choose a tag to compare

@bdubs426 bdubs426 released this 12 Oct 23:13

Beta 0.1.23 — App 213 / Driver 204

This release contains the completed-capture CLI admission correction and recovery for queued FireWire Control Protocol replies when interrupt delivery stalls. It retains receive watchdog recovery and normal STOP/finalization behavior.

Bounded physical qualification

On the tested Sony MiniDV setup, two short PLAY/STOP monitor cycles, a 15-second GUI capture, and a second short CLI-initiated capture finalized. Both saved files opened in playback. The app returned to ready state; no post-STOP lockout, reported command timeout, or reset storm was observed during this session.

The session recorded 19 watchdog receive recoveries, one routed command-reply recovery, and two startup bus resets. Each capture reported two CIP discontinuities and one incomplete frame. The known dropped-packet counter reported zero, which does not prove complete continuity. Capture continuity remains unresolved; this release is not qualified for pristine or loss-free capture. Driver start was delayed by about two minutes after boot, for an unknown reason.

Long-duration endurance, broad deck/controller compatibility, HDV, live DriverKit unload, surprise controller removal, and universal startup timing remain unqualified. No original recordings were modified.

Requirements

Apple silicon with macOS 26 Tahoe or macOS 27 Golden Gate. Intel Macs and older macOS versions are unsupported; later macOS versions are not currently supported or qualified. The full package is Developer ID signed and notarized and includes the app, DriverKit extension, normal CLI, and notices.

Assets

The ZIP's SHA-256 is 2722a557868fe9eb7c569d378b9f75c9c83d8eb26059888596bebf902207e085. Verify it with the included checksum file. Keep the matching manifest and provenance files with the archive.

Compiled public source: 8013570bd3ad84275a9006aff50b07a668ceda2f. The tested App213 and Driver204 executable SHA-256 values are recorded in the sealed package provenance. This release does not claim full capture-continuity qualification.