Leaderboard

The developers in the EMBY community are incredibly passionate and responsive to customers. I just bought a Lifetime Premiere because of that. I support the efforts of the emby team.

After opening and initializing the tuner (always) and receiving the signal from the tuner (+0-1 s), Emby needs to probe the TV stream first. This is done externally by running ffprobe (+1-2 s). Based on the result and the client capabilities, Emby configures ffmpeg accordingly (+0.x s) When ffmpeg runs, it probes the video stream again (+x s), it needs to wait for a video key frame (+0-1s), then it starts transcoding and writes HLS segments to disk, each of which covers 3 seconds (+3s). After the first segment is created and written to disk and Emby has detected that is is available (+0.x s), it is transmitting the first segment to the client (+0-1s). Only then, it's a matter of how fast the client player will show the first picture. TVnext can re-use an existing tuner stream (if same mux). All streams go through the server and are processed and parsed there, so no external probing is needed. The parsing (probing) may take 50-200ms, but TVnext doesn't wait for this. It stores and uses the probe result from a previous playback and sets up things immediately as if that information would be correct. It does that setup at 0T, even before it has received anything from the tuner. Only when it would turn out to be wrong (after the probing results are available), it would abandon the preliminary setup and re-create it (nothing has been sent out to the client within those max 200ms). It does not use ffmpeg for creating segments, it does that in memory instead and it sends out the first segment to the client immediately without waiting for the first 3 second segment to be complete. Then it depends on the client player and how long it will wait (building up a small buffer) until it starts playing. That's roughly why it takes > 8s with current Emby but only 500-1200ms with TVnext (without transcoding, which adds about 1s)

Check the /Items API and the AnyProviderIdEquals param for that API.

The abstraction would be a benefit, but there are a few issues that prevent us from using it. The first is, this is only available in the US. Emby supports multiple countries and languages. We do not want users to have different experiences. Amazon requires a catalog of music to be uploaded. This is not possible due to emby not being a centralised music provider with a database of songs. Thanks for the suggestion. Hopefully this improves in the future.

It is really cool that Emby has the ability to support multiple versions of the same movie. It would be nice to have a setting on the client side to allow the user to set which version should be selected by default. This could be as simple a user-entered string, or it could be a list of detected strings to choose from. It could allow multiple entries and it would choose them in the order entered. On the Kodi side, it would also be nice to get the "Choose the Best Version for Me" option that the Emby app has.

may be of interest... https://www.westerndigital.com/en-gb/products/external-drives/wd-elements-desktop-usb-3-0-hdd?sku=WDBWLG0200HBK-EESN just got 4...to use as a backup device (not in an array)

Also one of the last questions is what about locked items/fields? ATM it just ignores if the field is locked and updates it anyway, this is probably not the best way, probably going to need at least some settings arround this to allow uses more control over what happens when a locked item/field is encountered.

This works for me most of the time. Refresh metadata on that movie (replace all metadata and images) and then re-run the task to generate thumbnails.

Yes, that's what I am trying to tell you: Dizquetv is entirely dependent on you having a plex server. You cannot create channels at all without one. Once you have those you can add them to emby, but you will still require running a Plex server alongside it. Until dizquetv is refactored to use files directly from storage instead of being dependant on plex, you can't use only emby with it.

Nevermind, I noticed a PR in the pvr.iptvsimple github: "Fix supporting of local paths in Connection Manager" Although the PR hasn't been accepted yet, I found a test build containing that fix. I've tested it and it's working again under that build

Since the TV supports DTS I'm going to for the moment assume Emby is working properly and the problem was with their soundbar, which they originally told me they didn't have but apparently do.

I know you are just trying to help but I feel you are insulting my intelligence— it IS happening on the detail screen. I will post a video and pictures when I get home from work tonight.

@ragicoThe developers have not, as far as I'm aware, fully acknowledged that their app doesn't switch to HDR10, HDR10+, Dolby Vision when playing those types of content. Also, the developers never give time frames or guarentees as to when (or even if) something will be fixed. I'm on the latest beta version of Apple TV, and my HDR10 content and test Dolby Vision content still don't play in HDR. So we just have to wait and hope the developers do fix it soon. Searching the forum, it appears this issue has been known about for over 2 years, so I'm not expecting it any time soon.

Correct.

Hi. That is showing what your display supports - regardless of the current media. The limited means that only certain profiles of DolbyVision are supported (probably just 5 which is the streaming protocol).

