Leaderboard

The zealotry, the license fanaticism, the gnu org and their userland tools? Fair number of things i'm not a fan of. I don't completely hate slackware or alpine ,for example but shrug. My *nix exposure went from SvR4 to free/net/openbsd with a smattering of solaris, linux just has never been compelling for me.

@Abobadercan this be done? Then a mod could move existing topics into the catagory.

OK I sorted it out. Came back around to just looking at the cifs man page - https://linux.die.net/man/8/mount.cifs. My best estimate was this is what is used under the hood for docker desktop for the cifs volume type. Realized from that the option I really need to care about here are `uid` and `gid` which were not present in any example I could find about cifs for docker in general. Then was realizing the changes I was trying might not be taking effect as the volume was persistent...So I was essentially missing the proper parameters and I was testing this change incorrectly (i needed to stop and remove the container and then drop the backup volume and do an 'up' to put the compose all back in order with the new volume setting). I created a powershell script just to run through the steps needed to make the mount change effective in the docker-compose. This allowed for faster iteration to find out what the issue was. #stop container docker-compose stop #remove stopped container (to remove named volume) docker-compose rm -f #drop volume docker volume rm emby_emby-backup #recreate container and volume with new options docker-compose up -d #show us the permissions on the mount area docker exec embyserver ls -lah /mnt Here's what was actually needed in the end for the volume config to make the write possible. I tried a number of config options, but these two are all that was needed. emby-backup: driver: local driver_opts: device: "//192.168.0.80/toad/Container-Backups/Emby" type: "cifs" o: "username=myuser,password=mypassword,vers=3,sec=ntlmsspi,uid=2,gid=2" emby-data: driver: local Here's the container mount config for that volume (not much special here, omitted all but the backup mount): volumes: - emby-backup:/mnt/emby-backup How did I know to use user and group id of "2" for the cifs options? This below is in the docker compose template from emby docs. Because these are commented out, it will default as uid and gid 2 -> this is the 'bin' user. # environment: # - UID=1000 # The UID to run emby as (default: 2) # - GID=100 # The GID to run emby as (default 2) # - GIDLIST=100 # A comma-separated list of additional GIDs to run emby as (default: 2) You can confirm this user with a terminal into the container like below. Note the "bin" user column for /system/EmbyServer. This will confirm you are looking at the right process in this context (in case you commented the above lines and changed to a new UID/GID you could translate that for the cifs options). > docker exec embyserver ps -a PID USER TIME COMMAND 1 root 0:00 s6-svscan -t0 /var/run/s6/services 33 root 0:00 s6-supervise s6-fdholderd 172 root 0:00 s6-supervise emby-server 175 root 0:00 sh ./run 198 bin 1:20 /system/EmbyServer -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3 570 root 0:00 ps -a This will allow you to mount a share from your NAS right into the container (instead via the container host running docker desktop or similar), making the config a bit more portable. The point in general for involving a share for backups is to put them somewhere besides where the container is running (NAS and docker host are separate in my case). The end effect of the /mnt area I'm using is like below. Most of my mounts are read-only by design (so emby can't mess with my raw file data on the NAS). emby-backup is the only one here that is owned by bin user and bin group. > docker exec embyserver ls -lah /mnt total 8K drwxr-xr-x 12 root root 4.0K Apr 6 01:58 . drwxr-xr-x 1 root root 4.0K Apr 6 01:58 .. drwxr-xr-x 2 root root 0 Mar 15 04:04 audio-books drwxr-xr-x 2 root root 0 Dec 24 02:09 common-photos drwxr-xr-x 2 bin bin 0 Apr 6 01:59 emby-backup drwxr-xr-x 2 root root 0 Apr 4 15:49 movies drwxr-xr-x 2 root root 0 Mar 31 20:36 music drwxr-xr-x 2 root root 0 Apr 5 05:02 photos-c drwxr-xr-x 2 root root 0 Apr 4 03:52 photos-j drwxr-xr-x 2 root root 0 Apr 2 01:48 tv drwxr-xr-x 2 root root 0 Feb 23 04:46 vidbox drwxr-xr-x 2 root root 0 Mar 17 03:18 videos-misc One other wrench that made this harder to troubleshoot and I didn't see mentioned anywhere on the interwebs -> chmod or chown commands were not able to change the mount. So once the volume is created, it is "stuck" in that cifs options configuration and won't change. You must use the uid and gid options when re-creating the volume. This is something to bear in mind for production-related aspects (e.g. this would equate to an outage potentially for a critical business system). TBH, this does seem like something important for the backup plugin for emby. You want that volume you use for backups to be living somewhere else, and this is a reasonable way to accomplish that. Lastly, if you are in a bind and simply want to clone (to backup) the config volume for emby (or any other containers) and are using Docker Desktop this will make it a snap: https://hub.docker.com/extensions/docker/volumes-backup-extension.

