Leaderboard

Sure! Like I said before in this conversation - I love the idea of multi-node Emby-Server architectures and had thought out plans for this more than once over the years. But you can't always just do what you'd love to do. So let me set this straight once again: If somebody would come along, asking for such kinds of features and willing to pay for the development, then we could implement and deliver these features of course for that customer. It's surely doable - it just requires a substantial amount of work. Our actual users on the other side - are paying for a "Personal Media Server" and have no need for professional/enterprise features of that kind. It is neither fair nor acceptable to let them pay for the development of features which are far outside their patterns of use and of interest for less than one permille (0.1%) of users at best. From a business perspective, it can be expressed in a simple way: Either you have "thousands" paying a few dollars each - or you have a one or a few who are paying thousands of dollars each. Either case, you owe to those who are driving your business, and in this case, it's pretty clear who that is and so we are trying to serve them as best as we can by focusing on features with the highest demands and the greatest benefits for the majority of our users.

Just to answer the question: It's months of continuous work, preceded by a couple of weeks alone for prototyping, testing out options and working out a solid concept. Again - for the short-attention-span readers: this is not about a simple data layer change - it would require fundamental changes at varrious core elements of Emby Server, even down to client apps and APIs in various aspects to get equal results like now with SQLite. And like @ebrsaid: it cannot go in a way that we'd stop working on things for the Emby user base - which is and has been driving Emby for so many years already.

Not sure what you are asking here. Dev has already commented that they are working on it. Please exercise some patience and wait for an update, thanks.

Recently Aired Episode Refresh - Plugins - Emby Community

Would the Episode Refresh plugin work for this? It's not specific to TBA but you can adjust the schedule and number of days to look back (episode age).

Hi, Out of curiosity, I tried to replicate this to see what is going on. As best as I can determine, the Album Artist field/tag is not a major factor in what Song info is displayed, but the Artist field/tag is. As per what Luke said. Here's my example... When a Song has Title, Artist and Album, then all three are displayed, in that order, on the Full Screen Now Playing, but only Title and Artist are displayed on the Minimized Bar Now Playing (with Album being dropped). LHS images below: When a Song has Title and Album only, then both are displayed in that order on the Full Screen, but they are reversed on the Minimized Bar (I have no idea why). RHS images below: I think these results are the same situation as your examples? To further complicate things - different results may occur(???) when some Songs on an Album have the Artist, but others don't. And I also had to delete Albums from the library, rescan, put them back and rescan again to fully clear the database and try again to get the results above. The reversing of the Song and Album (as per RHS example) seems weird, but perhaps the best approach is just make sure all Songs have Artists assigned, otherwise inconsistences across the two Now Playing screens and across your library will be annoying. Hopefully this makes sense and is correct? Perhaps Luke can explain further?

That's just a worker-pool but not a micro service architecture. Most important for Emby is live-transcoding, and a single such transcoding job cannot be scaled by employing multiple nodes. Well - that's one of the points I tried to explain earlier: With an in-process db like SQLite, you need no caching because re-retrieving the data from the in-process database is (overall) much cheaper than using a caching server. (also, it's Redis, not Reddis) "Just don't have", "someone just needs", "you could write",... That's a lot of hot steam, mixed up with a few buzz-words, but essentially pointless in total.

Hi, I would like to have an option to choose H265 instead of H264 in the Transcode option. It will be smaller for all bad bandwidth (2~5Mbit ADSL), but will have a great quality. Mobile phone can benefit of it greatly too with the 4G and the limitation of download.

Another request for the same thing recently released movies is good but it basically hides new release movies because the theatrical release date was 2-3months ago and many digital only releases came out prior and take up the space.

Hi, hopefully it goes without saying that for TrueNAS I would only consider Scale.

Issue was resolved, in part, with newer patches of Emby.

Thanks for the reply. Can you at least get the website updated so other people don't waste their time trying to install emby on Linux while waiting for the new version?

Samsung 2019. Yup, all works now. Tweaked the area you said, and it sprung to life, thanks!

I submitted a crash report to Apple today after Emby crashed and the iPad restarted.

Grazie 1000!!! ci sono arrivato alla fine... ma grazie cmq

This hits the point exactly. At a (much) earlier stage this would have been easier to go for, but by now, the debt is so high, that it's very hard to even identify all the cases for which tests would need to be coded, to make sure that the behavior of every little nit remains identical (a parallel mode would probably be required which executes all db operations here and there and validates that results are identical). Another problem is that many API endpoints (by which client apps are interfacing) are using InternalItemsQuery, and this allows queries for anytrhing about anytrhing with anytrhing filtered by anytrhing or anytrhing else or anytrhing else witrh anytrhing or without anything, inluding anytrhing grouped by anything, sorted by anytrhing, etc. etc. While this provides great value and flexibility to clients, it is a nightmare for the server-side, because you can optimize queries, retrieval, caching and other processing only for something specifc but not for everything at the same time. It also allows to specifcy only certain fields to retrieve, which is nice, but it doesn't go together with caching for example - each cached entity needs to have all fields, so you need to decide what to do in which cases...etc. (just a tiny bite for the taste)

It really comes down to how much someone is willing to invest. If you can bill external resources with margin to handle the heavy lifting, then in theory almost anything is possible. In practice, I doubt many would actually pay for it as we're looking at 7 figures. What often gets overlooked is the overhead that comes with expanding core features. An architectural change like this essentially doubles everything: bugs, testing, release cycles and so on. Without a clear enterprise licence that companies are willing to pay for at a substantially higher rate than a personal licence, I do not think it is feasible. Personally, I would love to see this feature, but I doubt it would deliver the value people expect in a non-corporate setup.

Hi. Its really not in the picture because we cannot afford to pull our resources away from the mainline development even if someone were to pay for it.

failover with a hypervisor. hyper-v, kvm/qemu/proxmox, esxi, etc. you could just mirror a vm across multiple nodes and in case one node fails, the vm will still be available on the other node (a few seconds later, depends on your setup). no corruption, nothing. you dont want load balancing, you want high availablity, thats something completely different. you could offload your storage to a central... storage so that it does not have to be migrated (in case you dont want HA storage) easy

I installed Emby Server in a jail on TrueNas Core. But that is EOL so I can't update Freebsd anymore, it's now on 13.3. So I ended up installing the beta like @Lukesaid and that worked!! At least it works for now until I have a new server:-)

