Skip to content

Releases

KillFeed 0.5.1-alpha

KillFeed 0.5.1-alpha Pre-release
Pre-release

Choose a tag to compare

@kristofferlending kristofferlending released this 15 Nov 20:45

KillFeed 0.5.1-alpha

One fix, and it matters if you ever leave OBS recording for a long time.

Download: KillFeed.exe below (about 175 MB — ffmpeg and Tesseract are bundled). Windows 10/11.
SmartScreen warns once because the alpha is not code-signed: More info → Run anyway. The SHA-256 of
the exe is at the bottom of these notes.

Walkthrough: https://killfeed.no/guide


Fixed: in recordings over 13.9 hours, clips were cut from the wrong place

KillFeed reads a recording two frames a second and saves each frame as a numbered picture. The number
is the time: picture 7,200 is one hour in. The numbers had five digits, so picture 100,000 — 13.9
hours in — got a sixth, and the list was sorted as text, not as numbers. As text, 100000 comes
between 10000 and 10001. From that point every picture was shuffled into the wrong place in the
timeline, and everything after the first 1.4 hours of the recording got the wrong time.

A kill read at 00:33 was stamped as happening hours later. KillFeed then cut the clip at that later
time — after the game was closed — so the clip showed an empty room and a black screen, titled with
kills it did not contain. Kills read at the real time were never cut at all.

It only happens when a single recording runs past 13.9 hours, which is easy to do by leaving OBS
recording after you stop playing. Three recordings of 15–20 hours were hit on our test machine; every
shorter recording was fine.

What 0.5.1 does:

  • Pictures are numbered with eight digits and sorted as numbers. Recordings can now run for weeks.
  • If the numbering ever has a gap or is out of order, KillFeed stops reading that recording instead of
    guessing. A recording that stops gives no clips and is never deleted; a shifted clip gets published.
  • On first start, clips that were cut from the wrong place are moved to Other\_wrong-place\ and
    taken out of the queue, and so are the recap-bank pieces cut the same way. Nothing is deleted — you
    can look at them and delete them yourself. The log says how many were moved.

If your recordings were deleted after clipping, the kills in the affected part of them cannot be cut
again. If you still have the recordings, right-click one of their clips on the Dashboard and choose Re-clip the recording it came from.


Feedback: press Send feedback in the app. It puts a zip on your desktop with the log, your settings,
the clip list and the text KillFeed read — never video. It contains file paths with your Windows user
name and the names of players in your recordings, so look at it before you post it publicly; you can
also send it to us privately on Discord.


SHA-256 of KillFeed.exe: 7a5dbe8173d5270e362af1afde30515fb8c9bc00820a8947157544b7c37e555d

KillFeed 0.5-alpha

Choose a tag to compare

@kristofferlending kristofferlending released this 08 Nov 22:37

KillFeed 0.5-alpha

This release is about trusting what KillFeed says about a clip. Publish is now decided by how close
together the kills are rather than how many there are, you can tell KillFeed what actually happened in
a clip and it believes you over its own reading, and the clip browser became a tool you can work
through a hundred clips in. Text reading is about three times faster, and two ways KillFeed could
disturb a game are gone.

Download: KillFeed.exe below (about 175 MB — ffmpeg and Tesseract are bundled). Windows 10/11.
SmartScreen warns once because the alpha is not code-signed: More info → Run anyway. The SHA-256 of
the exe is at the bottom of these notes, so you can check the file is the one published here.

Walkthrough: https://killfeed.no/guide


Changed: what gets into Publish is now density, not a count

min_kills could not tell a double kill from three unrelated kills spread over a minute and a half,
because it only counted events in the window. A short called "3 kills" should show three kills that
belong together.

Publish now needs either two kills within three seconds of each other, or a run of three kills that
holds a pace of one every five seconds. One kill every five seconds is a good clip; three kills over
ninety seconds is not, whatever the count says. The thresholds are shorts.publish in
settings.json — double_s, pace_s, pace_need. Choosing Multikill or vehicle destroyed in setup
or Settings also lets a lone vehicle kill through on its own; Multikills only does not.

For anyone running from source: tools/queue_preview.py rebuilds the whole queue from the reports
without reading a frame of video, so a threshold can be tried out before anything is cut
(--double 5 --need 4 --pace 7).

New: tell it what actually happened in a clip

The whole threshold discussion had been guesswork, because nobody had checked what the clips really
contain. Browse clips now has + and − on kills and vehicles and a ✓ correct button, so
you can watch a clip and say what happened in it. That makes accuracy something measured rather than
argued about (tools/queue_preview.py --ledger reports how often the detector counts right and which
clips it misses).

Measured on 67 clips checked by hand: 48 counted exactly, 15 one kill short, 4 one too many. The
misses are mostly two kills inside one banner, where the banner shows a per-kill reward and a running
total in the same place and only one of them is legible. 0.5 starts saving both numbers raw, so the
counting can be improved against these checks without cutting anything again.

Changed: your correction now overrides the detector

Saying what happened in a clip used to change nothing about the clip. It was ground truth for
measuring the detector and nothing else: the title stayed wrong, the score stayed wrong, and the clip
stayed in whichever folder the counting had put it in. There was no way to tell that a correction had
any effect at all, which is a strange thing to ask someone to do twenty-three times.

Now the clip follows what you said. The title, the score, the queue and the folder all take your
number — in both directions. Say three kills where it counted two and the clip is retitled and moved
to Publish. Say one kill where it counted two inside three seconds and the "double" was imagined, so
the clip is retitled and moved out of Publish. Press undo and the detector's own count comes back.

Publish needs timings, and a count has none, so a human-verified count of pace_need kills or more
counts as dense enough: you corrected it upwards because you saw a chain, not four kills spread over
a minute. Two kills plus a double the detector actually saw in time still qualifies as before.

The card now says what the correction did — "title is now ..., moved to Publish" — instead of
"saved", and shows what the detector had thought next to your number so the difference stays visible.
The detector's own count is kept untouched underneath, so the accuracy report still measures the
detector against you rather than against itself.

Fixed: labels were lost when you quit

Saying what happened in a clip wrote the answer into the ledger in memory and never to disk, so a
labelling session survived only until the app closed. It saves on every answer now.

Fixed: the window never came back from sleep

Going to sleep for the game hides the window. Waking up again did not bring it back — deliberately,
so it would not jump in front of a game — and the only trace of the app left was a tray icon Windows
11 hides under the chevron. From the outside it looked like KillFeed had vanished.

It did not even need you to be playing: WARDOGS stays in the process list for a few seconds after you
close it, so starting KillFeed right after a session was enough. One five-second sweep, and the window
was gone. Sleep now remembers whether it was the one that hid the window, and if so puts it back in the
taskbar — minimised, so it can never take focus from whatever you are doing. If you had put it in the
tray yourself, it stays there.

Changed: text reading starts a few hundred processes instead of tens of thousands

Tesseract was started once per frame — around 130,000 times for a six-hour recording. It also takes a
list of images and reads them all in one process, writing the pages one after another, which is the
same work with a fraction of the overhead. A process start is not free on Windows: the Program
Compatibility Assistant attaches to every single one, and was sitting at 21 % CPU by itself during a
scan.

Frames are now read 200 at a time. Measured 3.2 times faster over 600 frames, with byte-identical
text. 200 and not "all of them in one go" because a batch cannot be interrupted part-way, and when a
game starts KillFeed has to let go of the machine at once — 200 frames is a few seconds. If a future
Tesseract version ever wrote the page breaks differently, every kill would land at the wrong time with
nothing looking wrong, so the page count is checked against the frame count and the batch is re-read
one frame at a time if they disagree.

Fixed: the Publish choice in Settings did nothing

The three choices — Multikill or vehicle destroyed, Every kill, Multikills only — were saved in
Settings to two values nothing reads any more, and the screen showed the choice from those same values.
So it could say Multikill or vehicle destroyed while vehicle kills were being kept out of Publish, and
changing it moved nothing. Settings now shows the rule that is actually in effect and saves to it, and
the clips you already have are re-sorted when it changes. If you went through setup with an older
build, open Settings once and check the choice — it may show something other than you expected, and
that is the rule you have been running with.

Fixed: KillFeed could wake up in the middle of a game

KillFeed asks Windows every five seconds whether the game is running. If Windows did not answer in
time — which happens under exactly the kind of load a game creates — the silence was read as "the game
has closed", and KillFeed woke up mid-round. Now an unanswered question means don't know, and KillFeed
stays asleep. Waking needs two "closed" answers in a row, ten seconds apart.

Changed: titles say only what the viewer can see

Titles no longer carry the distance. It was read from the kill feed down the left of the screen, which
is cropped away in a 9:16 short — so "(161 m)" was a claim about something the viewer could not see.
The distance still sorts the clip browser (Longest shot).

Fixed: the clip browser

  • Corrections showed nothing. Pressing + saved every time, but the number on the card did not move,
    and the line under it read "[object Object]". Both fixed: the number moves as you press, and the card
    says in words what your correction did.
  • The list re-sorted under your finger. Correcting a clip from two kills to three changes its score
    and often its folder, so the card jumped away after the first press. The order now stays put while
    you work. A Re-sort button lights up when your corrections have changed the order; the list
    rearranges when you press it, change view, search or sort.
  • Not checked. A new view with only the clips you have not said anything about yet, and a count of
    how many are left.

