All Activity

Hey Could i have the link to join emby beta on TestFlight?!! Thanks in advance

The biggest problem with AV1 is it is far too fragmented, and the community gatekeep information to prevent outside users from using it. They prefer to hang out on discord, and when you ask for help, they treat you like you're below them. We've had discussions about it on Doom9, and it's frustrating as heck as when someone is looking for help, if they get help, it's always "use this" with no explanation as to WHY. BlueSword is the only person I've come across in the AV1 community who actually cares and does their best to help people, while everyone else is apparently toxic. If we go back to the fragmentation, there are currently 4 or 5 forks that are recommended, all with their own different switches/commands, and not a single guide has been kept up to date in regards to what encoding parameters to use. So good luck on trying to figure out what to do! I've tried AV1 many, many times, and I can't make a single encode, size for size/vmaf score/xpsnr score, etc, that is better than my HEVC encodes. To give you an idea, I've been encoding since the Amiga days, so I do know what I am doing.

I'd like to say that something has improved with latest stable build. But on lg tv app i'm still watching the search circle more than in the past. something has definetly improved, but now it takes 2 minutes instead of 5 to show some results. Right now doing a search for a film with 4 words. The first word comes up really fast, like 15-20sek but the rest takes up to 2 minutes to get refined results. Although it doesnt look like it locks the server up completely. Streams don't get stopped in the background. One thing came to my mind, i see disk spin up when i do searches. But also when all disk are spun up it takes a long time. Could this be with not caching all metadata to metadata cache disk? How to force all metadata to be copied to the cache? And why no cronjob that does this at a regular base? Ssd/nvme is much faster than spining disk (Of course only if this is now the bottleneck instead of the database requests)

I don't think the video player (MPV) has an explicit play button but a play/pause toggle which maps to keyboard and remote buttons. The up/down arrow keys will bring up the video OSD.

QNAP, no idea. Windows, shut down Emby. Find this folder - C:\Users\YOURNAME\AppData\Roaming\Emby-Server\system\dashboard-ui\modules\emby-elements\emby-itemscontainer Rename the javascript file emby-itemscontainer to emby-itemscontainer_old and make a copy. Edit the copy in Notepad++ or whatever. It'll probably look like one huge line. Such is life. Search for 16 (there should only be one 16) and replace with 128 (or just pick a number). Save it and rename it to emby-itemscontainer. Make sure its still a javascript file. Clear every cache you can think of and restart Emby and if you're lucky the limit in a browser (and only a browser) will increase to 128. Hopefully you can do similar in/on QNAP. Note the hints about backups and not changing anything you can't change back.

Can you please provide the media info for an example? Thank

Just don't give Mr. Robot the password, I guess.

Many, many thanks for the offer! It's only EmbyIcons really and It shouldn't be too difficult, just hard work. An AI should be able to make a summery of the problems i will face and need to fix to lessen the work. It's kinda funny, i actually started the plugin as netstandard. Speaking of the portal, it seems to have problems deleting old versions. In case you are not aware.

Is there a help file or something that explains settings? When I launch Kodi I get the welcome message from the service. It syncs but seems to go through everything each time even when there are little or no additional media changes that should be identified. It takes several minutes to complete. Is that expected behavior? If not I am not sure the cause. Perhaps it is how my settings are configured? Any help is appreciated! Thanks

I have sent them via pm

As i was using the continue watching this evening, a clearer preference came to mind. My ideal configuration / infromation presentation. On continue watching (show thumbnails) (a) knowing a season i havent started yet is complete is critical (already working) (b) if season is not yet complete, knowing when the season finale will air would be nice. (c) Once ive started to watch said show, knowing i am at at the season finale position in my watched status would be nice. (d) knowing i am at at the season premier position in my watched status might be nice for some. use cases if i havent started watching a season i can see my watched position is on a premiere. i can see wether its complete or when its due to complete when i have started watching a season i can see wether season is complete or when due to complete. i can see my watched position is on a finale. On latest tv (show posters) Knowing show status would be nice (working) Knowing next air date would be nice (working) The TV Show poster overlay looks great https://www.themoviedb.org/tv/19614-it not sure why "Stephen king's IT" is complete rather than ended, the emby metadata says the show is ended. maybe as a 2 episode mini series, it confuses the plugin?

