Search the Community

I continue to experience the same problem with Music Library: Sort Title in nfo file is being overwritten by Emby. Example, this album with "...Meets the Saxophone Masters" as title, for which I changed SORTTITLE to "Meets the Saxophone Masters" (removing the starting ellipses). See images below: edited nfo has different Title and Sort Title, as do source files as viewed ion MP3Tag. Per @Luke's new guidance, I went into Folder view, did both Scan Files and Refresh Metadata on that folder and all its contents, but you can see in last image that nfo has been reverted to old, incorrect Sort Title. Log file is also attached. Why is Emby still not respecting either existing nfo nor embedded metadata? embyserver.txt

Emby server does not load sorttitle tag from nfo. "title" is loaded to "sort title". "title" tag and other tags are loaded successfully. my emby version: 4.8.1.0 on debian 12

My setup is based on a Debian 12 Bookworm LXC Container running on ProxMox 8.1.3. Spent quite some time on this and maybe this helps someone else to get it working. If not, I'm sorry... As I'm using an NFS mount within the container I'm using a privileged container. Under Options -> Features I've enabled "Nesting" and "NFS". Don't touch the LXC's .conf file just yet! Make sure there's no mount entries in it! On the ProxMox host: Find out the GID of the "render" group: getent group render I'm using 104 in this example. In the LXC container: Find a unused GID: cat /etc/group I'm using 112 in this example. Find the group name for the GID of the host's render group getent group 104 I'm using sgx in this example. Change the GID of the sgx group to the unused GID and update the filesystem: groupmod -g 112 sgx find / -group 104 -exec chgrp -h sgx {} \; 112 = new GID, 104 = old GID, sgx = group name. Find the GID of the container's render group getent group render I'm using 106 in this example. Change the GID of the "render" group to the GID of the host's render group and update the file system: groupmod -g 104 render find / -group 106 -exec chgrp -h render {} \; 104 = new GID, 106 = old GID, render = group name. Update the sources list: nano /etc/apt/sources.list Add the following lines: #non-free firmwares deb http://deb.debian.org/debian bookworm non-free-firmware #non-free drivers and components deb http://deb.debian.org/debian bookworm non-free Install the drivers: apt update && apt install intel-media-va-driver-non-free intel-gpu-tools vainfo Shutdown the container. On the ProxMox host: Update the LXC's .conf file: nano /etc/pve/nodes/<NODE NAME>/lxc/<CT ID>.conf Add the following lines: lxc.cgroup2.devices.allow: c 226:0 rwm lxc.cgroup2.devices.allow: c 226:128 rwm lxc.mount.entry: /dev/dri/card0 dev/dri/card0 none bind,optional,create=file lxc.mount.entry: /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=file Start the container. In the LXC container: Check if permissions are correct: ls -Alh /dev/dri Output should be similar to: total 0 crw-rw---- 1 root video 226, 0 Dec 10 21:21 card0 crw-rw---- 1 root render 226, 128 Dec 10 21:21 renderD128 Important is that it shows video and render as the groups! Check if VAAPI is available: vainfo Output should be similar to: Install Emby Server. I used the 4.8 Beta version as it seems to have some fixes for Intel Alder Lake-N CPUs. Add the Emby user to the video and render groups: sudo usermod -aG video emby sudo usermod -aG render emby Reboot your container and (hopefully) enjoy hardware acceleration! Try starting a movie and change the quality to something that would trigger transcoding. Check the CPU usage in the ProxMox Summary screen and watch the GPU in the container usage with: intel_gpu_top

Hello - I'm an intermediate user you could say - and I installed emby onto my main server a hp proliant running debian 12. install took maybe 15 seconds. before install i looked up what ports needed to be opened, and opened up 8096 (default) and a temp alt port just in case to avoid any frustration. and reloaded firewall. installed emby. went to browser and tried to open localhost:8096 and "Unable to connect: can't establish blah blah..." I tried connecting with 127.0.0.1, and my LAN IP addresses, and my external IP addresses. Nothing will connect. I chose to install the BETA version, so I decided perhaps beta was more beta than i wanted. So I reinstalled doing a rollback to the stable version. Same problem. Triple checked my firewall. Dunno what it's problem is. Even rebooted entire server. No change. I know I'm retarded, but this is getting to me. And with the week I've had I can't take any more of fixing other people's mistakes. I just wanted to relax and watch movies and unplug my brain. So, if anyone knows what I'm missing or doing wrong, I'd be obliged if you could please offer any assistance. Thank you.