All Activity

@LukeKinda love that you said this. My wife has been encouraging me to finally drop it for over a year... but the AppleTV app is the final piece of that puzzle. I got premier the day I started exploring Emby as an option as I knew it would eventually become our media server. Other things about the app I can absolutely deal with, as I know you all are working constantly to improve it... and OMG the product has come such a long way since I started 2 years ago, but the user app switching on AppleTV is where we get lost. We have... some... content... that I don't necessarily want my kids to go exploring in. My Living Room TV is shared and I absolutely cannot for the life of me remember to force close the app when I rarely get the chance to use the TV. The other stuff like alpha pickers and lyric support are like to haves, but not deal breakers in my house. Just the user switching. I think you all have done a great job with mpv and the UX of the Apple TV. Every release I cross my fingers for user switching. On a side note... hiding content from the home screen is a nice to have as well

What is this about? It just seem to be a garbage post.

Thank you. Now everything is perfectly clear but I also think our tax code is clear. I just really want the browser alpha picker in photos fix quickly and the ability to favorite/unfavorite from the Roku interface. Again I have NO alphapicker at all when browsing by photos in the browser and, even though the picker works when browsing my photo library by folder, even though I have no subfolders, Emby errors in any attempt to display the last 1/3 or so of my photo library. I just do not understand why it is so hard to fix a very basic function in the browser (alphapicker not showing when browsing photos) and in the Roku (the ability to favorite/unfavorite photos) Other things I have reported do seem like there are complexities but those two seem like they should be very simple to fix. BTW: My photo library is about 2000 items. So it is not even really big. Clearly I can live with Emby even with the bugs but these just seem so simple. Like it takes more time and effort to describe the problem that it seems like it should take to fix. My frustration comes when Emby asks for more and more info but never really seems to attempt the fix. It feels a lot like asking for something triggers a large bunch of delaying tactics with no attempt at really fixing the problem. It is like Emby feels if you delay working on a bug long enough the bug will go away or the person that reported in dies of old age. I know this sounds bitter but, sometimes, when dealing with Emby bugs bitter is exactly how I feel.

Think I fixed it. I literally copy-pasted my OP into Google Gemini and it gave me a list of suggestions and one of them worked. I should have just used AI to begin with and not wasted my time posting here. Anyway, the solution was to run command prompt as administrator, input "ipconfig /flushdns" and restart computer.

Thanks for answer. Ajother weird thing happen. I randomly try some movies and it flicker to black and white and then they play in COLOR , so itry that movie what play in black and white only and it play in COLOR too for some reason. Was there some update ? I am really confused.

Enough, I am unsubscribing from this thread. This was a perfectly good discussion topic until a day ago when someone hijacked this thread for off-topic bullshit. Learn some manners and create a separate thread for your grievances. Cheers!

OK thank you! I had no idea I was on the beta version. I appreciate your help. I wonder why, if a restart is required, it is shutting down but not starting back up?

Honestly I don't know how prevalent it is either and maybe it wouldn't be enough for the Emby team to make enough extra money.

Is the assumption here that the main complaint is coming from resellers? Genuinely asking. I have no context really for how prevalent that is. I've gotten the impression that it has mostly been people who want to provide access to groups of friends and family. I do see some people talking about how they have the 7 (one for each of 6 household members plus one communal) televisions in their household, plus their phone, a tablet, and a Windows device running Emby Theater. For a household with 6 people in it, that would be 25 devices. Give access to another house similarly sized (or two more half size) and that's 50 devices.

The grid uses a cache. The alphapicker uses chunked loading, just as if you scrolled down, only it can load larger chunks at once. Once it has loaded in the cache subsequent jumps can be instant. But once you move back from that grid it causes the cache to get destroyed at the same moment the grid is destroyed. The cache can also get destroyed if the Roku needs memory and garbage collects as you move into things forward from the grid. That is why you see it jumping instantly on the second alphapicker jump since it can use the cache it has already built and doesn't have to load anything. Also the current store app has a bug where the Folders view will attempt to load ALL the titles at once. This will cause a huge wait for that to load before you can even see any titles. But once it loads everything is fast because it has already been cached. But that initial wait can be huge if the user has a large library. That is why we want it to load in chunks to get to where you need to be rather than load everything at once. That is difference between folder view. This has been fixed in the Beta. We want to fix the alphapicker issue and already have a few solutions. But I need to get with @ebrand see if these solutions are really viable or not. We also have other fixes and improvements happening at the same time. It isn't that we are trying to be deceptive. It is the fact that some of these are very hard to pinpoint a cause. The short answer is there likely needs to be something watching the jump to make sure it completes, such as a Watchdog timer. But please give us some time to implement a fix for this. I know it is fun to pick on the fact it is broken. Damn thing. But please give us a few days to get something together. Thanks. tl;dr - That damned alphapicker hang thing will get fixed. There are many open tickets on the Roku tracker. Mind you some of these are my own suggestions turned into issues. But most of these are coming from users complete with forum posts in the issue tracker. I may get in trouble for showing the below image. But I want to show it to give you an idea of what goes on with the Roku tracker. As you can see we have 80 open issues. We have 149 requests to merge code. All of us contribute to making the app better as you can see. I publish most of my suggestions as pull requests. Some of them make it some of them don't. But they are there later to go back with and build something with. That is what you are seeing happen except without having to read the back and forth of the conversations we have and us argue with each other. We cannot really share out issues because it gives away what we are working on and how we are going to do things. But I can hopefully show the image above without getting into trouble. This is honestly what is happening. Please give us a bit of time to work on the issue tracker list. I am always giving these issue/fix numbers as reference in posts. It gets discouraging when people think we are just sweeping everything under the rug and never listening to them. Believe me it is exactly the opposite. Thanks for listening. I just wanted to make everything clear how we operate.

Thanks for the insight. So, this is what I did: I created a separate user since changing Emby's runtime user seems to be challenging. I installed sabnzb, installed Emby, added the Emby user to the new group I created, and then set the ACL permissions. Everything worked fine after that. I also installed radarr, sonarr and other arr stuff. All good now.

Now it's interesting. I stopped the current version of Emby. Then did the manual update. When it completed it started the server and I received the "Forbidden" again. Going to the path: /volume1/@appdata/EmbyServer It's empty. It looks like the update from Package Center 4.7.14.0-724071400 to the most current version hosted on the Emby site emby-server-synology72_4.8.5.0_x86_64.spk wipes out the config. And I think that is what explains the forbidden, htop and the Package Center says its running:

Any help please?

It would be a good feature ! I know I could use directly the standard m3u importer, but for those specific channels, I really need TVH (I pipe them with Streamlink).

Hi, how does the web app compare with those symbols?

Hi there, can you please provide an example?

HI, yes but what's important is the title and/or original title in Emby Server.

Yes this is true, so that would need to be looked at. But you could also import into Emby using m3u and then uninstall the TVH plugin.

It was removed from the server database due to the resource consumption that it was causing. This affects the size of the server database as well as the performance of database operations. That's why it's not integrated anymore, but the information is still accessible via specific functions for it.

Yes, it works for .m3u directly imported in Emby, but this option doesn't exist with the TVHeadend plugin :

HI, I would follow the same convention as iOS, since the two apps share a lot of resources. We just haven't added support for this yet in Apple TV, but we can.

Thanks so I have "Star Wars" in both the folder names and the titles: And not just in the file's name but the "main titles" as well: Any ideas?

I have both the FireTV Lite and also the FireTV 4K version. I noticed that the 4K version doesn't list all the titles that an actor appears in my library the way the Lite version does . Is that capability available in an updated Emby app, or is there a difference between the two Firesticks?