Yea, very sad. No interest in scale/linux for my server here. So "worst" case scenario i just throw full blown freebsd on my nas. Might poke at xigma. But on the other hand It's looking fairly likely that it's going to be forked, not sure whether they'll wait till core goes eol or whatever- but I'm keeping my eye out.

I recently found a need to look up additional information on a director. I was hoping to look at the director's profile and see not only the movies I had in my collection but also a list of other movies that they have directed. This would be displayed below the library's current movies. ex: My movies: Movie 1, Movie 2 Other movies by this person: Movie 3, Movie4 ================ This could help one expand their library and to discover a missing gem.

At the moment once themes finish, silence ensues. I'd rather have the theme start playing again. It also doesn't play after the film/show, I don't think? I love having it, it approximates the mood-setting of a DVD or Blu-ray menu, and avoids horrible silences, but it shuts off too much.

I know the answer to this is probably going to be no..... ...but.... A standalone music player for iOS would be very useful. Trying to get the wife to use the full client for music is just not happening. Something that was simple and intuative and quick and easy to use would be killer, something like spotify. The simpler the app is to use, the better. If all else fails, I have a project that's on the back burner that was an iOS music player for subsonic, but I could always target emby as well. It had an spotify a-like interface. Screenshot from as far as I got with the UI, it was playing back music from the server.

It'd be amazing if Emby has a feature like this one: setup a recording and: specify the number of equal minutes that the recording will be split in the names of the filenames .ts equal parts (or be given an increasing number) (Optional) ex: lets say I want to record a video from 09:00 AM - 12:0 PM, from the same Channel in 30 minutes equal parts, check screenshot. I'd select 09:00 and 12:00 as start and end time have an option called "Split recording every [ n ] minutes" and replace [ n ] with "30" for instance have an option for "Part names" to give the filenames a name at the end My recordings will be as follows: first recording started from 09:00 - 09:30 AM, filename will be "Recording 02 Feb 2024 - part 1.ts" 2nd recording started from 09:31 - 10:00 AM (or 09:30 - 10:00 AM), filename will be "Recording 02 Feb 2024 - part 1.ts" etc Note 1: I've m mentioned 09:31 AM instead of 09:30 AM bcz in some cases I've noticed some channels on my end end up not working well if i don't leave a 1 min break in between Note 2: if the time stamps are not equal, i.e. 09:00 AM - 11:45 AM, then the same equal splitting happens from beginning until end but the last part won't be 30 minutes instead it will be less and that's totally fine. Currently I am doing this manually and I think there would be other Emby users that could use this feature : ) Thank you!

I guess milage may very as the card doesn't support Virtualization. https://www.intel.com/content/www/us/en/support/articles/000093216/graphics/processor-graphics.html https://community.intel.com/t5/Graphics/Intel-ARC-A380-questions/m-p/1522997/highlight/true#M122239 Found this interesting

The progress bar is beside the point, I shouldn’t have even mentioned it. It could be supersized but doesn’t change the fact that skip buttons are missing

Step 1 Create a separate persistence model by using simple/poco classes like this: public class MyConfiguration { public string Property1 { get; set; } public string Property2 { get; set; } public IList<MyConfigDetailItem> Details { get; set; } = new List<MyConfigDetailItem>(); } public class MyConfigDetailItem { public string DetailProperty1 { get; set; } public string DetailProperty2 { get; set; } } Step 2 Implement loading and saving of your configuration data. Common options are: All-Custom Loading and Saving Do in which ever way you like, as if Emby server wouldn't even be part of the game Load/Save JSON Use Emby's Emby SDK Reference: IJsonSerializer where you use Emby SDK Reference: IJsonSerializer.SerializeToFile(Object, String) and Emby SDK Reference: IJsonSerializer.DeserializeFromFile<T>(String). You can use Emby SDK Reference: IApplicationPaths to determine the right folder for saving Use the classic way for persisting plugin configuration This works by defining a ... Step 3 Remove the loading/saving of the UI class which you currently have.Instead: When the config UI is to be displayed.. load your configuration model from Step1 using the procedure from Step2 Set the properties of the UI class using the values from the configuration model How you add the detail items depends on your chosen way of presentation (one of the ways laid out in my previous post) The UI will be shown When the user saves the configuration from the UI load your configuration model from Step1 using the procedure from Step2 (or use a static instance you may have in memory) set the properties of your configuration model to the values of the UI model save your configuration model to disk using the procedure from Step2 Summing Up This is clearly more involved than the "easy" method, but it provides flexibility and independence between the UI model and the storage model. I'm always doing it this way.