Well, did a bare metal build of my computer. Complete rebuild of my Autonomous System, went without a hitch! Other than a installer package my project is finished. Every service is capable of looking at failure conditions, analyze all its dependencies, determine what caused the failure (within predetermined guidelines) and restart and fix any service autonomously. This is HUGE! Pretty proud of it... Can see: CPU and Memory Utilization In Bound / Outbound Traffic totals Top CPU Processes (3) / Top Memory Processes (3) Storage Health / Storage Detail All Services Health All services Status Number of Devices Connected / Number Applications Seen PLEX / Emby / PIA Current Traffic AND YES THE WEATHER from my personal weather station. WHY? Because ALL of these items are part of the autonomous recovery scripts. Weather can tell WHY (or at least give a clue) why the connection (Starlink) to my gateway at a certain time was unavailable. Everything is monitored with set guide lines. Everything is documented. Everything is visual all on one control panel. Finished the google API. Everything is secure everything is available on my cellphone. If the automation fails, i can over ride the system and restart any service that is showing a fault condition. Over kill for a private server, absolutely! The coolest way to know or repair a service or its processes? No doubt! A pain in the .... well, yes it was. But well worth every hour put into it. No more guessing, no more wondering why something is down, no more being 400 miles away and finding out the service X, Y or Z is down. It should fix with out intervention.

Just send a PM if you don't want to post them here.

You need to pick a section type first...

netstandard2.0 TargetFramework This is a hard requirement for EmbyServer plugins as documented. Since yesterday, the plugin portal rejects plugin dlls which are not targeting netstandard2.0. It is not a change of policy - it's just an added check which should have been there ever since. @yocker - We are in the same boat in this regard. But it doesn't meant that all code needs to be rewritten. We have solutions for most of the typical issues (like via extension methods etc.) If you can assemble a list of code changes that are biting you, we can share the solutions we have, so that you don't need to rewrite all your code.

C# Version The C# version is largely irrelevant and (mostly) independent of the target framework. The C# compiler version determines the language features which the source code can use - but it still needs to compile code in a way that is compatible with the targeted framework. There exist a few very specific exceptions but but this doesn't change the big picture: You can compile a class library targeting netstandard2.0 with the latest C# compiler version just fine.

I think maybe this is the issue with the missing movies from collections. "I'm having the same issue as @----- and decided to delete all Collections and add them back. As they were being added back, some Collections were skipped before abruptly stopping altogether from reading them. Is this service still maintained?" These are the the replies from admins on another site. "It is not maintained at this current minute. This was announced numerous months ago it's in its current state at this time. It may be reactivated and maintained again in the future." "not sure if I follow correctly but we are aware of some of the collections that we've setup for the mass collections as either not having any items any more or we just don't have any content matching the collection, we are currently working on updating the lists with either replacements or the removal of said collections. The skipping of collections is not an issue and expected behavior whilst we update our list of collections." I have decided to just move on and use ABdb.tv for now and stop using the other mass collections to make my own collections.

I don't see such options.

The original collections came from Happyville and from these collections I searched and added them to make my personal collections.

They have for some reason removed the ability to set a default tab on the Roku. Now, if you happen to visit another tab, then next time it will take you there and you have to navigate back to the one you normally want. It's not hard, but it's out of line with the other clients (unless they plan to change them all!), and just that bit less convenient than it used to be. Paul

When enabling the "Settings->General->Screensaver" to "Backdrop Screen Saver", after 5 minutes of delay the Screensaver starts. It presents a random movie backdrop and doesn't cycle. The option "Photo slideshow time per slide" is set to "10 seconds". Also, the movie title and date no longer appear on the backdrop. This works fine with app-version "26.0.21" and is broken in app-version "26.0.22".

I recently migrated from windows server to Linux server. Then went well. I frequently leave a play list on shuffle running through the android app over night. Before the migration it would stop playing less than once a month. Now on the Linux server it stops several times a week. Not every night. Frequently when the phone is checked it's just sitting on the play list screen. Some times the screen is off and the app has to be opened. I've tired clearing the cache on the phone, but that did not help. I'll also note: The linux version doesn't seem as responsive on app open. I've never seen "connecting to server" before. After the migration I see it from time to time. The new linux server is hosted in a k3s node, the pod has no resources restrictions. The new server hardware is a significant upgrade from the previous server. Reviewing resource usage over night show the server required less than 1% requested cpu, and less than 80% requested RAM all night. Any idea what else I can try? Link to switch over thread:

Good glad it’s working! Everyone would appreciate if you submitted what’s missing! If you input your API key it raises the limit to 1000req/day. But as I mentioned above, it’s meant to be more of a throttle than a limitation. A run could take multiple days depending on device power and network speeds.

In your link it says logs would not be sanitized if obtained directly from the logs folder and should not be uploaded in the forums. How do I get them to you? I can let you know that since I last posted I have backed up my configuration to a backup and deleted the Embyserver folder at volume1/@appdata/EmbyServer. I'm assuming that I am now starting on a clean sheet but when I install the file again it takes ages to install and I'm back to the same situation of it freezing. If I install the previous version and restore the backup is that likely to work?

I also had a problem with collections losing items, and it turns out it was because I had set radarr and sonarr to export .nfo files. Apparently they do it not only on first import, but periodically. This caused the edits made by emby to the .nfo files to be ovewritten, including the collection info. If you're using external software to write .nfo files, this could be the cause of the problem.