Telegram RegisterThe public register of Telegram
Telegram profile photo for mcv-player

Channel

mcv-player

@mcv_player

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

270subscribers

+0 since we began measuring on 13 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002381965051
TypeChannel
Username@mcv_player
CreatedBetween 1 September 2024 and 23 February 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live14 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/mcv_player

Growth

27013 Aug 2026, 19:47 — 270 subscribers14 Aug 2026, 15:45 — 270 subscribers13 Aug 2026, 19:4714 Aug 2026, 15:45
2 measurements taken within a single day. 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 269–271 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 15:45270no change
13 Aug 2026, 19:47270first reading

Engagement

20 posts held, back to 23 February 2025the 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.

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

What this channel posts

Video runtime
26s
Average length
13s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

107 reactions across 15 posts, in 7 distinct kinds. The most used accounts for 50.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍5450.5%
3835.5%
🥰76.54%
🎉54.67%
🔥10.935%
🤓10.935%
🤪10.935%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 15 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 107reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 23 February 2025 to 28 April 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

28 Apr 2026, 03:37 UTC802 views6 reactionsread 13 August 2026
File

个人自用 Windows mpv 配置 基于 mpv-config 2026.04.28 1. 更新 mpv 至 2026-04-26 09:09 2. 修复流媒体传输问题 历史版本 #mpv@mcv_player

👍6

27 Apr 2026, 12:14 UTC457 views6 reactionsread 13 August 2026
File

个人自用 Windows mpv 配置 基于 mpv-config 2026.04.27 1. 更新 mpv 至 2026-04-24 10:04 2. 更新 uosc_danmaku 至 dyphire latest ver 3. 更新 uosc 至 dyphire latest ver 4. 更新 yt-dlp 至 2026.3.17 5.清理无用着色器 6.优化着色器搭配 7.增加 AnimeJaNaiV3 着色器。对于瑕疵的处理效果极好,同时尽可能保留原始画风,是比 Ani4K 和 Anime4K 更优秀的动画着色器。性能开销较大(比ani4k稍小),初次加载需要一定的预编译等待时间(程序可能会暂时冻结) 历史版本 #mpv@mcv_player

5👍1

7 Dec 2025, 09:43 UTC977 views4 reactionsread 13 August 2026
File

个人自用 Windows mpv 配置 基于 mpv-config 2025.12.7 1. 更新 mpv 至 2025-12-02 08:42 2. 更新 uosc_danmaku 至 dyphire latest ver 3. 更新 uosc 至 dyphire latest ver 4. 更新 yt-dlp 至 2025.11.12 5. ⚠️重要变更: 默认修正 Gamma 至 2.2 历史版本 #mpv@mcv_player

👍4

6 Oct 2025, 10:42 UTC≈1,190 views5 reactionsread 13 August 2026
File

个人自用 Windows mpv 配置 基于 mpv-config 2025.10.6 1.更新 mpv 至 2025-10-06 08:37 2.更新 uosc_danmaku 至 dyphire latest ver 3.更新 uosc 至 dyphire latest ver 4.更新 yt-dlp 至 2025.09.26 5.更新 smartcopypaste_II 6.为 YouTube 视频提供热图支持 历史版本 #mpv@mcv_player

5

22 Jun 2025, 10:09 UTC≈2,210 views12 reactionsread 13 August 2026
File

个人自用 Windows mpv 配置 基于 mpv-config 2025.6.22 1.更新 mpv 至 2025-06-22 08:54 2.更新 uosc_danmaku 至 commit 3cb20f2 3.更新 uosc 至 commit 75db6c1 4.更新 yt-dlp 至 2025.06.09 5.使用 d3d12va-copy 获得更高效的解码体验 6.更新 Thumbfast 7.修复IME无法自动激活 历史版本 #mpv@mcv_player

12

3 Jun 2025, 03:17 UTC≈1,110 views7 reactionsread 13 August 2026

如使用MX系列N卡请在mpv.conf底部加上 vd=h264_qsv,hevc_qsv,mpeg2_qsv,vp9_qsv,vp8_qsv,av1_qsv hwdec=d3d12va-copy

🥰7

1 May 2025, 12:27 UTC≈1,650 views12 reactionsread 13 August 2026
File

个人自用 Windows mpv 配置 基于 mpv-config 2025.5.1 1.更新 mpv 至 2025-04-28 09:38 2.更新 uosc_danmaku 至 commit a7779fb 3.更新 uosc 至 commit 77cb8bb ⚠️ 图片打开时隐藏音量滑块及其他无关控件 4.更新 yt-dlp 至 2025.04.30 5.使用更好的色度映射 6.优化 NNEDI3 配置并设为默认值,有效提高默认画质 7.补充拆分 console 时 缺失的commands.conf 8.修复 installer 9.更新 Thumbfast 历史版本 #mpv@mcv_player

👍12

3 Apr 2025, 11:46 UTC≈1,370 views6 reactionsread 13 August 2026

🤐停止扯淡!!漫谈显示器色彩管理 系列 第一章 第二章 第三章 第四章 尽管其中有部分小问题,但是并不妨碍这篇文章成为目前中文网络社区最好的显示器色彩管理普及文🍾

👍32🤪1

22 Mar 2025, 12:29 UTC≈1,580 views12 reactionsread 13 August 2026
File

个人自用 Windows mpv 配置 基于 mpv-config 2025.3.22 1.更新 mpv 至 2025-03-22 08:37 2.更新 uosc_danmaku 至 commit 9e9fdc3 3.更新 uosc 至 commit c99ab8d ⚠️ 适配新特性的同时无需键入即可激活 IME 4.更新 yt-dlp 至 2025.03.21 5.优化字幕样式 历史版本 #mpv@mcv_player

11🔥1

9 Mar 2025, 15:06 UTC940 views2 reactionsread 13 August 2026
Video

⚠️ 使用更合理的断网后显示逻辑

1👍1

Showing the 12 most recent of 20 posts we hold for @mcv_player. 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.

Citation-graph rank

Citation-graph rank — 1,224,976 of 1,480,975entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“mcv-player” (@mcv_player), 270 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/mcv_player.

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.