Leaderboard

Update was pushed, 4.9.3.28. Looks like the scrolling issue is fixed. Thanks @Luke

Du findest die aktuellste Beta Version immer auf Git Hub. https://github.com/MediaBrowser/Emby.Releases/releases Dort einfach die richtige Version runterladen, Emby runterfahren und dann drüber installieren.

I agree, i was about to make a post about this but i kept scrolling to see what other said, then i found this post, i would also want to add to be able to change the color, and support Arabic text also.

I find it highly ironic and amusing how half the Emby population are rampaging to the devs about how IPTV is broken and not fit for purpose… (it might be for all I know ) Then we have the other half happily re-selling their servers to the world who come here asking for help! As for Emby and advertising. I feel like it’s a battle we don’t even know what it is we are fighting for. I feel everyone who has and values their own content and wants to centrally manage it and deliver it to lots of different clients/machines locally and remote - well they will have already come across Emby. The number of people who have ripped dvds and blurays is decreasing year on year now, that bubble has kinda burst I feel, for the mainstream anyway. I’m sure there are kids who want to feel they are retro and are treating dvds like vinyl… Jellyfin - anyone going there is because of some feature that is missing here, there’s probably a good reason why Emby doesn’t have it so that will never change. Plex - they have the out of the box ‘free’ content to get people started. As well as the 3rd party integrations. That’s the draw I feel, it leads to extravagant flashy claims and screenshots. When someone looks at Emby and downloads it and they realise it’s an empty shell, that they have to fill it with content themselves - well you’ve lost them as they don’t understand the point of it. Do we as Emby want to go down that route? The first thing most of us would do is turn that crap off/disable it. The rest will feel Emby isn’t for them anymore. On the upside it would demolish plex. Honestly, I don’t know how the devs cope with competing directions they are being pulled in day-in day-out. They do an amazing job.

Screenshot looks great, and very promising, with the new functions!!! I'll test it out as soon as I can. Will likely be tomorrow, your time, before I can give any detailed testing feedback... stay tuned...

That's OK, I just wanted to know exact library setup within Emby for which endpoints to use. All clear now, I should have an update within the hour.

No. My music library is just: \\DS218PLUS\music. In the PM the example paths are direct copy+paste from Windows and Emby. I used this code and it seems to be working - but I don't know if this is the best approach or not??? def fetch_libraries() -> list[dict]: # get top-level virtual folders data = requests.get( f"{SERVER}/emby/Library/VirtualFolders", headers=HEADERS, timeout=15 ).json() # find the main music library music_lib = next((x for x in data if x.get("CollectionType") == "music"), None) if not music_lib: return [] # fetch one level down inside that library subfolders = requests.get( f"{SERVER}/emby/Items", params={"ParentId": music_lib["ItemId"], "IncludeItemTypes": "Folder"}, headers=HEADERS, timeout=15 ).json().get("Items", []) # return: first the main library, then its subfolders return [music_lib] + subfolders

Dev would have to comment further on why there are issues with avi transcoding. I personally saw issues with avi (XVID) files a long time ago and just converted all of them to h264 mp4 so they would direct play instead of transcoding.

Thanks for the update. Hope it goes well.

That should be mostly fixed in the next version with a lot of other bugs i found. It's going to be a HUGE update, tons of core logic changes, user theme agnostic, etc... I'm getting there but still lots of work to do still. Thanks!

The more I thought of it, the problem is the browser will not play the audio bluetooth from the NAS server. It plays it through the PC through the bluetooth connection to the bluetooth speaker. I did find an odd duck work around. RDP to another Windows box, bring up Emby in that browser and play the bluetooth connection through that PC. Then my working PC is free to output audio to my PC speakers.

We’d have to add options.

i solvented. The problem was the Adguard.

Thanks, I could have sworn you said something about having two apps. I'll make sure to pass on the correct reason next time. Probably tomorrow considering how often it's asked

Perfect, friend! I had Emby installed on Windows 11 for the first few months until I got a Raspberry Pi. Try going to the gear icon --> Server --> Settings --> Automatic Updates. I think you can disable it there.

No. They are created automatically when images are cached.

Heya all! Try the latest release from the website. Should be 1.9.4.0 https://ballingtons.com/products/

You can also try that IPTV app on an Android emulator, and then intercept those requests using a tool like Fiddler, so you'll know what kind of request headers your IPTV streams accept. Once you do that, you can tweak the streams you added through Dispatcharr accordingly. Good luck!

