Larix Broadcaster, our live streaming app, has been officially NDI Certified: https://ndi.video/product-finder/softvelum-broadcaster/

Channel
Softvelum
@softvelum
On this record: Growth · Engagement · Posts · Cite this entry
318subscribers
-5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001248943639 |
|---|---|
| Type | Channel |
| Username | @softvelum |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/softvelum |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 16:48 | 318 | -3 |
| 15 Aug 2026, 18:02 | 321 | -2 |
| 8 Aug 2026, 07:30 | 323 | no change |
| 7 Aug 2026, 23:36 | 323 | first reading |
Engagement
20 posts held, back to 29 October 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 41.5%
- avg views ÷ 318 subscribers
- Avg views / post
- 132
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 20 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 20 (29 October 2025 – 4 August 2026) |
| Views total | 264 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 07:30 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Recent posts
AJA SDI support is now available in Nimble Streamer. This update is aimed at video engineers who need practical SDI-to-IP and IP-to-SDI workflows without adding unnecessary components to the chain. Nimble Streamer can now receive SDI input from AJA devices, including embedded audio, and process it via Live Transcoder. It can also take a live stream already available in Nimble and output it to AJA SDI hardware with …
For broadcasters and OTT teams, SDI ingest is often only the first step. The real requirement is to keep all important service data available after the signal enters the streaming workflow, including subtitles and closed captions. Nimble Streamer now supports DVB teletext and closed captions from DeckLink SDI input, helping video engineers preserve subtitle and caption data for further processing and delivery. This…
The sports streaming market is growing fast, but the infrastructure gap is growing just as fast. Major rights holders have the OB vans, the satellite uplinks, and the crews. Regional leagues, university athletics programs, and community clubs have something different: volunteers with smartphones. For our piece in Streaming Media Magazine's Summer issue, we explored how the industry is closing that gap - not by givi…
Nimble Streamer WebRTC now supports HEVC/H.265 in WHIP and WHEP workflows. This update adds HEVC support in both directions: ~ WHIP ingest: publish HEVC video into Nimble Streamer. ~ WHEP playback: deliver HEVC video from Nimble Streamer to compatible WebRTC clients. Current browser support includes browsers on iOS and Chrome on Windows. For streaming teams and OTT operators, this makes it easier to keep HEVC in l…
Subtitle workflows often need format conversion: broadcast inputs may carry CEA-708 captions, while OTT delivery often expects WebVTT tracks for HLS. Our new article explains how Nimble Streamer converts subtitles both ways: - WebVTT to CEA-708 - CEA-708 to WebVTT Read the article: https://softvelum.com/2026/06/convert-between-cea708-webvtt/ #NimbleStreamer #HLS #WebVTT #CEA708 #OTT #VideoStreaming
We've added FLAC audio file support to Nimble Streamer Playout. FLAC is now accepted as a native input source and delivered as a live SLDP stream, with no transcoding stage in between. The audio passes through exactly as recorded, preserving every bit of the original quality. This is particularly useful for: ~ Music streaming services working with lossless libraries ~ Radio broadcasters archiving and playing back c…
We just released Opus audio support for RTMP and RTSP ingest in Nimble Streamer, and it makes a real difference for WebRTC delivery pipelines. Here's the problem it solves: WebRTC (including WHEP playback) natively uses Opus audio. But until now, most RTMP and RTSP streams arrived in AAC or MP3, forcing an audio transcode step before delivery. That meant added latency, extra CPU load, and more moving parts to mainta…
FLAC audio now in browser! FLAC support was added to SLDP, and it closes a gap that's been quietly frustrating professional streaming workflows for a long time. The problem: browsers have always been a lossy endpoint. No matter how clean your source audio, AAC or Opus re-encoding was an unavoidable step. With this release, Nimble Streamer can send FLAC over SLDP, and our Nimio player decodes it natively in the browse…
We've expanded Nimble Streamer's Enhanced RTMP support with six new codecs: Opus, FLAC, AC3, E-AC3, VP8, VP9. This builds on the Enhanced RTMP specification from Veovera Software Organization - the same spec that already brought HEVC and AV1 into RTMP-based workflows. Why does this matter for streaming infrastructure? ~ VP8, VP9, and Opus are the native codecs of WebRTC. Getting browser-originated content into RTMP…
AJA SDI: our team is working on AJA devices support for SDI in Nimble Streamer in addition to Blackmagic Decklink. Read more and contact us to get notified when it's out: https://softvelum.com/2026/05/aja-sdi-coming-soon/ #SDI #AJA
Hybrid broadcast workflows where legacy SDI infrastructure meets IP-based NDI production are the reality for most facilities today. The challenge is bridging them without adding complexity, hardware, or points of failure. Nimble Streamer handles this natively. It supports SDI and NDI as both inputs and outputs, meaning you can: ~ Take a baseband SDI feed from a Blackmagic DeckLink card and publish it as an NDI strea…
Showing the 12 most recent of 20 posts we hold for @softvelum. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 23 August 2026 — this entry's latest reading, not the date you are reading this.
“Softvelum” (@softvelum), 318 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/softvelum.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.