-
Notifications
You must be signed in to change notification settings - Fork 643
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
Better error reporting on app crashes #1243
Comments
Almost same issue here:
I can fetch metadata, comments, but can't watch neither download :(
|
got the same error as @polochon777 this week (on the last week on I still can download audio from Youtube using Text of the error:
My config:
MPV data:
|
I suspect yewtube is blocked by youtube... |
Interesting, I wonder if it could be worth re-introducing the API tokens from prior MPS-Youtube to allow folks a workaround? I'd think the issue is that with YouTube locking down video access (e.g. with ad-blocking), the best path would be api and api-key access? One could even prompt folks to add their key after installation. That is unless another method is found to fall back on, of course. Edit: Invidious is also having this issue, and pinned some info/discussions about workarounds they are evaluating: |
It's strange cause I have YT still working on an old MacBook running Mac OSX 10.6.
Setting :
mpv :
Just tried setting |
I guess its time to move backend from |
Hello, I've been having the same issue. Does anyone know which upstream project I should follow to be in tune with possible updates that will resolve the issue? I'm not familiar with the whole toolchain and how things are fitting together. |
Ok, for me the problem seem was from yt-dlp being version 2023.03.04. And an upgrade with pipx wouldn't update it. I had yewtube installed on a iMac G5 running Mac OSX 10.4.11, using pip3. There too yt_dlp was v.2023.03.04, and it wouldn't work. |
fixed: #1243 bumped yt-dlp version
Guys update to latest yewtube / yt-dlp version. Edit: |
Can confirm this fixed my issue with playback. However the core question I had with making this github issue was about requesting a method to launch a debugging session or pull debugging information from yewtube to help with diagnosing playback issues (and confirm upstream issues as appropriate). Is there a preferred method for pulling these logs/diagnostics? In this case, my method required screen-recording and going frame-by-frame to capture the yt-dlp failure message, so I'm just wondering what might be more helpful in the future... |
Hi, how can I install the latest version 2.10.5? Installing with pip/pipx gives me 2.10.4. When I give the command to install the latest version best regards, |
I was also trying to figure this out, I tried the repository version as well as the .tar.gz under "releases" ; all seem to show 2.10.4 |
So today I started having an issue that no results will play. Typically, long videos and certain results may fail to play (akin to #1208), but now no results are loading at all. There is a momentary flash and then the results list reloads.
Issue / Suggestion
This is likely an upstream issue overall, but wanted to bring attention to something that was making debugging quite difficult. After using a screen recorder at 30fps, I was finally able to record the result failing to play, and the result being then hidden and dropping to the list.
In my case there is an apparent ffmpeg error due to an HTTP error 403 Forbidden (this seems similar to older errors that came about due to API key setups before, but also possibly upstream).
My main concern is that there currently does not seem to be documentation on how to collect debug logs for use. I have tried using the
--debug
flag to no avail, but did see an old post on Linux noting--logging
, but I am not sure how that would work on windows and using pipx instead of pip...Can someone provide guidance on the best way to collect logs on this playback issue? And what might be the preferred way to submit that info in a PR for the documentation?
Your Environment
For yewtube:
And for mpv:
The text was updated successfully, but these errors were encountered: