Steamをインストール
ログイン
|
言語
简体中文(簡体字中国語)
繁體中文(繁体字中国語)
한국어 (韓国語)
ไทย (タイ語)
български (ブルガリア語)
Čeština(チェコ語)
Dansk (デンマーク語)
Deutsch (ドイツ語)
English (英語)
Español - España (スペイン語 - スペイン)
Español - Latinoamérica (スペイン語 - ラテンアメリカ)
Ελληνικά (ギリシャ語)
Français (フランス語)
Italiano (イタリア語)
Bahasa Indonesia(インドネシア語)
Magyar(ハンガリー語)
Nederlands (オランダ語)
Norsk (ノルウェー語)
Polski (ポーランド語)
Português(ポルトガル語-ポルトガル)
Português - Brasil (ポルトガル語 - ブラジル)
Română(ルーマニア語)
Русский (ロシア語)
Suomi (フィンランド語)
Svenska (スウェーデン語)
Türkçe (トルコ語)
Tiếng Việt (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
8K yes, 60 no, not even close.
hw acc on chrome also already turned ON
now I noticed though, in 8k60 mode, before buffering the video frames are also stuttered... now this indicate something in my hardware isn't working correctly...?
seriously though, anyone know any other site with free 8k60 video streaming?
my cpu just goes up to 100% usage and also got those same loading times, even tho my connection is fast enough to load that video.
Maybe this isn't well optimised yet.
And there are probably only like 1 or 2 8k60 videos on youtube anyway
https://www.youtube.com/watch?v=h3fUgOKFMNU
Older gtx 1080 (running at 84-86% usage, cpu around 4%), Firefox browser, Windows 11, 200 mb/s Internet. Another v8K vid on birds had my cpu at over 90% and gpu fluctuating betw. 35-55%. So it's not the same usage from video to video, it seems.
Don't know if it's approp. in this case but in general, flushing the dns cache helps with buffering.
Type cmd into Search, right-click to run as administrator.
Paste: ipconfig /flushdns
No, I didn't think so but thought I would mention anyway. But in general, flushing dns helps,with buffering, at least for me.
My hardware was showing fluctuating hardware use (up to 100%) but my specs aren't as high as OP's. Videos do seem to differ in what resources they consume.
or dns plumber
https://www.facebook.com/dnsanddone/
or seriously, change the routers dns servers to 1.1.1.1 1.0.0.1 (cloudfare) and/or 8.8.8.8 8.8.4.4(google)
they are faster than most isp dns servers
One can check if hardware acceleration is enabled in the browser. Someone did mention that the 8K videos are still relatively new and need further optimization. Maybe that's part of the puzzle. They surely aren't created equal in what resources they consume.
I replayed the NY vid and got an isolated instance of buffering lasting a second or so. Nothing occurring every x minutes, though. In my case, I think it was due to the gpu spiking.
Which is also what i previously suggested but seemed to have been ignored.
-
Even Youtube has Peak Usage times which can affect the playback of large content at certain hours of the day, if lower res content does not give the same results then that should be enough of a hint that its likely caused by Youtube.
And I have stated repeatedly that all I see on my screen is that the video seeking and buffering bar DO NOT indicate that there is any insufficient connection speed.
Please, do you people get it? The light grey buffering bar can be seen moving at way ahead of the red playback bar and the video would still be experiencing 3 seconds interval buffering and stuttering.
Well thanks everyone, looks like this is a mystery we have little hope to solve atm. At least now I found another person with ryzen pc experiencing the same issue, maybe this is amd specific issue? Who knows, maybe if more people can join this discussion and mention the same issue with amd cpu then we can start understsnding what's going on.
When was the last time you wiped the routing tables and flushed the DNS?
Youtube uses multiple connections to download into the buffer, the gray bar you see represents an approximation of how much and what parts of the media have loaded.
The gray bar being ahead of the playback doesn't mean you actually have a continuous buffer - there can be gaps, and if so it will stutter while it retrieves those pieces.
You can watch it happen live by inspecting the network requests - you will see
"/videoplayback?" requests sent while data is being loaded into the buffer
Youtube sometimes also releases new features slowly to certain groups or random groups of people - then they collect data from the playback and use it to analyse whether the feature is working / how well it is working / bugs, etc. You can see the active client experiment ids