Search the Community

Hello! I have several libraries with content to which I've been applying conversions to hevc/aac. The libraries are a mix of H264 content and hevc/H265 content. Up to now I've been manually evaluating each entry in the library before creating a new conversion task. However, it's pretty tedious. Does anyone know if it's possible to create a conversion task that will only convert content that is not already hevc/aac encoded? The options I am selecting are replace original, custom, mkv, hevc, aac, original quality. However, if the content is already hevc/aac encoded it looks like the task is still copying the data to a new container. The objective is to standardize the content format in my libraries to hevc/aac. Once the conversions are all complete I'll create a standing conversion task for each library to automatically convert new content. I appreciate any thoughts. Maybe I'm just doing something silly. As a side question, not super important, but I'm curious: one instance so far the original data was H264 encoded at 1 Mbps and the conversion to H265 increased the bitrate to 2 Mbps (same options selected as above), resulting in an overall increase in file size. I was able to correct it by modifying and performing the conversion job again. Can anyone point me to documentation that explains how the selection process for "original quality" works? I work with APIs day in and out at my day job so I've been toying with maybe writing some logic to automate submitting conversion tasks if nothing else.

Hey guys @@softworkz, Currently I am having issues playing media on devices which need transcoding to play the file. E.g my Oneplus 5T phone manages to direct play x265 encoded files and Emby works like a charm for that device. However when I try to watch on a notebook or PC which needs to transcode the x265 into x264 the video never starts or just stops after a few seconds. I restarted the emby server and the whole windows server multiple times but that does not solve the problem. I attached the server logs for you. embyserver.txt ffmpeg-transcode-ee2800e7-7a19-4344-b5ba-a7306af79f88_1.txt

Hi! I've been running a Dockerized Emby server based on the official Docker image (currently at v4.2.1.0), to be accessed from Roku boxes I have laying about the house, using the BETA Roku app. I also have a TVHeadEnd deployment which is fully functional, which also renders all streams as MPEG-TS container with MPEG2 video and AC3 audio. The Emby server is configured to access TVH using the Emby TVHeadEnd plugin (v1.4.4.0). This has worked flawlessly for months, but now I've noticed that Emby is for some reason transcoding from MPEG2 to H264. While this isn't costing too much, it's not what I want. Plex and other clients are more than happy to play back the MPEG2 video streams without issue. However, Emby is choosing to transcode the stream because "container is not supported". This means that for some reason, Emby - either Roku or Server? - decides it doesn't like the MPEGTS container and requires a "transcoding". The issue here is that the "transcoding" should limit itself to repackaging, since both the audio and video streams are supported by the Roku device(s). As I said, this used to work perfectly in earlier server versions. Sadly, I don't know exactly when this got "broken" (so to speak). I only noticed this accidentally yesterday while showing a friend of mine the "stats for nerds". Can you help me figure out what's wrong? In my mind, if the container is not supported then Emby can definitely repackage the streams as it sees fit - what it shouldn't be doing is transcoding them as this is wasteful and unnecessary. Like I said before, neither Plex nor Roku's UPNP/DLNA application have any issue in playing back the raw MPEGTS/MPEG2/AC3 streams. I'll be happy to provide more details if required. Cheers!

hi i am starting to feel like a bitch because i have not been able to play any files that is 1080P H264 since the last update please let me know why i paid premium and why should i stick with emby instead of plex i understand you are probably pulling your hair out many times a day , but i feel the same way on my end i did all i could to improve the server, did a reinstall, redone cabling and now server is connected straight to the router uninstalled a few assons please let me know what else am i supposed to do to be able to play this format with no issues thank you log8-7.txt

Hello emby team, Thank you so much for an awesome product. I left Plex a few years ago and have never looked back again. My main clients until rather recently have been x2 Minix Android devices running Emby for Android TV. These have been playing all of my content (besides H264 High 10) without any need for transcoding of the video stream. However since I swapped them out for Apple TV units it seems that all of my media requires transcoding. My initial concern regarding this was my h265 content but unless I am reading the logs incorrectly it would seem that even h264 content is being run through ffmpeg. In the H264 sample I've attached, the subtitle is not supported by the apple TV unit but it would seem that in addition to this the server is recoding the video stream as well? Stream mapping: Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264)) Stream #0:1 -> #0:1 (copy) Also for your information. Regarding the h265 content, I have run some tests with ffmpeg rewriting the tag with "-tag:v hvc1". This has allowed me to stream the files through iTunes (In mp4 format). Server & Client versions Emby: 3.2.70.0 Server: Debian 3.16.51-3+deb8u1 Client: Apple TV 4K - tvOS 11.2.5 Thank you for any assistance you can provide! MKV-H264-Server.txt MKV-H264-Transcode.txt MKV-H265-Server.txt MKV-H265-Transcode.txt

