LOOM Engine · v2.3.0Closed beta

Not a notification feed. A live-show engine.

Every event your community fires runs through one pipeline that decides what plays, when, how loud, and what it looks like. Your channel feels like a live show, not a feed of pop-ups.

  1. Arrival

    Every event lands on our servers first.

    Twitch sends your events straight to the engine, not to OBS. Twitch sometimes delivers the same notification twice: the engine recognizes the resend and plays it once. Two people who follow are always two follows.

    Source
    Twitch EventSub via OAuth: follows, subs, resubs, gifted subs, cheers, raids
    Optional
    Streamer.bot for donations (Streamlabs, StreamElements, Ko-fi…)
    Resends
    The same Twitch notification, recognized by its ID, plays once
    Resubs
    Twitch announces a resub only when the viewer shares it in chat: you get one alert, with their months and message. If it isn't shared, Twitch sends nothing and no alert plays
    Gifted subs
    A gift of 10 reaches Twitch as 1 gift + 10 sub notifications: you get one alert, not eleven
    Runs
    Server-side, ready before you go live

  2. Priority

    Big moments go first.

    Each event takes its place in the queue by importance, not by arrival time. A raid or gifted subs never wait behind a string of follows. Nothing is removed: priority changes the order, not the content.

    Order
    Raid, then subs, gifted subs and donations, then big cheers, small cheers, follows
    Same rank
    First in, first played

  3. Pace

    The queue speeds up, never rushes.

    When the queue fills up, alerts get shorter so your live doesn't fall behind. Each type keeps a minimum length so it stays readable, and big moments keep a longer one.

    Follows
    A burst becomes one welcome (Follow Grouping, one click in Settings)
    Busy queue
    Shorter alerts, with a readable floor per type
    Hold
    Quick Pause 30 s to 2 min, buffer of 5 to 30 alerts, overflow plays live

  4. Sound

    A follow spam never drowns your voice.

    The same alert type back to back steps its volume down. The first one lands at full impact, the chain stays audible without hammering your viewers.

    Smart Volume
    100 %, then 55 %, then 25 % for the same type in a row (on by default)
    Reset
    A new type, a raid, grouped follows or a wave start again at full volume
    Mastering
    Packs mixed to -18 LUFS / -1 dBTP, to sit under your voice

  5. Wave

    When the burst settles, the engine gives it a finale.

    The engine keeps count while a rush lasts. Once the queue is empty and the channel calms down, it reads the whole wave and plays one Wave Achievement that sums it up, with your biggest supporter named on screen.

    Closes
    Queue empty, then 5, 7 or 10 s of calm (your setting)
    Verdict
    One of four tiers, from a follower surge to legendary
    Spotlight
    Top supporter by name, for gifted subs, cheers and donations
    Plays on
    Every pack, each with its own finale

  6. Delivery

    Sent is not enough. The engine waits for proof.

    Your overlay confirms every alert it plays. If OBS reloads in the middle of one, that alert plays again when the overlay comes back, and the ones waiting are still in line on the server.

    OBS reload
    The alert in progress replays, the queue is intact
    Overlay gone
    The alert is logged as not shown and the queue moves on, instead of freezing
    Settings
    Applied to the open overlay, no OBS reload
    Pack switch
    During a wave, it waits for the finale instead of cutting it

Closed beta

Request beta access