Leaderboard

I am having a heck of a time with taskButton library. I think I have to temporarily disable the button on the plugin in page, and you'll have to run it from the scheduled task page. At least until I can figure out how taskButton is working now. I can see that auto organize utilizes that library. I'll see what it does now, and hopefully understand it enough to implement it in Top Picks.

youve been 'looking to improve this' since 2022 and still have not - as it's part of the premier experience that we are paying for then you are in breach of contract. either fix it quickly or make it a flaky free feature. downloads are the only thing i have premier for and it doesn't work reliably!

My adding is not automated. I convert DVDs and upload them manually, then edit the metadata as required - sort of a hobby. Waiting for Emby to add them by itself was frustrating. Cliking the SCAN link allows me to proceed with what I need to do in a timely fashion. Thanx again.

This isn't an Emby thing. It's this way all over the Internet. You want images to load fast and be able to get pulled from the browsers cache once they've been downloaded the first time. Static content, be it graphics, html, java script, video segment, etc are meant to be able to re-used for a period of time without having to retrieve them on every use. The internet depends on this working in this fashion. Organizations of all sizes from companies to ISPs make use of proxies or transparent proxies (you won't even know it's there) to hold static information when possible, to save bandwidth and deliver content quicker as the resource will already be local. Mobile operators do this and more. Not only will they cash things like images, but they also likely re-optimize them as well delivering a picture that's been scaled down to look the same on hand-held devices but save bandwidth. Content Delivery Networks (CDN) require this in order to be able to move the content closer to a user with regional edge servers. Many ISP do this as well in a transparent fashion as well so a 1000 users hitting Facebook will have content in common that won't need to be requested. 100 users watching the latest movies just posted on Netflex or Prime can be served up from local ISP cache vs using bandwidth for every user. There are methods that can be used to obfuscate static content by making it look dynamic, but then it can't be cached. Emby could also require an authorized session to delivery anything including images but they share the issue of "busing" the ability to cache the images. Nginx or other local reverse proxy caching is lost, every use of an item requires a delivery from the server. That's a lot more work on the server having to deliver much more data over and over as well as a lot more overhead needed for session/authorization management. In another thread, Luke mentioned the image retrieval code could be changed to require an API. That would stop private images from being exposed but would negatively affect image caching in general. I think a better approach would be to keep the current URL as is http://{public domain}/emby/items/{increment number}/images/primary But never deliver the content with that URL if the content is from "private" content areas such as Camera Upload or Home Video and Photos libraries it would require a different URL that includes a key some kind. The content would be delivered assuming the user has access to that content. For security I'd code it so the current URL only delivers content associated with sections in (list) while everything else would require an authorized key. This way, it's future proofed from a new addition or feature slipping through the cracks. Any new type of content types would have to be explicitly added to the list above in code to deliver content without a key. This approach would allow caching as usual from local nginx (or other reverse proxy) to transparent proxies or CDN deliveries, while protecting private content areas requiring authentication. This would provide the security required while providing the best performance possible. Each client app should be upgraded to directly support this, but the server could provide an interim solution to bridge the gap until each app is upgraded. For example, if the client is a Roku and not version X or higher (with new handling) accessing private content using the existing URL it would determine If the user has access to that content as well as check to see if the device has already been authenticated for the session. I just want to make sure any implementation added, doesn't adversely affect performance or the ability to cache images for the main library as you WANT/NEED them to be non-secured and fully cacheable.

Edit: There is a plugin version available now, please see ACdb thread. Emby MDBList Collection Creator URL: https://github.com/jonjonsson/Emby-MDBList-Collection-Creator This tool allows you to convert lists from MDBList.com into collections within your Emby media server. MDBList aggregates content lists from various platforms including Trakt and IMDB. Features List Conversion: Transform MDBList lists into Emby collections Metadata Refresh: Keep ratings up-to-date for newly released content Collection Images: Upload local or remote images for collections posters Seasonal Collections: Specify when a collections should be visible Collection Ordering: Show your collections in order of which one was update Backup & Restore: Additional utilities to backup and restore watch history and favorites Prerequisites: To use this script, you need: Python installed on your system "Requests" Python package (install with `pip install requests`) Admin privileges on your Emby server A user account on [MDBList](https://mdblist.com/) The script has been tested with Emby Version 4.8.8.0 and later, but other recent versions should also be compatible Please check out the GitHub Link for more detailed information

