Leaderboard

@LukeThat's something I might be able to work on, I too had to setup a Jellyfin instance alongside Emby to get my library in Music Assistant, which is not ideal especially since Jellyfin has had severe memory leaks for a while now making it completely unusable here.

It would be great to have Emby as a music provider for Music Assistant: https://music-assistant.io/ I'm forced to use Jellyfin as a provider for now: https://github.com/orgs/music-assistant/discussions/583 It probably wouldn't take too much effort to adapt the existing Jellyfin provider to the Emby API: https://github.com/music-assistant/server/tree/dev/music_assistant/server/providers/jellyfin

Hello, I'm using the new Emby app, v 2.207.2.0, with Emby Server version 4.8.10.0 (all running on Windows). Very excited about the new app by the way, job well done! Here's my question, is there a keyboard shortcut or windows remote button that will advance to the next or previous chapter when watching a video? A long time ago in the Emby Theater app the keyboard PgUp and PgDwn keys did this, but that function stopped working like a year ago. I was hoping it would work again in the new Emby App, but after installing and testing today it looks like it does not. I have found the following Emby support article that talks about keyboard shortcuts: Keyboard and Remote Support | Emby Documentation It mentions ChUp/ChDwn, PgUp/PgDwn, and Ctrl-F/Ctrl-B as all performing this next/previous chapter function. But none of these work in the new Emby (and they had stopped working on Emby Theater also for some reason). Any help would be greatly appreciated!!! Thanks!

Since it doesn't seem to be your server having a problem seeing as your phone doesn't have a problem, I would try to delete the Emby apps cache on the Shield or simply uninstalling the app and installing it again. Could also try and see if the Emby Android TV app works to confirm if it's the Shield it self that the problem. If nothing important is on the Shield and it can be setup fast again then a complete factory reset. Would be the most simple and easiest fix if it works.

When you have a file with DV and HDR10/10+, coverart plugin shows DV icon, so that's correct. @ebrCouldn't the plugin be modified to optionally read out the track naming or the tags created by MediaInfo plugin to distinguish HDR10/HDR10+?

Neither is this my forum post, nor did I mention anything in that post since I did not write it . The project seems to have evolved since the first post and you find everything here: RatingPosterDB.

Maybe this should be a question it asks me when i import a backup. Whether i want it to be a clone, or a (deep-)copy alongside the instance the backup is from.

Delete device.txt from programdata\data folder of second instance, restart server.

When you created this second instance; did you start from scratch, or did you copy files (specifically the /data/ directory of emby server) from the original server?

I guess it's a problem with proxmox or kernel. Check it later because I don't have the energy to do it now

The least you guys deserve for all the effort that goes into this great product! I'm abandoning my project. Way too many limitations to make it worth while but that's not an Emby issue. Maybe the AA interface could be tweaked to make it more practical but I honestly wouldn't think it's worth the time based on the number of potential users and the other demands on the team's time. Keep focusing where it counts so I can reap the benefits at home . Thanks,

I found this in the syslogs Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: AER: device recovery successful Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: AER: Uncorrectable (Non-Fatal) error message received from 0000:00:01.0 Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Requester ID) Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00100000/00000000 Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: [20] UnsupReq (First) Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: AER: TLP Header: 34000000 01000010 00000000 88468846 Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: AER: device recovery successful Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: AER: Uncorrectable (Non-Fatal) error message received from 0000:00:01.0 Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Requester ID) Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00100000/00000000 Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: [20] UnsupReq (First) Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: AER: TLP Header: 34000000 01000010 00000000 90059005 Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: AER: device recovery successful Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: AER: Uncorrectable (Non-Fatal) error message received from 0000:00:01.0 Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Requester ID) Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00100000/00000000 Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: [20] UnsupReq (First) Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: AER: TLP Header: 34000000 01000010 00000000 88468846 Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: AER: device recovery successful Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: AER: Uncorrectable (Non-Fatal) error message received from 0000:00:01.0 Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Requester ID) Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00100000/00000000 Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: [20] UnsupReq (First) Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: AER: TLP Header: 34000000 01000010 00000000 90059005 Feb 04 12:04:27 eddy kernel: pcieport 0000:00:01.0: AER: device recovery successful I found a solution on this page LINK, adding the option "pcie_aspm=off" to the kernel options helped. Unfortunately, this is a workaround. Although the error does not occur, CUDA still does not work. The oldest driver version I was able to install was 535.98, older versions threw an error when compiling the kernel module. Probably proxmox has too new a kernel for older drivers. All these versions had the same problem: 535.183.01, 535.98, 550.107.02, 550.142, 560.35.03 and 565.77 but then I had a problem with the message in syslog. In the next few days I will check nvidia toolkit, other ffmpeg and I will also check emby logs to see if they have changed.

February 8th. Mission completed! I have all three channels now. Kudos to Carlo! Cannot say too much good about your vendor's slow response. Channels at times do change, get added, deleted or renamed. Hopefully this vendor isn't always this unresponsive. 39 days. But thank your Carlo for sticking with it. You made it happen for sure.

OK we'll take a look at it. Thanks.

Hola, yo en peliculas he conseguido que suene de fondo un tema cuando te metes en ella pero en las series no lo consigo, he puesto una carpeta llamada theme-music en la misma ubicación que están los capítulos dentro de la serie pero no hay manera . dentro tengo un archivo llamado theme.mp3 y nada Solucionado!!!! se ha estropeado el deco y no me daba audio pero funciona

HI, we are working on it. Thanks.

In Chrome, what does the your device section look like on this page? https://hover-pointer-media-query.glitch.me/