Telegram RegisterThe public register of Telegram
Telegram profile photo for Tokyo Dawn Labs (RUS)

Channel

Tokyo Dawn Labs (RUS)

@tokyodawnlabsru

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

1,666subscribers

+17 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001834816338
TypeChannel
Username@tokyodawnlabsru
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held11
Confirmed unchanged2 times, most recently 18 September 2026
On Telegramt.me/tokyodawnlabsru

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 17 September 2026 and assigned it the closest of 31 fixed categories, at 54% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

1,6491,6671,6587 August 2026 — 1,649 subscribers7 August 2026 — 1,650 subscribers10 August 2026 — 1,651 subscribers13 August 2026 — 1,650 subscribers17 August 2026 — 1,653 subscribers20 August 2026 — 1,654 subscribers24 August 2026 — 1,651 subscribers27 August 2026 — 1,663 subscribers30 August 2026 — 1,664 subscribers1 September 2026 — 1,667 subscribers14 September 2026 — 1,666 subscribers1,6667 August 202614 September 2026
11 measurements spanning 38 days, net +17. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,646–1,670 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 07:361,666-1
1 Sept 2026, 18:031,667+3
30 Aug 2026, 02:071,664+1
27 Aug 2026, 03:361,663+12
24 Aug 2026, 09:431,651-3
20 Aug 2026, 19:551,654+1
17 Aug 2026, 11:441,653+3
13 Aug 2026, 16:051,650-1
10 Aug 2026, 06:111,651+1
7 Aug 2026, 15:411,650+1
7 Aug 2026, 03:151,649first reading

Engagement

8 posts held, back to 23 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 8 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

31 Jul 2026, 16:51 UTC625 viewsread 7 August 2026

Сегодня поговорим про алгоритм измерения громкости CBS Loudness, который используется в продуктах Orban. Для тех, кто не знает, Orban — крупный производитель оборудования для радиовещания, начиная с AM эры, потом FM, а потом и для стриминга. С инженерной точки зрения их процессоры обработки звука дают стандарт “того самого” звука на радио (рис. 1). Небольшая ремарка про наш интерес к алгоритмам измерения громкости.

31 Jul 2026, 16:51 UTC683 viewsread 7 August 2026

3. Для усреднения значений во времени разработчики посчитали, что для человеческого восприятия громкости время атаки 100 мс, время восстановления 500 мс. Сглаженное значение переводится в шкалу дБ. Если стрелочный индикатор имеет свою инерцию, то время атаки и восстановления сокращаются, чтобы итоговое время реакции все равно было 100/500 мс. Таким образом итоговый алгоритм: CBS-взешивание -> 8 октавных полос -> ат

29 Jun 2026, 11:42 UTC≈1,230 viewsread 7 August 2026

Ну и наконец еще одна идея, которую я недавно услышал от одного из продюсеров. Мы говорим, что алиасинг — это плохо, ведь при алиасинге гармоники “отражаются” от частоты Найквиста, а вот тот продюсер сказал, что ему нравится этот эффект, так как отраженные гармоники добавляют некоторое количество высоких частот и делают звук ярче. Так вот, если этот эффект разумно контролировать, то можно и яркость прибавить, и сдела

29 Jun 2026, 11:42 UTC≈1,080 viewsread 7 August 2026

Мы выпустили небольшое обновление 2.0.1 к Limiter 6. Измеритель громкости при некоторых условиях переставал работать. Довольно неприятная ошибка. В качестве небольшого оправдания скажу, что в версии 2.0 Limiter 6 индикатор громкости работает параллельно обработке аудио, на другом ядре процессора, поэтому не загружает работу в реальном времени. Ошибка как раз и связана с этой реализацией. В общем, если установили 2.0.

23 Jun 2026, 12:39 UTC≈1,090 viewsread 7 August 2026

На рис.6 гармоники от работы UPWARD режима Limiter 6. Видно плавное падение нечетных гармоник после третьей. Странные артефакты ниже -125 dB — это не алиасинг, а скорее всего последствия ошибок точности при вычислении экспоненциальных функций, которые используются в этом режиме. На рис.7 гармоники от работы клиппера Limiter 6 в параллельном режиме. “Идеальность” картинки связано с тем, что используется полиномиальна

Showing the 8 most recent of 8 posts we hold for @tokyodawnlabsru. 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.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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 14 September 2026 — this entry's latest reading, not the date you are reading this.

“Tokyo Dawn Labs (RUS)” (@tokyodawnlabsru), 1,666 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/tokyodawnlabsru.

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.