The data directory information is located in the documentation on the GitHub page. Will depend on the OS. In that directory, the log file is just log.txt. That being said, if no errors are given via yt-dlp, then it wouldn’t be logged regardless.

Yt-dlp logging was added in the most recent GitHub release, so anything from before may not have generated logs regardless.

Worth mentioning I am currently doing a complete rewrite for version 2.0 with lots of quality of life improvements and a fair bit more verbosity in error reporting. Historically, this was just a personal program so troubleshooting 3rd party interactions across operating systems was not a priority.

If you want to mess around with the MPV and yt-dlp pipeline. Try just running mpv <youtube_url> to see if it works outside of yt-feeds. Yt-dlp recently started to require a JS backend like Node or Deno, so that might be another thing to look into as that can cause bugs like this.

GrayJay seems like a neat project that I bet I would enjoy.

I created yt-feeds as I wanted an ultra lightweight TUI as I was getting tired of the 500Mb-1Gb electrons programs.

Thank you for continuing to troubleshoot. No worries with GitHub, I understand your concern!

Can you check the log file? In 1.0.5 I’ve added stderr dumps from MPV to the log file. If any errors occurred, that’d give us a place to start.

I might not be able to recreate the issue, but others might have the same issue so I’m happy to find the source problem.

Curious: is this with the attached configuration in the documentation, or with a custom configuration for either MPV or yt-dlp?

If this is with that configuration, can you try the from source version?

Edit:

Please use Github Issues for any bug reporting to allow for better tracking. The newest version of yt-feeds is now at 1.0.5 with improved error logging for better user reporting!

The attached configuration should not theoretically be necessary - I was able to see full functionality with blank configuration.

In my testing though, I’ve notice some configurations options can cause issues with the yt-dlp and MPV pipeline.

As per logging, it is automatically on with messages stored in the specified files in the documentation. As of 1.0.5, MPV and yt-dlp stderr is also logged. Anything prior to 1.0.5 will not feature this logging.

Edit:

Please use Github Issues for any bug reporting to allow for better tracking. The newest version of yt-feeds is now at 1.0.5 with improved error logging for better user reporting!

Update from today:

I could not replicate this issue. It is possible you initially were on 1.0.2, which had these issues.

Steps to replicate working build:

brew install yt-dlp 
brew install mpv
cargo install --git https://github.com/nate-craft/yt-feeds
yt-feeds

This was done with all default configurations set for MPV and yt-dlp.

Edit:

Please use Github Issues for any bug reporting to allow for better tracking. The newest version of yt-feeds is now at 1.0.5 with improved error logging for better user reporting!

In what environment is this setup?

Running the version 1.0.3 via the AUR with Yt-dlp built on 11 12 2025 and MPV built on 9 24 2025 as well as the the provided MPV and yt-dlp configurations is confirmed to work this morning.

Edit:

Please use Github Issues for any bug reporting to allow for better tracking. The newest version of yt-feeds is now at 1.0.5 with improved error logging for better user reporting!

Haven’t tested via MacOS yet, so I’m not sure about the issue from a glance.

As of yt-feeds 1.0.2, there was a yt-dlp issue that would do what you describe as yt-dlp requires a new flag to enable a JS backend to work around a YouTube change. I’d first check that to ensure it is on the newest version.

Otherwise, I’ll look into it on a Mac test environment tomorrow.

Edit:

Please use Github Issues for any bug reporting to allow for better tracking. The newest version of yt-feeds is now at 1.0.5 with improved error logging for better user reporting!

Hi - thanks for the question.

If the drive is mounted into native fileystem, rust’s files API should be able to read and write properly.

If not, feel free to submit an issue on GitHub and I’ll look into solutions.