Leaderboard

For me it sadly does and others have reported the same. Anyway.. It's sadly out of my hands and needs a change in Emby it self from the devs.

Thanks for narrowing things down @scottproI've tried an uninstall/reinstall & see no behavioral improvement... any update, @Luke?

@redoXiD Thanks for the analysis. Our tonemap_opencl filter is totally different from the regular one in ffmpeg (and faster), but your observation are probably still valid. @sa2000 Let's track this as post-ffmpeg migration task

Thanks, found the “split apart” button after scrolling. Didn’t know that was there. Thank you!

There used to be a "split apart" option and that would do at least part of what you want, if it still exists. Also you can edit the metadata of either movie to make them show up as unique.

Scroll down when on movie detail screen, click "Split Versions apart" button.

Yup. I read the guides and organized my media first, like the helpful guides in the help section suggested.

Go to the line in the NFO. ( the pencil icon next to the movie name) Look at the right end of the Genres line, click the little lock icon to lock that field from being changed.

I've tested the ass subtitles. Mkvs in my synology nas doesn't have fonts attached but the .ass subtitles have. I see that .ass subtitles with attached fonts are being succesfully rendered by Emby for android version on SHIELD TV. We're willing to see this feature in Emby Android TV App.

I have moved your post because it was completely off-topic. Please don't be afraid of creating new topics when you have a question

Thanks. Resolved for next update

The problem is that the number (f4) will change depending on how many filters are present before the tonemap filter (e.g. scale or no scale), so you should start later, like =tonemap=mobius:format=nv12:desat=0, even though, this might possible conflict with other tone mapping filters (sw tone mapping). In the new ffmpeg, this will be a separate filter named extratonemap_opencl, and tonemap_opencl will be the original one from ffmpeg, because extratonemap_opencl uses Intel-specific OpenCL extensions (which make it faster) and we need the default one for AMD GPUs.

I already figured that, which is why I used Emby's ffmpeg version inside the Docker container for my testing instead of a regular ffmpeg binary. Thanks for looking into this! As a temporary fix I used the "Parameter adjustment" option in the Diagnostics plugin, works great so far: Text to replace: tonemap_opencl@f4=tonemap=mobius:format=nv12:desat=0, Replacement text: tonemap_opencl@f4=tonemap=mobius:format=nv12:desat=0:m=bt709:p=bt709:r=tv, (this example also includes the tone so filter type, so one would have to adjust it or maybe it's also possible to use a shorter match without the filter type)

Thanks, I'll check both, subtitles and specials.

If you run Emby in a Docker container you can specify the host bind IP in the run/compose but only in bridge network mode, not host network.

It's not Emby rescanning for intro that removes the markers. Emby doing metadata scans removes all markers, including the intro once.

I slightly miss-spoke; users can't link it themselves, an admin has to add the users email via the severs user configuration page for them. All it does is pass the 'Remote (wan) access:' address listed on your server dashboard to the user when they login to app.emby.media, while telling your server this user session has been authenticated via emby.meia (the user successfully logged into their emby.media account), so the user doesn't have to use the local username+password configured on your server. It does still validate ssl certs if you've set that up; but you have to ensure the wan address on the dashboard is correct: 'https', uses the right domain/ip, and displays the correct port you want used.

Emby Connect allows a user to link their Emby.Media account to their local user account on your server. They can then login via app.emby.media, which will connect them to your server. This allows users to select from a list of servers if they have more than one linked to their Emby Connect account, without having to remember each ones address. It will keep track of changing addresses if you're just using a raw dynamic IP instead of a domain for external connections. It also allows users to reset their passwords on their own (via emby.media password reset), as a local user cannot reset their own forgotten password without involving a server admin (changing this has been an open feature request for years...). Essentially a DNS service with a few extra features specific to Emby.

Update to this bug, after further testing it seems to be only an issue within the UI not displaying the duplicated items. I have managed to leave one of the playlists play and it does in fact play the duplicated movie as every-other movie like I have set. It just doesn't display that movie more than once visually in the playlist lineup order list.

Not atm. I'm slowly working on making a fully contained plugin that installs the script by it self. Unknown when it's done.

*update* its been running for over a week now and everything has stayed in place. now just going to add new files and see how that goes

/home/<user>/.config/Emby Client Beta/cache/logs What splash screen are you seeing? include <pic> Pls.

Honestly, I just don't see this as a core function of our system and it carries with it a lot of risk (massively altering the actual media file system locations). Moving items to different physical locations and/or between libraries is really as easy as moving the files, adjusting the Emby library configuration and running a library scan. If you store the metadata with the media this will be a pretty fast operation and will preserve any customization you have made.

Tat, Consider you may have a collection of media that has not perhaps been conformed to all one standard and limited to specific codecs and bandwidth that are compatible and works for your hardware and for all your users. Yes, of course, Emby's advantage is that it can take care of that for you. But there can be limits. Maybe some of your media has timeline errors that only show up if you run a error probe check. Or some of your media might have a combination of high bit rate, high frames per second, high end audio and graphic subtitles all at once. This combination can be handled by Emby... but some server capacity and bandwidth for some remote users with different players and networks might NOT work 100%. OK, I understand you do not want have to test, remux or renecode your content, so it's all within some limit to make sure everyone can view it. But if you did do that, your issues might go away. Emby is suppose to be able to handle that. All online commercial streaming sites already do this automatic remux and limits all of their content, before any media even appears on their site. You are asking Emby to handle all the options that is not even done by any competitive service. Plex doesn't offer that. I believe Plex uses their servers. Online Netflix, Hulu, or Prime doesn't do that, their content is all remuxed and tested. I think that getting to the bottom what you're experiencing is that you are pushing the limits, beyond what can be expected to be handled automatically for every case on every media combination. If you want less errors, for the most part, you should use media that has bandwidth limits, specific audio codec and limited subtitle types so your media is more consistent. Using media that has many differnet issues, that might even have some uncaught file or timeline errors is always going to cause your streaming to run into problems.