All Activity

Fair enough - probably my bad wording and I am confusing the issue??? All I really meant was the optimum solution would be RELEASETYPE built-in to Emby. I wasn't meaning that I wanted this resolved by you. Sorry if I am being misleading here. The script is great as is, but the individual data-entry is going to be painful for many thousands of albums.

I think I'll just ditch all the ARTISTSORT/ALBUMARTISTSORT stuff and just focus on release types, which were the subject of this topic to begin with. Gimme few hours and I should have something workable.

Oh no!!! I've accidently widened the discussion instead of narrowing it, but I do have an answer (sorry, I mean opinion) for you on this... First, lets widen this again (oops!) to ALBUMARTISTSORT, ARTISTSORT, COMPOSERSORT. What happens when one entity (e.g. Person or Group) is all three (ALBUMARTIST, ARTIST, COMPOSER) and the SORT embedded metadata tags all happen to be different and all three map to the same "Sort Title" field??? Emby needs to ultimately make the management call (e.g.): Our customers are more likely to be contemporary-music-focussed, rather than classical-music-focussed - therefore ARTISTSORT takes precedence over COMPOSERSORT, where conflicts arise. Our customers are more likely to be contemporary-music-focussed, rather than classical-music-focussed - therefore ALBUMARTISTSORT takes precedence over COMPOSERSORT, where conflicts arise. Our customers are more likely to be song-focussed, rather than album-focussed - therefore ARTISTSORT takes precedence over ALBUMARTISTSORT, where conflicts arise. Of course, a different philosophy (or system architecture) will create a different set of precedences to follow. My examples are just examples, they may not even be logically correct(?) and they are not my own preferences (I am more contemporary-album-focussed myself). Whatever the "rules" are, could then possibly be documented so everyone knows what they are. "First/Last" would probably seem very inconsistent and confusing - because the "rules" would seem to be changing all the time. So, Emby makes the consistent rules, which then define the coding logic. Of course, consistent and creative tagging gives everyone control over their own set-up, with potentially no conflicts or priority issues to complain about, unless errors are made. Anyway, getting back to my main concern... With no easy way to currently get Album Tags into Emby (e.g. ROONALBUMTAG) and no native bulk editing of Tags within Emby, it is going to take me about 150 hours to add RELEASETYPE Album tags for my music library - and then, what if I change my mind and want to alter this - another 150 hours??? (Emby is a part-time hobby, not a full-time job - so the initial set-up is likely 6+ months - I could likely do this in 6 weeks with Mp3tag - and ongoing changes would be relatively easy.) The script that you created lets me set up EXACTLY the custom Discography pages I want, but I don't want to spend all my time on data entry!!!

What about now? "Are we there yet?"

Since Apple updated their tvOS to 26.4 and you can now enable continuous audio in settings to fix low audio when using sound bars, I get no audio from Emby app. i do however get perfect audio through infuse app which plays my Emby server content without problem. anyone else seen this. I’m guessing Emby app will need an update? Thanks Gary

OK, i finally figured out how to update emby without updating it at all i forced it to update to the latest version with this method for anyone else wanting to update emby on truenas scale. Follow these instructions to a t and it will update to the latest emby. go into the truenas scale dashboard go to apps Click on emby move over to the right side where it says emby and has edit and 3 dots click those 3 dots you will see convert to custom app and let it convert emby into a custom app and wait for the emby server to reload and start again.. Then click edit you will see the hyml for your emby app pop up scroll down to the line that says image you will see on this like the version of emby. change this version of emby to the new emby version available and scroll all the way to the bottom of this page when done and click save let it do it's thing and once done it will have updated your emby server to the latest version because it pulled the update that you forced and updated it. That is all you need to do and now you can do it every single time there's an update showing that you can't get because the one's in charge don't send updates out to us,

This is client based? https://emby.media/support/articles/Premiere-Limits.html

The first two would be the easiest because the server is the one enforcing the limit so it could do this without any involvement of the apps.