Yes, it's correct that this isn't supported directly. I should mention in this context that the idea of serialized saving of UI classes hasn't been part of the original concept of GenericEdit (the basis for having settings UI defined by C# classes without needing to write html/js code) at all. We just recognized at a later time that serialized saving of a UI class allows for an extremely easy way for developers to have a plugin configuration plus persistence model all at once with minimal code. It's a good fit for many (simple) cases but not for all cases, and your case just goes beyond those simple cases. So, why not add support for it now or later? I had surely thought about it, but the problem is that there's no one-fits-all solution. There are many different ways for how such a "one-to-many" relation can be represented in the UI: A selection list Which renders to an HTML SELECT element, either as dropdown or a multiline select There might be buttons for add, edit delete A plaintext section with line breaks A button aside would bring you to another page or dialog to configure the items A GenericList Which renders to what you can see in the existing sample. List can be nested, have 1 or 2 buttons, a toggle or a progress bar and each item can have subitems A number of repeated child UI sections (Emby SDK Reference: EditableObjectCollection). Each of those case is represented in the UI class in an entirely different way and that's the reason why there's no point in standardizing this for saving it the "super-easy" way. But let's get to a practical recipe for cases like yours..

Thank you for the suggestion, however, for some reason the private key was causing an issue. In the end I used Dicken's solution and that worked.

What's this worth? 50$ per version, 2$ a month? Plugin built into emby, with schedule task to recreate the collections. On schedule it will pull list data from API, delete existing collection if exists and recreate and then log activity so you can see the history from admin ui. Not sure what the other person is doing with pulling posters etc as the items will use whatever poster they have. Im sure I could have it so the collection could have a custom image/schedule but this adds complexity and time = $$$ and this currently meets the needs of what someone else was looking for.

Yep. Paste into notepad(++) first, always.

I had started an example a while ago, I'll try to complete it and add it to the beta SDK shortly. Emby SDK Reference: IPluginWizardView Custom saving means you do the saving on your own instead of saving the UI class directly. So, basically this means that you create your own model for the configuration which you persist to disk (or elsewhere) using a serialization technique of your choice. Once you need the data you do the loading on your own. Once you need the data for displaying UI, you load your persisted data model and use it to set the properties of your UI class. For saving, you do it the other way round. The models are documented, e.g. for ButtonItem: Emby SDK Reference: EditorTypes.ButtonItem I'll try to include an example in the advanced sample code mentioned above.

I dont need to use the product personally to be able to create/sell plugins/integrations/apps for people. I dont think I have ever used it personally beyond testing it every now and then on major versions. I dont use alot of products personally but I know how their APIs work for other integrations lol. Im confused how these posts are worthless, there is a provided API/SDK the API says the field is used as a time out the Dev says its a yes no flag but the information given wasnt correct.... So I guess if you dont want people to use the SDK, then remove it. Its not documented for the most part, not every device client functions the same way, so the SDK becomes very hard to use when dealing with devices and interactions with the users UI when they dont implement the same functionality, but yet its somehow pointless to ask for the clarification on how its expected to work on each device since there seems to be confusion on how its working from the Dev themselves .... This is what Im talking about in the SDK, TimeoutMs is a nullable int, when null it will show with a close button, when not null it will show as a non settable (short 2-3 second) faded toast. Sure seems clear, but from the above use he says on a firestick null and not null make no difference, but for the web browser it does, so now this complicates things even more since it doesnt seem that the clients are coded in the same format, so whos issue is that? If I made a plugin and said a popup will appear that requires a user to close it and then some UIs dont people will come complain to me because they didnt see the message or something on XYZ device .... Hence I now apparently need to make a matrix of what devices support what commands. _sessionManager.SendMessageCommand(null, sessionId, new MessageCommand { Header = "Warning", Text = msg, TimeoutMs = _pluginUiOptions.MessagesRequireClose ? null : 1 }, new CancellationToken());

I am the other guy I guess, but I hope you do not spam the forum, you start to show good post, if you keep this up, I will remove the moderation from your account, thanks.

Nice easy answer, just delete the = and leave the quotes or infact use the short code for the option i.e. -i instead of --included-library=

I figured it out. My emby docker was set to bridge mode. What was going on was on my local network, Emby wasn't connecting to new devices automatically. I had to enter my server name. Thanks for the response.

