Video append of XXXXXX failed for segment #X in playlist XX-placeholder-uri-XX

[efb4f5ff-1298-471a-8973-3d47447115dc]

Behavior of the program When opening a video to watch i get this error message in the player and the video is not playable. This happens randoms to me.

Expected behavior Dont get this message and play this vid.

To Reproduce Please add all steps to reproduce the behavior:

1. Go to 'watch a vid
2. See error

Screenshots

Desktop (please complete the following information):

• OS: [Win 10 Home]
• OS Version: [1909]
• FreeTube version: [0.9.2.]
• FreeTube build: [Release]

Additional context Add any other context about the problem here.

[GilgusMaximus]

As far as I figured it out, this is related to a problem with the player and the information in the dash formats. For me it only happened when I switched to 2k / 4k resolutions tho.

Do you have such a high resolution screen or switched to such a resolution?

[efb4f5ff-1298-471a-8973-3d47447115dc]

As far as I figured it out, this is related to a problem with the player and the information in the dash formats. For me it only happened when I switched to 2k / 4k resolutions tho.

Do you have such a high resolution screen or switched to such a resolution?

No i do not have such high screen resolution or swtitched to such resolution

[efb4f5ff-1298-471a-8973-3d47447115dc]

I'm really getting crazy of this error. This is on 0.11.1-nightly-484.

https://user-images.githubusercontent.com/73130443/104901702-a210fc80-5975-11eb-9eba-815d6f0a00f3.mp4

Things i tried to resolve the error, but didnt work.

• Closing the application -> Reopen -> Check if it's gone.
• Removing it from watch history -> Check if it's gone.
• Removing it from watch history -> Closing the application -> Reopen -> Check if it's gone.

[ShadowOfGannicus]

Same issue on some videos, but only when using "Dash Formats" video format. Found that switching default video formats to "Legacy Formats" in settings seems to be viable workaround for that issue.

[efb4f5ff-1298-471a-8973-3d47447115dc]

Just wanted to give a quick update: I cant seem to reproduce this bug anymore. I tried out all videos related to this issue.

[pawlosck]

I confirm. I can't see this bug since few weeks.

[GilgusMaximus]

Good to hear, then I am going to close this

[efb4f5ff-1298-471a-8973-3d47447115dc]

@GilgusMaximus could u reopen this i just encounterd this issue again. v0.13.1-nightly-930 Beta

[GilgusMaximus]

Sure. Still a weird issue tho

[efb4f5ff-1298-471a-8973-3d47447115dc]

@ChunkyProgrammer do u have any thoughts on how to fix this weird issue?

[ChunkyProgrammer]

@efb4f5ff-1298-471a-8973-3d47447115dc I think it's an upstream issue (chromium) https://github.com/videojs/http-streaming/issues/1080 but it looks like there's a work around

[k8188219]

@ChunkyProgrammer that work around is for older browser. latest chromium already fix that bug. If you want to investigate this problem. I suggest you try videojs/mux.js. Modify the example code to load the video which cause this error and add the following line. sourceBuffer.timestampOffset = -2;

[KingBright]

@ChunkyProgrammer that work around is for older browser. latest chromium already fix that bug. If you want to investigate this problem. I suggest you try videojs/mux.js. Modify the example code to load the video which cause this error and add the following line. sourceBuffer.timestampOffset = -2;

@k8188219 This exactly can fix my problem, but how can I fix it with videojs.js?

[k8188219]

@KingBright I don't know what problem you are dealing with. You need to provide more detailed information about your problem and how you fix it. Maybe consider opening another issue.

[EvilGremlin]

What i discoverd: Due to networks overload i have to often toggle VPN (by changing my LAN IP to be exact, actual route change and VPN is handled by my router) to get vidos playing at non-dialup speed, or playing at all. Looks like this error happens when player is waiting for response and buffer is too small, partial (like only audio) or no buffer. Cannot replicate while there is decent buffer present and video loads fast on both routes.

[peepo5]

Had this problem playing music as well for some reason CTRL+R fixed this

[Winterhuman]

I'm getting this issue when upgrading video quality but not from downgrading video quality, pausing playback before changing the quality usually makes the issue not happen, but, not always. Here's the issue I created which goes in more detail: https://github.com/FreeTubeApp/FreeTube/issues/1732

[hl2guide]

Yep I'm getting: video append of 895921b failed for segment #3 in playlist 10-placeholder-uri-10 when setting to 1080p

[peepo5]

That is an issue I get for around 1 in 30 videos (when using invidious API). It has never happened when visiting the invidious instance I am using directly, so it is only an issue with FreeTube. I wanted to try invidious again when using FreeTube, however it still has this problem. When I get this error, it is persistent with videos until maybe hours later?? I have not tested but a refresh does not fix.

[Winterhuman]

If anyone's looking for a fix, do the following if this is happening:

1. Change the video quality as you desire.
2. See video fail with usual errors reported above.
3. Change the video format to Legacy and then back to Dash.
4. Try playing again and see that the error doesn't occur this time, if not, repeat.

[billyray098]

Facing the same issue when I DOWNGRADE the video quality, haven't tested for upgrading yet but this is getting annoying

[peepo5]