I can see 3 possible limit notifications: 1. Max Simultaneous video streams (system) 2. Max simultaneous video streams (users 3. Device limit We should also have guidance how to remediate these.

Hi - I had it happen again once the other day, but I can't replicate it. I turned on debugging until reboot, so hopefully it will catch something. I was pretty confident of the time.

Hello, I am trying to send Emby notifications to a webhook endpoint (n8n). The problem is: the Test button for the notification service works but actual notifications from real events do not seem to reach the webhook at all What I am trying to accomplish I want Emby to send real notification events to my webhook endpoint, for example authentication events and report notifications such as new media notifications. What happens When I click Test in the notification service configuration, Emby sends an HTTP POST to my webhook endpoint and gets HTTP 200 back. But when real events happen, Emby only logs: Debug Notifications: Sending notification to Emby Server User Notifications N8N: ... and then nothing is received by the webhook endpoint. What I expected I expected Emby to send an HTTP POST to the configured webhook endpoint for real events, just like it does during the test. What I already checked I tried to narrow this down as much as possible: Webhook test works In the Emby logs, testing the notification service produces a real outgoing HTTP request and a successful response: Info HttpClient: POST http://10.20.1.24:5678/webhook/... Info HttpClient: Http response 200 from http://10.20.1.24:5678/webhook/... after 139ms So the endpoint is reachable and the URL is correct. Real notifications appear to stop before the actual HTTP request For real events, the logs show lines like: Debug Notifications: Sending notification to Emby Server User Notifications N8N: martin Has Authenticated on Martins-NAS ... Debug Notifications: Sending notification to Emby Server User Notifications N8N: New Media Report Notification But I do not see a following HttpClient: POST ... line for those real events, and nothing arrives at the webhook endpoint. Debug logging is enabled I enabled debug mode and reproduced the problem again. I have enabled almost all notification options without a limit on user or library: Any Any help is appreciated. embyserver.txt

This is not a bad idea but will require a fair amount of work because the apps all handle this locally. So something would have to be built to notify the server of these situations and all apps would need to be updated.

Hello, I figured it out by editing the default ports in the config/system.xml file and restarting server. Thought I had tried that already but was unsuccessful, hence the post. Maybe I didn't do it right the first time, dunno. Thanks tho

That would be determined by the exact message they received. What was that?

Please provide the ffmpeg log.

I've had some family tell me they've had warnings about streaming limits being reached. I'm not sure why, since I check and they are well below any threshold or limit. It would be great to have some alerting or notification to know when that is happening or how to troubleshoot it/remediate it. Is it a user limit? system limit? Device limit?

I just rebuilt me database, and found that for some reason, it was adding a collections folder. I stopped it and removed the option from the movies library. After scanning was complete, collections folder remained. I followed directions and deleted the items in the collections folder, the collections folder remained. I followed directions further "you must delete all individual collections within the library, then run a library scan to remove the library shell" but this option is unavailable. I went further and went to "C:\Users\YourUser\AppData\Roaming\Emby-Server\programdata\data\collections" and this item does not exist. I can not find any further info as to next step. Can someone please help.

Hello, I believe that was set some time ago, before I lost access, that is. I've had this running for several years until re-creating a new container.

This sometimes happens when providers are using some sort of geo-IP or user agent block, or you’ve not entered the right port details etc. Make sure you’re if you’re using a proxy on your mobile app that you’re using the same one where your installation is.

I don’t have the skills to dissect your logs but it’s pretty much always the provider using some non-standard method for keeping the connection alive. I would suggest using a dedicated app that’s been designed to handle the peculiarities. The other alternative would be to proxy the stream somehow.

ACME .Net libraries and tools are available for developers to build or integrate ACME clients. A feature built into Emby to request, deploy and renew TLS certs could solve a lot of headaches. Granted it could create some too though overall I would say it lands on the positive side.

Thanks! And yeah, last night I was working on the typography a lot, still lots to do in that area. some areas like the legends were never updated. I'll certainly look at your CSS. Still fighting w/ overriding every user theme option selected but slowly getting there. Sometimes I wonder if the juice is worth the squeeze there. It's getting frustrating at moments.

Well, it's a Windows-only software and you can configure it yourself.

Pretty niche yes, but could be nice to signify episodes that are finales and make their apperance slightly different, i.e. [ finale ] tag. I support this.