I just completely nuked my Plex installs, deleted my account, and officially gave Plex the f-off email. They refused to clear my account of any personal information along with past history unless I deleted it (and I have to wait 30 days before they actually purge and they refused to do it immediately), on top of this they wouldn't agree to allowing me to use my license on a new account if I ever came back. Bridge officially burned. Bumping this thread again and cheering you guys on to get some form of PMM over here!

I use Lite tv everyday but since I am in a country not supported by emby guide data, I had to edit my channels and xml provider. Its not that difficult. But yeah, if the cost of something I am not using is removed and it relieves the emby team why not.

Hi I can confirm turning off subtitles helped , ive switched on "Allow subtitle extraction on the fly" and that seems to have fixed it. I really should ahve tried that when i saw subtitles mentioned in the logs, Sorry

Yes that's what I have seen so fare. I have seen it play trailers, behind the scenes, featurettes, other. After skipping a couple of times I finally get to a movie. I have rotated logs, and shuffle played 1 of my collections. Here is how I can reproduce it every time I do this. Movies -> Collections -> any collection. embyserver (3).txt

Hi, yes it's on the to do list. It shouldn't be too difficult given what is currently happening.

This is very helpful for my setup. Am I correct in remembering that this change will need to be applied every time Emby is patched to a new version?

Looks like, not sure why it how, but the "run on windows startup" got re checked. So two servers got started... Not sure how. The live tv refresh task was failing and now it passes. I checked the event viewer. 0knkk0n knnnknk0k0 In the system log, it did report the Emby server serice terminated unexpectedly. What I did find, is on the restart it failed because it couldn't contact the ad for the user login. So I put a dependency on dhcp. Hopefully that will fix the restart.

I will test an MP4 container file

https://community.roku.com/t5/Solving-playback-issues/Roku-Dolby-Vision-support-in-Matroska-MKV-containers Most Roku TV models made presently only support DolbyVision inside the MP4 container. You can try posting in the thread above and getting a response from Roku. Emby is allowing the Roku to access the file directly unmodified and the Roku video player has control of the playback. We cannot force the video player to choose. Roku themselves determine this support.

Not seeing why it shutdown (embyserver-63847851954.txt) but the other two logs suggest you have the app and service running and the database is locked. 2024-04-05 20:50:09.473 Info Main: Emby Command line: C:\Emby-Server\system\EmbyServer.dll -service and 2024-04-05 20:50:38.072 Info Main: Emby Command line: C:\Emby-Server\system\EmbyServer.dll causing logs of errors *** Error Report *** Version: 4.8.3.0 Command line: C:\Emby-Server\system\EmbyServer.dll Operating system: Microsoft Windows 10.0.22631 Framework: .NET 6.0.27 OS/Process: x64/x64 Runtime: C:/Emby-Server/system/System.Private.CoreLib.dll Processor count: 20 Data path: C:\Emby-Server\programdata Application path: C:\Emby-Server\system SQLitePCL.pretty.SQLiteException: Busy: database is locked SQLitePCL.pretty.SQLiteException: Exception of type 'SQLitePCL.pretty.SQLiteException' was thrown. at SQLitePCL.pretty.SQLiteException.CheckOk(sqlite3 db, Int32 rc) at SQLitePCL.pretty.StatementImpl.MoveNext() at SQLitePCL.pretty.DatabaseConnection.Execute(IDatabaseConnection This, String sql) at Emby.Server.Implementations.Data.SqliteItemRepository.DeleteChapters(Int64 itemId, MarkerType[] markerTypes) at Emby.Providers.Markers.AudioFingerprintManager.UpdateSequencesForSeason(Season season, SeasonFingerprintInfo seasonFingerprintInfo, Episode episode, LibraryOptions libraryOptions, IDirectoryService directoryService) Source: SQLitePCL.pretty TargetSite: Void CheckOk(SQLitePCLEx.sqlite3, Int32) Need to ensure app and service are shutdown and relauch service to see if locked database resolves itself. If not you will need to do the steps in the KB for Locked databases. Also anything in Windows event viewer?