Firstly, sorry if this is the wrong place to ask. I'm new to emby, but I searched and couldn't find a solution. I use an HDHR Prime/WMC to record TV and recently my cable provider started switching to H264. I also use serverWMC to play recorded TV through emby. All MPEG content plays great, H264 does not. It starts transcoding, then dies after a few seconds. It looks like ffmpeg is the culprit, but I don't have much experience reading the logs yet and don't know why. Anyone else have this problem? Is it DRM? server-63591562818.txt transcode-04aa2b14-c805-46b6-bbc8-1b02ea06edb0.txt

Hi there! First of all, I'd like to thank everyone who contributes to this project. It's awesome! I'm having a transcode quality issue with a certain set of files that seems to be related to the value emby chooses for the -maxrate option of the h264 codec. Here's my evidence: I took the ffmpeg transcode command from the (attached) server log and ran it locally (I removed the segment stuff and limited duration with -t, but no changes other than that). Playing the result with a local media player resulted in the same aggressive artifacting I was seeing in my browser. Then, I ran the exact same transcode without "-maxrate 1165053", and boom, no visible artifacts. The bitrate is 2x larger than the original source (not really sure why that's the case), but I run everything over LAN and I have a lot of throughput headroom to spare, so I'd really like to make the trade-off for quality. Is there any way I can affect what emby chooses for maxrate? I've done some poking around and found this thread (https://emby.media/community/index.php?/topic/36226-transcode-quality-degradation-maxrate/), but not much info in there. Running server ver 3.2.15.0 on Ubuntu. Thank you in advance! Log.txt

First of all, Merry Christmas to all! I'm struggling with mkv or m2ts containing AVC/MVC content since a few months. I tried most of the tutorials around the web (makemkv, tsmuxer etc.), but til now, I cannot get this to work with Emby (or Plex). MKV does not work here at all since just Stereoscopic Player plays it). But Playing a MVC m2ts created with tsMuxer over USB connected HDD works. When starting the video (marked FSBS in Metadata) in the Emby app, the half of the 1st 1080p stream is on the one side, and the half of the 2nd 1080p stream on the other. But the video itself plays. When stream starts it looks kinda this (cannot see it absolutely, perhaps thew Streams overlap in the middle): Now to the weird behaviour: When I go into Tools Menu during Playback to change Position (the time doesn't matter), the Movie loads again to the requested time and the screen looks like this, which is an absolute correct working 3D MVC stream recognized by TV:

Hello. I recenrly switched to Emby from a Kodi+Plex setup. A unified library is really handy, and Emby for Kodi is miles better than PleXBMC, however, the mobile devices don't work as well. On this page it says that direct play is only supported with H.264 encoded video in .MP4, .MOV and .M4V containers, however, Plex offered direct playback of H.264 in an .MKV (it still had to transcode when selecting subtitles, even .srt's, but that's another story). Is this feature planned? I can just use Kodi on a jailbroken iPad, but the interface clearly wasn't made with touchscreens in mind. Thanks in advance

Hi, is there any chance you could add the source file codec's (H.264, DTS, MPEG4 etc) to the area where other information such as resolution is displayed? Plex does this and it's really handy to quickly identify a DVD or Blu Ray... and its reassuring. For android TV Thanks! EDIT sorry this is done with Cover Art! doh!

