fungos

joined 1 year ago
[–] [email protected] 7 points 4 months ago

No, that is counter intuitive. It may appear more expensive at first, but on the long run it is a lot more cheaper. It avoid vendor lock-in, recurring increase of dev costs and licensing and lots of other plagues of closed proprietary development like blackbox development and justification of hidden complexity as a driving factor on costs. I worked with legacy closed proprietary sw development and lock-in combined with legacy complexity made man-hour costs exorbitant. These are partially solved by open-sourcing, as kicking out a team and putting a new one is easier, but most importantly transparency as a driving factor on quality of development.

[–] [email protected] 0 points 4 months ago* (last edited 4 months ago) (1 children)

https://github.com/jellyfin/jellyfin-web/issues/4346

Lol at people down voting without a clue.

Anyway, that issue is 1 year old, and subtitles for some reason just keep getting worse with each update. It is not being taken seriously.

It is so easy to reproduce that there must be something more involved to it, explaining why some people dont have the issue.

I tested and validated with these clients: web, roku, android, android-tv, fire and LG

All have the same issue. So maybe some combination of factors with server.

The bugs are different depending on the media, sometimes delayed subtitles and most of times no subtitles at all. Also, trying to switch subtitles to other languages sometimes just dont take effect unless the playback is restarted. Anyway, it is baraly usable.

[–] [email protected] -3 points 4 months ago* (last edited 4 months ago) (3 children)

I really like Jellyfin and push for it, but since last release, it became barely usable. Unfortunately, it made me and all my users switch to Plex again. Where they preferred to buy the respective Plex clients instead of dealing with Jellyfin issues. It is sad, it could be money donated to Jellyfin at some time.

Seriously, if Jellyfin doesn't fix all subtitles issues with their clients, it will be really hard to be taken as a serious competitor in the area. I hope they take this issue seriously and fix it asap before further damage to the project happens.

[–] [email protected] 13 points 4 months ago (1 children)
[–] [email protected] 7 points 8 months ago* (last edited 8 months ago) (3 children)

mine was really sluggish for a long time, then I saw someone in here explaining their similar issue and their fix. I don't have the post link, but it was related to DNS settings. Basically for some reason using my pihole dns made only nextcloud sluggish, the fix suggestion was to use 1.1.1.1, which worked. Now, it is a pretty fast nextcloud.

[–] [email protected] 1 points 1 year ago

You're right! My bad. I did search for it, but couldn't find on their web site, but the code doesn't seems to have everything. I can't find the Android app source.

[–] [email protected] 8 points 1 year ago (2 children)

I have both setups (arr stack and stremio+torrentio), here my opinion.

Where stremio falls short is:

  1. cast integration: semi works with chrome cast, but when using torrentio I just cant get it to work. I need to get into screen mirroring, which is less than ideal. Not to mention it doesn't work with Roku/DIAL protocol.

  2. proprietary and closed- source. It will not take long until MPAA-eye will look at it and try to curtail it (eg. going after torre ntio or other addons).

I like it, but I prefer to control my destiny, so I keep my arr stack always close.

[–] [email protected] 2 points 1 year ago (2 children)

Awesome and thanks a lot for putting the time to explain it like this.

So for some reason I got side tracked with radarr and didn't see the need for trackt anywhere, but that seems the missing part on all this.

This also shows up that the Plex workflow is seamless (no Overseerr/jellyseerr need, no trackt need) than jellyfin right now.

Reading plex_debrid code, it seems it has some initial code on scanning current Jellyfin library, so finishing that code could remove the need of Trackt.

Now, one advantage of using Radarr ia that it will move and rename to a standad naming the incoming files, I think that only for this feature it is worth to keep it in the workflow.

So it seems like I'll need to fix plex_debrid to understand existing Jellyfin library and remove the need of trackt!

Thanks a lot!

[–] [email protected] 2 points 1 year ago (4 children)

Interesting. I installed here but I may be doing something wrong with my setup, because just using Jellyseerr is not triggering a RD download. First, using jellyseer required radarr anyway, the setup is like following:

  1. Jellyseer request a movie/show, put that request via radarr
  2. radarr will try search for a torrent via indexers (not working right now)
  3. Download via Black Hole Torrent, which is basically monitoring plex_debrid folders

Still, not working as things aren't communicating with each other correctly and I didn't set any indexers (or set jackett).

My setup feels wrong or too complex, can you give a bit more of details on yours? How the parts communicate? :)

[–] [email protected] 4 points 1 year ago (7 children)

plex_debrid looks the way to go with. I was put off it because its name and I use jellyfin. Reading more closely it works with jellyfin, so cutting off the middleman (radarr) seems like a very good solution!

Is there anything special to know about it before trying myself? Any issues or roadblocks you had when setting this up?

Thanks for the answer!

 

I'm considering using RD, but before sign-in up and paying for it, I would like to know if is there a way or a guide on how to get tools like radarr to automatically use RD for downloads instead of using VPNs and seedboxes/torrentboxes.

If you do have a similar setup, can you describe it? Thanks!

[–] [email protected] 5 points 1 year ago (2 children)

Reddit blockeado no meu pihole. Site mobile lixo e como quebraram os clientes de terceiros, não tem nem como querer usar denovo. Meu velho cliente Infinity ta funcionando perfeitamente no Lemmy (mudou o nome para Eternity), então tá tudo de boa. Falta mais corajosos migrarem para cá para gerar discussões interessantes, mas no principal uso meu, News Feed, tá tudo muito bom já!

view more: next ›