All Activity

I normally set it to Auto, but would think Native would be more efficient (all my content is either H.264 or H.265 which are all native). What advantages/disadvantages the MVP player have vs the Native player, and how does the Auto setting work?

Yeah, I can see that. Personally, I always separate my movie and TV content in separate rows.

Hi. If you mean you want this to be another special, you can just put it in a "specials" folder.

Hi All, I have recently bought the UGREEN DXP6800 Pro and I’m having issues getting Emby working. I’m installing this image in docker https://hub.docker.com/r/emby/embyserver I’m clearly doing something wrong as my Synology build is rock solid and this is all over the place. Do we have a docker install guide for the UGREEN until the native application is released? It doesn’t matter what method i use i still get issues with the server not creating LibraryMonitor for my media libraries even though Emby has RW permissions. Cheers, Chris embyserver.txt

But then you'd have a combo of thumbs (basically episode screengrabs, which I know some users would prefer but I'd find it abhorrent in CW row) and posters (movies) - never a good combo IMHO, I'm sucker for consistency. I like having series thumb in CW row, as it gives proper distinction and certain flair. I just wanted episode overlays on those. Now I have them and it looks great.

Limited power and limited audio/video support. For streaming services, I'm sure it provides everything needed but for streaming your own content, you may run into some of those limitations (more transcoding and/or remuxing needed).

Hi. Do you have a fresh example with the latest version of the app? The last set had some very strange file access issues on your server. Make sure it has adequate temp space as well.

New version has an awesome new feature that lets you combine two subtitles/two languages to display them simultaneously. This is great for me because my wife and I have different first languages. I tested it out watching a movie that was mostly in English but many parts were in Chinese so I combined Spanish and forced English so my wife could have Spanish subs for everything and when they spoke Chinese English subs appear for me. It’s not perfect but definitely very useful.

Thanks Ebr. I am curious to what the limitations are with this device.

Accessing YT content outside of their published and approved channels is against their ToS and is stealing. How do you think YT makes money (and pays all those content creators)? They do so via advertising and, when you circumvent that, you are cutting off the revenue not just to YT but to the actual creators. In addition, IMDb and RT data is not free. Once again, these are businesses and they sell access to this data. If this app is actually paying the subscription prices for this data then I stand corrected on this point but I've not seen evidence of that and I'd be very surprised if it is the case (both are quite expensive). Finally, any direct integration with content-acquisition systems is just something we cannot allow.

I would like to see this minor change as explained below for extras: For example, Deleted Scenes-This works great. You have a TV show episode and add "-deleted" to the end of the file, it shows up as "Deleted Scenes" underneath the TV episode as an extra Audio Commentaries- **change request**-If you have an episode and add "-audio commentary" to the end of file, it shows up as a separate version in the pull down menu. -If you add"-audio commentary-featurette" to the file name, it shows up exactly like that "audio commentary-featurette." What I would prefer is that it puts the audio commentary below the episode and drops the "-featurette" part.

Hi. There are limitations to the device itself but we run just fine on it.

Yes, it is the newest Fire TV stick on the Vega OS platform. I was just wondering if there are any limitations for Emby on this device or does it function as well as for other streaming devices.

Not only I'm a lifetime owner, I have been for a while (I remember MB3 and dealing with codex). I'm excited to read between the lines at the new Home Screen. That to me sounds exciting, hopefully it will give us much flexibility. Keep up the good work

Hey guys I see you love this service and everything. That's great to each his own. I was looking forward to using it as well I just found out the crazy stuff you have to do to get SSL certified so I tried to get a refund I had the service for about 3 hours and immediately canceled my subscription and requested a refund. They simply said you should know I guess basically by sending me a article on how to set up the server to me that is way too difficult for somebody to have to go through if they don't want to considering I just had no idea that I would have to do that thought by now that would be just included if you had to pay. My question is how good is the customer support about that kind of stuff cuz I may come back someday you never know.

Please go through the document I linked. You need to set up port forwarding on your router.

I still think that, if you choose "Primary" for the image type in a CW row, you should get the primary image of the actual item (the episode) not of its parent. Thumbs are a special case exactly because episodes don't have thumbs.

Just tried canyouseeme.org again, and it pre-populated with the IP address shown on the Emby dashboard (for remote access), but shows port 80 - this worked fine and confirmed the port was not blocked. But the port number on Emby dashboard is the default 8096 - if I enter that port number in canyouseeme, it cannot see the service and times out. My router does have something called NAT enabled but I've no idea what this is.

OK, laufe immer auf Stable. @Luke It seems not to be right, that his collection covers are now generated by Emby instead of being downloaded from the Web.