10.0.12 2024-04-06 09:49:42.312 T:3888 error <general>: Exception ignored in thread started by 2024-04-06 09:49:42.313 T:3888 error <general>: : 2024-04-06 09:49:42.313 T:3888 error <general>: <bound method Library.KodiStartSync of <database.library.Library object at 0xc1b747e8>> 2024-04-06 09:49:42.313 T:3888 error <general>: 2024-04-06 09:49:42.317 T:3888 error <general>: Traceback (most recent call last): 2024-04-06 09:49:42.317 T:3888 error <general>: File "/storage/.kodi/addons/plugin.video.emby-next-gen/database/library.py", line 160, in KodiStartSync 2024-04-06 09:49:42.320 T:3888 error <general>: 2024-04-06 09:49:42.320 T:3888 error <general>: self.RunJobs() 2024-04-06 09:49:42.320 T:3888 error <general>: 2024-04-06 09:49:42.321 T:3888 error <general>: File "/storage/.kodi/addons/plugin.video.emby-next-gen/database/library.py", line 667, in RunJobs 2024-04-06 09:49:42.324 T:3888 error <general>: 2024-04-06 09:49:42.325 T:3888 error <general>: if self.worker_update(): 2024-04-06 09:49:42.325 T:3888 error <general>: 2024-04-06 09:49:42.325 T:3888 error <general>: 2024-04-06 09:49:42.325 T:3888 info <general>: Skipped 6 duplicate messages.. 2024-04-06 09:49:42.325 T:3888 error <general>: ^ 2024-04-06 09:49:42.326 T:3888 info <general>: Skipped 19 duplicate messages.. 2024-04-06 09:49:42.326 T:3888 error <general>: 2024-04-06 09:49:42.326 T:3888 error <general>: File "/storage/.kodi/addons/plugin.video.emby-next-gen/database/library.py", line 356, in worker_update 2024-04-06 09:49:42.327 T:3888 error <general>: 2024-04-06 09:49:42.328 T:3888 error <general>: Continue, SQLs = self.ItemOps(int(index / RecordsPercent), index, Item, SQLs, WorkerName, KodiDBs, ProgressBar, StartSync) 2024-04-06 09:49:42.328 T:3888 error <general>: 2024-04-06 09:49:42.328 T:3888 error <general>: 2024-04-06 09:49:42.329 T:3888 info <general>: Skipped 20 duplicate messages.. 2024-04-06 09:49:42.329 T:3888 error <general>: ^ 2024-04-06 09:49:42.330 T:3888 info <general>: Skipped 104 duplicate messages.. 2024-04-06 09:49:42.330 T:3888 error <general>: 2024-04-06 09:49:42.330 T:3888 error <general>: File "/storage/.kodi/addons/plugin.video.emby-next-gen/database/library.py", line 580, in ItemOps 2024-04-06 09:49:42.332 T:3888 error <general>: 2024-04-06 09:49:42.333 T:3888 error <general>: Ret = self.ContentObject.change(Item) 2024-04-06 09:49:42.333 T:3888 error <general>: 2024-04-06 09:49:42.333 T:3888 error <general>: 2024-04-06 09:49:42.333 T:3888 info <general>: Skipped 9 duplicate messages.. 2024-04-06 09:49:42.333 T:3888 error <general>: ^ 2024-04-06 09:49:42.334 T:3888 info <general>: Skipped 30 duplicate messages.. 2024-04-06 09:49:42.334 T:3888 error <general>: 2024-04-06 09:49:42.334 T:3888 error <general>: File "/storage/.kodi/addons/plugin.video.emby-next-gen/core/season.py", line 48, in change 2024-04-06 09:49:42.335 T:3888 error <general>: 2024-04-06 09:49:42.336 T:3888 error <general>: self.SQLs["video"].update_season(item['KodiParentId'], item['IndexNumber'], item['Name'], item['KodiItemId']) 2024-04-06 09:49:42.336 T:3888 error <general>: 2024-04-06 09:49:42.336 T:3888 error <general>: File "/storage/.kodi/addons/plugin.video.emby-next-gen/database/video_db.py", line 396, in update_season 2024-04-06 09:49:42.339 T:3888 error <general>: 2024-04-06 09:49:42.339 T:3888 error <general>: Name = self.cursor.fetchone()[0] 2024-04-06 09:49:42.339 T:3888 error <general>: 2024-04-06 09:49:42.339 T:3888 error <general>: 2024-04-06 09:49:42.339 T:3888 info <general>: Skipped 10 duplicate messages.. 2024-04-06 09:49:42.339 T:3888 error <general>: ~ 2024-04-06 09:49:42.339 T:3888 info <general>: Skipped 21 duplicate messages.. 2024-04-06 09:49:42.339 T:3888 error <general>: ^ 2024-04-06 09:49:42.340 T:3888 info <general>: Skipped 2 duplicate messages.. 2024-04-06 09:49:42.340 T:3888 error <general>: 2024-04-06 09:49:42.340 T:3888 error <general>: TypeError 2024-04-06 09:49:42.340 T:3888 error <general>: : 2024-04-06 09:49:42.340 T:3888 error <general>: 'NoneType' object is not subscriptable 2024-04-06 09:49:42.340 T:3888 error <general>: 2024-04-06 11:24:50.526 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:24:50.526 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:25:00.534 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:25:00.534 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:25:10.542 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:25:10.542 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:25:20.548 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:25:20.548 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:25:30.552 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:25:30.552 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:25:40.557 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:25:40.557 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:25:50.563 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:25:50.563 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:26:00.581 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:26:00.581 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:26:10.589 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:26:10.589 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:26:20.605 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:26:20.605 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:26:30.612 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:26:30.612 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:26:40.618 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:26:40.618 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:26:50.625 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:26:50.625 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:27:00.635 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:27:00.635 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:27:10.643 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:27:10.643 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:27:20.649 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:27:20.649 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:27:30.655 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:27:30.655 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:27:40.668 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:27:40.668 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:27:50.681 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:27:50.681 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:28:00.686 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:28:00.686 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:28:10.692 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:28:10.692 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:28:20.704 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:28:20.704 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:28:30.712 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:28:30.712 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:28:40.723 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:28:40.723 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:28:50.727 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:28:50.727 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:29:00.734 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:29:00.734 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:29:10.750 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:29:10.750 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:29:20.754 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:29:20.754 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:29:30.759 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:29:30.759 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:29:40.766 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:29:40.766 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:29:50.773 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:29:50.773 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:30:00.779 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:30:00.779 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:30:10.785 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:30:10.785 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:30:20.789 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:30:20.789 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated 2024-04-06 11:30:30.793 T:3887 info <general>: Skipped 9 duplicate messages.. 2024-04-06 11:30:30.793 T:3887 info <general>: EMBY.database.library: open_EmbyDBRW waiting: updated

