Leaderboard

Hi Below is a draft of music tag's that emby supports/imports. Caveats: 1) first pass 2) Support was based on Picard Standards. The chart shows the Picard mappings to other standards (Source: Musicbrainz) 3) To @Happy2Playpoint I added a column for ffprobe support. This is a determining factor for requests to support additional tags. 4) @Luke I wasn't sure about Original year/date. I think it is only used if release date is blank. I hope this is a start, please correct as needed (I am sure I missed something). @cayars when the list is corrected/accurate maybe you can turn it into documentation. -Vicpa Emby _MusicBrainz_Picard_Tag_Map.xlsx

I think I was short on sleep that day. Yes, system.xml is correct.

To me that suggests a firewall issue on host as that is the only thing that should block other LAN clients.

Bonjour, Rien à voir un problème quelconque. Je tiens juste à dire que je trouve Emby vraiment génial ! J'étais sur Plex avant, et je ne regrette pas d'avoir changé. Par contre, si des développeurs voient ce message, j'aurai juste 2 recommandations à faire, concernant la section "Musique" 1 : Il serait bien, dans le client Emby (sur Android TV), d'avoir les informations de "Interprête" quand on lit les fichiers audio. Pour l'instant, on a juste l'artiste de l'album, avec l'album et le nom de la piste. 2 : Quand on choisit "Genre" dans la musique, il serait bien d'avoir une option pour avoir les artistes qui s'affichent, pour l'instant on a juste tous les albums qui s'affichent, ce qui n'est pas pratique si on cherche juste un artiste dans un genre particulier. Voilà c'est tout. Merci beaucoup aux développeurs pour leur travail ! Et merci à eux aussi s'ils prennent en compte les demandent des utilisateurs, pour améliorer l'application au fur et à mesure dans de futures mises à jour. PapaMok

LOL, not at all. We love discussing this topic and I personally learn so much from folks jumping in and adding their experience. Me too! It still needs a few things, but I've pretty much given up on Plex at this point and Emby is my only media server now. Thanks @cayars! Glad to hear a fix is in the works.

Thanks @Happy2Play. @jedd it sounds like you have a reverse proxy inline which is fine to use to distribute apps sharing the same ports but the way you're doing this isn't going to work for Emby. There are two styles of setting up the URL for reverse proxy identification and redirection which are: domain.ext/service service.domain.ext Service of course being the key to know what this is. So for you it would be either https://domain.ext/emby or https://emby.domain.ext. For web browsers either will almost always work and doing the service as part of the path requires no DNS entries or changes so it's the easy method. Using the subdomain.domain.ext method typically requires a CNAME record to be added to to your domain for each new entry. However it doesn't have to be like this. Instead you can setup one time a wild card entry so anything like xyz.domain.ext or 123.domain.ext will get forwarded to your reverse proxy. That also allows you to use a wild card cert for your whole domain vs having to renew all the individual certs. So once setup this way it can actually be cleaner and easier to use as well. Just add a 404 response page in your reverse proxy for any subdomain that doesn't match or forward it to your main site, whichever fits. The reason you need to use the subdomain.domain.ext format is that you have application on hardware devices that you have no control over using the host name. They don't speak "web" but instead use an API and possibly web hooks to communicate with Emby. They except the to take the host name and port variables and use those with a hardcoded API string. As a quick example, let's assume the API is going to use "https:// + hostname + /web/index.html#!/startup/manuallogin.html?serverId=GUID + port" to assemble the API call. Here is what both would look like using the following for the host entry of "great-media.com" with a port of 8920. https://emby.great-media.com/web/index.html#!/startup/manuallogin.html?serverId=GUID:8920 https://great-media.com/emby/web/index.html#!/startup/manuallogin.html?serverId=GUID:8920 If you try and get creative with the hostname entry doing something like "domain.ext/emby:8920" it gets even uglier. Does that make sense? So while doing testing with a reverse proxy seems to work ok in a browser it will be broke for most apps because at best there is an extra "/emby" in the URL that it isn't expecting. So switch to the subdomain.domain.ext method and these problems go away.

Sorry, no not exactly like that at this time. You can, however, do fairly significant visual modifications to the web app using custom CSS. There is a forum out here with lots of examples of that. Thanks.

I've increased the database cache size to 1024 MB and I think it works much better and smoother. Previous it was 96 MB.

I guess, kind of.

When I add metadata to my music videos (year, album, artist, track number etc), it automatically links to the artist in my music library. So, when I go to their page, I see their music videos. My question is, is it possible to have a link like this for the specific album as well? Meaning when I go to an album and see all of the songs, the video will also show at the bottom. Subsequently, the album would be linked to from the music video itself: Am I doing something wrong or is that just not supported?

Hi, it's a good idea, but not supported at this time.

Semi-automatic will do

At the same time doesn't downloading from Settings-Logs accomplish user needs? But don't know how well this works on all platforms.

Yes there are currently limitations of the Store version. App: Emby for Windows 1.1.388.0 &AudioCodec=ac3,eac3,aac,mp3,opus &TranscodeReasons=AudioCodecNotSupported 16:18:59.067 Stream mapping: 16:18:59.067 Stream #0:0 -> #0:0 (copy) 16:18:59.067 Stream #0:1 -> #0:1 (truehd (native) -> ac3 (native)) Browsers are limited also as every browser has its own limitations.

Hi, are you by any chance running the Windows store version of Emby Theater? If so try using the Desktop version of Theater which usually is much more robust in playback. You can download it here: https://emby.media/emby-theater.html

@LukeFor Synology, it would be extremely helpful if we we could make the log folder a configurable path. This would make the log files quite easy to get to quickly using a network share or from File Station in the DSM 7 UI. It might need an intermediate or a confirm screen that does a quick write test to the new path and warns the user if permissions is wrong.

Additional note: After this happens, rebooting or logging off from windows results in endless loading. If I try to reboot, the message "Rebooting..." stays for a very long time and rebooting doesn't happen. The same for logging off. I was only able to use the reset button. But I don't know if there is a connection between this.

If you need to keep the keep emby internal - then I would look at Sony and Panasonic - both have now moved to AndroidTV/OS. For a 'main' TV, personally, the decision to buy a TV should not be based on what software it can run - but on the build quality/Panel/technology, picture processing CPU, black levels, Connectivity etc and what real AV features it has (scaling etc). If a TV lasts lets say 10 years, do you really think that the current TV's are going to complete with a $50 HDMI stick with all the latest Codec's etc. Taking AV1 as an example, when (if?) it becomes the standard, then it's going to mean the majority of TV's made before 2020 cannot play it because the internal hardware is not available ... As an example, I have and still daily use a 12 year old Panasonic TH-46PZ81B Plasma - It's 'apps' (at the time) are long gone, infact it just about had Ethernet, but with an HDMI stick, 1080p content still looks STUNNING - on par with LG OLED for sure in terms of PQ. The build quality and 'Core' features of the set have made it last - in those 12 years, I've probably gone through 3 or 4 Samsung LED TV's because the panels/screens failed ...

Emby for LG TV's 1.0.31 has been released. Stay tuned to the blog for the release announcement.

Emby for LG TV's 1.0.31 has been released. Stay tuned to the blog for the release announcement.

Fricking Cloudflare! Cloudflare caching was on, along with normalising URLs. Disabling the cache (not that important to me) and turning off the normalise made Emby work how it should. Not sure if it was moving to Proxmox or just something else. My external and int IPs were the same, as were MAC Addresses, so not sure why the issue happened. Still sets 'Auto' to 1.5mbps at 720p though, which I can't change anywhere. Changing it works fine now, when before, it would cause a hissy fit. It works! Shh, or it might stop.