Leaderboard

Just chiming in that i also an seeing this issue with a Hisense TV with the Android for TV app or the sideload app. I see this with Audio that is EAC3 when above 448 kbps. DTS, Truehd and others do not expreience this issue along with EAC <=448kbps. As the kids watch movies over and over one of the older movies they finally rewatched had this issue but i can confirm i have many others like this that they do not have access to.

Hello it would be nice to have a Manual Subtitle Offset. So that I can tap the Offset time at myself. Right now, in the Android App I only can press -50ms or +50ms. If I want key in - 2 Minutes, its long way to do it. It would be easier if i can type - 2 Minutes and all is done and not press -50ms till i have reach it. Regards Firefox

Updated 15 Sept 2023 - description at bottom of this post Updated 06 August 2023 - description at bottom of this post Updated 05 August 2023 - description at bottom of this post As requested, import and export .actors folders people as a seperate plugin. I have done this fairly quickly so have not extensively tested it/checked it all works falwlessly! Everything should log to its own files and keep out of Emby's main logs now If you don't know what it is or does then you don't need it! Use at your own risk, this plugin creates files (export) and changes Emby database (import) Create files writes to media folders and / or writes to metadata cache library Scheduled task * Updated 24/03/23 ===================== I have left the old version here incase the newer one doesn't work properly. I have NOT tested it! There is now an option to select the import metadata directory preference for \Metadata\library or \Metadata\people directories. Code has been added to change the path that the image is put to when the option is selected. Other than this change, both versions are the same (one with this change and one without) - no need to upgrade if you do not want to. Kodi_actors_Folders.zip Kodi_actors_Folders_(MetadataPeopleFolder).zip Updated 20 June 2023 Fixed Null Reference Exception when Actor image path is not null but an empty string - this shouldn't happen but seemingly can happen! When it occures the plugin simply exits, and doesnt finish its task. The Fix Now logs this as a path error and skips over it to continue so the plugin doesn't just quit and exit. Also a code edit for getting Images from http paths [ERROR - Debug Below] messages in your logs. Code to wait for the filesystem to actually save the temporary file to disk before trying to copy it & Exception Trace logging if it still fails. Logging made better for overwrite / do not overwrite destination instead of a error Logs should all go into the log directory on all systems now. If anyone still gets this null reference error, please let me know Kodi_actors_Folders(20-07-2023).zip * Updated & Reuploaded with Import changes to metadata path & option to write to a-z folders Kodi_actors_Folders(21-07-2023).zip Kodi_actors_Folders(21-07-2023) (2nd Release).zip 05 August 2023 * Fix for sporadic null reference error (caused by http.listener) - which stopped export. * Improved Invalid name handling * Added MovieList Export on activation * Added Timeframe option of people to export Kodi_actors_Folders (05-08-2023).zip 06 August 2023 * Added Error Traps for random export errors, recovers fully now,continues and logs (if selected). Kodi_actors_Folders (06-08-2023).zip 15 September 2023 * Added Import / Export of Provider ID stub files * Corrected settings that didn't save properly. This was done primarily for my own use, so it might not be ideal for everyone. Basically it allows you to export imdb,tmdb,tvmaze ids (currently just these three, I will add more provider ids later) with the poster images I have not tested the import yet but the code is there to do it... This is solely to help prevent duplicate people in my database and eventually make my db more and more correct over time, and also to work with my other plugins.... They are just plain text files with the provider id inside. Kodi_actors_Folders.zip

Believe me, nobody knows. Its been done for 3 years and it just sits there waiting and waiting and waiting

I continue in English... Yes, it was designed that way, but there is a bug which causes the player module to crash in the e4k code when playing local content. This seems to have a side affect. The player no longer keeps track of played content. (Emby) progress updates depends on that information. -> Due to Kodi limitations, the content progress reset function works on a pattern. Kodi doesn't report this action in a direct manner (via API).

je genau.... Vielleicht sollte man lokalen content aus der Verarbeitung ausschließen....

Do you have anything like Radarr or Sonarr setup? They could have miss-identified the original files and replaced them with what they thought were upgrades. Emby itself would not have done this unless you explicitly setup a conversion job for that particular media and told it to replace the old files with the new conversions. Seems unlikely.

I can see thar emby live tv doesnt have this option. What a PITY. This should be an elementary function. I guess I will have to switch to Kodi og Plex.

I have tested adding tags and genres to over 7000 movies at a time. It takes a few minutes, but does work. If it doesn't work for you, I will fix the problem ASAP. Vic

It has to re-evaluate each episode in the Season to have something to match the new Intro to (that's how chromaprint works) - but it should not be re-generating a new fingerprint for each episode every time. So it should just be a single new fingerprint (for the new episode) and then a mathmatical calculation on previously calculated/stored values - taking a very small amount of time. This was mentioned a while back in another post (mayeb 3-4 weeks ago) - I'm not sure if it got fixed but Luke acknowledged it was an issue I believe. The fix may be in the latest beta only ...

I reverted back to 8.2.8 and everything updates as per usual. Either a repair or manual update was the only way to get artwork to refresh on 8.2.9.

After testing on my second AppleTV and it not happening, I force closed the Emby app and it seems to have resolved for now. Had no idea restarting the entire AppleTV didn’t automatically do that. Will report back if it happens again.

Also, that movie takes place entirely within an airplane with similar lighting throughout. I wonder if that consistency could also help produce high-compression...

Very 'clean' video (no grain etc) with no complex scenes and generally low 'movement' make for a highly compressable video.

as @Spaceboysays above - for MKV then mkvtoolnix is your best bet - as it retains all parts of the MKV in the split - incl subs etc. You can also do multiple splits in a list. Avidemux is your friend for timings (as you have already identified ) - try and use key frames if you can (although I think mkvtoolnix may insert them - not 100% on that) For the MP4's - then personally I would just convert them to MKV's .. mkvmerge -o newfile.mkv oldfile.mp4 or use one of the many mkvmerge GUI's

Haven't used it since strm support was removed, but after testing the latest version on beta 39, I see it missing quite a few movies that have proper IDs. Probably needs an update for the latest versions. Carlo

I am positive I'm not the only one who thinks this, but for a product that has a paid subscription the communication to end users is severely lacking. Beta Updates, Road Maps, Lack of Community Managers, More in depth responses to feature requests to name a few areas that honestly, are very average or non-existent. The fact that community members that make plugins have better engagement and responses to updates/requests/planned changes is pretty average tbh. When it comes to beta updates, it seems we get this string of updates then shit breaks and we get no communication on what's being done to fix it. How hard would it be to have a dedicated thread that communicates what's being worked on for the next update, an eta, issues that are known and what's being focused on, and what's currently a struggle to diagnose and fix? I think the same goes for literally any feature request. The token "Yes we can look into this in the future" response is a joke tbh. It literally reminds me of my mum saying Maybe to me as a kid. Don't get me wrong I love Emby as a product, I just think it's about time the communication gets an over hall.

Hi. There is always room for improvement and we continually strive to do better. We are a small team but that is actually what makes us much more responsive than a lot of larger ones IMO. At times I feel we are kinda between a rock and a hard place here...because we grew out of the open-source environment we have a very strong sense of "community" with this product. That is a good thing but it also seems to set an expectation with our users that they should have detailed insights into our internal operations. There are a lot of reasons why this isn't practical with us no longer being such a project. You don't have these types of insights into any major product from a large company - and you don't have direct contact with the actual people behind the scenes with those companies either. The last two server beta cycles have been very long - way too long - and that has exacerbated things. That is not how we planned them but stuff happens and here we are. One of our primary goals for the future will be to get back to much shorter release cycles of the server. So, thanks for the feedback and we will strive to do the best we can on the communication front but do realize that our internal operations are not intended to be public. We want to keep the sense of community we have built and Luke and I are still committed to direct communications with our users instead of building layers of isolation that would only obfuscate things further. In the end, what we really want to do is build, deliver and support the best damned personal media server there is and that will continue to be our top priority. Thanks.

You're going to have to delete the rows from the MediaItems table. When you try to do that, you're going to get errors about foreign key constraints from other tables, so basically, you'll need to delete rows from those other tables first before you can delete the rows from MediaItems. Try it with something like DB Browser for sqlite to see what I mean. This is assuming you have experience working with databases though.

Since we are talking about hardware implementations, the 8 bit bs 10 bit even with the same codec is not trivial. But as an answer to the OP's question: No platform currently offers 10bit h264 hardware decode (except the non working Rockchip RK3229). No platform currently offers hardware encoding either. 10bit h264 is very exotic format. Its use is almost completely limited to self encoded material by the anime community. Chip makers have no plans to include hardware implementations now or in the future.