Hi, the main reason we don't do this is that people move from one device from the next and then don't realize what they're looking at when the sort and filter options from another device are applied. At least that's the reaction we got to it in the past.

Wops, i will fix that. I don't feel comfortable with messing with the Emby user and passwords (if even possible) but i can look into making the password system better. I just never really felt it was needed as it was just watch parties. All i can think of for now is separate passwords for creating and deleting though. Both and be equally destructive.

@yockerMovie search is working excellent now mate, I have come across a bug when making a watchparty from admin though, when I click create party, I get this... The default 15 does not seem to work, even if I type it in again. If I put in 1 it worked (I didn't try any others but 15 definitely didn't work for some reason) Can I suggest some improvements on user security, if possible, that is. At the moment I have to give the same admin password to everyone so they can create watch parties, that same password is used to delete them so someone could go rogue and delete everyone's watch parties and plenty of us have that one family member or friend that will bloody do that I would suggest using emby login credentials to create a watch party and deleting a watch party can only be done on the party page by the creator or admin via the admin panel.

Good news mate that one seems to be working I have a busy morning with work but I will run some more tests as soon as I catch up and report back.

Happy to test mate, sitting here working from home so can test in between jobs haha

Ahh, i forgot about the limit i added to not bog down the plugin. I will try and fix it but i need you as test subject as i don't have that many movies in my library to test with.

@yockerhave now tested a watch party and all seems to be good apart from one thing. The search to select a movie or tv show does not seem to be working, only way to find a movie is via the drop down and that does not work well at all when you have 12,000 movies lol

This might work with single user, though i'm not sure. You can also set something up rather easily with Home Assistant and Emby integration. Like a play button that sends a play command to all open Emby instances.

That's part of why I made it easy to mark shows unwatched from Aperture so I can undo their wreckage... and my wife is not innocent in any of this either!!!

Shows You Watch: Your Personal DVR-Style Home Row (Finally, No More Noise!) Let me explain a feature that's a possible game-changer for multi-user households: Shows You Watch. The Problem If you're like me, you've got multiple users on your system—family members, roommates, whoever—and they all request content. That's great! But here's what happens: Latest Shows becomes a complete mess. My wife is watching three different reality shows. My kids are into anime. My buddy who I gave access to is binging some crime documentary series. And me? I'm just trying to keep up with the two or three shows I actually care about. The result? The shows I'm actively following get buried under a mountain of content I'll never watch. I'm scrolling through 30+ items just to find the one show I want to continue. It's exhausting. The Solution: Shows You Watch Think of Shows You Watch as a pseudo-DVR home row — but smarter. Here's the concept: You mark the shows YOU actually care about in Aperture, and Aperture creates a custom library that displays ONLY those items. No noise. No clutter. Just your shows. What You Get: A dedicated "Shows You Watch" section on your home screen with only the series you're following Next episode tracking in Aperture — see exactly what's coming up and when Progress indicators In Aperture — know where you left off at a glance "Days until" countdowns In Aperture — "Tomorrow", "In 3 days", etc. Behind count — if you're 5 episodes behind, you'll know How It Works: The system tracks what you've been watching recently Only continuing (not ended) series qualify Your personal "Shows You Watch" library gets created automatically This library appears in both Aperture AND your media server (Emby) The best part? It's per-user. My wife has her Shows You Watch, I have mine. We're not stepping on each other's toes. The Virtual Library Bonus Here's where it gets really nice: Shows You Watch creates an actual library in your media server called something like "Shows You Watch - YourName". So even when you're browsing directly in Emby (not through Aperture), you've got quick one-click access to continue your shows. It shows up right on your home screen. No more hunting. If you're running a multi-user setup and haven't explored this feature yet, give it a shot. It's the difference between your media server feeling like a chaotic shared Netflix account vs. your own personalized DVR.

I would consult with @TeamB I believe he attempted that very thing with PlaybackReporting and found it not worth it.

For top picks, why re-invent the wheel when you can also utilize trakt endpoints like api.trakt.tv/shows/trending and api.trakt.tv/movies/trending? I believe those are based on like_count, list_count and comment_count and are updated quite often What other enhancements are you thinking?

I am thinking about opt-in for a share your emby watch history with other Aperture users as a way to get more top pick variation and potentially other community level enhancement. All anonymized of course

I should have built this as a multi-tenant platform on AWS and sold inexpensive monthly subscriptions!

This is maybe coming with the Smart Playlist feature? We can only speculate because it hasn't been communicated.

IMO this is an excellent opportunity for Emby devs to demonstrate that they are 3rd party Dev friendly. We all know this won't be an issue on Jellyfin and it will be yet another reason to switch over to Jellyfin.