Yes we would need to see the server log for a specific example per the instructions in link above. Also what is your set library metadata provider order on that library?

Currently a bug but Emby /programdata/metadata/people.

no problem i will It seems only to be a few apps that do it, Emby Spotify and Youtube. Also i dont get instant sound coming through when i switch on the tv and start watching a tv station, the receiver comes on automatically and then it goes to the tv mode, no sound comes through the speakers, eventually you start to hear a dull hiss and then the sound starts to come through, im not sure if its a tv or receiver problem. The tv is still under 5 year warranty but the receiver is older from 2014. I just discovered the server was transcoding audio material when i played dts formats, so that had stopped due to disabling audio transcoding, i have enabled it again and it is transcoding dts material again, my tv only supports dolby formats you see.

تم الحل

I added the show and by default I got English per my settings. Changed the show settings to Spanish/United States and ended up with English titles and happen overview on episodes. Series overview was correctly in Spanish. @Lukethere still seems like a disconnect somewhere as it should get the available language. I will guess since there is no official-spa it fell back to episode? As we don't see the failure ""NotFoundException: error fetching "," error on language. 2024-04-05 14:58:20.009 Info HttpClient: GET https://api4.thetvdb.com/v4/series/389597/episodes/official/spa?page=0 2024-04-05 14:58:20.130 Info HttpClient: GET https://api4.thetvdb.com/v4/episodes/7979142/extended episode data I guess translation is lost at this point so parsing language doesn't happen? { "status": "success", "data": { "id": 7979142, "seriesId": 389597, "name": "I’m Used to It", "aired": "2024-01-07", "runtime": 24, "nameTranslations": [ "jpn", "kor", "eng", "pt", "deu", "fra", "spa", "rus", "ita" ], "overview": "十数年前。「ゲート」と呼ばれる、異次元とこちらの世界を結ぶ通路が出現し、ゲートの向こう側に潜むモンスターと戦う者を、人々は「ハンター」と呼んだ。\r\nハンターは覚醒時の魔力量によってランク分けされ、水篠旬は最も低いE級の中でも最弱と言われていた。\r\nある日、ダンジョンに参加した旬。ダンジョンをクリアするも、その奥にはもう一つの入り口があった。", "overviewTranslations": [ "jpn", "kor", "eng", "pt", "deu", "fra", "spa", "rus", "ita" ], "image": "https://artworks.thetvdb.com/banners/v4/episode/7979142/screencap/6580af81ebb87.jpg", "imageType": 11, "isMovie": 0, "seasons": [ { "id": 1871836, "seriesId": 389597, "type": { "id": 1, "name": "Aired Order", "type": "official", "alternateName": null }, "number": 1, "nameTranslations": null, "overviewTranslations": null, "companies": { "studio": null, "network": null, "production": null, "distributor": null, "special_effects": null }, "lastUpdated": "2024-04-02 19:33:43" }, { "id": 1871837, "seriesId": 389597, "type": { "id": 3, "name": "Absolute Order", "type": "absolute", "alternateName": null }, "number": 1, "nameTranslations": null, "overviewTranslations": null, "companies": { "studio": null, "network": null, "production": null, "distributor": null, "special_effects": null }, "lastUpdated": "2024-04-04 08:50:54" } ], "number": 1, "seasonNumber": 1, "lastUpdated": "2024-02-05 09:42:46", "finaleType": null, "year": "2024", "productionCode": "", "nominations": null, "characters": null, "contentRatings": [ { "id": 27, "name": "16", "country": "bra", "description": "Suitable for viewers over the age of 16", "contentType": "", "order": 0, "fullname": null } ], "remoteIds": [ { "id": "https://gamma.app/public/Solo-Leveling-1-Ep1--8gy8h1h07hjn71c", "type": 4, "sourceName": "Official Website" } ], "tagOptions": [], "trailers": [], "networks": null, "studios": null, "companies": [ { "id": 2908, "name": "A-1 Pictures", "slug": "a-1-pictures", "nameTranslations": [ "eng" ], "overviewTranslations": [], "aliases": [], "country": "jpn", "primaryCompanyType": 2, "activeDate": "2005-05-09", "inactiveDate": null, "companyType": { "companyTypeId": 2, "companyTypeName": "Studio" }, "parentCompany": { "id": 4641, "name": "Aniplex", "relation": { "id": null, "typeName": null } }, "tagOptions": null }, { "id": 372, "name": "Tokyo MX", "slug": "tokyo-mx", "nameTranslations": [ "eng" ], "overviewTranslations": [], "aliases": [], "country": "jpn", "primaryCompanyType": 1, "activeDate": null, "inactiveDate": null, "companyType": { "companyTypeId": 1, "companyTypeName": "Network" }, "parentCompany": { "id": null, "name": null, "relation": { "id": null, "typeName": null } }, "tagOptions": null } ], "translations": { "nameTranslations": [ { "name": "I’m Used to It", "language": "jpn" }, { "name": "I'm Used to It", "language": "kor" }, { "name": "I'm Used to It", "language": "eng" }, { "name": "Estou acostumado", "language": "pt" }, { "name": "Ich bin es bereits gewohnt", "language": "deu" }, { "name": "J'ai l'habitude", "language": "fra" }, { "name": "Ya estoy acostumbrado", "language": "spa" }, { "name": "Я привык к этому", "language": "rus" }, { "name": "I'm Used to It", "language": "ita" } ], "overviewTranslations": [ { "overview": "十数年前。「ゲート」と呼ばれる、異次元とこちらの世界を結ぶ通路が出現し、ゲートの向こう側に潜むモンスターと戦う者を、人々は「ハンター」と呼んだ。\r\nハンターは覚醒時の魔力量によってランク分けされ、水篠旬は最も低いE級の中でも最弱と言われていた。\r\nある日、ダンジョンに参加した旬。ダンジョンをクリアするも、その奥にはもう一つの入り口があった。", "language": "jpn" }, { "overview": "10여 년 전. '게이트'라고 불리는 다른 차원과 이쪽 세계를 이어주는 통로가 나타났고 게이트 너머에 숨어 있는 마수와 싸우는 자들을 사람들은 '헌터'라고 불렀다. 헌터는 각성 시의 마력량에 따라 랭크가 나뉘었고 성진우는 가장 낮은 E급 중에서도 최약이라고 불렸다. 어느 날, 던전 공략에 참가한 성진우. 던전을 클리어했지만 그 안에서 또 하나의 입구가 발견됐는데...", "language": "kor" }, { "overview": "Around ten years ago, gates that connected our world to another dimension began to appear, leading to the rise of hunters who would traverse these gates to fight the magic beasts within. Sung Jinwoo, E-Rank hunter, is the weakest of them all.", "language": "eng" }, { "overview": "Há mais de dez anos, estranhos portais vêm se abrindo por todo o mundo, e por trás deles há dungeons cheias de monstros. Desde então, algumas pessoas, os caçadores, despertam poderes que as permitem entrar nas dungeons, derrotar os monstros e trazer de volta artefatos muito valiosos, mas uma vez despertado, o poder não se altera mais. Jinwoo é um caçador de Rank E, o mais baixo, e sempre tem problemas nas dungeons, mas ele precisa do dinheiro, então continua se arriscando. Mas a dungeon em que seu grupo entrou pode ser muito pior do que parecia inicialmente...", "language": "pt" }, { "overview": "Jin-Woo Sung ist als schwächster Hunter bekannt und muss dementsprechend einiges Gerede seiner Hunter-Kollegen über sich ergehen lassen. Doch Ju-Hee Lee, eine junge Heilerin, ist stets um ihn besorgt und hilft ihm, Anschluss zu finden.", "language": "deu" }, { "overview": "Il y a un peu plus de dix ans, des portails reliant notre monde à des dimensions alternatives sont apparus. Ceux qui ont éveillé leurs capacités pour combattre les hordes de monstres qui en surgissent sont appelés des « chasseurs », classés selon des rangs bien définis. Ces guerriers sont indispensables à la survie de l'humanité.", "language": "fra" }, { "overview": "A Jin-Woo Sung lo conocen el cazador más débil de la humanidad, lo que lo convierte en objeto de burla de sus compañeros, aunque Ju-Hee Lee, una joven sanadora, siempre se preocupa por él y le ayuda a hacer amigos.", "language": "spa" }, { "overview": "Около десяти лет назад начали появляться врата, которые соединяли наш мир с другим измерением, что привело к появлению охотников, которые пересекали эти врата, чтобы сражаться с магическими зверями внутри. Сон Джин Ву, охотник Е-ранга, самый слабый из них.", "language": "rus" }, { "overview": "Circa dieci anni fa, iniziarono ad apparire dei portali che collegavano il nostro mondo a un'altra dimensione, portando all'ascesa di Hunter che attraversavano questi cancelli per combattere le bestie magiche al loro interno. Sung Jinwoo, Hunter di grado E, è il più debole di tutti.", "language": "ita" } ], "aliases": null }, "awards": [] } } UI