Hi Emby Team, I know there are already many threads dealing with subtitle issues... i just have a simple question... why does the "LG Emby App" encode the video when selecting PGS Subs while "LG Plex App" does direct play on the same file an the some pgs subs selected? imho this cannot be an LG Prob. Greetz nanuk

I have the movie and TV show theme music addon. If I am viewing a supported title that plays music and exit the app the music does not stop. The music only stops if I back out of the episode or movie first.

Myself and friends have gigabit/10gigbit that I share my server with. However, EVERY single time somebody connects from a new client or for the first time, it transcodes DESPITE them having 1Gb/s+ speeds when streaming 8-10Mbps due to "lowering bitrate due to quality settings". I don't understand how the clients (or is it the server?) are so bad at detecting internet speeds. It's literally mis-calculating a client's ability to steam a video by orders of magnitude. Like others, I have to give "the talk" to new users where I try to explain that Emby is bad at detecting speed and can be remedied by going into settings > playback settings > and selecting some arbitrarily high video bitrate so that emby doesn't try to transcode unnecessarily again on that device. This talk isn't easy with non-technical people who are hearing the term "bitrate" for the first time. Then it get's more confusing for them when I have to explain that it's a per-device-setting and not a global ("sticky" across all devices) setting. More confusion. - Is it the clients which are all terrible at detecting speed? Is it my server? Is it something else? - Is there no possibility of adding the ability for the admin or user to set a default "playback video bitrate" for users across ALL devices? I'm open to other fixes. Sorry if this is abit "rant-y" Thanks.

well considering time it took to restart and do the vacuum compared at a regular restart, I'm thinking that I might need perhaps to do few restarts so the process can run through the whole db no ? (I have seen the limit of rows it can run through for optimisation in the Database tab).

