Jump to content

Search the Community

Showing results for tags 'transcoding'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • Non-Emby General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support


  • Emby Blog


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

  1. TikiShack

    How can I improve transcoding?

    My media server will be running OMV. It’s an older motherboard/CPU that was specifically selected for its low power consumption. Can I just add a decent graphics card to get adequate transcoding? Or will I need to upgrade the mobo/CPU?
  2. zyfinity


    Am I better off buying a $250 NZD pc with an i7 3770 with 16 GB of ddr3 1600mhz ram and add a spare Rx 570 I have to help for transcoding or should I get a pentium g5400 build with 8gb of ddr4 ram, which one will perform better, I can put the Rx 570 in either build since I have it lying around spare but want to know which would be better since the pentium also has better quicksync, both are a similar price, I want the build with the most possible h265 1080p to h264 1080p transcodes possible as I share with alot of my friends.
  3. I'm considering to create an h265 version of my movies for remote streaming that allows a decent quality with a low bitrate, However there is a potential problem if the client can't direct play the video stream and the server transcode from a h265 version, that could potentially overload my server with multiple streams. My request is to have an option to disable transcoding for h265 codec, so if the client can't direct play the stream the server switch to transcode the h264 file. I know that Emby choose the better version to play but if the user manually selected the h265 version the server will transcode that version.
  4. I check my server dashboard often. Most times I check it, it shows my users (friends) watching content via Direct Play which is great. Once in a while it will be Direct Stream and very seldom transcode. I have my library set up in a way to direct play ( smaller file sizes etc) However when I check this Playback Reporting, it looks like most everything is Direct Streaming? Unless I am reading it wrong. Im just wondering why when I check my dashboard it says everything Direct Plays but this Playback Reporting looks like everything Direct Streams? Screen Shot attached. Thanks
  5. Hi gurus, I have the following situation: Emby server on shield 2015 version emby server does not play files when these need transcoding of dvdsub subtitles (vlc displays codec as SPU (i.e. pictures). works fine with srt and mov_text. Disabling hardware transcoding doesn't help nore does subtitle extraction. logs attached of situation with hardware transcoding on. Thanks guys! edit: problems exists both on shield emby client 1.7.43g and webbrowser (opera and safari) embyserver.txt ffmpeg-transcode-4628573d-ee69-4e82-9a04-d68d631ddb43_1.txt
  6. Hardware detection logs are attached to the post. I had an emby server installed on xpenology that I have backuped using the plugin and I used this backup to restaure the configuration on a new ubuntu 18.02 box with a different cpu (an Intel 3770), Now the advanced options under transcoding show the cpu of the old installation. When I restart Emby the hardware dectetion log shows the old CPU So I think there is an issue that when restauring a backup, it keeps some settings regarding the cpu of the older configuration. Does anyone know if there a way to make Emby detect the cpu of the new installation? I have looked for a similar issue on the forum and elsewhere but I saw nothing. Here is my actual cpu: lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 58 Model name: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Stepping: 9 CPU MHz: 2935.183 CPU max MHz: 3900,0000 CPU min MHz: 1600,0000 BogoMIPS: 6799.81 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 8192K NUMA node0 CPU(s): 0-7 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Here is an extract of server log: 2019-07-14 16:56:38.727 Info Main: Application path: /opt/emby-server/system/EmbyServer.dll 2019-07-14 16:56:39.001 Info Main: Emby Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb Operating system: Unix 64-Bit OS: True 64-Bit Process: True User Interactive: True Runtime: file:///opt/emby-server/system/System.Private.CoreLib.dll Processor count: 8 Program data path: /var/lib/emby Application directory: /opt/emby-server/system 2019-07-14 16:56:39.039 Info App: Application version: 2019-07-14 16:56:39.041 Info App: Loading assemblies 2019-07-14 16:56:39.083 Info App: File /var/lib/emby/plugins/StudioImages.dll has version 2019-07-14 16:56:39.083 Info App: File /opt/emby-server/system/plugins/StudioImages.dll has version 2019-07-14 16:56:39.087 Info App: File /var/lib/emby/plugins/AudioDb.dll has version 2019-07-14 16:56:39.095 Info App: File /opt/emby-server/system/plugins/AudioDb.dll has version 2019-07-14 16:56:39.104 Info App: File /var/lib/emby/plugins/Tvdb.dll has version 2019-07-14 16:56:39.106 Info App: File /opt/emby-server/system/plugins/Tvdb.dll has version 2019-07-14 16:56:39.115 Info App: File /var/lib/emby/plugins/Fanart.dll has version 2019-07-14 16:56:39.124 Info App: File /opt/emby-server/system/plugins/Fanart.dll has version 2019-07-14 16:56:39.133 Info App: File /var/lib/emby/plugins/Emby.PortMapper.dll has version 2019-07-14 16:56:39.141 Info App: File /opt/emby-server/system/plugins/Emby.PortMapper.dll has version 2019-07-14 16:56:39.150 Info App: File /var/lib/emby/plugins/NfoMetadata.dll has version 2019-07-14 16:56:39.152 Info App: File /opt/emby-server/system/plugins/NfoMetadata.dll has version 2019-07-14 16:56:39.161 Info App: File /var/lib/emby/plugins/OMDb.dll has version 2019-07-14 16:56:39.170 Info App: File /opt/emby-server/system/plugins/OMDb.dll has version 2019-07-14 16:56:39.180 Info App: File /var/lib/emby/plugins/Emby.Dlna.dll has version 2019-07-14 16:56:39.191 Info App: File /opt/emby-server/system/plugins/Emby.Dlna.dll has version 2019-07-14 16:56:39.194 Info App: File /var/lib/emby/plugins/MovieDb.dll has version 2019-07-14 16:56:39.204 Info App: File /opt/emby-server/system/plugins/MovieDb.dll has version 2019-07-14 16:56:39.204 Info App: File /var/lib/emby/plugins/MusicBrainz.dll has version 2019-07-14 16:56:39.214 Info App: File /opt/emby-server/system/plugins/MusicBrainz.dll has version 2019-07-14 16:56:39.223 Info App: File /var/lib/emby/plugins/Emby.Server.CinemaMode.dll has version 2019-07-14 16:56:39.232 Info App: File /opt/emby-server/system/plugins/Emby.Server.CinemaMode.dll has version 2019-07-14 16:56:39.234 Info App: File /var/lib/emby/plugins/OpenSubtitles.dll has version 2019-07-14 16:56:39.243 Info App: File /opt/emby-server/system/plugins/OpenSubtitles.dll has version 2019-07-14 16:56:39.270 Info App: Loading MBBackup, Version=, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/MBBackup.dll 2019-07-14 16:56:39.270 Info App: Loading StudioImages, Version=, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/StudioImages.dll 2019-07-14 16:56:39.270 Info App: Loading AudioDb, Version=, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/AudioDb.dll 2019-07-14 16:56:39.270 Info App: Loading Tvdb, Version=, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Tvdb.dll 2019-07-14 16:56:39.270 Info App: Loading Fanart, Version=, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Fanart.dll 2019-07-14 16:56:39.270 Info App: Loading Emby.PortMapper, Version=, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.PortMapper.dll 2019-07-14 16:56:39.270 Info App: Loading NfoMetadata, Version=, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/NfoMetadata.dll 2019-07-14 16:56:39.270 Info App: Loading MediaBrowser.Plugins.Anime, Version=, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/MediaBrowser.Plugins.Anime.dll 2019-07-14 16:56:39.270 Info App: Loading OMDb, Version=, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/OMDb.dll 2019-07-14 16:56:39.270 Info App: Loading Emby.Dlna, Version=, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.Dlna.dll 2019-07-14 16:56:39.270 Info App: Loading MovieDb, Version=, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/MovieDb.dll 2019-07-14 16:56:39.270 Info App: Loading MusicBrainz, Version=, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/MusicBrainz.dll 2019-07-14 16:56:39.270 Info App: Loading Emby.Server.CinemaMode, Version=, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.Server.CinemaMode.dll 2019-07-14 16:56:39.270 Info App: Loading OpenSubtitles, Version=, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/OpenSubtitles.dll 2019-07-14 16:56:39.270 Info App: Loading IsoMounter, Version=, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/IsoMounter.dll 2019-07-14 16:56:39.270 Info App: Loading MediaBrowser.Api, Version=, Culture=neutral, PublicKeyToken=null 2019-07-14 16:56:39.270 Info App: Loading MediaBrowser.WebDashboard, Version=, Culture=neutral, PublicKeyToken=null 2019-07-14 16:56:39.270 Info App: Loading MediaBrowser.Model, Version=, Culture=neutral, PublicKeyToken=null 2019-07-14 16:56:39.270 Info App: Loading MediaBrowser.Common, Version=, Culture=neutral, PublicKeyToken=null 2019-07-14 16:56:39.270 Info App: Loading MediaBrowser.Controller, Version=, Culture=neutral, PublicKeyToken=null 2019-07-14 16:56:39.270 Info App: Loading MediaBrowser.Providers, Version=, Culture=neutral, PublicKeyToken=null 2019-07-14 16:56:39.270 Info App: Loading Emby.Photos, Version=, Culture=neutral, PublicKeyToken=null 2019-07-14 16:56:39.270 Info App: Loading Emby.Server.Implementations, Version=, Culture=neutral, PublicKeyToken=null 2019-07-14 16:56:39.270 Info App: Loading Emby.LiveTV, Version=, Culture=neutral, PublicKeyToken=null 2019-07-14 16:56:39.270 Info App: Loading Emby.Server.MediaEncoding, Version=, Culture=neutral, PublicKeyToken=null 2019-07-14 16:56:39.270 Info App: Loading MediaBrowser.LocalMetadata, Version=, Culture=neutral, PublicKeyToken=null 2019-07-14 16:56:39.270 Info App: Loading Emby.Notifications, Version=, Culture=neutral, PublicKeyToken=null 2019-07-14 16:56:39.270 Info App: Loading Emby.Codecs.Dxva, Version=, Culture=neutral, PublicKeyToken=null 2019-07-14 16:56:39.271 Info App: Loading Emby.Codecs, Version=, Culture=neutral, PublicKeyToken=null 2019-07-14 16:56:39.271 Info App: Loading Emby.Server.Connect, Version=, Culture=neutral, PublicKeyToken=null 2019-07-14 16:56:39.271 Info App: Loading Emby.Server.Sync, Version=, Culture=neutral, PublicKeyToken=null 2019-07-14 16:56:39.271 Info App: Loading EmbyServer, Version=, Culture=neutral, PublicKeyToken=null 2019-07-14 16:56:39.538 Info SqliteUserRepository: Sqlite version: 3.26.0 2019-07-14 16:56:39.539 Info SqliteUserRepository: Sqlite compiler options: COMPILER=gcc-6.3.0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOKENIZER,ENABLE_FTS4,ENABLE_FTS5,ENABLE_JSON1,ENABLE_PREUPDATE_HOOK,ENABLE_RTREE,ENABLE_SESSION,ENABLE_UNLOCK_NOTIFY,ENABLE_UPDATE_DELETE_LIMIT,LIKE_DOESNT_MATCH_BLOBS,MAX_SCHEMA_RETRY=25,MAX_VARIABLE_NUMBER=250000,OMIT_LOOKASIDE,SECURE_DELETE,THREADSAFE=1 2019-07-14 16:56:39.566 Info SqliteUserRepository: Default journal_mode for /var/lib/emby/data/users.db is wal 2019-07-14 16:56:39.569 Info SqliteUserRepository: PRAGMA synchronous=1 2019-07-14 16:56:39.619 Info AuthenticationRepository: Default journal_mode for /var/lib/emby/data/authentication.db is wal 2019-07-14 16:56:39.620 Info AuthenticationRepository: PRAGMA synchronous=1 2019-07-14 16:56:39.680 Info ActivityRepository: Default journal_mode for /var/lib/emby/data/activitylog.db is wal 2019-07-14 16:56:39.680 Info ActivityRepository: PRAGMA synchronous=1 2019-07-14 16:56:39.689 Info SqliteDisplayPreferencesRepository: Default journal_mode for /var/lib/emby/data/displaypreferences.db is wal 2019-07-14 16:56:39.689 Info SqliteDisplayPreferencesRepository: PRAGMA synchronous=1 2019-07-14 16:56:39.699 Info HttpServer: Adding HttpListener prefix http://+:8096/ 2019-07-14 16:56:39.700 Info HttpServer: Adding HttpListener prefix https://+:8920/ 2019-07-14 16:56:39.863 Info SqliteItemRepository: Default journal_mode for /var/lib/emby/data/library.db is wal 2019-07-14 16:56:39.863 Info SqliteItemRepository: PRAGMA synchronous=1 hardware_detection-63698720203.txt
  7. ShadowKindjal

    Best GPU for Transcoding

    I'm currently running my emby server off of an e5-2670 processor with 64 GB of ram on Linux. I typically have up to 10 concurrent streams so I added an RX 580 to improve the transcoding performance of my server. Well, my 580 graphics card is malfunctioning and needs to be pulled out of commission so I'm looking to upgrade. Would anyone be able to recommend a graphics card that will easily be able to handle at least 20 concurrent streams? Right now my content is limited to 1080p but I would also like to stream 4k content at some point. I know there's an issue with Nvidia cards limiting concurrent streams to 2 but I've heard that the drivers can be patched to get around this issue. Is that also true? Any help would be appreciated.
  8. xontik

    Hardware transcoding

    Hi everyone ! I'm back after upgrading my graphic card ! I had trouble using transcoding because my old GT430 didn't support NVENC, but now i'm using an GTX980 I'm sure this big boy can easily transcode a lot of thing, but unfortunatly it won't... As u can see in dash board picture, it's using nvidia nvenc to encode but using sofware decode, i think this is the bottleneck here... How can i force using hardware decode instead of software ? Thanks for this awesome product Ben
  9. nitin.sidhu23

    Hardware transcoding on raspberry pi4

    Hello I am using raspberry pi 4 as an emby server. Emby is running as a docker container. I have mounted the /dev/dri directory into the container. But i am having issue with transcoding of 1080p HEVC movies. Raspberry pi 4 should be able to hardware transcode these? Even if i run the container as root, it was always that it is software transcoding. I have bought the premiere subscription and hardware transcoding is enabled in the server setting docker-compose file is: emby: image: emby/embyserver_arm32v7: restart: always container_name: emby ports: - 8096:8096 - 8920:8920 #optional devices: - "/dev/dri:/dev/dri" environment: - UID=0 - GID=0 - GIDLIST=0,44,107 volumes: - /mnt/media/appdata/emby/config:/config - /mnt/media:/all_media - /mnt/media/appdata/emby/transcode:/transcode I have attached the related logs here. is it possible to do hardware transcoding on raspberry pi 4? embyserver.txt ffmpeg-transcode-58e1fc73-f99b-441b-95bb-806a0d8a8bf1_1.txt hardware_detection-63697349429.txt
  10. Hi, I have my Emby server on Shield TV, and everything works fine unless I want to transcode files bigger than ~2GB. The transcoding process causes the Shield to run out of memory (RAM) and it restarts the Emby Server. No error is displayed on logs since the restart is caused by the lack of memory (I checked that trough adb access to my Shield). This problem occurs during conversion (sync) or transcoding during playback. I have already tried the following Emby versions: You can check the transcoding log in attachment. Tips for developers: I don't know, but the -rtbufsize keyword for ffmpeg could limit the amount of RAM used in the process. Could this trick be an easy way to overcome this issue? Thank you very much. ffmpeg-transcode-.txt
  11. My emby server only go up to 720p 1,5mbps on auto decision transcoding but I can manually go up to 4k 40 mbps without problems or buffering. Hw acceleratet transcoder (up to hevc for encoding and decoding) and 50mbps upload. So why is emby not go higher in quality and Bitrate? It can be so much more than that what emby think is good.
  12. Hi, Quite new to Emby but impressed so far and have an active Emby Premiere subscription. I am having issues with files not playing direct when they do on other apps such as Plex and DLNA and also over WIFI to my mobile phone. I get direct play error in stats for nerds (screenshot attached) and on dashboard Transcoding (226 fps) 10.4 Mbps H264 AAC H.264 (AVC) NVENC/DEC H.264 (AVC) NVENC/DEC Android TV is on wired Gb Lan so no issues there This always happens when trying to play 1080p video and is such unwatchable as it is jerky and audio is way out of sync. Been through all the settings i can think of and the only way I have managed to play the content is when Audio Output is set to downmix to stereo then the same file plays direct. Everything related to streaming and transcoding is either set to max or auto. I have even put the IP of the Android TV box in the Hostng settings and turned off subtitles. Logs are attached. Just one more thing I am unclear about, how does the server know if I am connecting from with my home network or connecting from outside? Thanks and regards, remux.txt server.txt transcode.txt
  13. Hey, my emby Server setup: Ubuntu Server 18.04 Intel Xeon E-2126G (Quick Sync Video, H.265 encode/​decode, VP9 encode/​decode) P11C-I Intel No I stuck on get hardware transcoding working. I installed VAAPI but emby don´t show any available hardware transcoding settings. Is here a way to get it work?
  14. ProperlyFormattedDataFile

    MPEG2 (ATSC) Playback on Roku Stick / Stick+ is very glitchy

    Hi, I'm using Emby on Linux with an HD Homerun for Live TV. Playing back MPEG2 content without transcoding results in a lot of graphical glitches that aren't present in the recording itself when transcoded to H.264 at a similar bandwidth. For example frames will freeze, or movement in the frame will leave blocky trails. Other than setting the maximum bitrate below the broadcast bitrate, is there any way to force the Roku client to always transcode to H.264? Thanks
  15. genfuzuki

    Transcoding green glitches

    Hi, I seem to have an issue with transcoding some movies. Every now and then (four or five times a minute the video breaks up with a green distortion for a few seconds (attached). I have two examples of different movies transcoding from 1080p H264 to 720 on my Roku Locally and on my IOS app remote (Direct stream is fine) so assume it is when transcoding. The server is an i5 with 16GB Ram and Intel 4000 GPU, SSD for Windows OS, SSD for Emby Cache and movies are on a USB3 Drobo. GPU is being used for transcoding and set to auto. Plex is also installed on the same server and does not suffer with these problems but would really like to uninstall so I can use Emby as my default media server. Any ideas ?
  16. Hi, I noticed that transcoding has some troubles with the red parts in a movie. In the original video it's all nice and clean but when I transcode a movie (for baking in subs) I see strange bars appearing like this: The original movie doesn't have problems with red colors. There are no issues with other colors, only red. I already lowered the H264 encoding CRF but that didn't made any difference. Are there other users who experience the same and is there a solution to fix this? Thanks!
  17. I have update from 4.0 and now I am having major issues with transcoding videos for playback to a Roku. Nothing in my setup changed other than the emby server update. I have tried to look at the logs but am unable to make heads or tails of them as I am not use to looking at these sorts of logs. Information about my Emby setup Base is Windows 2012 Server R2 1 x 1TB Hard drive 1x 5TB Hard Drive Cache is currently set to a USB3.0 Flash drive (this is a trial item. Was set to a folder on the 1TB hard drive prior.) Transcoding cache is set to a RAM disk. As the transcoding space is temporary and should be quick access I created a RAM disk on my server for the purpose of this. Any logs that would be needed please let me know. If others are experiencing this as well I would like to know. If there is anyway I can rollback my Emby Server version that would be helpful as well.
  18. I have a bunch of DVDs ripped that have commentary tracks/alternate audio tracks. I've been trying to replace them with HD video files. Many of these video files do not have the alternate audio tracks attached. IS there a way to copy the audio tracks from the original mkv to the new mkv? (i am aware that they might not sync up 100%
  19. Hi, I am having some issues doing hardware transcoding through docker. I have everything setup correctly (I think) but it looks like it's still using software. I've setup my emby user as a member of the video group, set permissions to /dev/dri/renderD128 to 777, and have the hardware decoder mapped through docker. See below for my docker-compose config: # Emby Media Server emby: image: emby/embyserver container_name: emby restart: unless-stopped network_mode: bridge ports: - "8096:8096/tcp" - "8920:8920/tcp" environment: - TZ=${TZ} - UID=${PUID_EMBY} - GID=${PGID_KODI} - GIDLIST=44 volumes: - ${PICKYDIR}/emby:/config - ${DOCKERDIR}/media:/mnt/share1 - ${DOCKERDIR}/backups:/mnt/share2 - ${SSD}/transcode_emby:/transcode devices: - "/dev/dri/renderD128:/dev/dri/renderD128" Any other ideas? embyserver.txtffmpeg-transcode-50eb18ad-ccac-460a-aa92-d25b2f210ad6_1.txthardware_detection-63692603061.txt
  20. Everything works fine when using direct play, when transcoding for whatever reason, be it bitrate, video container or whatever, video starts playing, after few seconds it freezes. The receiver itself is responsive and I'm able to start playing a different video after a freeze. General flow when starting the chromecast is as follows: - Receiver asks initially for a low bitrate video - Playback freezes after a few seconds cause transcoding is enabled to lower bitrate - After the freeze, I select the movie again and send it to the Chromecast - This time the receiver doesn't ask for a lower bitrate of the video, direct play is selected and the video plays fine all the way through That's for files which don't need transcoding, for files which can't use direct play I'm not able to go past a few seconds no matter what I do. Transcoding works perfectly fine in the web app in Firefox and Chrome. The Android app also works fine. There's nothing interesting in the server's logs, I can add them if you need them though, ffmpeg's logs also look normal. The only messages the web app is getting from the receiver are regular progress events, which just send periodically the time which chromecast is stuck at. When looking in the admin panel you can see the activity indicator showing the movie being played, with the playtime moving forward and then periodically moving back to the time Chromecast is stuck at, e.g: 00:04 00:05 00:06 00:04 00:05 I'm unable to debug the receiver as my device isn't whitelisted, that'd certainly help with this situation. This issue only started recently, a month ago, maybe two months ago or something. Before that, chromecast was working perfectly without any issues. Emby server version is, it's available on the internet, I can provide access to Emby devs if necessary.
  21. Secundo°

    Transcoding clarification

    Hello, I'm not very familiar with transcoding. I want to use hardware acceleration for my new emby server. My old emby server was installed on a single board computer. With 2 simultaneous streams the Cpu was throttling and at 100%. Because the Cpu on the new server should mostly be used for other tasks, I decided to use a dedicated gpu for media transcoding. My understanding was that emby almost exclusively uses decoding and only need encoding for tasks like converting files. But this seems to be wrong. I read in some threads (e.g. https://emby.media/community/index.php?/topic/62545-video-card-advice-for-hardware-transcoding/)that the consumer grade nvidia cards only support 2 simultaneous encoding streams/sessions (decoding is unrestricted). After this hint I also noticed this in the support matrix on nvidia website. Now is my question: Whenever transcoding is necessary does emby also need one encoding stream for one decoding stream? My new understanding is that emby uses decode to convert the current file codec to raw video/audio data and then uses encode in order to turn this raw video/audio data to a more compressed version supported by the streaming client, because the raw video/audio would use a way to much bandwidth for streaming. And if the two gpu encoding streams are exhausted, does emby then simply use the cpu for further encoding? Additional info/ off topic: There will be a maximum of 8-10 simultaneous streams on my new server. I plan to buy the new Gtx 1650 which was released 3 days ago. I will buy this card in around 1-2 months. I think the price of this card will drop much in the near future because it is a horrible value card for gamers (rx570 is ~30% much better at ~10% lower price, most reviews advise against this card for gaming and declare it 'dead on arrival'). But looking at the matrix for supported hardware codecs (https://developer.nvidia.com/video-encode-decode-gpu-support-matrix) this card fully supports every decoding codec (H.264/H.265/VP8/VP9/...) and almost every encoding (no hevc b frames). And whats quiet important for me, this card draws only around 75W and is really silent. Thank you English is not my native language
  22. drops77

    Transcoding Temp always full

    This has actually been happening for a while now. I don't usually trans-code only when i forget to unselect subtitles( Thank you for allowing use on roku to select No subtitles, which sometimes doesnt stick). I am on on ubuntu 19.04 and this also would happened on ubuntu 18 and the previous emby servers. So its not an isolated issue or regression . I have attached a screenshot of my server with no activity and my hardrive full Anyone else having this issue?
  23. I've been using Emby for a while now and just recently I've discovered that I cannot stream HEVC/x265 content - it needs to get transcoded for some reason. Logs: embyserver.txt https://pastebin.com/Tvpzj41N ffmpeg-transcode https://pastebin.com/42aZEcYi I do have to note that I'm running emby in docker. I've tried running it with different base docker image (ubuntu based ffmpeg image https://hub.docker.com/r/jrottenberg/ffmpeg/ ) to get newer version of ffmpeg (4.1) but then I was getting ffmpeg related errors. I do need to note that everything is working butter-smooth on my Android phone (Oneplus 6) version 3.0.45 without transcoding. Above logs from web app are coming from Chrome on Mac OS.
  24. Hello, I've been using Emby for quite a while without any issues that would prevent me from watching videos, etc. However, after updating the server to the latest version ( on armv7 on Debian) there are some issues with video playback. Before the update, I was able to stream videos (H264 in MKV containers) without the need to transcode them. I am running the server on a RaspberryPi 3B, so transcoding would not be an option as it definitely can't happen in realtime (log attached). After the update, the videos somehow need to be transcoded in order to be played back properly. TranscodeReasons=ContainerNotSupported Why is there a flag set for mkv not being supported? Few lines higher: 2019-04-22 11:54:23.059 Info App: Profile: Unnamed, Path:*****.mkv, isEligibleForDirectPlay: True, isEligibleForDirectStream: True This would not be an issue if the transcoding was happening in realtime, but its not. I tried disabling hardware acceleration in the server settings, and yes, it did prevent the transcoding process from executing, the video did start, but it was choppy, it kept buffering after three seconds of playback, which I suppose was playing OK before updating. Note that I obviously tried playing different files, with similar results. I have to note that I am using an app remotely, yes, connections both on the server and client side are an another variable in the process, but I highly doubt it could have such an impact, this wasn't happening before. I'll test it in a few days using local connection and post the result here. Attaching emby and ffmpeg logs (I replaced my IP with some text for safety reasons). Thanks for the help. --Edit: I've found some older logs from previous server version, the transcode flag was still set, but it wasn't transcoding the file but "StreamTranscode". I also attached the old logs. embyLog.txt ffmpegLog.txt oldFfmpegLog.txt oldEmbyLog.txt
  25. Hi All, I have mostly made posts moaning about how stuff doesn't work right/the way I want to, but I'm going to give back to the community today! For the TL;DR skip down a few paragraphs, just me venting my woes I go into how I got hardware acceleration to work when it wasn't and everything said it should have been on an Ubuntu LXC container I originally built a FreeNAS machine, on which I planned to store loads of stuff including media, and saw that it had media player plugins. I didn't think too much of it at the time (except I didn't want to use Plex because my experience with it showed that it wasted resources/was the 'dummy' version) so I specced out my server and I built it. I chose a Sky Lake/Kaby Lake cpu for a number of reasons, but one of them was the iGPU. I tried using an Emby plugin but that didn't work (now know it's a whole .NET issue with FreeBSD) and then tried a Docker container of Emby - worked fine, but no hardware acceleration. I wasn't sure why, but I knew I needed more power in the server for the transcoding and other stuff I was using it for so I got a Kaby Lake Xeon cpu, making sure to get one with an iGPU, and kept on plugging away. To cut to the chase: - found out I needed to pass /dev/dri to docker - found out I needed VAAPI to get use of the gpu, but FreeNAS did not support it so it would need to be in a VM and FreeNAS was going through lots of changes - looked around for a few other operating systems that could be used for my purposes, tried OMV - it didn't like ZFS - landed on Proxmox, perfect for my needs - can spin up debian/ubuntu LXC containers easy peasy while passing through whatever I want from the root OS & can make VMs for other OS'/things I want more secure - found out that my motherboard had the C232 chipset & I needed the C236 chipset to use the iGPU - Finally bought the right motherboard Honestly, you would think I had done absolutely no research! But a lot of this was new to me and I didn't realize what I would be using the machine for (didn't know how much use I could get out of Emby per se - I already had an HDHomeRun and Apple TVs...). So I swapped in the right motherboard (plus I got some more SATA ports - gonna be cloning my zpool later to a much larger one w/ more redundancy since I'm using the machine for work too now) and went about making sure that dev/dri and fb0 were passed through to the Emby LXC container. *****Skip to Here***** At this point I double checked that everything was being passed through to the container (eg lspci) & went through the Emby documentation (they state that it Emby should have all the drivers that it needs built in, e.g. their own FFmpeg build). However, when I would play a file that was a direct feed it played fine, but when I tried playing a 4K HVEC or 9/10Bit/VP9/VP10 whatever they actually decided to call that, the video would just load and never start. I went into the console and VAAPI was indeed installed and showed that it was able to decode/encode the appropriate files for my cpu. Checked the log - it looked like FFmpeg was doing it's thing and transcoding the file writing stuff to the temp folder and including a transcoding rate (e.g. at one point it said it was transcoding at 66.6 x frames ). I was about to post on the forum, but I really really really have been wanting to get this working. So I looked around and I found the following site, or rather series of files from the VAAPI sites: https://github.com/intel/media-driver The genesis before that link was basically that VA API needed some extra libraries/intel media SDK to operate depending on the OS/CPU. So that link is for an addition driver that has links to two other libraries that are needed first (libva & GmmLib) along with their dependencies/reqs to build them. Follow the links and cit clone those libraries over to a build directory, make them and install them. For less experienced people the GmmLib instructions are less clear: after git clone GmmLib, make a build directory for cmake & change into it you issue the cmake command with '-DCMAKE_BUILD_TYPE=Release', the site just shows you the possible options. I left out the -DARCH=64 bit because from what I saw on the internet others didn't use it, but you DO need to reference a cmake build file for the command. That is in the root folder of the build folder you made. so either add '..' at the end or '/wherever you git cloned to/gmmlib' to the end of the cmake command and it will run. Then you do the make -j8 command followed by the make install command. Once those two guys are added I git cloned the media-driver bit in, followed the instructions, restarted the container and honestly didn't expect anything to have changed. But hardware transcoding started working like a charm! I do NOT know if it was a combination of those libraries, if it was a dependency of libraries (or maybe just me having to reset the BMC a bunch of times b/c my fan control script was acting up, but I highly doubt that's what it was) but after the above everything worked. As a final note, I don't think this is a shortcoming of the Emby team. As far as I can tell people are using hardware transcoding via the VAAPI files Emby installs just fine. Maybe it had to do with the specifics of my case - Emby running in an LXC container, the LXC container running inside of Proxmox, the fact that because I have IPMI the BMC has it's own video device that are seen in the OS'. I'm just happy I got it to work (maybe can help the Emby team do some investigating) & hope this can help others save some time. Cheers!
  • Create New...