As an experiment have you tested when using a wireless connection for the Shield? I know it's counterintuitive, but I've heard things...

Why: I use fuse file system as my media path. So emby can not detect the changes so that the only way is to scan the whole library. It's okay in the small library, but it will spend a large time to scan a large library. I request to add an API to enable scanning of individual folders, OR update some exist api, such as I can past a scan_path param to /Items/{Library_Id}/Refresh? That means a lot for me, I am tired to fully scan a huge library which build at fuse file system

Replied in the linked topic.

You need to use this API: https://dev.emby.media/reference/RestAPI/LibraryService/postLibraryMediaUpdated.html

I am now seeing in the web app the Next Up Thumbs, using TV CoverArt, are now cropping the top and bottom of the TV overlay image.

HI, yes we are working on adding more countries. Thanks.

Didn't know that I assumed since the recordings can start straight away that that was the cause for the live tv to start slow. Using mpv from command line it starts videos immediately but starting network stream it takes much longer. Currently I have sports on 3 channels and it's a pain switching between them. In WMC it was near instant for the channels in the same Mux and a second if it wasn't. It's all good knowing about TVnext but when will we actually get to try it.

Please add Korea. emby is very popular recently.

So I've fiddled with this some more. No idea as to why, but it seems that it looses the server connection for that function. If I go into the app, and select 'change server' and just re-select it, the problem fixes itself. Weird. I figure it's some windows gremlin of some type as I don't see how/why the app would loose it's connection to the server as it's on the same machine.

I feel like being able to 'buffer/pause/watch' is a big part of DVR functionality either during live broadcasts or when something is currently recording. Windows media center and Tivo have it nailed so I'm hoping you all can make the equivalent in Emby. Thanks for working on this and here's to a good year of advances!

I have implemented a new config store that should work on both 4.7 and 4.8 Latest version of plugin pushed to catalogue (1.0.0.2) Unfortuanatly you will need to enter in your mappings again. In Stable 4.7 emby you should be able to see the old config in the config folder: Emby-Server\programdata\config there should be a file something like this: classification-mapping.xml that has your old config in it. The new config file is called: classification_mapper_config.json and is now in JSON format instead of XML

60 seconds on xmltv isn’t high if you’re programmatically dynamically generating the xml at the point of GET. You saying it’s high is entirely subjective.

sorry i screwed this up but the 2 mediainfo stats are for 17again & 40days. both are 1080p.

Thank you for your reply！ Yes, I am able to customize the tag after. But yet, there is a chance my kid sees some porn pictures through the thumenails if he creates a tag name same as one of others. And from others point of view, Emby leaked their pictures to other Emby users. Both situations will put Emby into troubles! You should take it seriously I guess.

Ok, thanks

Can we hope that emby will play HDR, HDR10+ and Dolby Vision Profiles 5 and 8 in Apple TV?

HI, how are you trying to install it? Are you sure that you have the correct ip address? Is any emby server log file generated? Emby Server Data Folder

Cool, more info. Thx. I'll start by stating that with a 12-thread CPU numbers in top will look inflated unless you turn off Irix mode (shift-i) but that's okay. In this case Emby is still tying up 2+ threads for direct play and that's too much. Now, your box seems to have a lot of overhead and that could be affecting things all around. I see what I think are at least 2(?) VMs (qemu-system-x86) that are somewhat busy. Are these associated with Emby in any way? Then there is rslsync and smbd doing something, not terribly busy. But the shfs process looks busier than you might expect. All of these are tied to I/O operations/services. Is this a steady state? My limited understanding of shfs is that it's FUSE based and for user shares and file caching but I have no idea if it can be tuned or how. If Emby is reading/writing to the same areas and having to go through these services I wonder if that also skews the stats. Concurrency and contention can make things worse. What jumps out the most is seeing that CPU usage overall (total) for system operations is over 28% while user operations are 24%, a bit lopsided. I would follow the advice from @rbjtech and try to isolate Emby and go back to basics. See if you can play media from a storage device/volume/location that is not managed or used by smbd, rslsync and shfs. Maybe stop the VMs temporarily. Bring things back in one-by-one and hopefully that will help identify what makes the load shoot up. On a bare metal box and even in Docker direct playback should use very little resources. But you have a few layers and side things possibly contributing to the load and maybe amplifying it.