I'm on 9.4.19 and have the same issue. It will run for days without moving. kodi.log

Yes, great idea. I only have to setup each person one time on each device. And its only ~10 devices and 4 people. So only 40 times entering a password. I really don't know why I was complaining

This is only thing that keeps me still checking Emby to see when I can start testing and offer feedback.I am now using Channels and it’s dream to use.

Hi! I would like to play DLNA folder of my another device in Emby. Can I do this? Also, I would like to share by this way as part of one of my playlists this DLNA files via internet like BebbleUPnP Server works.

تم الامر شكرا لك

Hi, what did you configure as the image language for the library? Did you check MovieDb to see what images are available?

@Happy2Playwell thank you very much. For anyone who's interested, as suggested I looked into usersettingsbuilder.js and chenged the values from 'docked' to 'closed' in these lines and it seemed to work after restart (not sure if both are necessary): { return null != val ? this.set("drawerstyle", val, !1) : this.get("drawerstyle", !1) || "closed" }, UserSettings.prototype.settingsDrawerStyle = function(val) { return null != val ? this.set("settingsdrawerstyle", val, !1) : this.get("settingsdrawerstyle", !1) || "closed" } I also tweaked some other values but one I can't get my head around. I would like to enable backdrops by default for users but could't get it to work but the line to do so is there and seems to be simple enough, any idea how it can be done?: UserSettings.prototype.enableBackdrops = function(val) { return null != val ? this.set("enableBackdrops", val.toString(), !0) : !!(val = this.get("enableBackdrops", !0)) && "false" !== val }

