only 360p resolution in some videos
Official Instance
- [x] The bug is reproducible on the official hosted instance, or is API-related.
Describe the bug
only 360p videoStreams available in some videos.
To Reproduce
example videos (might change over time): watch?v=DkzQxw16G9w
Expected behavior
1080p or higher is available on youtube.
Logs/Errors
output of pipedapi/streams/DkzQxw16G9w:
{
"title": "How Big Can a Person Get?",
"description": '',
"uploadDate": "2013-04-15T14:01:07-07:00",
"uploader": "Vsauce",
"uploaderUrl": "/channel/UC6nSFpj9HTCZ5t-N3Rm3-HA",
"uploaderAvatar": "",
"thumbnailUrl": "",
"hls": null,
"dash": null,
"lbryId": null,
"category": "Science & Technology",
"license": "YouTube licence",
"visibility": "public",
"tags":
[],
"metaInfo": [],
"uploaderVerified": true,
"duration": 944,
"views": 21168845,
"likes": 411358,
"dislikes": 7381,
"uploaderSubscriberCount": 23900000,
"uploaded": 1366059667000,
"audioStreams": [],
"videoStreams":
[
{
"url": "/videoplayback?...",
"format": "MPEG_4",
"quality": "360p",
"mimeType": "video/mp4",
"codec": null,
"audioTrackId": null,
"audioTrackName": null,
"audioTrackType": null,
"audioTrackLocale": null,
"videoOnly": false,
"itag": 18,
"bitrate": 0,
"initStart": 0,
"initEnd": 0,
"indexStart": 0,
"indexEnd": 0,
"width": 0,
"height": 0,
"fps": 0,
"contentLength": 42869491,
},
],
"relatedStreams": [],
"subtitles":
[],
"livestream": false,
"proxyUrl": "https://pipedapi",
"chapters": [],
"previewFrames":
[],
}
Browser, and OS with Version.
backend 1337kavin/piped:latest@sha256:de3e1a7c8cf8d4dfcd61935ff48b5d884295f31d95a5562ce5b4ccde3672bc32, with 1337kavin/bg-helper-server:latest@sha256:087caa963351117595833bbf8a65b991a763ede9add1668c1b6c68671253a5d4
Additional context
No response
see https://github.com/TeamNewPipe/NewPipe/issues/12126
We need to wait for some extractor changes and then implement a proxy for SABR.
I don't have any interest in working on that though since I personally don't use Piped anymore.
Looks like it's now temporarily fixed in the new extractor version.
I was able to drop-in NewPipeExtractor into Piped-Backend, just with a few tweaks to Piped-Backend.
This patch has the required changes if people don't want to wait for Piped's NPE fork to update and are OK with using a custom Piped-Backend version.
@hugoghx how do I apply the patch for building in docker?
@hugoghx how do I apply the patch for building in docker?
I tried it with git apply <name of patchfile> but this didn't work out due to some "corruption error". Instead I manually updated the files and built the container image.
If you want, you could build your image with docker container build . -t <cool name here> using the applied changes in my repo https://git.ghoscht.com/ghoscht/piped-backend. You could always also apply the changes from the patch file yourself and rebuild.
Thanks, didn't know about git apply, Here's the image: https://hub.docker.com/r/nieveve/piped-backend
Thanks, didn't know about git apply, Here's the image: https://hub.docker.com/r/nieveve/piped-backend
Thank you so much! This solves it for me.