Leaderboard

Hi, the quality setting is a per-app setting, not a user setting. I think the next release of the server will help make this a little more clear. So maybe a more appropriate server option would be to ignore the user's quality setting.

Hi there, please attach the emby server and ffmpeg log files as well. thanks.

So it's definitely happening much less often now, but I just had my first one where playback immediately paused on starting the next song.

Thank you.

I don't have an ETA but we're working hard on it. Thanks.

Thanks for the quick reply! Yep, that's exactly what happened, I feel so dumb I forgot I edited all of my users' permissions when I was busy making changes. I had revoked the Notifications permission from every user... including myself. We're back in business, thank you so much!

HI, did you check the permissions of your emby user to see what they're granted access to?

Wonderful. I'm still on 4.8. But I may dl the Beta.

Just started testing for the last hour or so, so far it seems to be stable now

I'm running the Xbox app version 2.219.70.1. Enabling the option to allow higher bit rates, appears to have solved the issue. Tried a video that was 71mb/s, and it's showing Direct Play now. Hardware wise, I've got a Xbox Series S on wired gigabit.

@JatorI have a work around for you, I just need time to integrate it into the code. This will take me a day or so because of family commitments. Vic

@Ninko That info is very helpful. I will work on it later today. Vic

Personally I'd check the permissions on the dll file in your plugin folder... Media "is Movie" should list all your movies.. Check permissions for all your mapped shared folders just to be sure.

No, it is real I think. I believe i know why it is happening. It is on our list for review. Thanks.

Hi there! Still a little ways out yet as we continue to build out our platform, but I haven't forgotten this. We have a new blog post going live tomorrow that has an updated roadmap and the big section to look at will be our App Curation Templating System. This should greatly increase the speed at which we will be able to curate additional apps for HexOS, including Emby. As far as your other questions: 1) Updating Emby will be as simple as updating the container. We haven't decided if we want to do "auto-updates" just yet, but we probably will. We can snapshot app directories before updates to give you a way to "roll back" if an update breaks something, so auto-updates become less "scary" in that setting. 2) Not entirely sure just yet. Because we are using a Docker container, in theory you could pass it the display device for the purpose of doing this, but I'm 100% theorizing here. I haven't deployed Emby or configured GPU-based transcoding for it. We're still experimenting with Intel ARC GPUs on Plex and haven't even touched iGPU support just yet. All of that being said, home media servers are a primary use case for us, so supporting all that the app can do is something we will strive for.

i actually loved that part of it! basically it gave me the list of what i had to get today to be current! almost like a "here is what to watch for today" in the words of google (when they were defending the DEI AI Art stuff) "Thas not a bug, it is a feature" lol

The essence of bugs is that they are not anticipated, so typically not flagged. This is why logs are needed (which record the main things that are going on in the background, which you wouldn't want to see on the screen, and so may show what went wrong). Paul

In order to use ffmpeg for transcoding, a android 9+ is required. So what you can do is just play videos and will direct play without transocding, like mp4 with h264, aac/mp3.

It seems the problem was a simple lack of RAM. I added a swap file to my machine so that the total memory including swap is 2GB, and Emby seems to stay up, now. The only reason I didn't do this simple thing before was that I misremembered already having tried, but I guess not. So, now we could focus on the actual, functional problem I'm having with Emby:

Hi, yes, I agree with you that some built-in bulk editing features would be great for music for Emby, especially for those fields that are not imported directly from embedded metadata. HOWEVER, I'd recommend using a third-party tagging program (e.g. Picard or Mp3tag or similar) for updating all imported metadata tags such as Albums and Artists and Album Artists. Do you use anything like this? IMPORTANT, also note, if you make changes to your music info within Emby only and then later on rescan your music library, then Emby will likely just re-import your embedded metadata that you haven't updated, and revert back to what you had before, so you may have wasted a lot of time. (AFAIK, making changes within Emby only, updates your Emby database only and does not change the original embedded metadata within your music files.) I'd recommend Mp3tag if you haven't tried it already. The basics are quick to learn and you can easily bulk edit your metadata, including cover art. It's also possible to script sophisticated Auto Actions that, once set up, can save a massive amount of time for making bulk changes to a whole library. Using a dedicated music tagging program will also allow other systems, besides Emby, to make use of your updated changes.

Hi, it should be resolved in the next app update. Thanks.

Woohoo! That is all

Hi, stay tuned for our new app that will be coming. Thanks.

Bulk editing of metadata is something we'd like to add for a future release. thanks !