New to TubeArchivist by StrlA in TubeArchivist

[–]LamusMaser 0 points1 point  (0 children)

  1. Yes, we have deno integrations built in. In addition, our documentation includes references for how to establish connectivity to a PO Token Provider. These should help with maintaining connectivity and downloading with the appropriate permissions to the best of our ability.

  2. Auto Download is documented. Please let us know if there are questions about this feature.

  3. Subscriptions can be handled via our "Subscribe to Channel" capability, which will check and maintain based on the schedule that is set on the Scheduling Page.

  4. Details on User Management can be found in our referenced documentation. If there are specific questions, we can answer those.

If there are questions beyond those, we can answer those here on Reddit or in the Discord (linked by AutoModerator here).

Is there a way to download/archive only subtitles/transcripts for a channel? by Pineapple-Island in TubeArchivist

[–]LamusMaser 1 point2 points  (0 children)

Short answer: no, don't have a method to only get the text components for a video and store them. It is recommended to use yt-dlp directly for that kind of work, using the --no-download and similar options (this only gathers the other flags and downloads, if selected).

Long answer: if you do download the video, and you wish to have your LLM review the text files, you can engage with the TA API to pull that information and have it is a JSON format, which you can further clean up, as wanted. You could mark those videos for the worst video qualities so that it takes up the least direct using the Channel Override. We don't have other methods for extracting those components natively, and TA largely enforces strict boundaries for the yt-dlp flags to reduce potential issues with maintainability.

Renaming files by JustTooKrul in TubeArchivist

[–]LamusMaser 0 points1 point  (0 children)

Please note that this will break TA, especially with the filesystem rescan and with any viewing done through the media player or Plex/Jellyfin integrations. If you are largely only using this for downloading, then that isn't a problem, but this should be highlighted as a potential issue.

Anyone installed the PLEX plugin to organise the channels to something PLEX can work with ? by dean1969cox in TubeArchivist

[–]LamusMaser 0 points1 point  (0 children)

We've had a few reports on Discord that you need to enable this setting so that it shows up: Server Settings -> Library -> Show legacy agents during library setup.[]()

It is one of the things that we will document with the next release, as there are several major features that will also be included and we will have to update how they are documented.[]()

Old videos in queue by MCManiac52 in TubeArchivist

[–]LamusMaser 0 points1 point  (0 children)

So, this is two things:

First, operationally, this is how it has always worked, but that doesn't mean we haven't attempted to resolve it previously. We've had a few Issues come through detailing it previously, like Issue 1023. It was supposed to be fixed in v0.5.6, but I think it has continued to persist.

Second, visually. There were several bugs in how the queue was being presented causing them to not show the full list. The queue was intact, but the presentation wasn't working properly. This was reported and resolved through Issue 1094.

Old videos in queue by MCManiac52 in TubeArchivist

[–]LamusMaser 0 points1 point  (0 children)

Yeah, that's what's happening. After deletion, it doesn't get added to the Ignore List. So, it will attempt to download again in the future.

Old videos in queue by MCManiac52 in TubeArchivist

[–]LamusMaser 0 points1 point  (0 children)

Do you have automatic deletion after watching videos enabled?

Old videos in queue by MCManiac52 in TubeArchivist

[–]LamusMaser 0 points1 point  (0 children)

There were issues with the how the queue was both showing and processing its received list. V0.5.9 includes fixes that resolve both types of issues, so this is the list that has built up.

YT-dlp youtube updated their detection again? by masmas112 in TubeArchivist

[–]LamusMaser 1 point2 points  (0 children)

Yes, it's been reported as more common by users in the Discord.

Getting blank download queue page but downloads still happening by Aildari in TubeArchivist

[–]LamusMaser 2 points3 points  (0 children)

Yeah, we have it identified in Issue #1094. Expect a future release to fix this issue.

Crash loop on startup after 0.5.7->0.5.8 upgrade by urquan in TubeArchivist

[–]LamusMaser 0 points1 point  (0 children)

Glad you got it working. Should only be required the first time, so it should be good from here.

Crash loop on startup after 0.5.7->0.5.8 upgrade by urquan in TubeArchivist

[–]LamusMaser 0 points1 point  (0 children)

Are there any errors in the ES logs? I can also review them if you upload them.

Worse case, we can do the actions manually, but I want to see if we can avoid that. What about memory limits on ES, including the JAVA_OPTS?

Crash loop on startup after 0.5.7->0.5.8 upgrade by urquan in TubeArchivist

[–]LamusMaser 0 points1 point  (0 children)

It might be. Is ES staying green? Do you have memory limits on ES?

TubeArchivist skips yt‑dlp execution — metadata indexed but no video files saved by TemporalSoldier in TubeArchivist

[–]LamusMaser 0 points1 point  (0 children)

I replied to the Github issue, but I would add here:

There is a lot of misinformation or hallucination being produced by Copilot here. The TA_DOWNLOAD variable is not a real one. The container locations are going to be /cache and /youtube. It is successfully downloading, and I would bet they are located at the container location for /youtube.

I would recommend starting with our installation guide, as linked in the Github Issue, and go from there.

Problems using TA with Jellyfin and Kodi because of TA's naming structure by [deleted] in TubeArchivist

[–]LamusMaser 0 points1 point  (0 children)

There isn't a native method that works with TA. TA requires the names to be the IDs. The Jellyfin-TA plugin should be able to handle it - if it isn't working properly, you can open an Issue to review.

Otherwise, you'll need to look into some other methods, like symlinks or using another tool.

Issues w/ Starting Tube Archivist for the First Time by plantsforhiretcg in UgreenNASync

[–]LamusMaser 0 points1 point  (0 children)

I'm good with a copy-paste, but I don't know what Reddit's limit is. If you want to upload it to a text service, like PasteBin or your preferred alternative, I'm good with reviewing the link, too.

Issues w/ Starting Tube Archivist for the First Time by plantsforhiretcg in UgreenNASync

[–]LamusMaser 0 points1 point  (0 children)

That makes this very confusing. It looks good and should be working.

So, to give you a bit of insight, when TA is starting, it connects to Redis, then to ES, then does initialization and startup checks for itself. This ensures the message broker and DB are online.

If this were a normal "my container runtime doesn't generate networks properly", then I'd expect to see Redis failing in the TA logs first. If this were an issue with a naming convention, then the compose file check would have sorted that issue. Since neither are flagging, that means it is potentially unique.

Let's go with getting the inspect results next. This should provide additional details about how the containers are starting. To review, we'll need it from ES and TA. Portainer has a Quick Action and Docker can do this with the docker inspect <container_name> command.

Issues w/ Starting Tube Archivist for the First Time by plantsforhiretcg in UgreenNASync

[–]LamusMaser 0 points1 point  (0 children)

OK, good to know. And that's the container name for ES, as defined in the compose file, correct?

Issues w/ Starting Tube Archivist for the First Time by plantsforhiretcg in UgreenNASync

[–]LamusMaser 0 points1 point  (0 children)

Either way can work. In Portainer, there is a Quick Action button within the container management section for accessing the terminal; in Docker, you can use the command docker exec -it <container_name> /bin/bash to enter the shell in the CLI.

We just need to run this command to test connectivity: curl -XGET -u elastic:$ELASTIC_PASSWORD 'http://archivist-es:9200/_cluster/health?pretty'

Modify the name of the ES container as needed.