Bonjour à tous, Je ne sais pas si je suis dans la bonne section, alors n'hésitez pas à me corriger si nécessaire. Je vous présente mon projet pour générer des fichiers ".strm" à partir d'un fichier M3U existant ou à télécharger. Voici le dépôt GitHub : M3U-Strm-Generator. (https://github.com/Koma-D/M3U-Strm-Generator) Je ne suis pas un codeur, j'essaie d'apprendre avec ChatGPT. Problématique Mon fichier M3U était colossal et je souhaitais structurer les différents liens qu'il contenait, afin de créer des médiathèque pour EMBY. J'ai donc créé un script en Python à partir d'un dépôt existant nommé "m2strm". Cependant, ce dépôt n'étant plus à jour, j'ai décidé de m'en inspirer et d'ajouter mes propres fonctionnalités. Fonctionnalités Gestion des chaînes : Recharge et organise les chaînes de télévision à partir d'un fichier de configuration. Gestion des films : Recharge et organise les films à partir d'un fichier de configuration. Gestion des séries : Recharge et organise les séries à partir d'un fichier de configuration. Chaque série créée dans chaque dossier de groupes sera transformée en dossier de séries pour éviter d'avoir tous les épisodes en vrac. Journalisation : Enregistre les erreurs rencontrées lors du traitement dans un fichier "error.txt". Génération de logs : Création automatique de fichiers de log pour les nouveaux films, séries et chaînes. Nettoyage automatique : Nettoie les noms de répertoires et fichiers pour éviter les conflits. Utilisation Création d'un répertoire : Créez un répertoire où seul le script sera utilisé pour éviter les erreurs. Étape 1 : Ouvrez votre terminal et lancez la commande suivante pour générer le fichier "Config.cfg", qui sera utilisé pour la suite. Utilisez la commande avec l'option /C. Étape 2 : Une fois que vous avez modifié les informations dans le fichier "Config.cfg", lancez la commande avec l'option /U. Cela générera un fichier "unwantedgroup.cfg". Ouvrez ce fichier et supprimez les groupes de la liste si vous souhaitez qu'ils soient traités et que leurs fichiers soient générés. Étape 3 : Lancez le traitement avec la commande principale. Assurez-vous que le téléchargement est désactivé dans le fichier Config.cfg si vous avez déjà un fichier M3U. Le traitement sera lancé et vos dossiers seront créés en fonction de vos critères. Vérification des logs Consultez le fichier "error.txt" pour toute erreur rencontrée. Les fichiers de log pour les films, séries et chaînes ajoutées seront générés automatiquement dans le dossier "log" créé à la racine du script. Pour ceux qui s'y connaissent en programmation, n'hésitez pas à me dire ce que je peux améliorer ou ajouter à ce script déjà fonctionnel. J'apprécierais vos tests et vos retours ! Merci à tous !

HI, thanks for sharing.

I personally don't use nginx so I don't know the specifics or actual implementation for Emby, but I can give you some ideas to try. EDIT: I removed what I original wrote. Basically, it used a session tracking in nginx. It could get things like the device id, emby token, username, device name, from a few places but theideal place would be setting a rule on a URL starting with "http://server:port/emby/Users/authenticatebyname" You then process the response to response which has everything you need to know it's a authorized user. I had other trips written such as calling the API or a request to a URL that would require authorization (using headers nginx received). If emby gives you back a response they would be authenticated and if emby gives you an error on your known URL then they aren't authenticated. You could then update the session variable to reflect the auth status. So, you could have a rule on "http://{public domain}/emby/items/{increment number}/images/primary". You do the check as mentioned with the received headers from the inbound request and if it's successful you would pass the URL to Emby Server which would return an item pic. You could also set up a rule looking at http://{public domain}/webhooks and when executed you would parse the payload which has user information. You then match that up to a session on nginx and with the success or failure notification you receive from webhooks. EASIER METHOD Use the nginx secure links module. Available to compile in your own nginx if needed but built into most binary releases. Pretty decent explanation and use here: https://www.f5.com/company/blog/nginx/securing-urls-secure-link-module-nginx-plus This is one of the examples, but I'm not fond of it as is. I would not bind an images to an IP, nor would I use an expiration date on the command line. Every rewrite of an image would have a different expires in the URL which would break caching if using a CDN like Cloudflare. For that matter it would break nginx caching as well if used. I'm referring to the ability to have all users getting the same URL for graphic links. It wouldn't matter if your proxy or a CDN has a "private" graphic cached as no one would know it even exists unless they were logged in to your system and received a rewrite URL with the hash in it. Example I don't like but it's helpful to understand how it would work. location /files { root /var/www; secure_link $arg_md5,$arg_expires; secure_link_md5 "$secure_link_expires$uri$remote_addr enigma"; if ($secure_link = "") { return 403; } if ($secure_link = "0") { return 410; } } User clicks a link /files/pricelist.html?md5=AUEnXC7T-Tfv9WLsWbf-mw&expires=1483228740 The location is /files which matches so it sets the root to /var/www It has two arguments defined which is md5 and expires. These variables are pulled from the URL so: md5=UEnXC7T-Tfv9WLsWbf-mw expires=1483228740 It then calls a function secure_link_md5 passing the expires, the URL and the remote IP address and "enigma" <--- secret word secure_link_md5 function check the date and if expired sets $secure_link= 0. If not expired secure_link_md5 generates an md5 checksum on the info passed in (expires, uri, remote ip, "enigma"). This checksum is compared to $arg_mf5. if it doesn't match $secure_link is set to an empty string "". If it does match it will build the new URL by starting with the root defined as "/var/www", followed by the location which is "/files" and finally the $uri variable which is "/playlist.htm" giving is /var/www/files/pricelist.htm It would then send this request on to the server. Another example and closer to how we should implement it. No expire or binding to IP. server { listen 80; server_name secure-link-demo; location /videos { secure_link_secret enigma; if ($secure_link = "") { return 403; } rewrite ^ /secure/$secure_link; } location /secure { internal; root /opt; } } User clicks on a link "https://videos/80e2dfecb5f54513ad4e2e6217d36fd4/hls/bunny.m3u8" and after being parsed is matched to the location /videos. This time we take our uri which is "/hls/bunny.m3u8" and our secret "enigma" to generate an md5. If our generrated md5 doesn't match the URL md5 we set $secure_link = "", otherwise we set $secure_link to the URI. We then rewrite it to /secure/$secure_link which becomes "/secure/hls/bunny.m3u8 " Then then gets processed by the location /secure which is "internal" meaning it only applies to internally created URLs. This will take the URL it's processing starting with /secure and prepends It with the root variable and end up with "/opt/secure/hls/bunny.m3u8" It should be easy to see how that could be used with Emby to block direct access to the images. Person Opinion on Implementation I really wouldn't want the EmbyID (graphicI) used directly in the link where it's easy to see. I'd probably take the ID and pad it with 4 characters then the ID and then another 4 characters. Assuming the code runs really quick I'd even try something like creating a hash of the EmbyID. Then grab the first X characters then Y characters after that. For the URI I could then use X+ID+Y. That should be similar to creating random characters for padding. You could get fancy like generate 2 random numbers from 1 to 9. With the first random number you would grab Random1-1 chars from the junk hash and then Random2-1 chars from the just has. Create the URI string by writing Random1 number + first set of chars + ID + Random2 chars + R2 number.. Later when you need to get your actual ID back look at the first number of the URI and strip that many chars of the front. Look at the number at the end of the string and strip that many from the end of the URI leaving you with the actual ID. Only reason to do that at all is to have a slick way to hide the ID in the URI so it's not in the same place all the time but would float around, making it harder to figure out a pattern. I'm sure that last bit is way overkill for most people that just want to prevent people from being able to use the same URL over and over again just adding 1 to the ID while being able to access all your pics. Just follow the "bunny" example which should be pretty easy and will get the job done. Carlo

Hmm - I should not have to tell emby it's private - it should be out the box ! Emby need to fix the inappropriate method to assign id's when used on the internet - for local, fine, it makes little difference, but when exposed to the internet - the mindset of security needs to be changed - radically - you are well aware of this ...

It IS an Emby thing because as you have repeated above - it's because emby is just incrementing the id. If it used a hard to guess random id - ideally alpha numeric, then we wouldn't be having this conversation because the 'key' as you put it, would be 'impossible' to guess in the first place. A quick solution is to simply increase the numerical langth of the id and randomise it - that way, any image is much harder to guess but you can retain the clients/api etc. It's not ideal, but it's better than what we have today. Not 100% sure where caching comes into this - the idea is to stop a brute force access to the image in the first place. Once it's been read, yes, of course it's in a cache 'somewhere' but so what if it is ? It will have a TTL and be removed from the cache in due course.

Oh didn't realise I could do it at the library level. Just tested and I also didn't realise that Emby was smart enough to wait for the recording to finish before converting, so that's all good. Tested and it just converts everything new, with the perfect settings I needed. So I'll document it for myself because I'll forget if I ever have to rebuild

Hi. There are user-based options for this but I warn you that it WILL cause playback problems. Your best approach is to provide content that won't require transcoding for these people.

Should be sometime next week.

To provide free access to your family and friends (which the software is licenced for) you need to: (1) set up your server with your videos, and setup user logins with the access they each require, (2) configure your server and router for remote access, (3) tell your users the server address and their login. Your users can then access your server, when properly set up, using a browser for free. You can also enable them to use any Emby clients for free if you subscribe to a Premiere licence for your server; but otherwise most clients require a one-off unlock payment for full functionality. The links given above provide more information on the various steps. Paul

Okay I guess that's good and brings us back to it just being a labeling issue with what is being displayed in the dashboard like in the other thread you linked. Sounds like they're working on it. Thank you for the help! Makes me feel better.

That's a remux log, there was no video transcoding occurring - video stream was copied, only audio conversion.

Hm, I knew I've seen a similar topic recently, took me a minute to find it. Have a read here, it appears that's just incorrect labeling. You can also post ffmpeg log written for that session, though.

https://emby.media/community/index.php?/lostpassword/

I advice people to look up Tdarr/Fileflows and Bazarr, should fix most if not all Subtitle problems when set up right. Can be set up to be fully automated and handle everything before a file hits Emby.

In my experience, videophiles use the exact terms but no biggie. As I said, the discs (save dual layer DV) can be ripped to streaming friendly formats in full quality. There is really no reason to try and replicate the disc image these days.

@Lukelooking at a clean install to me it looks like the issue is coming from Episode guest stars/people. Noticed it via Game of Thrones episodes. https://api4.thetvdb.com/v4/episodes/3436421/extended?meta=translations { "id": 64033338, "name": null, "peopleId": 247832, "seriesId": 121361, "series": null, "movie": null, "movieId": null, "episodeId": 3436421, "type": 4, "image": null, "sort": 0, "isFeatured": false, "url": "247832-gethin-anthony", "nameTranslations": null, "overviewTranslations": null, "aliases": null, "peopleType": "Guest Star", "personName": "Gethin Anthony", "tagOptions": null, "personImgURL": "/banners/v4/actor/247832/photo/60629d5d52bfb.jpg" } Since these are not cached had to look at TVDB api. Don't see this issue at series level.

Never. Move on. The 1990's called and they want their hair back.

It would be great if the plugin would also sync liked songs (in both directions) like LMS does.

Thanks for the help! Wasn't an emby issue afterall!

When it comes to media server solutions, we believe that Emby is the number one product for users who value privacy, customization, and reliability. Today, we're going to take a closer look at some of Emby’s key strengths that make it an ideal choice over other media server solutions. 1. Prioritizing Privacy and Security Security is a central part of Emby’s design. Unlike some media server alternatives that have limited security options, Emby gives users control over who can access their media and how they access it. With Emby, you can setup secure HTTPS connections, ensuring data is encrypted as it’s transmitted or easily set up access via a reverse proxy amongst other options. User permissions are also straightforward to manage, giving you full authority to create individual access levels for each user in your household or server network. Your media is yours, and Emby ensures it stays that way by giving you the ability to implement strong encryption options that protect against unauthorized access. 2. Simplified, Intuitive Setup From the moment you install Emby, you’ll notice a streamlined, easy to navigate interface. Whether you’re setting up for the first time or managing your media library, our layout is intuitive and user-friendly. Emby is accessible to both beginners and advanced users, with step-by-step guidance to get you started and powerful customization options available for those who want to tailor their media experience further. Want to hide your remote users from a login screen? You can do that! Want to set up those same users with an easy way to access your server? Emby Connect allows you to do that! There are so many ways in which Emby simplifies user management and access to make it easier and more secure for your users! Other media servers can be clunky and involve multiple steps to perform basic tasks, but Emby simplifies this with a unified interface that makes media organization and management easy. 3. Seamless and Efficient Transcoding As mentioned in our previous blog, transcoding is a key feature for media server users, and Emby’s transcoding engine is optimized to handle media formats and devices with impressive efficiency. Whether you're streaming a 4K movie, using HDR tone mapping, or watching a video on a low-bandwidth connection, Emby has the ability to dynamically adapt to your network and hardware capabilities, delivering smooth playback across devices without unnecessary buffering or interruptions. Emby can also utilize hardware acceleration (Emby Premiere only), ensuring that high-resolution content plays seamlessly without consuming excessive CPU resources. This is particularly helpful if you have multiple users streaming from the server simultaneously, as Emby ensures each session gets the best possible quality. 4. Comprehensive Library Management Emby’s library management capabilities are designed to provide the best possible organization and personalization options. With Emby, you can create custom collections, tag media, and even use rich metadata that automatically pulls in posters, descriptions, and trailers to enhance your experience. The smart playlists and customizable views allow users to organize their media in a way that feels personal and unique. For those who have extensive media libraries, Emby also makes finding and managing content effortless. Search filters and sorting options let you locate titles instantly, and Emby’s advanced metadata scraping ensures your library looks how you want it to. 5. Cross-Platform Compatibility In an age where we use a variety of devices daily, Emby is engineered to be versatile. Emby offers applications for nearly every platform, including Windows, macOS, Linux, Android, iOS, Roku, smart TVs, Android TV, tvOS, web browsers and more, giving users the flexibility to stream and manage their media library from practically any device. The versatility that our server provides doesn’t stop there – it also supports a wide range of formats, ensuring that no matter what file type you prefer or where you choose to watch, Emby is ready to deliver the best experience. 6. Constantly Evolving Features with a Supportive Community Emby is continually updated with new features based on user feedback and technological advancements. Our development team and community via these forums, work hand-in-hand to enhance Emby’s performance, refine its interface, and introduce new options that make media management a more rewarding experience. As an Emby user, you’re part of a passionate community that we believe values innovation, feedback, and the enjoyment of seamless media streaming. View the full article

HI, yes ultimately we plan to hook this into the multi-version system that we have for normal video files. Thanks.

yes 1. Change the name of any 'admin' account to something else that is not admin - if an attacker doesn't even know the account name, then they cannot even attempt to login. 2. Ensure the clients are hiding all the usernames and set it to only show those that have previously logged in. 3. Disable remote 'Admin' access (or whatever you have called it). Do you really need to admin emby remotely ? If yes, then there are secure options to do this. 4. Ensure you use a nonemby admin account for all your 'normal' activity. 5. Ensure all non-admin accounts have the correct permissions setup - and give least priviledge - ie if they don't need delete, then remove it ! 6. Try and ensure you are using https - and ideally a reverse proxy and use default ports. (80 redirect to 443) 7. If not using a reverse proxy, change the default ports to something not commonly in use. 8 ... There are LOADS more but this will get you started .. MFA is actually well down the list - there is zero point having that until your security foundations are solid .. @sa2000Other than - Secure Your Server | Emby Documentation - which just discusses TLS - would it be a good idea to have a Knowledgebase with a list similiar to the above on ALL the 'best practice' items the user should do before they even attempt to click the 'remote access' button for emby ? The 'out the box' security profile for emby is pretty shocking tbh ...

Sometimes friends will share their server but can't be arsed to set up the trakt plugin or they are still on an old version and dont want to add peoples trakt manually. also some people prefer to use simkl which is another service like trakt. trakt or simkl being part of the player or webapp would take away those issues. also would be nice to have an integrated watchlist using either of those

Actually I've gone through all of this and I believe all of the options discussed here work just fine in the latest versions of the server and app. Thanks.

This fixed my issue. Thanks!

Small guide to help Url to connect to: http://localhost:8096/mediabrowser (Building Mono should not be necessary once mono official release has been updated.) Linux: Building Mono: There's three way to do this: Build everything from source. Use Pokorra's repo and rebuild mono-opt. Use someone else's prebuilt package for Pokorra's repo First option: Mono, see http://www.mono-project.com/Compiling_Mono_From_Git Libgdiplus, see https://github.com/mono/libgdiplus Second option: Source file to build mono-opt package are available at https://build.opensuse.org/package/show/home:tpokorra:mono/mono Rebuilding Pokorra's mono-opt package is very distribution and version specific. For Fedora, see this guide https://fedoraproject.org/wiki/How_to_create_an_RPM_package For debian based, see this guide https://wiki.debian.org/HowToPackageForDebian Don't forget to install libgdiplus Third option: For Fedora, install the 3 packages for your arch via yum(yum localinstall {package_name}):x86mono-opt-3.2.7-0.20140110git319f562ca7.fc20.i686.rpm mono-opt-devel-3.2.7-0.20140110git319f562ca7.fc20.i686.rpm mono-libgdiplus-opt-2.10-9.fc20.i686.rpm x86_64mono-opt-3.2.7-0.20140110git319f562ca7.fc20.x86_64.rpm mono-opt-devel-3.2.7-0.20140110git319f562ca7.fc20.x86_64.rpm mono-libgdiplus-opt-2.10-9.fc20.x86_64.rpm Then open a console, type this to set the right mono: . /opt/mono/env.sh You also add this line to the user's ~/.bashrc running mediabrowser so you need to type it everytime. Finally, go to mediabrowser's folder, type: mono MediaBrowser.Server.Mono.exe MediaBrowser: Unzip mediabrowser Open a terminal If using Pokorra's build, type at prompt(this will set environnement variables): . /opt/mono/env.sh Go to mediabrowser's folder and type: mono MediaBrowser.Server.Mono.exe Mac: Build Mono for git, see this link (Error in doc: autogen should be autogen.sh) Build libgdi+, TBA (MacPorts?) (Require x11) Unzip mediabrowser In a Terminal, go to mediabrowser's folder and type: mono MediaBrowser.Server.Mono.exe Notes: If your mono installation is in a non-standard path, create a file called env.sh with this content in mediabrowser folder(don't forget to substitute path): export PATH=/opt/mono/bin:$PATH export LD_LIBRARY_PATH=/opt/mono/lib:$LD_LIBRARY_PATH export PKG_CONFIG_PATH=/opt/mono/lib/pkgconfig:$PKG_CONFIG_PATH Before running mediabrowser in mediabrowser folder in Terminal, type this command: . /opt/mono/env.sh

I love when people say "everyone" or "no one" does something. Because a statement like that is always wrong.

Just give up with Emby for Android downloads, they've been crap for years and still are to this day.