Highlights

Segra can automatically create highlight reels from your full session recordings by detecting important moments like kills, deaths, goals, and other game events.

How Highlights Work

Highlights are created from bookmarks in your session recordings:

Bookmark Types

Segra creates different types of bookmarks during gameplay:

Manual Bookmarks

Press F8 during gameplay to create a manual bookmark at the current moment.

• Useful for marking clutch plays, funny moments, or anything you want to remember
• Manual bookmarks are not included in auto-generated highlights, but they appear on the timeline so you can find them quickly when clipping by hand
• You can change the hotkey in Settings > Hotkeys

Automatic Bookmarks

Segra automatically creates bookmarks for game events:

Kill

When you eliminate an opponent:

• Included in highlights by default
• Works across the supported game integrations (see Game Integration)

Death

When you are eliminated:

• Not included in highlights (usually not a highlight-worthy moment)
• Still visible on the timeline for review
• Useful for analyzing mistakes

Goal

When you score (Rocket League):

• Included in highlights
• Auto-detected via game integration

Assist

When you assist a teammate:

• Not included in highlights by default
• Still visible on the timeline for review

Creating Highlights

From Session Recordings

Automatic Highlight Generation

Enable Auto-Generate Highlights After Recording in Settings > Highlights (requires Enable Highlights to be turned on):

• Segra automatically creates a highlight reel after each session recording
• Only creates highlights if the session has highlight-worthy bookmarks (Kill or Goal)
• Saves processing time by running in the background

Highlight Algorithm

Segra uses a smart algorithm to create engaging highlights:

Time Window

By default, each bookmark gets a 4-second window before and after (configurable from 1–60 seconds in Settings > Highlights):

• 4 seconds before - Provides context for what led to the moment
• 4 seconds after - Captures the result and immediate aftermath
• Total of 8 seconds per bookmark at the default padding

Segment Merging

Overlapping segments are automatically merged:

• Whenever two bookmarks' padding windows overlap (8 seconds total at the default 4s/4s padding), they're combined into one continuous clip
• Prevents choppy transitions and duplicate footage
• Results in smoother, more watchable highlights

For example:

• Kill at 1:00 → Clip from 0:56 to 1:04
• Kill at 1:02 → Clip from 0:58 to 1:06
• Merged result: One clip from 0:56 to 1:06

Fast Processing

Highlights use stream copy technology:

• Segments are extracted without re-encoding
• Processing is extremely fast (seconds instead of minutes)
• Original video quality is preserved
• All audio tracks from the source recording are kept, along with their track names
• No generational quality loss

Game Integrations

Segra has built-in integrations for popular games to automatically detect events:

Counter-Strike 2

• Kills
• Deaths

Integration listens for CS2 Game State Integration (GSI) events on a local HTTP endpoint.

League of Legends

• Kills
• Assists
• Deaths

