Lightweight YouTube client for Linux
Either I somehow broke the script, or it behaves in a weird way. I have set in `~/.config/youtube-viewer/youtube-viewer.conf` to NOT use yt-dlp ``` $ cat .config/youtube-viewer/youtube-viewer.conf | grep ytdl download_with_ytdl => 1, arg => "--really-quiet --force-media-title=*TITLE* --no-ytdl *VIDEO*", arg => "--ytdl-raw-options-append=\"format-sort=ext,res:*RESOLUTION*\" *URL*", ytdl => 0, ytdl_cmd => "/usr/bin/yt-dlp", ``` but the debug log shows the opposite when playback starts. ``` $ youtube-viewer --debug =>> Search for YouTube videos (:h for help) > novel 729 lygmos ** GET https://www.googleapis.com/youtube/v3/search?key=(removed)&maxResults=20&part=snippet&prettyPrint=false&q=novel%20729%20lygmos&type=video ==> 200 OK (2s) ** GET https://www.googleapis.com/youtube/v3/videos?id=ZmfVLOtjLnc&key=(removed)&maxResults=20&part=contentDetails,statistics,snippet&prettyPrint=false ==> 200 OK 1. Novel 729 ~ Λυγμός (Official Audio) Novel 729 Of 1y 234K 04:16 =>> Select one or more videos to play (:h for help) > 1 ** POST https://youtubei.googleapis.com/youtubei/v1/player?key=(removed) ==> 200 OK (1s) :: Using `player_response` to extract the streaming URLs... :: Using invidious to extract the streaming URLs... :: invidious: found 0 streaming URLs... :: Found 0 streaming URLs... => Description (removed because it is useless) -------------------------------------------------------------------------------- -> Resolution: best -> Video itag: 38 -> Video type: video/mp4 -> Command: /usr/bin/mpv --really-quiet --force-media-title=Novel\ 729\ \~\ Λυγμός\ \(Official\ Audio\) https\:\/\/www\.youtube\.com\/watch\?v\=ZmfVLOtjLnc ``` I noticed the line about invidious, but there is no relevant setting in the config file about it, so I do not think it matters. So what gives? p.s. The searched song was selected on purpose so as to get exactly ONE result and not dozens. It happens with anything.
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be resolved. The issue was opened by pitsi and has received 4 comments.