Feedback: press Send feedback in the app. It puts a zip on your desktop with the log, your settings,
the clip list and the text KillFeed read — never video. It contains file paths with your Windows user
name and the names of players in your recordings, so look at it before you post it publicly; you can
also send it to us privately on Discord.


SHA-256 of KillFeed.exe: e0c7c2d7033c16da1d73c10a2b61a278054c3b268cc8cfa82881a6430f687331

KillFeed 0.4.1-alpha – a paused app that said it was done, and three smaller fixes

Choose a tag to compare

@kristofferlending kristofferlending released this 02 Oct 12:14

KillFeed 0.4.1-alpha

Four fixes on top of 0.4-alpha. One of them is the worst bug this app has had, and it only shows up
when you combine two things that look harmless on their own.

Download: KillFeed.exe below (about 175 MB — ffmpeg and Tesseract are bundled). Windows 10/11.
SmartScreen warns once because the alpha is not code-signed: More info → Run anyway.

Walkthrough: https://killfeed.no/guide


Fixed: a paused KillFeed said "Done" instead of "paused"

Pressing Run now while paused started a run that stopped on the first file and then reported
"Done: 0 ready to publish, 0 in Other" — which reads exactly like a finished run that found
nothing. The only clue was a bare "Stopped." line in the log.

Asking for work now lifts the pause instead of starting a run that cannot do anything, and it says
so. A run that was interrupted no longer borrows the word Done: it says how far it got — "Stopped
before it finished — 3 of 16 recording(s) done, 13 left for next time."

This mattered more than it sounds. Reset and start over deletes every clip first and clips again
afterwards, through the same path. Paused, it would delete everything and then quietly clip nothing,
leaving you with no clips, no recap and an empty recap bank — and an app reporting that it was done.
That is how it was found, on a real library of 223 clips. The recordings were untouched, so a single
run rebuilt all of it, but the half hour spent working out what had happened was not fun. That
combination is no longer reachable.

Fixed: the dialog that deletes everything had Enter on the wrong button

Both dialogs put the gold primary style, the keyboard focus and the Enter key on the first button.
In Reset and start over that button is Reset and start over. Enter now belongs to Cancel in both,
and Escape closes them.

Saving a setting that changes how clips are cut no longer opens that dialog at all. It used to pop up
on Save with the destructive option under the cursor. Now it is a line of text: your existing clips
were cut with the old values, and Rescan everything redoes them when you want.

Fixed: a vehicle kill was named and counted twice

Destroying an occupied vehicle fires KILL CONFIRMED and VEHICLE DESTROYED in the same instant. Both
counted as separate achievements, so a clip of two vehicle kills was titled "2 kills, 2 vehicles
destroyed"
— four things for what the viewer saw happen twice.

It is named once now: that clip is "2 vehicles destroyed". And it is worth 2 in the queue rather
than 3, so a three-kill streak outranks a single vehicle kill instead of tying with it. The Publish
rule still sees both banners, so vehicle clips qualify exactly as before.

Fixed: wrong titles in the clip browser

The browser read the stored title out of the ledger, so clips cut before that fix kept showing the
old double-counted title — 13 of 223 on a real library. Title and score are now worked out from the
counts when the page is built, the same way the nightly upload does it, so they are right without
re-cutting anything.


Everything in 0.4-alpha still applies: honest detection from the banner only, two kills in a row
counted as two, the clip browser with hover-to-play and ▲▼ marks, the recap bank, lone kills skipped,
and recordings deleted once they are clipped. Those notes are worth reading if you are coming from
0.3: https://github.com/kristofferlending/killfeed/releases/tag/v0.4-alpha

Feedback: press Send feedback in the app — it puts a zip (log + text hits, never video) on your
desktop. Drop it in #feedback on Discord.

KillFeed 0.3.1-alpha

Choose a tag to compare

@kristofferlending kristofferlending released this 30 Sep 08:14

KillFeed 0.3.1-alpha

A correctness release. Same features as 0.3, but the kill detection no longer trusts the wrong part of
the screen, the packaged build no longer writes enormous files, and a long short with two lonely kills
in it no longer lands in Publish.

If you are on 0.3: replace the exe, then run Advanced → Maintenance → Rescan everything → Start fresh
so your clips are rebuilt with the stricter rules.

Download: KillFeed.exe below (about 175 MB – ffmpeg and Tesseract are bundled). Windows 10/11 only.
SmartScreen warns once because the alpha is not code-signed: More info → Run anyway.

Fixed: clips with no kill in them

