Tester downloads

On Windows PCs with an NVIDIA card, most phone footage was still taking the slow path in 0.1.7, with a message saying the card's path had failed. The cause was a change in how the video engine handles colour tags: it was being asked to convert them, which cannot be done on the card. Kime now tags rather than converts on that path, and footage that genuinely needs converting is decoded on the card and finished on the processor. Previews of phone clips are back to being quick.

Turning hardware acceleration off in Settings used to stop every preview with an error, on Windows and on Mac. It now does what it says: the card's own fast path is avoided, and the computer's ordinary encoder takes over.

Asking for captions to be drawn into the picture, on a copy of Kime that cannot do it, now says so plainly and leaves the captions beside the cut as a file - rather than failing with an internal error.

Both Macs are on 0.1.8 as well, signed and notarised. On an Intel Mac this is the first version that can save video at all: every earlier Intel build asked the encoder for a quality mode that only Apple silicon has, and was left with no encoder. That was found by a check added tonight, and it never affected Apple silicon Macs. On both, the hardware-acceleration switch now hands the work to the computer's ordinary encoder instead of stopping every preview.

On Windows PCs with an NVIDIA card, opening new footage failed with “graphics card unavailable” and then “the graphics card refused”. The card was fine. The copy of ffmpeg inside Kime had been built without the two pieces the card's fast path needs, and nothing checked for them. That copy is rebuilt, and Kime now asks for those pieces before choosing that path rather than assuming.

If the fast path fails for any other reason, Kime now falls back to the card's own encoder instead of to a software one it does not carry - so the slower path is slower, not a dead end. The reason is written to the log rather than lost.

The publishing tool that was packed into 0.1.6 by mistake is out, and the download is smaller for it.

Both Macs are on 0.1.7 as well, signed and notarised. They never had the graphics-card problem - the card path in question is NVIDIA's - so on a Mac this version is the re-cut fix: after a clip is replaced, the results screen now reports the cut's real length and the strip lands on the moment you pressed rather than the one before it. The Apple silicon download is smaller for the same reason as Windows.

Kime can update itself. Settings, then Updates, then Check now - an update is downloaded and checked against its signature before anything is replaced. Nothing happens on its own: no check runs when the app opens, so you are never interrupted by one.

An update will not install while a cut is being made. It waits, and says so, rather than replacing the thing your footage is being run through.

Macs can be updated for the first time. Until now the update file listed Windows alone, and a Mac asking whether it was current was told yes whatever version it was actually on.

This version still has to be downloaded by hand, on both platforms - it is the first one that carries the updater, so there was nothing in 0.1.5 to fetch it with. From here on, Check now is enough.

This download is about 16 MB bigger than it should be. A tool used for publishing releases was packed into the app by mistake; it is never run and it comes out in the next version. Nothing to do about it at your end.

The cut panel is one sentence you can edit: make a video plus stills, with 12 stills, about 1m 30s, from the moments Kime picks, favouring action, called clip-0419. Press any answer to open its choices, and Save as my defaults keeps all six. The three cards of labelled rows are gone.

A new question with it - who picks the moments, Kime or the ones you have marked - and the price of the AI pass now sits on the walkthrough card in both states, rather than appearing only once the switch is on.

Cuts that asked for stills record them again. The files were being written and never recorded, so the results screen showed none of them; this had been true since 25 August. Cuts already made cannot be repaired - the rows were never written - so they have to be made again to show their stills.

A cut whose folder name has brackets in it - "test 5 (2)", which Kime creates itself when you re-run under a name already used - showed a black poster and black tiles in the library. The stills were always on disk; now they appear.

Auto goes back for the words when it hears speech. It was running the speech preset with no transcript, which left half the score weighting nothing and cuts that could not follow sentences.

The line between talking footage and everything else moved up, measured against thirteen real talking-head files. Two children playing ball with a steady camera no longer come back as five seconds of a thirty-second request.

A file whose header claims eighteen hours for three minutes of video is now timed from its own packets instead of believed. That file ended in "No candidate segments found"; it cuts to seven segments.

A cut with no stills shows a frame of itself at the shape of the footage, rather than a blown-up filmstrip. The boot screen draws the mark, and the library footer is gone - what it carried is now said where each decision is made.

The app icon drops its black tile, which disappeared into a dark taskbar, and steps back from the edge of its canvas so it stops looking bigger than everything beside it. This is the first Windows build where that reaches the installed app.

Both Macs are on 0.1.5 now as well, signed and notarised: the Apple silicon build needs macOS 14, the Intel build macOS 13.4 Ventura.

Talking footage is cut on sentences: a moment opens where a sentence starts and closes where it ends, and never inside a word - the words Kime heard decide the edges.

Choosing Talking now turns on the speech add-on, sets the Long moment pace, and has your AI read what was said rather than a picture of the speaker.

Auto recognises an interview and treats it as Talking.

Swapping a moment out of a cut keeps its edges between words too.

Both macOS builds are now on 0.1.4 as well, signed and notarised.

The bundled ffmpeg no longer refuses to start on older Intel Macs, which is what 0.1.3 got wrong. The Intel build stays on macOS 13.4 Ventura and above; the Apple silicon one needs macOS 14, and every Apple silicon Mac can run that. Both now tell Finder the truth about what they need, so a Mac that is too old is turned away at the door rather than failing part-way through a job.

The app and its installer now carry the chevron mark - the old glyph icon is gone from the taskbar, the window and the setup file.

Both macOS builds now carry the mark too, and every build finally states its own version on the Settings screen rather than the one before it.

The Intel build runs on Ventura again. 0.1.2 was built against macOS 14 by accident and would not start below it, which is the whole reason the Intel build exists.

Fixed: a brand-new install refused to open its first video. Nothing needs Kime's library to exist before the first cut any more.

The two waiting screens - preparing a preview and making a cut - now share one language: the same field of bars, the same large figure, the same named steps and the same words for how long is left.

Shipped for macOS on 30 Aug; the Windows installer followed on 31 Aug with the same fixes.

The speech add-on is now off until you ask for it. A first run no longer downloads 460 MB unprompted.

Your AI key is kept in the operating system's secure store rather than a plain text file.

The results screen saves when you say so: an out-of-date cut says so on the player, and the action follows you down the page.

Fixed: replacing a moment could leave both the old and the new one in the cut, Undo all did not undo everything, and the player kept the previous cut after re-cutting.

Portrait footage is no longer stretched in previews.

First tester build. Windows only.

Drop in a long file, get back a short cut and a set of full-resolution stills.

Kime finds moments itself, on this computer. AI is off until you turn it on.