Integration polls the League Live Client Data API (https://127.0.0.1:2999/liveclientdata) every 250ms.

PUBG

• Kills
• Deaths

Integration parses local PUBG replay files written to %LocalAppData%/TslGame/Saved/Demos after each match.

Rocket League

• Goals
• Assists

Integration uses on-screen OCR to recognize goal and assist banners in real time.

Dota 2

• Kills
• Deaths
• Assists

Integration uses Dota 2's Game State Integration (GSI) on a local HTTP listener at http://127.0.0.1:1341/.

Minecraft

• Deaths

Integration tails the Minecraft Java latest.log (vanilla and Lunar Client). Bedrock Edition is not supported.

Rust

• Kills (players only)
• Deaths

Integration tails output_log.txt next to the Rust executable. Deaths come from the You died line. Kills are read from Rust's combat log. Segra appends the combatlog command to your existing +jump, +reload, or inventory.toggle binds in cfg/keys.cfg (next to the Rust executable), backing up the original to keys.cfg.segra-backup. Segra re-applies the binds after Rust exits, because Rust rewrites keys.cfg on quit. If you have none of those binds, kills are not detected.

RuneScape: Dragonwilds

• Deaths

Integration tails %LocalAppData%/RSDragonwilds/Saved/Logs/RSDragonwilds.log for the death-state transition.

War Thunder

• Kills
• Deaths

Integration polls War Thunder's local HUD message endpoint at http://127.0.0.1:8111/hudmsg to detect events in real time. The local .clog combat log is read only to extract the player's nickname.

WARDOGS

• Kills
• Deaths

Integration uses on-screen OCR on the lower-middle of the screen. A KILL CONFIRMED notification creates a kill bookmark (assists are ignored), and the CALL FOR HELP downed prompt creates a death bookmark.

Grand Theft Auto

• Deaths

Integration uses on-screen OCR to detect the WASTED notification and bookmark the death, including both the red story-mode banner and the light-gray GTA Online banner. Supports GTA V / Online and Rage Multiplayer.

Deadlock

• Kills
• Assists
• Deaths

Integration uses on-screen OCR to read the KILL and KILL ASSIST stamps above the crosshair and the Respawn in countdown box.

Battlefield 6

• Kills
• Deaths

Integration uses on-screen OCR to read the kill card below the crosshair, including multi-kill streaks, and the killer card shown when you die.

Valorant

• Kills
• Deaths

Integration reads the top-right kill feed by color to find your entries. Deaths are confirmed with OCR and require the English UI language.

Overwatch (Beta)

• Kills
• Assists
• Deaths

Integration reads the elimination notices below the crosshair by color. Kills and assists only work with color blind mode off.

Fortnite

• Kills
• Deaths

Integration parses local Fortnite replay files in %LocalAppData%/FortniteGame/Saved/Demos after you leave each match. Fortnite's Record Replays setting must be on.

Highlight Generation

Segra's automatic highlight generation works from bookmarks that have already been recorded — either manual (F8) or events emitted by a supported game integration.

How It Works

1. Bookmark collection - The recorder gathers all bookmarks attached to the session
2. Filtering - Only bookmark types tagged with [IncludeInHighlight] (currently Kill and Goal) become highlight segments
3. Padding & merging - Each bookmark is expanded by the configured padding (default 4s before / 4s after); overlapping windows are merged into one continuous clip
4. Stream-copy export - Segments are extracted without re-encoding and concatenated into a single MP4, preserving every audio track and its name from the source recording

Enabling Highlights

In Settings > Highlights:

• Toggle Enable Highlights to allow highlight generation for this session and to surface AI-related options
• Toggle Auto-Generate Highlights After Recording to run highlight generation in the background as each session ends
• Adjust the Before Highlight and After Highlight padding to change how much context is included around each bookmark

To use different padding for a single game, enable Highlight Padding in that game's override panel under Settings > Games > Game Detection. See per-game overrides.

Improving Results

To get better highlights:

• Add manual bookmarks (F8) for moments your supported game doesn't tag automatically
• Enable per-game integrations under Settings > Game Integrations for the titles you play
• Tune the Before Highlight and After Highlight padding values so each highlight gets enough lead-up and reaction time

Highlight Output

Generated highlights are saved to the Highlights folder:

Segra/
└── Highlights/
    ├── Counter-Strike 2/
    │   └── 2024-01-15_14-30-45.mp4
    ├── League of Legends/
    │   └── 2024-01-15_15-22-10.mp4
    └── Rocket League/
        └── 2024-01-16_18-45-33.mp4

Each highlight includes:

• Video file - MP4 with all highlight segments
• Metadata - Game, source session, bookmarks included
• Thumbnail - Preview image
• Waveform - Audio visualization

Highlight Length

Highlight duration depends on the number of bookmarks:

• Few bookmarks (1-5): 8-40 second highlight
• Many bookmarks (10+): 1-3 minute highlight
• Dense action (20+): 3-5 minute highlight

Segra automatically merges overlapping segments, so actual duration may be shorter than total bookmark count × 8 seconds.

Editing Highlights

Create Custom Clips

You can create custom clips from highlight videos:

1. Open a highlight in the video player
2. Use the timeline to select specific moments
3. Click Create Clip to extract just those segments

This is useful for creating ultra-short clips (15-30 seconds) for social media.

Re-generate Highlights

If you manually add or remove bookmarks from a session:

1. Open the session recording
2. Add/remove bookmarks as needed
3. Click Create Highlight again
4. Segra re-generates the highlight with the updated bookmarks

Delete Unwanted Highlights

Right-click any highlight and select Delete to remove it. This frees up storage space.

Troubleshooting

Best Practices

Performance Tips

• Highlight generation is very fast due to stream copy (usually under 10 seconds)
• Highlight processing runs in the background while you keep recording
• Multiple highlights can be generated simultaneously
• Storage usage scales with the number of bookmarks (more bookmarks = longer highlights)

Related Features

• Recording - Capture gameplay sessions with bookmarks
• Clipping - Create custom clips from highlights
• Uploads - Share highlights online