this post was submitted on 16 Jul 2024
21 points (95.7% liked)

Selfhosted

39167 readers
386 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I'll start by saying that I really love Tube Archivist. It works flawlessly in doing what it does (archiving YouTube videos), and the UI and UX are great.

However, no matter what browser I use (Edge, FF, Opera, Samsung mobile, FF mobile, etc...), I run into issues where the video will play, but the interface freezes... I can't do anything on the screen until I refresh.

I don't have it set to any strange codecs, so videos are in vp9. But I also tried a few different codecs to see if the quality/size could be better optimized, and had the same issues with freezing UI then.

If I run the videos through Jellyfin, they work fine. It's only through the TA web interface where things lock up.

Is this normal? Does anyone have any suggestions on how to get this working better?

you are viewing a single comment's thread
view the rest of the comments
[–] Showroom7561@lemmy.ca 1 points 1 month ago

I wonder what heck is going on, then.

I've used multiple computers with FF, and it happens on all of them. Granted, this problem happens no matter what browser I use, so I know it's not a FF problem.