Here's a way how you can do this: At first - so you better understand this step by step - install the "Folder Sync" plugin. With that plugin, you can configure a number of folders (typically network folders, but in this case, just local folders on the server). Now configure a folder, name it "FolderSyncTest" and configure an empty dir on the server as path. Leave "access to all users" checked for now. Once you have done this, go to an item (e.g. a song), use "Download to.." and you will see the FolderSyncTest folder. Use that for download. Now the file will appear in that folder on the server. With your plugin, you can watch that folder for changes and whenever a new file arrives, you inject your metadata/images. So, how to get the file to the actual recipient? You can either replace the file in the library (temporarily) or create a special library for those file (e.g. "Transfer"). In either case, you use the Emby API to make it download the changed file to the actual recipient. Understood so far? Next question is "Who IS the actual recipient?" - your plugin cannot know this. And probably you want the download feature to work exactly as normally. You can do it like this: For every download target of every user - you create a folder-sync folder of the same name but with a suffix like " (with metadata injection)" - and this time with permissions only for the respective user. So, each user will see the double amount of entries in the "Download to.." dropdown list, each entry with and without that suffiix. Based on that name - after removing the suffix - your plugin will know the name of the download target and initiate download of the enriched file to that user's location. 3rd Level The above will work, but it depends on another plugin - yes - plugin! As the functionality you need is implemented by a plugin, you can of course do that part in your own plugin as well - and hidden as that part needs no UI in your case. The bottom line is - you don't need the folder sync plugin for implementing this - it's rather that -I- needed that plugin to understandably explain the concept

Unfortunately, I don’t have a solution for this problem. I quit using Windows edge and I moved to Windows app where there was no problem. Although couple of days ago, I opened it by accident on the Windows edge and it was working fine. So it is a little bit strange but I don’t know what happened.

Some further updated ones for a couple of the new plugins.

From my search online, the following - driver: nvidia count: all capabilities: [gpu, video] is equivalent to --gpu all. --- Here is the diagnose of the problem by Gemini Issue Summary When running the official ARM64 (aarch64) Docker container (emby/embyserver) on an ARM host with an NVIDIA GPU passed via NVIDIA Container Toolkit, hardware acceleration fails to expose NVENC or CUDA capability. Checking the bundled ffmpeg binary inside the container reveals that the aarch64 build explicitly disables CUDA and omits NVENC/CUDA capabilities during compilation. Diagnostic Logs Container Architecture: aarch64 Running ffmpeg -version inside the emby/embyserver container shows: ffmpeg version 5.1-emby_2023_06_25_p6 Copyright (c) 2000-2022 the FFmpeg developers and softworkz for Emby LLC built with gcc 13.4.0 (crosstool-NG 1.28.0) configuration: --cc='sccache aarch64-emby-linux-gnu-gcc' --prefix=/home/embybuilder/Buildbot/armv8/ffmpeg-armv8/package ... --disable-cuda-llvm ... Checking for NVENC encoders yields no results: / # /bin/ffmpeg -encoders | grep -E "libnvidia|nvenc" (empty output) Root Cause Compilation Flags for ARM64 (ffmpeg-armv8 The toolchain configuration for aarch64 uses --disable-cuda-llvm and omits --enable-cuda, --enable-nvenc, and --enable-ffnvcodec. Architecture Parity: While the x86_64 / amd64 builds of emby-ffmpeg include full NVENC/CUDA support out of the box, the aarch64 target build appears to assume mobile/SBC targets (e.g., Raspberry Pi) rather than ARM64 servers equipped with NVIDIA GPUs. Proposed Solution for the Emby Team To provide feature parity for ARM64 server environments equipped with NVIDIA hardware, please consider updating the build pipeline for ffmpeg-armv8 / aarch64: Update ffmpeg-armv8 Build Flags: Enable CUDA and NVENC headers in the ARM64 build matrix by adding: --enable-cuda \ --enable-nvenc \ --enable-ffnvcodec \ --enable-cuvid (And removing --disable-cuda-llvm where appropriate). Include NVIDIA Runtime Libraries in the ARM64 Container Image: Ensure libnvidia-encode / nv-codec-headers or dynamic CUDA loader headers are bundled in the base ARM64 container image to support NVIDIA Container Toolkit runtime injection. Please ensure that ffdetect and ffprobe are also rebuilt with the same CUDA/NVENC/FFNVCODEC flags in the aarch64 pipeline. Since Emby's NvidiaCodecProvider calls /bin/ffdetect nvencdec at startup to discover GPU features, updating ffmpeg alone without updating ffdetect will prevent Emby from listing NVENC encoders in the Dashboard UI.

While I'd also like to see this feature added, Emby seems to have many more features than Jellyfin. [redacted] Is anyone seeing that Jellyfin has caught up? They do have some different features like watch together, but they're still well short of what Emby has....I think.

When it first happened, I was wondering what it said because it was very quick and had to reread some threads in the forum to find out what it was. I think people will be curious when they first see it. IF there was a way to make it not show until after X seconds that would be nice because then only the people with slow connections would see it. Otherwise, I see its purpose.