MacHuna icon

MacHuna

Graphic wipe conversion for macOS. Downloads and release notes.

Current release

v2.0.0 25 September 2026
macOS 26 or later Apple silicon Everything bundled — nothing else to install

First launch

macOS will ask before it opens it

MacHuna is not signed with an Apple developer certificate yet, so the first time you open it macOS says it cannot verify the developer. That is expected. Three steps, once per machine.

  1. Move MacHuna to your Applications folder and double‑click it. macOS refuses to open it and shows a warning. Click Done.

  2. Open System Settings › Privacy & Security and scroll down. There is a line about MacHuna being blocked with an Open Anyway button. Click it and confirm.

  3. It opens, and opens normally from then on.

Verification status

What has been proven on a desk, and what hasn't

MacHuna is built by one person, with access to some desks and not others. Rather than let you find out the hard way, here is exactly where each output stands. Most of this is a statement about what has and has not been loaded onto real hardware, not about whether it works — with one exception, audio in EIF, which is genuinely not built.

OutputStatusWhat that means
Kahuna SWSclips, TGA sequences, stills Confirmed Verified on a live Kahuna mainframe. All seven standards checked byte‑for‑byte against reference files, along with fill and key, 16‑channel audio, the auto and loop play flags, and the >4 GB split. This is the path that has been in daily use.
K-Frame EIFKayenne, Karrera, GV Korona Untested on a desk The format was reverse‑engineered from real Kayenne clips and the header verified byte‑for‑byte. Converting between MOV, SWS, TGA and EIF is expected to work — it just has not been proven on a desk yet. Check the result before relying on it.
Audio in K-Frame EIFthe one known gap Not built yet EIF clips you create are silent. K-Frame keeps clip audio in a companion .eaf file. MacHuna can now read one — converting an EIF to QuickTime MOV brings its sound with it — but it cannot yet write one, so audio is still dropped when converting to EIF, and MacHuna tells you so in the log. The open question is which of the eight channels a K-Frame expects when reading. If you know, or can find out on a desk, that is the last piece.
K-Frame TGA Untested on a desk Coded and routing correctly. Frame naming and format are taken from documentation rather than proven.
QuickTime MOVSWS, EIF or TGA out to ProRes Nothing to confirm A ProRes 4444 file with the key as a real alpha channel, and sound where the source has any. It is an ordinary video file rather than a desk format, so there is no hardware question hanging over it — if it opens in your NLE, it is right. One caveat: ProRes carries no field‑order flag, so an interlaced source may need the field order setting by hand in your NLE.
Sony MVS TGA Untested on a desk The four‑character clip naming is assumed from documentation. 25i field order defaults to TFF on an engineer's advice, with a toggle in the app if motion looks wrong on your desk.
720p1280×720 Not available Pulled in v1.6.8 because it was quietly producing corrupt files — the encoding maths is wrong for 1280‑wide output. Shipping something broken seemed worse than shipping nothing. I would like this one back: 720p/59.94 is still on air in the States, so it is a real gap rather than a dead format. It needs a reference file and a desk to check against.
SD, sF and 2160p Not available Not there yet, but not ruled out either. A standard only goes in the dropdown once it has been checked against a real reference file, because a wrong one produces files a desk will not read. If you need one of these, get in touch — with a reference file to work from, adding a standard is straightforward.
ConfirmedLoaded onto the real desk and verified. Use it.
Untested on a deskWritten to spec and believed correct, but never proven on the hardware it is for. It may work perfectly. Check the output before you trust it on air.
Not built yetKnown not to work. Not a bug — a feature that does not exist.
Not availableNot in this version. Ask if you need it.

One more caveat on a confirmed path. Progressive‑to‑interlaced conversion assumes top field first, which is standard for 1080i HD, but this has not been checked on a genuine 1080i Kahuna. If you have one and can look, that is a five‑minute job that would settle it.

If you have a K-Frame or a Sony MVS, testing one of the rows above and telling me what happened is the single most useful thing anyone could do for MacHuna. It is how the Kahuna row came to say Confirmed.