Hi ebr the main reason is to split a large recording in smaller ones either due to IPTV issues, or low resources on the PC. In my case, I've found it that on some channels if I leave Emby recording for 1hr+, sometimes the channels might stop or disconnect (which is an IPTV issue not Emby one), but when I scheduled the recording to different smaller pats of 30 mins, it recorded them flawlessly and never had an issue. If the channels connection goes down and it's set for 1hr+, I ended up losing it as Emby wouldn''t restart the recording -- thus my solution to split them in smaller ones. Just to clarify on this feature request, this is only for Scheduled recordings, not for an existent one. I am currently doing this manually, splitting the recordings per each part and manually changing the time stamps.

Salut, il y a un tuto en anglais ici, mais je rejoins @Randdrick ce n'est pas simple. En résumé, il te faut un domaine associé à ton accès internet (par exemple chez noIP) Il faut rerouter les flux associés à ton serveurs Emby (dans ton exemple 32600) vers celui-ci depuis ta box (ton serveur doit disposer d'une adresse IP Fixe). Demander un certificat Let's encrypt associé au domaine déclaré (noIP) Générer un certificat pfx à partir des fichier Let's ecrypt à renseigner dans Emby renouveler régulièrement le domaine et le certificat Personnellement j'utilise Emby sur un Synology et les renouvellement de certificats sont simplifiés, il y a un service dédié. En revanche il me semble si tu te connectes avec Emby connect, l'authentification est chiffrée même si ton serveur ne l'est pas. Il suffit d'associer un utilisateur Emby au compte Emby Connect

This scenario is unsupported by the hardware. ---------- Reason for locking: