meeb

Might be something damaged with your SQLite db (e.g. hard kill on a process which was writing to the db at the time), try a "repair": 1. Stop the container...

The next release will have two split background workers, one that indexes media and one that downloads media, rather than N pools of workers doing generic tasks. This could probably...

The SQLite db should be able to handle millions of entries on paper. The issue with locking multiple writes at once. Assuming you have `TUBESYNC_WORKERS` env set to `1` this...

Have you tried `:v0.9` or `:latest`? Any improvements with your issues?

I've not got a NAS handy to test it on, however I would suspect the advice for you would be use Postgres once support is added.

This might be possible, I'll look into it. The `info.json` style output is directly written by `yt-dlp` so for this requested feature to be possible `yt-dlp` needs to support writing...

This is currently by design. TubeSync was originally designed as a PVR-like tool for YouTube so it was, at first release, capped to 720p or higher. This has been reduced...

I think the video actually will download, I noticed this myself earlier but hadn't got around to making an issue for it yet. I'm pretty sure this is just a...

Is there anything in your container logs @Casuallynoted ? Any actual Python errors would be in there and it would be pretty difficult to diagnose your issue without more information.

Thanks for the confirmation @Jimmni - in the interim if the (exact match) is visible and the media is downloaded you can ignore the template incorrectly saying it'll be skipped...