All Activity

You may well be right about HTTP technically qualifying as Direct Play when the original file is delivered unchanged. But that's really beside the point I was making. A checksum only proves that the bytes arriving at the client are identical to the bytes on the server. It does not prove that the client then buffers, demuxes, decodes and outputs those bytes equally well. In fact, your own argument about buffering, throughput and the player confirms exactly that distinction. My point is what happens after those identical bytes reach the client. A good example is my Ugoos AM6B+ running Android. With the Emby Android app, I have certain media where specific HD audio tracks remain silent. The very same files and audio tracks work correctly in Kodi on the same Ugoos, under the same Android installation. That does not happen on my Shield, so I'm not claiming that this is some universal Emby Android audio bug across every device. But it does demonstrate the point perfectly: Same hardware. Same operating system. Same file. Same AVR. Different playback engine — different result. So your 120 Mb/s + TrueHD example proves that your particular material works with your particular setup. It doesn't prove that Emby's Android playback path is equivalent to Kodi's, nor that it exposes everything the underlying hardware is actually capable of. Dolby Vision Profile 7 FEL makes that distinction even clearer. Successfully receiving the original DV7 stream over HTTP does not mean that the playback engine is actually processing the FEL. Transporting all the information and actually using all the information are two entirely different things. And that brings us straight back to the problem of the thread starter. If the original 4K file arrives unchanged but the client nevertheless interprets or handles it incorrectly, then the fact that the transfer itself was bit-identical obviously doesn't solve the problem. That's why I brought up direct access to the original media through something like SMB and a capable playback engine such as Kodi in the first place. It removes parts of Emby's playback path from the equation and lets software that demonstrably handles these files correctly deal with them. So yes, you may be right about the definition of HTTP Direct Play. But proving that HTTP can transport an unchanged file was never the interesting question. The interesting question is what the client does with it once it gets there.

Hi, were you able to get connected with https?

Hi, there are force transcoding options in the app now for many formats.

In newer versions there needs to be something in the western folder with an image. it could be a video, or it could be a folder.jpg file.

Hi, we are working on improvements to this. Thanks for the feedback.

Let's separate two different claims, because they're getting mixed together. 1. "HTTP alters the file." This one is testable. Download the file from Emby over HTTP and run a checksum against the source file on disk. They match, bit for bit. Nothing is added, removed or re-encoded — it's a byte-for-byte transfer, the same as any download. And Emby itself tells you what it's doing: the dashboard says "Direct playing", "Remuxing" or "Transcoding". If it says direct play, the server isn't touching the stream, regardless of transport. 2. "It stutters at high bitrate." That's a different problem, and I don't doubt you're seeing it. But it's a buffering/throughput issue on a specific client, network path or player, not evidence that the file was modified. Stuttering means the player isn't getting bytes fast enough or isn't buffering enough of them — the bytes it does get are still the original ones. For reference: I run Blu-ray remuxes at over 120 Mb/s with TrueHD and I've never had an issue. The TrueHD passthrough is the giveaway, actually — my receiver locks onto a genuine TrueHD bitstream. If HTTP were altering anything, that lossless track wouldn't survive intact. So SMB may well work better on your setup, and there are good reasons to prefer it — no argument there. But "HTTP can't do direct play" is a different statement, and it isn't accurate.

Hello Luke i tested Emby on WIndows (more versions) in Virual Machine and version 4.7.14 had collage in Folders view and show Czech names (not folders names) afted this version, this features disappeared ;-( Logs embyserver.txt Screenshots

HI, we'll take a look at this. Thanks.

See my explanations here: and here and here You can try to sugar-coat HTTP all you like – it’s not ‘direct play’. That’s simply not true. And we can go through it another 1,000 times – the stuttering and jerkiness will remain, no matter how powerful the hardware is. Of course, if I want a film without HD sound, in Full HD with a video bitrate of 6 Mb/s, then that stupid HTTP is enough.

So it sounds like you don't just want to transcode at a certain framerate, you also want to force transcoding if something is a higher framerate?

Yes, I do. When I go to my Emby in my web browser, I now see another library called “Trailers” that also has the Trailers plugin logo, and inside it I also see the “New and Upcoming Movies” folder. But when I go into that folder, it plays random internet trailers in English for movies I don't even want to watch—it's as if it just randomly picked them out. But as I said, this is all just in the browser and not in the Emby plugin on Kodi.

Hi, we are looking into it. Thanks.

The issue is you are trying to blame Emby for something that Emby has no control over. Why is your drive not staying mounted when it goes to sleep? It should still be mounted just goes to sleep. Mine stay this way on both Windows and Linux. The enclosures are USB and they sleep and stay mounted just fine. Why does it not always appear when you boot the PC? What type of drives are these? What is the enclosure? As stated by others this isn't an Emby problem. It is a hardware or OS issue. Fix your power plan that is turning off the hard drive after a period of time of no use. That is what this sounds like. You want the drive to always stay mounted and that power plan is causing it to unmount. It can still fall asleep and wake just fine. A temporary solution is turn off real time monitoring. Use scan library instead. Then when adding new media navigate to the folder view of that type of library. In this case I've added new media to this particular folder inside my Movies library. Rather than scan the entire library I just want to update this folder. I can do that with scanning just the library in the folder. Did you know you could do this? If you add new media across your libraries just use the normal scan library to cover all. But when adding to just certain folders you can just scan those folders. If you add a new episode to a series. You can also just click that series name on the 3 dots menu. Find the scan library and just scan in that series. Quickly. It works at any level and will just scan at that level.

HI, how does Emby for LG 1.0.51 compare?

Di you have emby premiere?

Sorry, but I've been using Kodi for more than 15 years now, and I'm really at my wits' end with this plugin—or rather, with how it works. I can't even access the “Remote Trailers Selection” feature in the Emby plugin anymore.

Thanks for following up !

Hi, that is not idiotic if they are both named with the same episode number.

In the future I would suggest you tick the options to use .nfo files, and further down tick the option to save artwork into media folders along with download images in advance. No need to rescrape.

This, so very this. Emby is stupid from time to time and loves to merge episodes, even when you tell the server NOT TO DO IT. it's extremely frustrating. I recently had it happen with One Piece after adding some episodes. Even with Absolute Naming it decided to be completely idiotic and merge a bunch of episodes together. I had to split them apart and edit the metadata manually to fix it.

Your hardware is faulty. It is not a given that an external HDD enclosure won't mount from time to time after reboot. A proper working enclosure will always mount, ALWAYS. As for sleep time, you're just adding that now to defend yourself. Having it go to sleep when it's attached to the server just shows you have no clue what you're doing, which was apparent the moment you said you're using an external drive for your media..Have your system setup CORRECTLY. I'd argue this is a 100% your problem, not an Emby problem.

Trailer Naming | Emby Documentation

Pfad fuer benuzerdefinierte intro and probably you need a resync.

Yes, I created a library in the Emby server, as shown in the screenshots above. I also synced it with Kodi using the Emby plugin, and I can manually select and play these trailers in Kodi. Do these trailers have to have a specific name? Does the word “trailer” have to be in the name?

Did you sync the trailers?