Hi there, I'm having trouble streaming a handful of movies to my WD TV Live, and after much digging I suspect this to be a bug in Media Browser Server. Most of my files stream directly (without transcoding) and play without issue, but a few cause Media Browser to (incorrectly, AFAIK) fire up FFmpeg and then immediately terminate the process. The result is a screen like this on my WD TV Live: Contrary to what the above message says, my WD TV can indeed play the video file as-is without transcoding (see below). My entire library is MKV / H.264 encoded with HandBrake, ranging from High Profile @ Level 4.0 to 5.1. Most of the videos that fail to play are HP@L5.0 or L5.1, but a few are L4.0. According to the WD TV Live's User Manual, appendix page 211, the device supports a maximum of HP@L4.1 1920×1080p30 w/ a bit rate of HD:40. However, I routinely stream HP@L5.0 and HP@L5.1 videos over DLNA using Serviio and they play fine without issue. So the WD TV is certainly capable of directly playing the videos that are failing without any transcoding, but Media Browser appears to be attempting to transcode them anyway, and for some reason it immediately kills the FFmpeg process - even though FFmpeg doesn't throw any errors or abend. Curiously, if I copy the FFmpeg command that Media Browser tries to run and run it manually in command prompt, it works like a charm. Thus I suspect this is a Media Browser bug. Here's the relevant portion of the Media Browser Server log file (full version attached): 21:06:47.4049 Info - App: C:\Users\BobaFett\AppData\Roaming\MediaBrowser-Server\ffmpeg\old\20140105\ffmpeg.exe -fflags genpts -i file:"M:\MB3\Shared\Disney\Brave (2012) [1080p].mkv" -map 0:0 -map 0:1 -map -0:s -vcodec libx264 -force_key_frames expr:if(isnan(prev_forced_t),gte(t,.1),gte(t,prev_forced_t+5)) -vf "scale=trunc(min(iw\,1920)/2)*2:trunc(min((iw/dar)\,1080)/2)*2" -preset ultrafast -crf 23 -r 23.97602 -vsync vfr -profile:v baseline -level 41 -map_metadata -1 -threads 2 -acodec aac -strict experimental -ac 2 -ab 128000 -af "adelay=1,aresample=async=1,volume=2" -y "C:\Users\BobaFett\AppData\Roaming\MediaBrowser-Server\transcoding-temp\533d0985-6037-a22e-7474-7dd0d8ceeec7.ts" 21:06:48.0960 Debug - HttpServer: HTTP GET http://192.168.0.153:8096/mediabrowser/Items/445cc5e11de0ae3b2e93b9473ccb6bda/Images/Primary?params=ec86bcdb5a084c10534a540f0de1eea2;jpg;512;512 21:06:48.1510 Debug - HttpServer: HTTP Response 200 to 192.168.0.159:43914. Response time: 54.003 ms Url: http://192.168.0.153:8096/mediabrowser/Items/445cc5e11de0ae3b2e93b9473ccb6bda/Images/Primary?params=ec86bcdb5a084c10534a540f0de1eea2;jpg;512;512 21:06:48.8850 Error - App: Error streaming media The specified network name is no longer available System.Net.HttpListenerException at System.Net.HttpResponseStream.EndWrite(IAsyncResult asyncResult) at System.IO.Stream.<BeginEndWriteAsync>b__17(Stream stream, IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory`1.FromAsyncTrimPromise`1.Complete(TInstance thisRef, Func`3 endMethod, IAsyncResult asyncResult, Boolean requiresSynchronization) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.IO.Stream.<CopyToAsyncInternal>d__2.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Api.Playback.Progressive.ProgressiveStreamWriter.<StreamFile>d__3.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Api.Playback.Progressive.ProgressiveStreamWriter.<WriteToAsync>d__0.MoveNext() 21:06:48.9210 Debug - HttpServer: HTTP Response 500 to 192.168.0.159:43913. Response time: 1530.0875 ms Url: http://192.168.0.153:8096/mediabrowser/videos/445cc5e11de0ae3b2e93b9473ccb6bda/stream.ts?Params=e1b92f346f00d5aad781f913ab298f25;test;445cc5e11de0ae3b2e93b9473ccb6bda;false;h264;aac;;;;128000;2;;1920;1080;0;41 21:06:49.9131 Info - App: Killing ffmpeg process for C:\Users\BobaFett\AppData\Roaming\MediaBrowser-Server\transcoding-temp\533d0985-6037-a22e-7474-7dd0d8ceeec7.ts 21:06:50.0281 Info - App: FFMpeg exited with code -1 21:06:50.0361 Info - App: Deleting partial stream file(s) C:\Users\BobaFett\AppData\Roaming\MediaBrowser-Server\transcoding-temp\533d0985-6037-a22e-7474-7dd0d8ceeec7.ts Note that in addition to transcoding the video to HP@L4.1, in all cases I observed Media Browser attempts transcode audio tracks to 2.0 ch AAC, which is unnecessary because the WD TV Live supports all Blu-ray audio codecs and channel layouts (e.g., Dolby TrueHD 7.1 ch, DTS-HD MA 5.1 ch). FWIW, I have no problem streaming (transcoding) the same files to my Roku 3 via the Media Browser channel. Here are my system specs: Media Browser Server version 3.0.5267.16902 Windows 7 64-bit SP1 WD TV Live Streaming Media Player (Gen 3) - WDBHG70000NBK-02 Attached are the full Media Browser Server log file, two ffmpeg transcode log files, and the MediaInfo dumps of the files that are failing. Please let me know if you require any additional information and I'll be happy to provide it. I have a little bit of experience writing Windows .NET apps in C# and using FFmpeg, so if there's anything I can do to help with this issue, just let me know. Thanks! mediainfo-brave.txt mediainfo-princess-frog.txt mediainfo-snow-white.txt mediainfo-toy-story-2.txt mediainfo-toy-story-3.txt mediainfo-toy-story.txt mediainfo-up.txt transcode-61fb02dd-c06f-4304-a533-135ffe597d17.txt transcode-461e8d72-acee-48ff-a52a-dd38147e7299.txt server-63537597258.txt

Hi all, Looking for outside wisdom on this one - Have the latest and greatest MB3 server installed (3.0.5050.37565) on a clean install and small amount of h264 WTV files (8 total). However, I've noticed that the metadata is not being saved by MB Server for the movies to the folders at all (for any of them) - upon inspection I'm suspecting it has something to do with trying to get the run time of the movie itself, which seems to return as a massively huge number. Case example is the movie Angels & Demons - I've used VideoRedo to create the .wtv file from a re-encode I made from the original. Link to the metadata from the library explorer is here http://paste2.org/UKGVK1Lc , and the relevant part of the logfile is here which is detailing the error http://paste2.org/U4YsYvUF - to me, it appears the move length value is aborting the saving of the metadata file, would that be correct? I should point out there's absolutely NO problems with playback, the file itself plays back perfectly, runtime length is correct, however it's a wee wrinkle that has me puzzled (and the lack of the metadata obviously stops the values pulling through to MBC displays). Anyone have any ideas?