Leaderboard

Yes, it work fine... using it on 2 Android TV.

Yes this was it, a big ty to @troy_

While Emby already has recommendations built in based on previously watched items I find they are not all that helpful. They seem to be based on genre only, for example, because you watched a comedy here are other comedies in your library. I do like how the also directed by/appear in recommendations work though. What would be great is if Emby could incorporate Trakt's recommendations as they are much more sophisticated. Trakt's recommendations are not only based off of what you have previously watched but also what your Trakt friends and other Trakt users have watched. It takes user ratings and trending/popular media into account. Ideally Emby would include full Trakt integration allowing users to rate media after watching, view lists and recommendations, and view upcoming media all from within Emby but for now I think recommendations would be a nice addition. Trakt has the potential to give Emby that community feel and allow users to discover new media, find something to watch, and recommend media to other users. http://docs.trakt.apiary.io/#reference/recommendations

Hi @Luke I'll try and get a log tomorrow at some point. As I've said previously, I've kind of got around the issue by creating a manual m3u so I'm still able to use Emby to some extent. I also came across a thread last week purely by chance that was discussing all the new Live TV features that are currently being worked on. Obviously, I wasn't aware of this when I originally raised this issue. Please accept my apologies if I sounded like I was moaning un-necessarily.

I can't believe I overlooked that.. I don't recalll ever disabeling it, so that's still weird. But yup, it's working now. Thanks everyone.

You don't have any provider enabled - hence no results. Enable at least TMDB. Edit: Cross-posted.

@AthielD how are you suppose to get a result if you have no providers enabled to query?

I see no queries in your log. Could you: 1. Temporary disable automatic port mapping as your log is flooded with Port mapper errors: 2. Run Rotate log file Scheduled task: 3. Post a screenshot of enabled library providers and their order: 4. Try to Identify an item with any criteria (name, ID) 5. Post server log.

Vacuum of the DB brought it down to 560MB. I've relented and wrote a script that will push any "favorite shows" from the STRM folder to an EmbySTRM folder nightly. If the series disappears in the STRM folder it'll delete it in the EmbySTRM folder. This is the best thing I could come up with so that new episodes are added to, or removed series are purged from, the system automatically. I'll see if the devs can weigh in here before I try to enable logging and dig into the way it might be working. If the continue watching results for episodes has to be calculated on the fly currently, perhaps the current or next episode could be stored in a sort of header record for the series and it could be calculated during playback events, library scans, or trakt.tv syncs so that pulling the "continue watching" list is a bit more efficient.

1 and 2 is all that is needed. Did you debug, does the server request any data from your plugin?

my server rebuild and your question prompted me to do some further testing. I realised a mistake in my understanding, product description and function. At the episode level there are persontypes "Actor" and "Guest Star" (as well as directors, writers etc), at the series level there are not "Guest Stars" only "Actors" (as far as i can tell) (as well as directors, writers etc) Anyways the original purpose of cleaning the bio page should have removed person type "Actor" from episodes duplicated with "Actor" at the series level not just person type "Guest Star". This has been corrected in v0.1.0.1 Because of the fundamental change test mode would be recommended again. Unfortunately @sydlexius i don't think this changes the situation re: your request above...there is no Actor/Guest star distinction at the series level (as far as i can tell) Emby.GuestStarCleaner v0.1.0.1.zip

You can not put a IMDB in a TMDB field. Put it in the IMDB field to search that ID on enabled provider sites.

works now (direct playback) in ATV (forced dts/hd paththrough checked) and sideload app (no settings available), but still no dts popup and only for streams up to 5.1 7.1 streams are still distorted

That's what I found out. I posted to soon. But yea my endpoint was not connected.

Hi, we'll take a look at this. Thanks for reporting.

I feel like you missed the obvious@alucryd, I don't think he is on Ubuntu. Neither am i and he found my issue.

just a heads up, I have found the issue with the context menu, I have a fix/work around for it but want to also spend some time trying to remove some of the warnings in the log so will have a new version in the next few days.

Its not a problem with emby It's a issue with the stream source not with emby I'm suggesting how emby could help with theses

Hi When viewing folder thumbnails or photos and home videos, either in the browser or in Emby Theatre, there's an option to show filename and year. Filename is definitely useful but I want to see the exact date the photo or video was taken, not just the year it was taken in. For users with write permissions in Emby, you can edit the metadata for each file individually to find the date taken but for users with read only access there's no way to see it. Please can we have the date displayed in the thumbnails screen rather than just the year? Thanks, Warren.

Are you positive? Can you double check that it was direct playing?

Just got 3.2.92 on my P7P. Live TV discolor issue appears to be fixed!

@AphxTwstr Can you try updating to the latest version of the sideload build? https://emby.media/emby-for-android.html We've updated our embedded video player to the latest version. Let's see if it plays better with that. Thanks !