What changed

v2.0.0 25 Sep 2026 Current

MacHuna rebuilt as a native Mac app. The converter underneath is unchanged, so every file it writes is identical to the one it wrote before.

Drag in, convert, drag out. Drag files straight onto the window from anywhere in the Finder, and drag finished files straight out again to wherever they need to go, without opening the destination folder. Double‑click a converted file to watch it. Drag any clip onto the player to open it, converted or not.

Write beside the source files. For the memory stick handed to you under pressure: tick it and the output lands on the same drive as the sources, in a folder ready to carry to the desk. MacHuna checks the drive is writable and has room before it starts, rather than filling it halfway through.

A player you can scrub. The same four‑way view of fill, key, composite and level, but now with a timeline you can drag to any frame and playback that stays smooth. It reads the file’s own bytes at full resolution — nothing is transcoded, so what you are checking is the file itself and not a copy of it. Transparency sits on a chequerboard, because over black a black fill with a full key looks exactly like nothing at all.

A full menu bar, with a keyboard shortcut for everything that matters, and reordering a batch from the keyboard. The user manual is inside the app, and Report a Problem fills in the version, your Mac and your current settings before handing you a draft — nothing is sent until you send it.

Your settings come across automatically the first time it runs, and it replaces the previous version in place. Nothing about the files on your desk changes.

v1.11.0 18 Sep 2026

A clip with no key now produces an SWS with no key plane — instead of a black one that never keyed and doubled the file.

Converting something without a key used to write a full key plane anyway, flat black, and tell the desk it was there. Loaded on a Kahuna it shows a Key panel that is solid black, and it does not key. It never worked; it only made the file twice as big.

Now the rule is simply that a key plane is written when there is a key. Every keyless file is half the size — a 52‑frame wipe drops from 896 MB to 448 MB, converts in about half the time, and a clip twice as long fits under the 4 GB split. Files that do have a key are unaffected.

Confirmed on a live Kahuna on 18 September, loading both versions side by side. This is the first thing MacHuna deliberately does differently from the software it was modelled on, and it was changed only once a desk had shown the old behaviour was useless.

v1.10.3 17 Sep 2026

Adds QuickTime MOV output: turn an SWS, an EIF or a TGA sequence back into an editable ProRes 4444 file, with the key as a real alpha channel and the sound intact.

Until now material could go onto a desk but only came back off as a folder of TGA frames. A QuickTime is what an edit suite, a grade or an archive actually wants. Sound comes from the SWS itself, or for a K-Frame clip from its companion .eaf file, which MacHuna can now read. It is an ordinary video file rather than a desk format, so there is nothing about it waiting to be proven on hardware.

Name each file, or leave it blank to take the source name. A TGA sequence declares no frame rate of its own, so you set one — 23.976 through 60, including the 29.97 and 30 that broadcast standards do not offer progressively. If the sequence is itself interlaced, tick TGA source interlaced and it is deinterlaced on the way: a 25fps interlaced sequence becomes a 50fps progressive MOV of the same length, with no combing.

Also in this release: the Kayenne formats are now called K-Frame, which is what they are — Kayenne is one of three control panels that drive a K-Frame, alongside Karrera and GV Korona, and the clip store lives in the frame.

v1.9.1 10 Sep 2026

Fixes some files being read half a line out, which made the picture look split down the middle with the sides swapped.

The video does not always start at the same place in an SWS file — the header says where, and some files put it later. MacHuna had always assumed. This affected conversions as well as playback, so if you have ever converted a file that displayed this way, convert it again.

v1.9.0 10 Sep 2026

The Video Player now opens split files.

A clip over 4 GB is stored as a folder of 2 GB parts, and the player could not open one at all — the file dialog treats the folder as somewhere to go into, so you ended up picking a single part. Select the folder, or any part inside it, and the whole clip loads. The info strip confirms it with Split: 3 parts.