WARDOGS puts kill information in three places: the banner under your crosshair, the money HUD in the top
right, and the kill feed down the left side. Only the banner is about you – the other two show what
everyone on the server is doing, and both are outside the frame once a clip is cropped to 9:16.

Until now any text in any of the three counted as your kill. That produced shorts titled "1 kill (216 m),
1 vehicle destroyed"
where nothing at all happens on screen: the kill was real, but it was someone else's,
in a corner the viewer never sees.

  • Only the banner under the crosshair can create a kill or a vehicle kill.
  • The money HUD contributes the amount, the kill feed contributes distance and victim. Neither can create
    an event on its own.
  • A distance is only attached when the banner fired within 2.5 s of that feed row.
  • An event has to be read in at least two frames within 1.5 seconds, so a single misread frame is not enough.
  • A bare "KILL", "DESTROYED" or "DELIVERED" no longer means a kill.

Fixed: 15-second clips that were 1.4 GB

-ss and -t sat between the recording and the watermark in the ffmpeg command, so the duration was read
as an option for the watermark instead of the cut. Only the packaged build has a watermark, which is why
this never showed up when running from source: the exe wrote everything from the cut point to the end of
the recording. Two 15-second clips came out at 1.4 GB each.

New: kills have to be a burst

Two kills twenty seconds apart used to be chained into one 30-second short where nothing happens in
between – the kind nobody finishes. Kills now only count towards Publish when they land within
Advanced → Shorts → Kills must be within N s of each other (10 s by default). A vehicle kill still
carries a clip on its own, and anything that does not make the cut goes to Other\ as before.

Changing that setting also re-sorts the clips you already have, moving them between Publish\ and
Other\ so a stricter value cleans up the queue instead of only applying to the next thing clipped.

Known in this alpha

  • WARDOGS only, Windows only, English only. Clips carry a small "KillFeed alpha" mark.
  • Tuned on 1080p/1440p with the HUD at 100 %. Other HUD scales may miss kills – tell us.
  • Lead-in before the kill is 8 s by default (Advanced → Seconds before the kill). Infantry players: tell us
    if that is too short or too long.
  • Weapon and class are not detected yet – only kills, vehicles, distance and victim.
  • Settings and log live in %APPDATA%\KillFeed. Delete that folder to run the setup again.

Feedback: press Send feedback in the app – it puts a zip (log + text hits, never video) on your desktop.
Drop it in #feedback on Discord.

v0.3-alpha

v0.3-alpha Pre-release
Pre-release

Choose a tag to compare

@kristofferlending kristofferlending released this 20 Sep 07:45

KillFeed 0.3-alpha

Automatic WARDOGS shorts and daily recaps – all on your own PC. No account, no upload, nothing leaves your machine.

Download: KillFeed.exe below (about 130 MB – ffmpeg and Tesseract are bundled). Windows 10/11 only.
Windows SmartScreen will warn because the alpha is not code-signed yet: More info → Run anyway.

What it does

Point it at your recordings folder once. It then sits in the tray, and after every session (once the game is closed) it reads the kill feed from the video and makes:

  • Publish\ – vertical 9:16 shorts (15–30 s) with a multikill or a vehicle kill, ready for YouTube Shorts / TikTok / Reels, with a title in a .txt next to each
  • Other\ – single kills, kept in case you want them
  • Recaps\ – a chronological 16:9 recap of the day's kills, built automatically when enough is collected

The same kill from two recordings (replay + backtrack) becomes one clip. Ready-made 9:16 recordings (Aitum Vertical) are used as-is; 16:9 recordings get a centre crop.

Getting started

  1. Run KillFeed.exe. The setup asks four things: where your recordings are, what to make, what is good enough to publish, and where the clips should go (a OneDrive / Google Drive / Dropbox folder syncs them to your phone).
  2. Press Start KillFeed. Done – it starts with Windows from now on.
  3. Play. Check the Dashboard or the output folder after a session.

Recording setup for OBS, ShadowPlay, Medal and Aitum: Recording guide in the app, or #setup-help on Discord.

Feedback

Press Send feedback in the app – it puts a zip (log + text hits, never video) on your desktop. Drop it in #feedback on the Discord server together with your resolution, recording tool and class (heli / infantry). If a clip missed or cut wrong, the clip filename is enough.

Known in this alpha

  • WARDOGS only, Windows only, English only. Clips carry a small "KillFeed alpha" mark.
  • Tuned on 1080p/1440p with the HUD at 100 %. Other HUD scales may miss kills – tell us.
  • Lead-in before the kill is 8 s by default (Advanced → Seconds before the kill). Infantry players: tell us if that is too short or too long.
  • Weapon and class are not detected yet – only kills, vehicles, distance and victim.
  • Settings and log live in %APPDATA%\KillFeed. Delete that folder to run the setup again.