All Activity

HLG, HDR10+, advanced HDR10+, DV IQ, DV2, DV profile 7 FEL using both layers, AV1, VP9 and some other newer codecs are not supported. The Shield is getting old and could use a refresh.

Not sure why it really matters if it was developed using AI, or not. I see nowhere that it says they hand jammed all the code themselves. No matter how it was developed they did the work putting together for people to decide if they want to use it. I used to develop stuff myself using COBOL on a mainframe and I could complain how the developers now have all the GUI tools making their jobs much easier and how they aren't real developers either. Everything is going AI nowadays and making apps is no different. If anything, they could give credit to Emby for making and releasing the APIs which made it possible for them to make this app.

Hello. Any updates please? Thank you

Wow I didn't know that, apart from files with HLG HDR this must be one of the few exceptions the Shield doesn't support. I enabled transcoding on the server and tested multiple episodes. They all play now, but fastforwarding to skip intro's sometimes results in the episode freezing or the subtitles not running in sync anymore. I'm afraid my Synology DS916+ might not be a bit slow for transcoding so I'll have to live with that. If the decoding could be done in app like for the other application that would be great. The only issue that remains is that when the app automatically starts playing the next episode the default subtitles are no longer selected. Sometimes it works to select them while the episode is playing, but most of the time that doesn't work so I have to stop the playback and manually start the episode again with the subtitles selected. When manually starting an unplayed episode the default subtitles are always selected and play without issues.

thanks!

Yes

Having the same issue. Any updates on a fix?

this one?

I recommend keeping at least "skip videos with existing markers" on as other wise it will run detection on everything, even files that has already been processed. Going to check later today if I forgot to add those settings to the data manager or else they get ignored and reset when changed.

Only for people with slow, or bad connections. Those of us with faster connections find it an annoyance that could be solved by only showing it for those having connection issues.

Can I just say, f. auto correction on mobile phones. That previous post is almost unreadable.

No, I'm stuck on TOS 4 as 5 is for x86 CPU's and mine is ARM.

This is a massive improvement!

It allows you to cancel though, so if the server is offline you no longer have to wait for the connection attempt to time out.

Yes, I have those checked. But, interestingly, the schedule shows as this today: I haven't knowingly changed any setting since reporting in this thread.

Oh interesting. I'd be curious why LibreELEC does such a good job at smooth playback on the Pi4 while the Emby linux beta is choppy

The new toast on emby start up that says something like connecting to the server, the toast is unnecessary.

Forget it – the admins here just make promises without ever implementing a solution or keeping their word

@Pejamas You can look at it

All my quality settings are, and had always been set to Auto, and everything worked fine until 5he latest updates. I reported this same 4K issue a couple of days ago. This issue started for me after updating to the lastest 3 versions. It's even reporting 4k as 720p in some cases, and 4k media stutters horribly. The only workaround for this issue to get 4k working, was to manually set the quality to 4K-40mbp in quality settings, otherwise...This is how 4k media plays (Attached) Hope this gets fixed soon. Screen_Recording_20260826_214143_Emby.mp4

No I got bored and gave up. @softworkz@Lukeif PluginUI is the future it would be good if the official plugins were updated - almost all of the ones I looked at are still using html/js

Nope still ended the scan at 0.3%

I needed a url to a user configuration page I was able to use apiclient.get url, and then had to remove the /emby and added the user Id I am noticing a bug, which I can write up tomorrow.

Not the names — the type. Whatever you called them is fine; the app has never cared, and I have a test library here called "Pel·lícules rares 日本語 ñ ½" that goes through without complaint. What mattered was the kind of library you picked when you created it: the app had a fixed list of kinds it understood, and one it didn't recognise sank the whole list. So "Documentaries" and "Radio" are perfectly good names. If either of them was set up as something unusual — an audiobooks library, say — that would be the one. But you don't need to go and look: it's fixed either way, and knowing which one it was wouldn't change anything now. And you were right about the youngest one being significant. That sentence is what split it into two bugs instead of one. I'd have been looking for a single cause otherwise, and the sign-in half would still be sitting there. As for days versus minutes — the minutes were only possible because your first post described both symptoms accurately and told me which account got which. That's the part that's actually hard, and you'd already done it before I started.

I will attempt it tomorrow and report back, Thanks Luke