As one who got one of the password reset emails I am going to just assume you've been breached by enforcing a password change. I use a password manager and so the likelihood of my account on here getting compromised is slim at best. To be perfectly honest getting an email with basically no context is either getting deleted as a phishing attempt, or getting marked as phishing likely hindering your ability to send forum emails in the future when it is blocked by email providers. There should have been more context to this. Instead, you should be reminding users by encouraging best password practices: 1) Enforce a strong password on the site. 2) Use a forum plugin to check passwords against Pwned Passwords to see if they've been seen before: https://haveibeenpwned.com/Passwords 3) Encouraging those users to check https://haveibeenpwned.com/ to ensure they have actually not been compromised and to use a password manager with strong, random passwords going forward. 4) On a forum login or registration (when you can capture passwords in plaintext before encryption) you should be checking against Pwned Passwords to ensure it is a strong password. You'll note many sites do this now. For those users, there is a very real risk if they're reusing passwords their personal Emby instance could also get compromised.

Oh, I did fully read the announcement else I wouldn't be here in this thread. I had to however search for it as an email with " For security reasons, the administrator of Emby Community has required you to reset your password." isn't exactly what you said above. You have to see it from the eyes of somebody who got a password reset email out of the blue on a forum they have not posted in which is normally "oh, this has been breached" and that is what I mean. I am also still going to assume that regardless of what you say as this is the very first time I have gotten this from any community. My other points are correct. Take it as you will. My other points are fully valid and instead of disregarding them somewhat rudely you should take them on board as a lesson and not assume for yourself I have no idea what I am talking about here... I do in-fact run a couple large communities myself one of which actually has a few million members... Checking against https://haveibeenpwned.com is an excellent way to combat spammers also as it enforces stronger passwords and prevents what you're describing from occurring in the first place...

@Anthony Musgrove

We've been getting clobbered by spam the last several days using very old accounts.

Restoring your older db will only lose users watched data and have to reimport anything added in that timeframe (library scan). But with the SCB plugin you can restore only said users/userdata if you needed to in this scenario. But overall best practice is having a full backup of Emby programdata folder if possible. As for db cache size if you have the RAM you should set it to 1.5 to 2 times your library.db size to provide better performance as the default isn't really for such a large media collection.

We don't really suggest selective backups where you choose to backup one piece of the data folder. I would backup the entire data folder of the server, while omitting the cache and transcoding-temp subfolders.

My... horrible... fix for this is to update the entrypoint for the official emby docker image thusly: The entrypoint has a base64 encoded version of the fix script and then hands back to /init Important: you shouldn't trust the code below, somebody could edit this post or I could be evil. You don't know. You should base64 encode your own script until the container can be fixed. services: emby: image: emby/embyserver:beta . . . deploy: resources: reservations: devices: - capabilities: - gpu . . . entrypoint: [ "/bin/sh", "-c", "echo IyEvYmluL2FzaAoKTlZJRElBX1ZFUlNJT049JChscyAvdXNyL2xpYjY0L2xpYmN1ZGEuc28uKiB8IHNlZCAtRSAncy8uKmxpYmN1ZGFcLnNvKFwuMXxcLik/Ly8nIHwgdHIgLWQgXFxuKQoKY2QgL3Vzci9saWI2NCAmJiBcCmxuIC1zIGxpYmN1ZGEuc28uJHtOVklESUFfVkVSU0lPTn0gbGliY3VkYS5zby4xICYmIFwKbG4gLXMgbGlibnZpZGlhLW9wdGljYWxmbG93LnNvLiR7TlZJRElBX1ZFUlNJT059IGxpYm52aWRpYS1vcHRpY2FsZmxvdy5zby4xICYmIFwKbG4gLXMgbGlibnZpZGlhLWVuY29kZS5zby4ke05WSURJQV9WRVJTSU9OfSBsaWJudmlkaWEtZW5jb2RlLnNvLjEgJiYgXApsbiAtcyBsaWJudmN1dmlkLnNvLiR7TlZJRElBX1ZFUlNJT059IGxpYm52Y3V2aWQuc28uMSAmJiBcCmxuIC1zIGxpYm52aWRpYS1jZmcuc28uJHtOVklESUFfVkVSU0lPTn0gbGlibnZpZGlhLWNmZy5zby4xICYmIFwKbG4gLXMgbGlidmRwYXVfbnZpZGlhLnNvLiR7TlZJRElBX1ZFUlNJT059IGxpYnZkcGF1X252aWRpYS5zby4xCgpsbiAtcyBsaWJudmlkaWEtZW5jb2RlLnNvLjEgbGlibnZpZGlhLWVuY29kZS5zbyAmJiBcCmxuIC1zIGxpYm52Y3V2aWQuc28uMSBsaWJudmN1dmlkLnNvICYmIFwKbG4gLXMgbGlibnZpZGlhLWNmZy5zby4xIGxpYm52aWRpYS1jZmcuc28KbG4gLXMgbGlidmRwYXVfbnZpZGlhLnNvLjEgbGlidmRwYXVfbnZpZGlhLnNvCgovaW5pdCAkQA== | base64 -d > /nvidia-fix-init && chmod +x /nvidia-fix-init && /nvidia-fix-init $$@", ]

Thanks for sharing that !

The easiest solution is simply to add the series to TVDB. I have just done that (it will have tvdbid=429017), though it may need to go through moderation before you see it. Being only four episodes it didn't take long. Paul

It's something we can look at in future updates. thanks for the feedback.

@Baenwort You can't as the id is only used and gotten from TVDB. Really no different the IMDB ids as nothing comes from IMDB.