Long clips also load without running out of memory: the player now decodes a batch of frames at a time instead of reading the entire video plane in one go, so a 1000‑frame clip peaks at 1.4 GB rather than needing 5.5 GB in one lump. That was never really a split‑file limit — a single large file would have failed the same way.

v1.8.1 9 Sep 2026

Two fixes to the new item list.

The list now genuinely grows when you make the window taller — v1.8.0 claimed that and did not do it — and the scrollbar sits beside the list again rather than out at the edge of the window.

v1.8.0 9 Sep 2026

Batch numbering is now a list, so you can see what every file will be called before you convert it.

Each selected item gets a row showing its output name — alpha.mov → 42.SWS. Type a number per row, or tick Number sequentially and the first row fills in the rest. Converted rows lock with a tick and never run again, so you can add more files and convert without redoing anything. A ✕ removes a row, and the numbers below close up or stay put depending on how you are numbering.

Previously the numbering happened invisibly and you found out what each file had been called by reading the log afterwards. The Start number, Start slot and “Use source file number” controls are all gone, replaced by the list.

v1.7.1 8 Sep 2026

MacHuna now tells you, in the log, when an output has never been tested on the desk it is for.

Converting to K-Frame EIF, K-Frame TGA or Sony MVS TGA writes a note saying so at the head of the batch. Kahuna SWS says nothing, because it is confirmed on real hardware and warning about it would be false caution. Converting a clip that has audio to EIF now also warns that the audio is dropped — see the verification table above for why. Nothing is blocked and no dialog appears; you are simply told where things stand.

v1.7.0 7 Sep 2026

A Help menu, with update notifications and a way to get in touch.

MacHuna now tells you when a newer version exists: a strip appears at the top of the window with what changed and a Download button. If you are up to date, offline, or the check fails for any reason, nothing appears at all — it is built for galleries and trucks with no route out. Help › Report a Problem and Suggest a Feature open an email with the version, your macOS and your current settings already filled in; nothing is sent until you send it. The user manual is now inside the app, so it opens with no internet.

The update check only ever reads one small file. It sends no information about you or your files, and there is no usage tracking.

v1.6.21 7 Sep 2026

A finished conversion now clears the selection, so the next one starts from nothing.

Previously the batch stayed loaded after converting, so reopening the folder browser offered Add to List and the files you had just converted came along and were written a second time. This now applies to every conversion, sequential or bespoke, and after a cancelled batch too. The auto‑incrementing start number is not reset.

v1.6.20 3 Sep 2026

The app reports its real version to macOS.

Every build used to report version 0.0.0 in Finder, so you could not tell one copy from another. Press ⌘I on the app to check which version you have. A copy still showing 0.0.0 is older than this release.

v1.6.19 3 Sep 2026

Clearer message when Sony TGA output is limited to one clip.

It now opens with how to convert a batch anyway, by ticking Use bespoke names, rather than leading with the restriction.

v1.6.17–18 3 Sep 2026

A blocked batch takes you to the field that needs fixing.

Every offending bespoke field is marked in red with the reason for that row, and the panel scrolls to the first one and focuses it. Correcting a duplicate clears the mark on its partner as well.

v1.6.13–16 3 Sep 2026

Bespoke per‑item output numbers and names.

Give each item in a batch its own output number, or its own four‑character clip name for Sony TGA, instead of taking an auto‑sequence. Blank, duplicate and already‑present values stop the batch and name the offenders, so nothing is ever overwritten. Batches can also be built from more than one folder.

Older releases are listed in the development notes that come with the app.

Problems and requests

MacHuna was vibecoded by one person against real desks, so it improves fastest when someone says what went wrong. There is nothing to sign up to.

machuna@dnsvision.tv
  • Something went wrong. Send the version, your standard, the source file and what the log said. MacHuna writes a conversion log into the destination folder after every batch, and that usually answers it.
  • It needs to do something else. A format, a standard, a naming convention your facility uses.
  • You have a K-Frame or a Sony MVS. Those output paths are written but have never been loaded on a live desk. If you can test one and report back, that is the most useful thing anyone could do for MacHuna.