My Wild Idea For Preventing Duplicate "Continue Watching" Entries Hey everyone, I want to get your feedback on a proposed solution to a common annoyance before I build it. The Problem When you watch a movie or show from an Aperture recommendation library, you might see duplicate entries in "Continue Watching" - one for the original item in your library, and one for the Aperture copy. Why this happens This happens because Emby links items together by their IMDB/TMDB IDs. When both the original and the Aperture STRM file share the same IDs, the media server treats them as related and syncs playback state between them. The ideal fix would be for Emby to add a "Hide from Continue Watching" option per-library, so we could exclude Aperture libraries from that home row entirely. But until the devs add that feature, we need a workaround. The Proposed Workaround (It's Workarounds All The Way Down) Part 1: Fix the duplicates with prefixed IDs Instead of using real provider IDs: IMDB: tt1234567 TMDB: 12345 Aperture would write "prefixed" IDs in NFO files: IMDB: aperture-tt1234567 TMDB: aperture-12345 Why this fixes duplicates: Emby sees aperture-tt1234567 and won't link it to the original tt1234567 No more duplicate Continue Watching entries But this creates a NEW problem: Now when you watch something from an Aperture library, the watch history doesn't track back to the original. The original item in your real library won't show as "watched" because Emby can't match the prefixed ID to anything. Part 2: Fix the watch history problem with attribution sync So we need a workaround for the workaround. During the watch history sync job, Aperture would: Detect items with aperture- prefixed IDs that were played Strip the prefix to get the real IMDB/TMDB ID Find the original item in your library by that ID Mark the original as watched in Emby via API Record the watch history in Aperture's database This way, your original library stays accurate - items you watch via Aperture recommendations still show as "watched" in your real Movies/TV library. It just happens on a delay (every 30 minutes) rather than instantly. Alternative: Webhooks (real-time, but more setup) I could make the watch history attribution happen in real-time using Emby webhooks. When playback ends, the media server would immediately notify Aperture, which could then mark the original as watched right away. But this would require server admins to: Install the webhooks plugin (Emby) Set up the webhook URL pointing to Aperture Configure which events to send That's a lot of extra work and configuration for users, and more stuff I do not want to provide support for, so I'm leaning toward the polling approach (30-minute sync) that works out of the box with zero additional setup. Trade-offs ~30 minute delay before originals get marked as watched (sync runs every 30 min, you can adjust to your liking but this is what I would make my default) Requires Aperture library resync to Emby after enabling/disabling It's a workaround for a workaround - not elegant, but functional Would be an opt-in toggle in Admin Settings (disabled by default, labeled as "Experimental") Questions for You Is duplicate Continue Watching actually bothering you? Or is this a non-issue for most people? Would you enable this feature? Even knowing it's a stack of workarounds with trade-offs? Any concerns or edge cases I'm not thinking of? Better ideas? If you know of a cleaner approach, I'm all ears. Looking forward to your thoughts. If there's enough interest and no major red flags, I'll build it as an optional feature in an upcoming release.

although I am fine with using OpenAI or Ollama for fully local deployment, but since you made the effort to add more providers, consider the idea of adding openrouter.ai provider with their vast model support -some on free tier! Just an idea!

Aperture 0.4.2 Beta: Multi-LLM Support is Here! Hey everyone! I'm excited to share a beta release of Aperture 0.4.2 featuring multi-provider AI/LLM support. This has been one of the most requested features, and it's finally ready for testing! What's New? Multi-Provider AI Support You're no longer locked into OpenAI! Aperture now supports: OpenAI (recommended - GPT-4o, GPT-4o-mini, text-embedding-3-large, etc.) Anthropic (Claude 3.5 Sonnet, Claude 3 Haiku, etc.) Google (Gemini 1.5 Pro, Gemini 1.5 Flash) Groq (Llama 3, Mixtral - blazing fast inference) Ollama (run models locally - llama3, mistral, nomic-embed-text) LM Studio (local models with OpenAI-compatible API) Any OpenAI-compatible endpoint Per-Function Configuration The real power here is per-function provider selection. You can now mix and match: Function Use Case Example Setup Embeddings Semantic search, recommendations OpenAI text-embedding-3-large Chat AI Assistant with tool calling Anthropic Claude 3.5 Sonnet Text Generation Explanations, synopses Groq Llama 3 70B (fast & cheap) Want embeddings from OpenAI but chat from Anthropic? Go for it! Dynamic Cost Estimation The new AI / LLM Setup tab includes a cost estimator that: Pulls real-time pricing from providers Estimates costs based on your library size Factors in your content growth rate Shows $0.00 for self-hosted options (Ollama, LM Studio) Other Improvements Setup Wizard Overhaul - Now includes multi-provider configuration Admins can re-run setup - Click "Re-run Setup Wizard" anytime to reconfigure Capability Detection - Warns you if a provider doesn't support features like tool calling Automatic Migration - Existing OpenAI configs are automatically migrated How to Test Pull the beta image: docker pull ghcr.io/dgruhin-hrizn/aperture:llm Or update your docker-compose: services: aperture: image: ghcr.io/dgruhin-hrizn/aperture:llm # ... rest of config Important: This will run a database migration that updates your embedding model names. If you've been using OpenAI embeddings, they'll be migrated to the new format automatically. THIS COULD TAKE A FEW MINUTES, BE PATIENT. Aperture logs will show you progress. Known Issues / Feedback Wanted This is a beta, so please report any issues you find! Particularly interested in: Local LLM users - How's Ollama/LM Studio working for you? Non-OpenAI embeddings - Any quality differences you notice? Cost estimates - Are they accurate for your setup? UI/UX - Is the new AI Setup tab intuitive? Screenshots What's Next? Who knows? Ideas come to me daily, and your feedback is the roadmap. Thanks for testing! Drop your feedback below. Docker Image: ghcr.io/dgruhin-hrizn/aperture:llm Branch: feat-vercel-ai-sdk-multi-llm

I have had the request to support it, I am building a branch using the Vercel AI-SDK now which supports many providers, OLLAMA being included so you can BYOAI. It will be deployed to a different testing tagged and I will have more information when I need testers as I have no local LLMs setup here.

Having some form of Nested Collections would be great! I'd be quite happy with just two levels (e.g. Master Collection and Sub Collection). This would probably be enough to do 95% of the collection groupings I would like. I could then reduce 600+ current collections to about a dozen master ones and ideally see the sub collections within these. Showing/hiding the sub collections in certain views would also be great, but if this is a large technical hurdle to overcome, then at least having the nesting ability in some form or another would probably be better than nothing at all (e.g. show master collections, followed by sub collections). Play/shuffle from the sub collections, and not the master collections, would also be fine for me (though I get that this may not work for everyone). Would only 2 nested levels make the technical implementation any easier? How many levels does everyone who wants nested collections practically need? How many levels would suffice for the majority, as opposed to waiting a lifetime? Once the new smart features (views/collections/playlists/whatever) are available then I think my collections/playlists will increase greatly, so perhaps Nested Collections (in whatever guise Emby can easily implement) will be a good next step...

Haven't revisited this in some time, related discussion in another topic made me remember. Any movement on this, @Luke? If this: is the only concern, I reckon there's an easy compromise that I'm sure (mostly) everyone would agree on: make the ability to play/shuffle available only in the lowest/deepest collection, i.e. if no sub-collection - retain current behavior; if sub-collection present - hide play/shuffle on parent collection; ditto for sub-collection within sub-collection, however many layers you want to implement. There's no need to add/consider additional logic or necessity for further complexity, the only criteria should be: nested collection present yes/no? Play/shuffle available no/yes. And ultimately only collection containing items would be playable, just as it currently is. My 2c

All plugins - Scroller fixed, TV theme songs - down source removed Onto into ytrailers next

Looks like you are getting your wish. How to do this "right" is often the opinion of the user, and often differs by user. I'd rather have the option that I have to tweak, than no option at all, which is what I have now.

This I do agree on.

Agree to disagree. I don't wont devs to half measures this and say well that's "good enough" and then forget about it/move on. This should have been fixed YEARS ago. The fact that it isn't is incredibly sad.

I guess if you are happy to wait a lifetime for features then sure - those of us who used nested collections before were perfectly happy with the compromise. Maybe add back as API created only (as it was previously), that way - only the more advanced users can use it and they are aware of it's limitations.

Personally, never had an issue with this - as you just name the sub-collection (or the sort-order) with a prefix that puts it 'last' in a normal sorted order. When you open the main collection - you only see the sub-collections anyway - so that works just fine. Not hiding the sub-collections is not a good enough reason to disable this functionality imo. Hide would be nice, but not essential.

No good mate, I selected the movies library, then typed in 'Predator' and nothing came up at all and the 'select content' drop down was still at the very start of the library.

Completely disagree. Either do it right or don't do it at all. Doing something halfway will only cause more issues down the road for the devs