I would like to add my opinion on this by linking my post that was marked as duplicate. Generally, I don't think it is that helpful to set the default version depending on size or quality. I stated it in the linked post, most of the time, I have two MP4 files, a subbed and a dubbed version, and this leads to inconsistencies with the default version being set by Emby. I would like to have an option to set a string or something that is recognized in the file name to be set as default version, like in the first post of this thread stated. And because I read a discussion regarding "Auto" setting for video internet quality: "Auto" does not work properly. I use the web client in Chromium Edge (connection not local) and when the setting for video internet quality is on "Auto", even a 720p 1 Mbps MP4 file is streamed with a "reduced bitrate", while this does not happen when I set the internet quality to "4K - 40 Mbps". I already disabled the ability to transcode a video for my users because that lead to quality problems as well (lower resolutions being played on auto), but with video transcoding disabled and the internet quality set to "4K - 40 Mbps", my videos are being directly played without transcoding and without bitrate reduction. By the way, these problems do not occur on the android app.

It could be for anything that has a path. It does Equals. The condition returns true if at least one matches.

@Orionas21between these two it sounds to me like the windows machine will be more powerful and will perform better.

New version 2.0.0.0 in the plugin catalogue: General: Redesign of the settings web page Channels: Unlimited number of channels Added an option to cache program data until the guide data runs empty As an alternativ to Channel Rules, you can now also choose between Collections and Playlists Playback: More granular control over playback progress reporting Improvements to "Continuous" playback with Roku devices New playback method "Native (Archive)" This new playback method was created by the Emby Devs. Similar to Playlist playback it will play the real library videos, but with the big difference that playback is purely initiated by the client app, without any remote command execution. This is why it also works for Roku devices on a WAN network. And although the real videos are played, the whole thing is treated like live TV. This means that channel zapping is possible and no dialogs for playing the next episode are displayed. Unfortunately, the new playback method does not yet support all features. As the name "Archive" suggests, it will currently always start all videos from the beginning. In addition, only very few Emby apps automatically advance to the next video. If you want it to be improved even further, each of you should raise your voice in this thread. Export API: New security concept that should simplify some things while making the API endpoints more secure. Because of all the changes, I expect there will be bugs. That's why it will only be available for Emby 4.8.x.x installations. Regardless of that, before you install the new version from the catalogue, it's important that you delete the previous VirtualTV.dll and also the VirtualTV.xml config file! As usual, you should also clear your browser cache.

KSPlayer KSPlayer is a powerful media play framework for iOS, tvOS, macOS, xrOS, visionOS, Mac Catalyst, SwiftUI, Apple Silicon M1 . Features iOS, tvOS, macOS, visionOS, Mac Catalyst, Apple Silicon M1, SwiftUI. Multiple audio/video tracks. hardware accelerator. 4k/HDR/HDR10/HDR10+/Dolby Vision text subtitle/Closed Captions/image subtitle(dvbsub/dvdsub/pgssub) Picture in Picture Record video De-interlace auto detect Spatial Audio 360° panorama video. libsmbclient protocol https://github.com/kingslay/KSPlayer

Please add Austria as it is like Germany.

Already covered earlier in this topic. But just to refresh everyone's memory, to release worldwide you have to have the status of being a Samsung partner, and that requires a monetization strategy that is profitable for Samsung. It's not like the other app stores where you just submit once and check off a list of what countries you want. If you're a free app you and you're large enough that they feel they need to have you, then you can get through. Everyone else has to pay them sufficiently that they feel it's worth it for them.

Hi there, does the TMDB Scraper of Emby support the production order sorting of TMDB. I have quite a trouble adding Phineas and Ferb to my Emby Collection. Most of it are double Episodes in Production Ordner but i can only choose: airdate, dvd or absolute in the metadata editor.

You are funny. You're going crazy about getting a feature from a software, that you are discrediting in a way, that no sane person who would be sharing the same view and opinion, would ever use that software, neither bother to post in the forums of that software at all.

I finally switched to using Emby (on a Mi Box Android TV) as my primary TV instead of Kodi! The Mi Box has no dedicated play/pause button so you have to use the main select/enter button instead. It works fine except the On-Screen Display appears every single time I pause playback! I'm able to access those OSD controls with either the UP or DOWN buttons so I'd really really like to disable it from showing every time I pause. I assuming the devs don't want to make this the default, so could we just add an extra option in the settings menu? "Don't show on-screen controls when paused" I could probably deal with a much less robust OSD appearing (like Netflix does), but I figured just adding this optional setting would be much quicker to develop. This is all I want for Christmas :-)