Solution for now is change to legacy player

[PikachuEXE]

@peepopoggers You mean legacy video format?

[peepo5]

yes

[absidue]

I haven't tried this yet, but I noticed FreeTube uses video.js 7.14.3 (released on the 27th of July 2021), while the current stable version of video.js on npm is 7.17.0 (released on the 10th of November 2021). It might be worth trying to upgrade the dependencies and seeing if that helps.

[absidue]

Okay so upgrading video.js to 7.17.0 seems to fix the issue, however it's definitely not a drop in replacement, here is a list of issues i've noticed after upgrading video.js, videojs-overlay and videojs-vtt-thumbnails-freetube to the latest versions (the other video.js plugins are all up to date already):

• quality selector is missing from the player (i'm guessing videojs-http-source-selector needs an update, although it seems to be abandoned, last commit was in 2019)
• when opening a video page it doesn't automatically start playing the video
• shorts overflow the bottom of the window and take up the whole width of the player, instead of being restricted to the visible area like before
• there are probably other issues too that I haven't noticed yet.

[peepo5]

interesting investigation. this error is one of the most annoying to it would be great to get this fixed.

[absidue]

After my investigation I started trying to fix the issues, after spending way to much time on it and only making it worse, I'm leaving it up to you guys that know and understand vue.js, video.js and the black magic that is FreeTube codebase better than I do.

[VictoriousFan]

I'm getting this same error after clicking on a random video in my subscriptions I'm using the latest FlatPak distrubution, with no config changes at all I've only subscribed to a few channels. Pop!_OS

[absidue]

@nsde There was no need to comment again considering there hasn't been a FreeTube release since the last time you commented 🤦. Commenting again doesn't help anyone.

[nsde]

@nsde there hasn't been a FreeTube release since the last time you commented

Sorry, I didn't check that first. But is there any fork of FreeTube which is maintained actively?

[efb4f5ff-1298-471a-8973-3d47447115dc]

@nsde FreeTube is being actively maintained. See https://github.com/FreeTubeApp/FreeTube/commits/development

Edit: Also no there is no fork of FT the is maintained actively.

[absidue]

@nsde FreeTube is actively maintained (see the commits in this repository) there just hasn't been a release. Nobody has tackled this issue yet as that involves updating the video.js dependency which breaks a bunch of stuff. Feel free to create a pull request when you have updated the dependencies and fixed all associated issues though.

[4-FLOSS-Free-Libre-Open-Source-Software]

I haven't tried this yet, but I noticed FreeTube uses video.js 7.14.3 (released on the 27th of July 2021), while the current stable version of video.js on npm is 7.17.0 (released on the 10th of November 2021). It might be worth trying to upgrade the dependencies and seeing if that helps.

for video.js there is upgrade to 7.18.1 in 03e80596c62b831e70092def87e3dc81966deb43

[4-FLOSS-Free-Libre-Open-Source-Software]

I tried it with the new version "7.18.1", it did not fix this issue. Still manual CTRL+R required for refresh to resume video.

[stemy2]

It happens to me when i'm watching a video in 720p and switch it to 1080p.

[4-FLOSS-Free-Libre-Open-Source-Software]

Okay so upgrading video.js to 7.17.0 seems to fix the issue

Then you can try new freetube-0.17.0-RC with "video.js": "7.18.1",

[pawlosck]

Okay so upgrading video.js to 7.17.0 seems to fix the issue

Then you can try new freetube-0.17.0-RC with "video.js": "7.18.1",

Is there AppImage, snap version or tutorial how to build/run from source.

[absidue]

@pawlosck you don't need to build from source if you want to use the 0.17.0 RC, just download it from this link https://github.com/FreeTubeApp/FreeTube/actions/runs/2484662180 (you need to be logged into GitHub)

[pawlosck]

Okay so upgrading video.js to 7.17.0 seems to fix the issue

Then you can try new freetube-0.17.0-RC with "video.js": "7.18.1",

Bug still exists in 0.17 -> AppImage

[4-FLOSS-Free-Libre-Open-Source-Software]

In today's Release v0.17.0 Beta, the issue is still not fixed.

[efb4f5ff-1298-471a-8973-3d47447115dc]

@4-FLOSS-Free-Libre-Open-Source-Software there was never anything being mentioned in the release notes that this is fixed.

Please do not clutter the comment section with your comments because they dont contribute anything to solving this issue.

I have also saw this kind of behaviour of u in other issues as well. E.g. only posting a screenshot in the comment section of an error message that is already well explained in the description of the issue.

Or saying maybe X could work even though it isnt related at all to solving the issue.

Again do not do this! Otherwise it will considered as spam and u'll get removed from the repo.

[kubo6472]

Per #2443 which now no longer happens, but this exact thing happens instead.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[4-FLOSS-Free-Libre-Open-Source-Software]

This issue is not stale

[billyray098]

This issue is not stale

yes, experiencing the same problem in the latest version as well, although not as frequently.

[ChunkyProgrammer]

Might be relevant https://github.com/iv-org/invidious/issues/2848

[anonaddict]

Can confirm this still happens

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[torriem]

Still happening. In fact nearly every video will eventually freeze for me unless I switch over to legacy formats.