-
-
Notifications
You must be signed in to change notification settings - Fork 19
Cannot launch video anymore #211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Confirmed. The video URLs extracted by A workaround would be to set in the config-file: force_fallback => 1, ...which will use |
Thank you, the workaround works for me now. |
Thank you, the workaround works for me too. |
I'm also getting some new errors. I'm 99% I was not getting them last week. I'm I strongly suspect this to be related to youtube strangling invidious and/or changing the interface. Regarding yt-dlp, I also make heavy use of it on the command line, and have not I only use the CLI version of pipe-viewer never the GUI, on Archlinux.
I have
I also tested all this removing the caches and restarting a fresh,
I do not use the default player
Pipe-viewer is only responsible for browsing, not downloading. I only take the "URL". I have been using for many many years some custom Basicly,
So in the last day(s) I noticed that: Searching seems to work fine. But when i press ";i22" to get info on video "22" I immediately get,
It then takes an awfull lot of time to get the metadata. That 1478 line,
It also seems that pipe-viewer is not caching that request or making use of That is, if i press again ";i22" it does a new network request, and takes a lot Playing. If I know press "22" to "play" the video, same error message, same awfull delay again. force_fallback => 1 doesnt seem to make any difference ???? I also tried to change the user agent. $ yt-dlp --dump-user-agent
From,
To,
But then I start getting,
And cant neither search nor download. About Instances. I also never quite understood this quite well. I had always assumed that with the default,
Since I am very skeptical of the future of invidious, I assumed I was "safe" pipe-viewer would never make use of invidious. Am I correct in this assumption ? Why that contact with an invidious instance, "401 unauthorized" to "https://inv.nadeko.net/api/" then ? Why with "0" is there a ~/.config/pipe-viewer/current_instance.json than ? I think I can understand that with "1" a ~/.config/pipe-viewer/instances.json shows up. |
Just used this,
$ pipe-viewer
Hhhm ... so it used the fallback even when I have "force_fallback => 0,"
Hmmm again is using the fallback...
That url "https://www.youtube.com/watch?v=87O0M_F7cb4" gets passed to |
@m040601 The extraction of video info ( Regarding |
I can now confirm this. Thanks for the prompt fix. |
About the user_agent. I made a type in my previous comment. I was trying changing this option,
To
But that fails, at least for searching with,
And then pipe-viewer auto closes. |
The value for |
I'm using force_fallback = 1, and in the last couple days, I've come across more and more videos that pipe-viewer fails to get yt-dlp to download and play. When running yt-dlp on the url directly, it works fine. Could this have something to do with the test of drm encryption that youtube's been trying out? Example log:
yt-dlp 2025.03.21, pipe-viewer 0.5.3 cli -Michael. |
Hello, since few days, I cannot launch anymore any videos like this:
recording.mp4
This is my configuration file:
I'm using pipe-viewer version 0.5.3 on Void linux.
Best regards.
The text was updated successfully, but these errors were encountered: