The video stopped playing back and then kept oscillating continuously between saying that “YouTube forces us to wait for (‘two seconds’ or ‘one second’) before continuing playback.” After the “one second” notice, it goes back to two seconds and it keeps oscillating forever. This is the first time I’ve ever seen this notice and am wondering who else here may have been experiencing this recently.

  • goofsqueak@lemdro.idEnglish
    2·
    16 hours ago

    same here 😔✌️ i rarely get past this and when i do i just do a bunch of random crap

  • Sidyctism II.@discuss.tchncs.de
    1·
    1 day ago

    I just tried changing the extraction point to “android vr”, that seems to get rid of the counter entirely. Videos just play normally now

  • valar@lemmy.ca
    4·
    2 days ago

    Been happening to me a lot just now. The debug app had a message recommending to enable “Share Visitor Data” under Advanced Settings, but I haven’t tried it.

  • als@lemmy.blahaj.zoneEnglish
    8·
    2 days ago

    I’ve been having this for a fair few days now. I don’t have the same issue with NewPipe so have been using that till this gets fixed. It’s been reported here #2761

    • Prathas@lemmy.zipOP
      3·
      2 days ago

      I actually don’t even know how to use a custom DNS, haha, but it’s good that you were at least able to pinpoint the issue!

      • jaygray91@piefed.zipEnglish
        5·
        2 days ago

        Aw geez, wish I can help more. But IMO the dev is very aware of this. IIRC when 5.2.4, this current latest version, dropped, I remember seeing in-app popup pointing to that GitHub issue that the dev opened.

  • thingsiplay@lemmy.ml
    51·
    2 days ago

    I don’t use PipePipe, but FreeTube. Since YouTube updated their system to use SABR (I don’t even know what exactly that is, I just know it causes issues for us), I get sometimes a reload loop for some videos. In some cases my IP is blocked. Only a VPN helps in those cases. This plagues me / us for weeks and months. I’m surprised you didn’t encounter this issue earlier; probably because the developers of the app you are using did a good job.