Victor

So it’s a YAML quirk then?

Must not have quotation marks. Removed them and now it’s working.

Man that’s finicky…

My client showed that to me and I read it. I just imagined myself as someone who doesn’t know what Jellyfin is, and that text didn’t help much.

Ew. Yeah, good changes coming in that case. Glad they ironed that out!

Brilliant. 👍

Though sometimes you go to the website and it’s not much better.

Dude yes. Among my comments you’ll see that I ranted about this for a few days in the comments of another post. That’s even worse, when you can’t even find out for yourself.

any DB access now goes through the core library

Out of curiosity, this is better because of encapsulation? Protection from bad plugins?

I’m serious, there’s so much lazy posting on Lemmy regarding software releases.

• no mention of what the software is or does ✔️
• no mention of what’s interesting about the software or this release. ✔️

Jellyfin is quite a big name, but still, the pattern is clear.

just a small recap:

Postiz is a […]

Lovely to see that. And in the title. Thank you for that. 😙

At least they’re self-aware.

This all still doesn’t address the first thing I wrote:

Jellyfin with the same library takes mere seconds before I see the first movie/episode poster cards.

Why can Jellyfin perform perfectly on the same hardware? Very snappy. It’s obviously not the hardware’s fault, but more a lack of optimization — and testing. If they tested/dogfed their app on WebOS at all, they’d know it’s ass.

Edit: I just did a quick research on this in the Plex forums, and it seems like a lot of posts detail the same experience as mine: Plex used to work great until a year or more ago where it just turned into an unoptimized mess where even stepping left or right to a different poster, or button, has like a 1+ second lag.

It’s very clear this is Plex’s fault. It wasn’t always like this.

Every single post is ignored by Plex and automatically closed due to inactivity (from Plex). They don’t care.

Ah okay. Yes, it seems to be indeed. 😅

Jellyfin with the same library takes mere seconds before I see the first movie/episode poster cards.

How do you explain this? Every other app is very quick to load on the TV… Plex is the only issue.

If you use a dedicated streaming device

What do you call a TV? The streaming isn’t the problem, it’s the loading or processing of data from the server, and/or transitions between views, that are the issues here.

Streaming is fine. Once I start a 4K HDR 5.1 movie with direct play (full quality), there is no issue, even when seeking. It’s only the browsing and loading/displaying of data that is super slow. And only on Plex.

Yeah dude. Besides Plex, the TV is FUYOOOH! 😙👌

No rain here. ☀️👍

What TV is that? I have an LG OLED TV from 2019 running WebOS, so that’s the version of Plex I am using.

My Plex library loads instantly on my phone and on the web.

I am using the Plex app on my LG TV, to be more precise. That’s the WebOS version of Plex. On my phone and on the web, it loads instantly.

I would probably still want to use Plex due to its superior interface, despite this shit they are pulling. But Plex on my TV is so UNBELIEVABLY slow. I have a large library, like almost 14 TB and still growing. But there’s no reason it should take almost a minute (or more than?) for the first content to show after starting the app.

Jellyfin with the same library takes mere seconds before I see the first movie/episode poster cards. It’s inexcusable how poorly optimized Plex is.

Found a good one ☝️

Mm, interesting.

Are we sure they are using semantic versioning?