@Dariusthe explanation is here And here is the long version.

I checked and you were right, thank you. Issue resolved.

Yes sorry, the problem still exist. And i can add : i just updated on IOS 26 beta 7, emby still crashing my iphone

and also remove the additional 's'

Scratch that. Its almost 11pm E here. I dont think I will be able to get someone's credentials tonight to run a debug on my PC. I'll have to wait for them to share that info with me in the morning. I'll post the debug as soon as I get it.

Thanks, that's super helpful. I thought I had a good idea of what I've got installed and doing stuff on my server but this never occurred to me. I do have it installed, and it does get used - some anime get released and only have a Japanese description, and then at some point it changes to english. I now realise that is after this job ran at 3am by default. I've changed the frequency to a closer interval like in my original post and hopefully that does the job. Thanks all!

This is what I experienced too. Scrolling through chapters or actors doesnt register as interacting so it closes the menu after a timeout. But regardless if it did register it as interacting, the info menu shouldn't disappear until the user chooses to back out of it once they're done reading

Just buy yourself a small nuc with intel cpu.. Then bind your current NFS share into this new nuc. And then you can transcode your files.. This is how I solved my problems.. My current NAS does not support hardware trascoding.. so i have done it like this.. Lets assume the IP of the nas is 192.168.1.5 I have edited Fstab via ssh: nano /etc/fstab There I have entered the shares from my old nas like this: 192.168.1.5:/export/MEDIA1 /mnt/media1 nfs defaults 0 0 You have to create the shares before: sudo mkdir -p /mnt/media1 This way you make sure the files will be visible from your emby nuc..

I've had the Chapters OSD time out on me on my phone while I was scrolling through them. I assume it only registers contact with the screen as an interaction, so when I flicked across the screen to quickly scroll towards the end of the chapter list, it believed I'd stopped interacting even though the list was still scrolling.

Hi. Make sure nothing is blocking that device from reaching our server specifically (mb3admin.com).

Hi, yes hopefully soon pending Synology review. Thanks.

In this installment of our Emby Community Spotlight series, we're highlighting three new users with completely different builds. One leverages serious archival storage and years of media curation; another keeps things lean and affordable; and a third takes a no-nonsense approach with hand-me-down hardware. Each setup proves that no matter your budget or complexity, Emby can be tailored to fit your needs! User 1: 3.3 Million Entries, 400TB of Storage, and a Custom-Tuned Library OS: Windows Server 2025 CPU: Intel i7-7700 RAM: 48GB GPU: NVIDIA GTX 1660 (transcoding) Storage: 64GB NVMe (OS) 500GB NVMe (cache & image storage) 50TB local RAID (primary library) Four Synology NAS units (~400TB raw capacity) Transcode Cache: SATA SSDs in RAID 0 Media: Films by decade TV series split into "Running" and "Archived" libraries Separate volumes for music, audiobooks, ebooks, photos, YouTube downloads Comic book library (50TB) stored on a separate Emby instance Clients: Nvidia Shield TV Nokia Box 8000 Apple TV 4 Multiple Smart TVs (LG & Samsung) Android beamers iPhones, iPads, Android phones & tablets across multiple countries User 2: A Low-Cost, Low-Fuss Setup That Gets the Job Done Server: OrangePi 5+ 256GB eMMC 8-core CPU 16GB RAM Storage: Synology DS224+ with 2x8TB WD Red Other Infrastructure: System76 Meerkat (handles web/misc services) Ubiquiti UCG Ultra router External backup drive Clients: Android phones (various Pixel models) Android tablet Roku Chromecast Web browsers User 3: Old PC, New Life OS: (Windows 11 Pro) CPU: Intel i5-9400 (Quick Sync for transcoding) RAM: 32GB DDR4 Storage: 10TB Toshiba N300 4TB WD Red (2019) 3TB WD Red (2016, pending replacement) 1TB WD770 NVMe 1TB Kingston NVMe (used for cache and transcoding) Clients: TCL 4K Android TV LG 4K webOS Android phones and tablets Roku Xbox Series X Want to Share Your Emby Setup? From server racks to single-board computers, the Emby community is full of creative solutions. If you’re running Emby on something interesting, or even something ordinary, and want to be featured in a future spotlight, join the Emby Community Forums and share your setup. You might see your system in Volume 5! View the full article

You have summarized this entire thread with those few words.

this sounds cool, do you have any project names?

.com is the current version - you should not be using .org any more. Check that you have set up the login in Emby for .com using your username (not email address as I first wrote here) - the wrong name will fail silently. Paul