All Activity

yeah, eomby is pretty good looking, but has got some things that makes it unusable on some hardware - login method is too difficult for younger or older users - missing ABC sidebar in Emby for (Apple) TV app - not loading every content every time on apple tv - movie version handle is look really better than Plex, but difficult to choose between the versions, if the user know about it (and if I setting up the versions not grouped together, its harder, because nothing tag/mark/anything show me which is which -on Apple TV, the subtitles are too small, and can't change the size but on the other hand - emby can handle automatically the content sharing if you have only 1-1 library - can play dovi mp4 on apple tv - cloudless (but Plex can be too if I switched of the remote play and can be self hosted too like emby)

I found at least one issue, I try to fix it.

Have stopped using this plugin now

It seems like we have at least 2 points of data showing a truncation of the moviedb id values for robin hood and save the last dance. Was just poking around and noticed another example of this incorrect/truncated id causing a metadata issue. I found "save the last dance" had a similar issue where it drops the last 2 digits of the moviedb id for metadata. this caused a mix up with the poster/image for gladiator but other metadata for save the last dance. The other id values are right. the middle moviedb value should be 9816 and not just 98. Even renaming the file like this and refreshing files did not change anything: "Save the Last Dance (2001) [tmdbid-9816].mp4" I see why the incorrect moviedb 98 value is bringing back the artwork for the movie record in general - as this is the highest priority image pull per my library settings (i think these were defaults). other metadata looks correct (actors, etc.) due to tvdb being the highest priority for actual metadata: So that at least explains why i can have most of the metadata right but have the wrong art. I wonder if i should just drop themoviedb altogether for art and metadata?

Made a post here that was supposed to be on another forum thread - whoops!

Emby server windows version 4.8.5.0 If I schedule to record programs A and B, consecutively on the same channel, then two recordings are created. The first recording is called A and contains program A. The second recording is called B and contains program A followed by program B. To watch program B I have to skip through all of program A. There is no problem if the consecutive recordings are on different channels. This behaviour started occurring a few months ago.

I have the same issue, deleting and reinstalling the app didn't fix it. I thought emby was supposed to transcode video's?

Often I watch a recorded TV program while it is still recording, maybe time shifted by 30 minutes or so. When I attempt to stop watching the program the Emby client hangs and is unresponsive. The remedy is to "force stop" the app, or to reboot the TV. When I stop watching the TV program Emby has finished recording. I typically record 10 minutes after the scheduled program end, so when I stop watching I have not reached the end of the recording. Emby server is uneffected. I can re-watch the recording without issue.

I think this was when I was originally working with The Book of Eli (2009). I recall playing with metadata on this one after having the image for it being something silly (not a movie poster/cover). Since then I had removed and re-added this movie and metadata, so I'm not sure the issue is happening or could happen in the same way now. After poking around some more, I see there's actually a sort title in metadata for each movie which handles the book of eli case perfectly ("the" is scrubbed from the beginning). Thus, The Book of Eli shows up next to other titles in emby like Brave, Bloodshot, and The Boondock Saints - just like you'd expect with skipping articles. So I think this case is a misnomer or was related to some other metadata artifact issue I was working to solve earlier. This doesn't solve my file naming convention at this point (since I have a ton of movie files that start with "The "). But that's not a huge deal since I can find them on emby in a snap.

So...there's definitely something up here. I have not seen this kind of behavior before and I've worked with hundreds of movies on emby. Specifically, working with: https://www.themoviedb.org/movie/8367-robin-hood-prince-of-thieves https://thetvdb.com/movies/robin-hood-prince-of-thieves https://www.imdb.com/title/tt0102798/ Title (Year) >> Robin Hood - Prince of Thieves (1991) This is a multi-part movie (but I had this problem even working with one mp4 file - i.e. half the movie). This shows the default external IDs. the "83" in the middle there is wrong (where open water comes up per earlier posts). I manually replace it with this - the correct IDs for all 3 (only had to edit moviedb one). I refresh metadata for it like this And it doesn't change anything and reverts the moviedb value back to 83. So I try the file-based id tattoo approach like this - again i have a multi-part movie (2 sides of the dvd to get the whole thing): Doing a file refresh on the library then changes something else....that's pretty cute, huh? So the problem then becomes a mis-ID of the tvdb value like shown (now that the file name fixes up 8367). 66490 is some tale of two kitties, sure enough. Interesting point also is the imdb id changed - which also points to two kitties. I think this is the first one I just can't get a handle on and when I fix one ID issue it seems to move elsewhere. I'm not quite sure if this is due to the multi-part/stacking, but I believe I'm following the correct way to do this with a folder for the movie parts and proper naming. I'm wondering if I even need that tmdb id value on the folder or just the files in the folder (that is not clear). I put it "everywhere" since I was having issues with parts of the metadata for this flick. Even if I update the identifiers (tried even removing and redoing those manually) in the emby system, any metadata refresh seems to wipe them out enough to cause a metadata issue. Any thoughts welcome. If it matters, I'm using version 4.8.3.0.

It might be trying to fall back to the HDR 10 layer, with limited success. You're still better off to use quietvoid's tools to fix these so they are compatible with your hardware.

It's been about a month or so now. Any updates or etc?

I fight with Emby developers often. I never fought with Plex developers, they just either did nothing or banned me for mentioning Emby. It was very frustrating to deal with Plex on any level. But dealing with Emby is at least a continued give and take. They may take offense at some of the things I say but I also take offense at some of the things they say. It is a robust give and take and, with Plex, it was all giving on my side and taking or theirs. Emby is mostly fun but Plex was almost never fun.

this exact thing just happened to me, here are logs from library scan: 2024-05-02 21:23:22.216 Error SqliteItemRepository: Error saving items *** Error Report *** Version: 4.8.5.0 Command line: C:\Users\Administrator\AppData\Roaming\Emby-Server\system\EmbyServer.dll -service Operating system: Microsoft Windows 10.0.17763 Framework: .NET 6.0.29 OS/Process: x64/x64 Runtime: C:/Users/Administrator/AppData/Roaming/Emby-Server/system/System.Private.CoreLib.dll Processor count: 8 Data path: C:\Users\Administrator\AppData\Roaming\Emby-Server Application path: C:\Users\Administrator\AppData\Roaming\Emby-Server\system SQLitePCL.pretty.SQLiteException: Constraint: FOREIGN KEY constraint failed SQLitePCL.pretty.SQLiteException: Exception of type 'SQLitePCL.pretty.SQLiteException' was thrown. at SQLitePCL.pretty.SQLiteException.CheckOk(sqlite3 db, Int32 rc) at SQLitePCL.pretty.StatementImpl.MoveNext() at SQLitePCL.pretty.DatabaseConnection.Execute(IDatabaseConnection This, String sql) at Emby.Server.Implementations.Data.SqliteItemRepository.SaveItemsInTranscation(IDatabaseConnection db, List`1 tuples, MetadataRefreshOptions metadataRefreshOptions) at Emby.Server.Implementations.Data.SqliteItemRepository.SaveItems(List`1 items, MetadataRefreshOptions metadataRefreshOptions, Action`1 afterSave, Boolean disableForeignKeys, CancellationToken cancellationToken) Source: SQLitePCL.pretty TargetSite: Void CheckOk(SQLitePCLEx.sqlite3, Int32) 2024-05-02 21:23:22.217 Error ProviderManager: Error validating children for Movies 13870 \\omega.wangfei.com\ZEUS\Media\Movies *** Error Report *** Version: 4.8.5.0 Command line: C:\Users\Administrator\AppData\Roaming\Emby-Server\system\EmbyServer.dll -service Operating system: Microsoft Windows 10.0.17763 Framework: .NET 6.0.29 OS/Process: x64/x64 Runtime: C:/Users/Administrator/AppData/Roaming/Emby-Server/system/System.Private.CoreLib.dll Processor count: 8 Data path: C:\Users\Administrator\AppData\Roaming\Emby-Server Application path: C:\Users\Administrator\AppData\Roaming\Emby-Server\system SQLitePCL.pretty.SQLiteException: Constraint: FOREIGN KEY constraint failed SQLitePCL.pretty.SQLiteException: Exception of type 'SQLitePCL.pretty.SQLiteException' was thrown. at SQLitePCL.pretty.SQLiteException.CheckOk(sqlite3 db, Int32 rc) at SQLitePCL.pretty.StatementImpl.MoveNext() at SQLitePCL.pretty.DatabaseConnection.Execute(IDatabaseConnection This, String sql) at Emby.Server.Implementations.Data.SqliteItemRepository.SaveItemsInTranscation(IDatabaseConnection db, List`1 tuples, MetadataRefreshOptions metadataRefreshOptions) at Emby.Server.Implementations.Data.SqliteItemRepository.SaveItems(List`1 items, MetadataRefreshOptions metadataRefreshOptions, Action`1 afterSave, Boolean disableForeignKeys, CancellationToken cancellationToken) at Emby.Server.Implementations.Data.SqliteItemRepository.SaveItems(List`1 items, MetadataRefreshOptions metadataRefreshOptions, CancellationToken cancellationToken) at Emby.Server.Implementations.Library.LibraryManager.CreateItems(List`1 items, BaseItem parent, MetadataRefreshOptions metadataRefreshOptions, BaseItem[] collectionFolders, Boolean triggerItemAdded, CancellationToken cancellationToken) at MediaBrowser.Controller.Entities.BaseItem.ValidateChildrenInternal(IProgress`1 progress, CancellationToken cancellationToken, Boolean recursive, Boolean refreshChildMetadata, BaseItem[] collectionFolders, LibraryOptions libraryOptions, Dictionary`2 newItemIds, MetadataRefreshOptions refreshOptions, IDirectoryService directoryService) at Emby.Providers.Manager.ProviderManager.RefreshCollectionFolderChildren(MetadataRefreshOptions options, CollectionFolder collectionFolder, CancellationToken cancellationToken) Source: SQLitePCL.pretty TargetSite: Void CheckOk(SQLitePCLEx.sqlite3, Int32) i created a new library and accidentally made the path the parent folder of the entire media library. ALL items in ALL libraries disappeared. deleting the offending library did not help. had to delete and re create all libraries, PITA.

For the one who started this thread...I thank you. As a tech; I deal with computer issues ALL DAY and having the end user tell me exactaly what is going can be a difficult one. Coming from the PLEX world. I see what works and what does not. Certain things that people consider a useless feature some use it all the time. From day one when I installed Emby and for a purposes it does what I want it to do. Even using the Symfonium has been a great expereince for me. I like emby becuase; unlike Plex, I can customize it..Just like the Onn 4K streaming from Walmart; I would rather use that than Roku becuase it can be customized and the product just works for ALL my purposes. However, since ALL my family and friends use Roku. The one issue for the alphapicker is a MAJOR issue for me. BUT..Luke, Speechless and Ebr all of them has been "right on it' they have helped so much and THEY need a high five from me...Unlike plex forums that could takes to get a response back. Still EMBY for the WIN!!

@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

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.