Jump to content

Search the Community

Showing results for tags 'Transcoding'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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
    • Android TV / Fire TV
    • Windows & Xbox
    • Apple iOS / macOS
    • Apple TV
    • Kodi
    • LG Smart TV
    • Linux & Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • 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
  • Testing Area
    • WMC UI (Beta)
  • Other
    • Non-Emby General Discussion
    • Developer API
    • Hardware
    • Media Clubs

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

  1. Hi, I compiled my own ffmpeg build in order to use vaapi acceleration. It is working fine when I am transcoding without any scaling (e.g. from 1080p 30MBit to 1080p 5Mbit). However, when I change the resolution (e.g. from 1080p 30MBit to 480p 1Mbit) the scaling is off and I only see the top left segment of the original picture (see "down scaling 480p.png and "org scaling 1080p.png). Without vaapi acceleration the scaling works fine. I am running emby on Openmediavault 3.0.84 with Intel HD Graphics P4600 (Dell T20), as you can see in the server log (Log.txt) attached. So, what could be the problem? I would be delighted if you guys could help me. Thanks, kaufhauslicht Log.txt transcode_log_480p.txt transcode_log_1080p.txt
  2. Good Evening, I am submitting this issue as I can't seem to find a way have the chromecast maximum bit-rate respected. There is an option in the web browser and the android client to specify the max bit-rate however it doesn't seem to actually pay attention to it. Below there is a screenshot where I have specified a max bit-rate as 3mbps and the server dashboard shows that it is trans-coding at 5.6mbps, the same happens from the web app on android and from the native android app. I have attached the full server lot and some of the relevant trans-coding logs. Please let me know if there is anything else that I can submit to assist. server-63635846400.txt ffmpeg-remux-4de2156a-7532-4988-959a-f02839ad183a.txt ffmpeg-transcode-a341d09a-6f12-4705-97da-dc47265cf1dd.txt ffmpeg-transcode-ca113fd6-f9bb-4c3e-a869-6a41719c86c0.txt ffmpeg-transcode-ee51c2b7-dd04-480a-8c50-7100f4b023f6.txt
  3. Hi all, Redshirt explained something about the different video play methods in another thread, which explained a lot the me: Transcoding will occur on all the mobile clients if they don't support the codec/container of the source video, or they can't access the media directly. Transcoding is a necessary evil. Streamcopy is a form of transcoding, it means the device supports the stream, but not the container. It's just not as cpu intensive as a full transcode. Direct play and direct stream are two different things. Direct play means that the client can access the file directly. IE it can see the windows shares. Direct stream means the client couldnt' see the file directly so the server is streaming it without transcoding. However...I see a lot of movies on my Android device are transcoded and I wondered what decides which play method is choosen. Can someone explain me? - Is it the use of codecs on the server? - Is it determined by the client? - Is it determined by the video/audio file format? - ... somethinge else? help this noob!
  4. compu2mil

    Desactivar Transcoding

    Hola buen día, me gustaría saber si se puede deshabilitar la transcodificacion.
  5. Greetings, I've really been enjoying running Emby on an old Mac Pro that was given to me; generally with the two Xenons I figured it'd do alright and for the most part I've been correct - across a vast range of media it plays things back flawlessly. However, I watch a lot of Anime (which is an understatement) and a lot of it features subtitles of the ASS variety. Usually when I watch them with VLC on a computer just like the one I have Emby running on, they move fluidly with all the crazy animations that the subbers have added; but in Emby when streaming to any other client that apparently isn't the case. They are often just a little slow, even in shows that have really minimal subbing and in the ones that have crazy stuff going on I've actually seen it pause the video intermittently and take a break during heavy sections like the openings and endings. If you wanna see what a log looks like of me watching an entire episode of something you can find it attached Log.txt . Basically, is there anything I can do to improve playback and prevent this from happening? I really don't want to bake these in to my files, but maybe I'd experience more uniform experiences if I shelled out for a GTX 950 with NVENC or something. What's your opinion? Anyone else have this happen to them? Thanks -Kb
  6. I am CPU transcoding to Android mobile client over the internet (LTE). When I seek using the scrub bar server CPU utilization goes from 90% to 100% and stays there for at least several minutes. When I look at the running processes in task manager, I see a second ffmpeg process was started, I presume to support transcoding from the new seek location. Yet the previous ffmpeg process was not shut down - the two ffmpeg processes are hogging 100% CPU, at 50% each. When I stop playing the Android client one ffmpeg process stops, while the second ffmpeg lingers at 10% CPU for several minutes before terminating. I did check transcoding without seeking through the movie, in this case the server and transcoding are well behaved with ffmpeg using the typical 90% CPU (i7-6800K, slow and 22 quality settings). If I stop playing at the client, the single ffmpeg process terminates immediately. It seems the server would be much more responsive if the unneeded second ffmpeg process were terminated promptly. I suspect this unnecessary server load is degrading the user experience. Perhaps it is not that hard to track down and resolve? Please let me know if there is anything further I can do to help troubleshoot besides the attached logs. Android client is 3.8.x.x beta within the past two days, not sure where to find the version number in the app. Thanks! server-63633825041.txt ffmpeg-transcode-4099a602-80de-4868-a1c2-6ced9ef179f6.txt ffmpeg-transcode-ccf995f1-dae1-460d-974a-1cdca25b27f8.txt ffmpeg-transcode-4b804d44-38b4-437a-98b8-c9572c19c3ae.txt
  7. hooray4me

    Hardware Transcoding Centos 7.2

    I am having some issues getting hardware transcoding to work properly with Emby Server on Centos 7.2.1511. I have successfully installed Media Server Server Studio and build the necessary custom ffmpeg. When I try to play something that should get transcoded I get an error. What is strange is when I run vainfo as seen above, it trys libva info: Trying to open /opt/intel/mediasdk/lib64/iHD_drv_video.so But the emby transcoding logs show it trying libva info: Trying to open /usr/lib64/dri/i965_drv_video.so How do I make emby use the version that shows from vainfo? The analyzer tests pass: [media-admin@DFES ~]$ ./sys_analyzer_linux.py -------------------------- Hardware readiness checks: -------------------------- [ OK ] Processor name: Intel® Core i7-6700K CPU @ 4.00GHz -------------------------- OS readiness checks: -------------------------- [ OK ] GPU visible to OS -------------------------- Intel® Media Server Studio Install: -------------------------- [ OK ] user in video group [ OK ] libva.so.1 found [ OK ] vainfo reports valid codec entry points [ OK ] /dev/dri/renderD128 connects to Intel i915 -------------------------- Media SDK Plugins available: (for more info see /opt/intel/mediasdk/plugins/plugins.cfg) -------------------------- H264LA Encoder = 588f1185d47b42968dea377bb5d0dcb4 VP8 Decoder = f622394d8d87452f878c51f2fc9b4131 HEVC Decoder = 33a61c0b4c27454ca8d85dde757c6f8e HEVC Encoder = 6fadc791a0c2eb479ab6dcd5ea9da347 -------------------------- Component Smoke Tests: -------------------------- [ OK ] Media SDK HW API level:1.21 [ OK ] Media SDK SW API level:1.21 [ OK ] OpenCL check:platform:Intel® OpenCL GPU OK CPU OK This is ffmpeg version: ffmpeg version N-86566-g067e42b Copyright © 2000-2017 the FFmpeg developers built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-4) configuration: --extra-cflags=-I/home/media-admin/ffmpeg_build/include --extra-ldflags='-L/home/media-admin/ffmpeg_build/lib -ldl' --bindir=/home/media-admin/bin --pkg-config-flags=--static --enable-shared --enable-libmfx --enable-nonfree --enable-gpl --enable-decoder=aac --enable-demuxer=mov --enable-libxcb --enable-zlib --enable-protocol=http --enable-filter=aformat --enable-filter=volume --enable-filter=aresample --prefix=/usr libavutil 55. 66.100 / 55. 66.100 libavcodec 57. 99.100 / 57. 99.100 libavformat 57. 73.100 / 57. 73.100 libavdevice 57. 7.100 / 57. 7.100 libavfilter 6. 94.100 / 6. 94.100 libswscale 4. 7.101 / 4. 7.101 libswresample 2. 8.100 / 2. 8.100 libpostproc 54. 6.100 / 54. 6.100 configuration: --extra-cflags=-I/home/media-admin/ffmpeg_build/include --extra-ldflags='-L/home/media-admin/ffmpeg_build/lib -ldl' --bindir=/home/media-admin/bin --pkg-config-flags=--static --enable-shared --enable-libmfx --enable-nonfree --enable-gpl --enable-decoder=aac --enable-demuxer=mov --enable-libxcb --enable-zlib --enable-protocol=http --enable-filter=aformat --enable-filter=volume --enable-filter=aresample --prefix=/usr and my vainfo: [media-admin@DFES usr]$ vainfo error: can't connect to X server! libva info: VA-API version 0.99.0 libva info: va_getDriverName() returns 0 libva info: User requested driver 'iHD' libva info: Trying to open /opt/intel/mediasdk/lib64/iHD_drv_video.so libva info: Found init function __vaDriverInit_0_32 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.99 (libva 1.67.0.pre1) vainfo: Driver version: 16.5.1.59511-ubit vainfo: Supported profile and entrypoints VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: <unknown entrypoint> VAProfileH264ConstrainedBaseline: <unknown entrypoint> VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : <unknown entrypoint> VAProfileH264Main : <unknown entrypoint> VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : <unknown entrypoint> VAProfileH264High : <unknown entrypoint> VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointEncSlice VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileVP8Version0_3 : <unknown entrypoint> VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileVP9Profile0 : <unknown entrypoint> <unknown profile> : VAEntrypointVideoProc VAProfileNone : VAEntrypointVideoProc VAProfileNone : <unknown entrypoint> Here is the rest of the transcoding log. https://tv-internal.securefamily.cloud:8920/emby/videos/7199a462b0d7e08b46eae2b629b4cf01/hls1/main/0.ts?DeviceId=51c87acac428fadb310d4701d8a7176608e4963e&MediaSourceId=7199a462b0d7e08b46eae2b629b4cf01&VideoCodec=h264&AudioCodec=aac&AudioStreamIndex=0&VideoBitrate=808001&AudioBitrate=192000&Level=51&Profile=high&PlaySessionId=6f952a1b69bf48b8bfbc9fdfba527d0c&api_key=e3d6cf64fb104da49a7b946daa01a008&CopyTimestamps=false&TranscodingMaxAudioChannels=6&EnableSubtitlesInManifest=false&Tag=709d00d94b625e4115acb8c1940e5ec4&RequireAvc=true&RequireNonAnamorphic=false&DeInterlace=true&SegmentContainer=ts&MinSegments=1&BreakOnNonKeyFrames=False {"Protocol":"File","Id":"7199a462b0d7e08b46eae2b629b4cf01","Path":"/storage/TV Shows/Paw Patrol/Season 2/Paw Patrol - S02E04-05 - Pups Save the Penguins + Pups Save a Dolphin Pup WEBDL-720p.mkv","Type":"Default","Container":"mkv","Name":"720P/H264/AAC","IsRemote":false,"ETag":"709d00d94b625e4115acb8c1940e5ec4","RunTimeTicks":14025279488,"ReadAtNativeFramerate":false,"IgnoreDts":false,"IgnoreIndex":false,"GenPtsInput":false,"SupportsTranscoding":true,"SupportsDirectStream":true,"SupportsDirectPlay":true,"IsInfiniteStream":false,"RequiresOpening":false,"RequiresClosing":false,"SupportsProbing":true,"RequiresLooping":false,"VideoType":"VideoFile","MediaStreams":[{"Codec":"aac","Language":"eng","TimeBase":"1/1000","CodecTimeBase":"1/48000","DisplayTitle":"Eng AAC stereo Default","IsInterlaced":false,"ChannelLayout":"stereo","BitRate":192000,"Channels":2,"SampleRate":48000,"IsDefault":true,"IsForced":false,"Profile":"LC","Type":"Audio","Index":0,"IsExternal":false,"IsTextSubtitleStream":false,"SupportsExternalStream":false,"Level":0,"IsAnamorphic":false},{"Codec":"h264","Language":"eng","TimeBase":"1/1000","CodecTimeBase":"125/5994","NalLengthSize":"4","IsInterlaced":false,"IsAVC":true,"BitRate":4211058,"BitDepth":8,"RefFrames":1,"IsDefault":true,"IsForced":false,"Height":716,"Width":1280,"AverageFrameRate":23.976,"RealFrameRate":23.976,"Profile":"High","Type":"Video","AspectRatio":"16:9","Index":1,"IsExternal":false,"IsTextSubtitleStream":false,"SupportsExternalStream":false,"PixelFormat":"yuv420p","Level":31,"IsAnamorphic":false},{"Codec":"subrip","TimeBase":"1/1000","CodecTimeBase":"0/1","DisplayTitle":"Und Default","IsInterlaced":false,"IsDefault":true,"IsForced":false,"Type":"Subtitle","Index":2,"IsExternal":false,"IsTextSubtitleStream":true,"SupportsExternalStream":true,"Level":0,"IsAnamorphic":false}],"PlayableStreamFileNames":[],"Formats":[],"Bitrate":4403058,"RequiredHttpHeaders":{}} /home/media-admin/bin/ffmpeg -c:v h264_qsv -i file:"/storage/TV Shows/Paw Patrol/Season 2/Paw Patrol - S02E04-05 - Pups Save the Penguins + Pups Save a Dolphin Pup WEBDL-720p.mkv" -map_metadata -1 -map_chapters -1 -threads 0 -map 0:1 -map 0:0 -map -0:s -codec:v:0 h264_qsv -preset 7 -look_ahead 0 -b:v 808001 -maxrate 808001 -bufsize 1616002 -profile:v high -level 4.1 -force_key_frames "expr:gte(t,n_forced*3)" -vf "scale=trunc(min(max(iw\,ih*dar)\,720)/2)*2:trunc(ow/dar/2)*2" -copyts -vsync -1 -codec:a:0 copy -copypriorss:a:0 0 -f segment -max_delay 5000000 -avoid_negative_ts disabled -start_at_zero -segment_time 3 -individual_header_trailer 0 -segment_format mpegts -segment_list_type m3u8 -segment_start_number 0 -segment_list "/transcoding/transcoding-temp/27a5187f4519d6b8cd458ce2826b887e.m3u8" -y "/transcoding/transcoding-temp/27a5187f4519d6b8cd458ce2826b887e%d.ts" ffmpeg version N-86566-g067e42b Copyright © 2000-2017 the FFmpeg developers built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-4) configuration: --extra-cflags=-I/home/media-admin/ffmpeg_build/include --extra-ldflags='-L/home/media-admin/ffmpeg_build/lib -ldl' --bindir=/home/media-admin/bin --pkg-config-flags=--static --enable-shared --enable-libmfx --enable-nonfree --enable-gpl --enable-decoder=aac --enable-demuxer=mov --enable-libxcb --enable-zlib --enable-protocol=http --enable-filter=aformat --enable-filter=volume --enable-filter=aresample --prefix=/usr libavutil 55. 66.100 / 55. 66.100 libavcodec 57. 99.100 / 57. 99.100 libavformat 57. 73.100 / 57. 73.100 libavdevice 57. 7.100 / 57. 7.100 libavfilter 6. 94.100 / 6. 94.100 libswscale 4. 7.101 / 4. 7.101 libswresample 2. 8.100 / 2. 8.100 libpostproc 54. 6.100 / 54. 6.100 Input #0, matroska,webm, from 'file:/storage/TV Shows/Paw Patrol/Season 2/Paw Patrol - S02E04-05 - Pups Save the Penguins + Pups Save a Dolphin Pup WEBDL-720p.mkv': Metadata: encoder : libebml v1.3.0 + libmatroska v1.4.1 creation_time : 2014-12-21T18:31:30.000000Z Duration: 00:23:22.53, start: 0.000000, bitrate: 4211 kb/s Stream #0:0(eng): Audio: aac (LC), 48000 Hz, stereo, fltp (default) Metadata: BPS : 135217 BPS-eng : 135217 DURATION : 00:23:22.496000000 DURATION-eng : 00:23:22.496000000 NUMBER_OF_FRAMES: 65742 NUMBER_OF_FRAMES-eng: 65742 NUMBER_OF_BYTES : 23705260 NUMBER_OF_BYTES-eng: 23705260 _STATISTICS_WRITING_APP: mkvmerge v7.3.0 ('Nouages') 64bit built on Oct 22 2014 18:53:34 _STATISTICS_WRITING_APP-eng: mkvmerge v7.3.0 ('Nouages') 64bit built on Oct 22 2014 18:53:34 _STATISTICS_WRITING_DATE_UTC: 2014-12-21 18:31:30 _STATISTICS_WRITING_DATE_UTC-eng: 2014-12-21 18:31:30 _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES Stream #0:1(eng): Video: h264 (High), yuv420p(tv, bt709, progressive), 1280x716 [sAR 1:1 DAR 320:179], 23.98 fps, 23.98 tbr, 1k tbn, 2k tbc (default) Metadata: BPS : 4073248 BPS-eng : 4073248 DURATION : 00:23:22.528000000 DURATION-eng : 00:23:22.528000000 NUMBER_OF_FRAMES: 33627 NUMBER_OF_FRAMES-eng: 33627 NUMBER_OF_BYTES : 714105596 NUMBER_OF_BYTES-eng: 714105596 _STATISTICS_WRITING_APP: mkvmerge v7.3.0 ('Nouages') 64bit built on Oct 22 2014 18:53:34 _STATISTICS_WRITING_APP-eng: mkvmerge v7.3.0 ('Nouages') 64bit built on Oct 22 2014 18:53:34 _STATISTICS_WRITING_DATE_UTC: 2014-12-21 18:31:30 _STATISTICS_WRITING_DATE_UTC-eng: 2014-12-21 18:31:30 _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES Stream #0:2: Subtitle: subrip (default) Metadata: BPS : 97 BPS-eng : 97 DURATION : 00:22:53.237000000 DURATION-eng : 00:22:53.237000000 NUMBER_OF_FRAMES: 499 NUMBER_OF_FRAMES-eng: 499 NUMBER_OF_BYTES : 16666 NUMBER_OF_BYTES-eng: 16666 _STATISTICS_WRITING_APP: mkvmerge v7.3.0 ('Nouages') 64bit built on Oct 22 2014 18:53:34 _STATISTICS_WRITING_APP-eng: mkvmerge v7.3.0 ('Nouages') 64bit built on Oct 22 2014 18:53:34 _STATISTICS_WRITING_DATE_UTC: 2014-12-21 18:31:30 _STATISTICS_WRITING_DATE_UTC-eng: 2014-12-21 18:31:30 _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES libva info: VA-API version 0.99.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: va_openDriver() returns -1 [AVHWDeviceContext @ 0xf6c580] Failed to initialise VAAPI connection: -1 (unknown libva error). Device creation failed: -5. [h264_qsv @ 0xf8cc00] No device available for decoder (device type qsv for codec h264_qsv). Stream mapping: Stream #0:1 -> #0:0 (h264 (h264_qsv) -> h264 (h264_qsv)) Stream #0:0 -> #0:1 (copy) Press [q] to stop, [?] for help [NULL @ 0xfa69e0] non-existing SPS 0 referenced in buffering period [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened [h264_qsv @ 0xf8cc00] Error initializing the MFX video decoder: not initialized (-8) Error while decoding stream #0:1: Internal bug, should not have happened Too many packets buffered for output stream 0:1. Conversion failed!
  8. Hi all, I´m new to Emby/Synology so please bare with me if I ask any dumb questions... I recently bought a new DS416 in order to consolidate all media (movies, photos, music, etc) and coming from PC/MediaPortal I have decent knowledge of how things work in general. However, I´ve ran into some issues with my Emby setup and hopefully someone else out there has experienced the same problem(s) and has a magical solution... My DS416 runs on 4 Western Digital Red NAS 3TB harddrives (SHR) with DSM version 6.1.1-15101 Update 4. Emby Server is recently upgraded to version 3.2.19.0 and is setup according to Embyserver for NAS and Synology : Setting Up Your Media Library Share. After this I´ve imported all my videos and everything seems ok except the playback which sucks... My friend who recommended Emby said something about subtitles, i.e. Emby tries to transcode certain types and therefor the CPU is constantly on ~99% (where mono eats about 49% and ffmpeg about 49%). I´m not sure what to do about that more than I´ve done below..?!? So, any help here is greatly appreciated. He also mentioned that native apps are better than 3d part, i.e. browsers, but regardless if I try to watch a movie on my Ipad (native app), my Sony Bravia (native app) or from Firefox, the playback is lagging in 90% of the cases. If/when I disable the subtitles the playback usually gets better but regardless filetype (avi, mkv, mpeg) there´s always a lag and when I check the Emby Dashboard for active devices, the playback is almost always in Transcoding Mode instead of Direct Play or Direct Streaming. Every single movie that´s lagging through Emby, works perfect with VLC from my old (network attached) computer regardless if I use subtitles or not. Besides my old computer, everything else is connected wireless, i.e. my TV, all devices, etc. I´ve also tried to use hardware acceleration; VA API and Intel Quick Sync but no change at all. My router (Asus RT-AC87U with MerlinWRT) is setup with port-forwarding and Emby has both an in-home and remote address which are tested and working. The general WiFi throughput on the LAN side is between 150-500Mbit depending on the connected device and that is sufficient for casting a 720p movie to a Chromecast on the 2d floor without any lag. I don´t intend to use the DS416/Emby to stream to multiple devices, I just want to be able to watch a 720/1080 video at home, from my Sony TV, with smooth playback and subtitles. So, my questions are: 1. Anyone else having the same problem? 2. Have I missed something in the setup? 3. Is there any other/newer ffmpeg version that´s better for my DS416? Like I said, I´m new to DS416/Emby but I know my way around computers/network/routers/etc and I´m more than willing to try out any solution that might fix my problems. Tnx in advance. Cheers,
  9. alchemi183

    Confused by download setting

    Can someone help me understand the server-side user setting called "Allow downloading that requires transcoding"? Server > Users > {select a user} > Downloading There are two settings that can each be independently enabled/disabled per user: * Allow media downloading * Allow downloading that requires transcoding The first seems pretty self-explanatory and I have it enabled for all users. The second setting is relatively new (I don't remember seeing it before) and it confuses me. I understand what transcoding means in the context of video playback over the network, but not what it means in the context of downloading a media file. What does transcoding have to do with a file download? Any help you could give me in understanding that setting would be appreciated. The wiki doesn't show the setting (yet?).
  10. 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
  11. Question for folks, and while I've run my own server/library for quite a few years now, I'm not entirely sure the best language to use with the community, so please bear with me. I did some searching for relevant threads, but I'm not entirely sure what to keyword search on, truth be told. I just picked up a Synology 916+, and I'm running the Emby app as a server on it. Running great. Question is about transcoding support. I went with the shield because it can stream some of the widest selection of video and audio codecs. But when I was running Moana for my son, I noticed the 916+ CPU was pegged at 100%. Not shocking if it's transcoding. I confirmed in the logs that it WAS transcoding, I'm just trying to understand why. It's an MKV package with h.264 encoding, two audio streams encoded, DTS-HD pass thru and DTS-HD -> AAC. I'll post two different sections of logs. I'm not sure the most relevant. The one first looks most relevant, but will include a block after that (from earlier in the log) that might be: Block 1: I think most relevant Stream #0:0: Video: h264 (Main), yuv420p(tv, bt709, progressive), 1920x804 [SAR 1:1 DAR 160:67], 23.98 fps, 23.98 tbr, 1k tbn, 180k tbc (default) Stream #0:1(eng): Audio: dts (DTS-HD MA), 48000 Hz, 7.1, s32p (24 bit) (default) Metadata: title : Surround Stream #0:2(eng): Audio: aac (LC), 48000 Hz, 5.1, fltp Metadata: title : Surround [libx264 @ 0x209fc20] using SAR=1/1 [libx264 @ 0x209fc20] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 [libx264 @ 0x209fc20] profile Main, level 4.0 Output #0, mpegts, to '/var/packages/EmbyServer/target/var/transcoding-temp/35068d1055a4a879cab336d840c40511.ts': Metadata: encoder : Lavf57.56.101 Stream #0:0: Video: h264 (libx264), yuv420p, 1920x804 [SAR 1:1 DAR 160:67], q=-1--1, 23.98 fps, 90k tbn, 23.98 tbc (default) Metadata: encoder : Lavc57.64.101 libx264 Side data: cpb: bitrate max/min/avg: 5068000/0/0 buffer size: 10136000 vbv_delay: -1 Stream #0:1: Audio: aac (LC), 48000 Hz, stereo, fltp (24 bit), 128 kb/s (default) Metadata: encoder : Lavc57.64.101 aac Stream mapping: Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264)) Stream #0:1 -> #0:1 (dts (dca) -> aac (native)) Block 2: Less certain {"Protocol":"File","Id":"d35722b76bfbbfae223da72991767538","Path":"/volume1/*******/Movies/Moana/Moana.mkv","Type":"Default","Container":"mkv","Name":"1080P/H264/DTS","IsRemote":false,"ETag":"25b53afbbfd9eb96cacda9cb1654e673","RunTimeTicks":64328230000,"ReadAtNativeFramerate":false,"SupportsTranscoding":true,"SupportsDirectStream":true,"SupportsDirectPlay":true,"IsInfiniteStream":false,"RequiresOpening":false,"RequiresClosing":false,"SupportsProbing":true,"RequiresLooping":false,"VideoType":"VideoFile","MediaStreams":[{"Codec":"h264","TimeBase":"1/1000","CodecTimeBase":"1001/48000","NalLengthSize":"4","IsInterlaced":false,"IsAVC":true,"BitRate":12614057,"BitDepth":8,"RefFrames":1,"IsDefault":true,"IsForced":false,"Height":804,"Width":1920,"AverageFrameRate":23.97602,"RealFrameRate":23.97602,"Profile":"Main","Type":"Video","AspectRatio":"2.40:1","Index":0,"IsExternal":false,"IsTextSubtitleStream":false,"SupportsExternalStream":false,"PixelFormat":"yuv420p","Level":40,"IsAnamorphic":false},{"Codec":"dts","Language":"eng","TimeBase":"1/1000","CodecTimeBase":"1/48000","Title":"Surround","DisplayTitle":"Eng Surround","IsInterlaced":false,"ChannelLayout":"7.1","BitDepth":24,"Channels":8,"SampleRate":48000,"IsDefault":true,"IsForced":false,"Profile":"DTS-HD MA","Type":"Audio","Index":1,"IsExternal":false,"IsTextSubtitleStream":false,"SupportsExternalStream":false,"Level":0,"IsAnamorphic":false},{"Codec":"aac","Language":"eng","TimeBase":"1/1000","CodecTimeBase":"1/48000","Title":"Surround","DisplayTitle":"Eng Surround","IsInterlaced":false,"ChannelLayout":"5.1","Channels":6,"SampleRate":48000,"IsDefault":false,"IsForced":false,"Profile":"LC","Type":"Audio","Index":2,"IsExternal":false,"IsTextSubtitleStream":false,"SupportsExternalStream":false,"Level":0,"IsAnamorphic":false}],"PlayableStreamFileNames":[],"Formats":[],"Bitrate":12614057,"RequiredHttpHeaders":{}} /var/packages/EmbyServer/target/ffmpeg/bin/ffmpeg -ss 00:37:11.059 -f matroska -codec:0 h264 -codec:1 dts -codec:2 aac -i file:"/volume1/*******/Movies/Moana/Moana.mkv" -map 0:0 -map 0:1 -map -0:s -codec:v:0 libx264 -force_key_frames "expr:gte(t,n_forced*5)" -copyts -avoid_negative_ts disabled -start_at_zero -pix_fmt yuv420p -preset superfast -crf 23 -maxrate 5068211 -bufsize 10136422 -x264opts:0 subme=0:rc_lookahead=10:me_range=4:me=dia:no_chroma_me:8x8dct=0:partitions=none -vsync -1 -map_metadata -1 -map_chapters -1 -threads 0 -codec:a:0 aac -strict experimental -ac 2 -ab 128000 -af "volume=2" -y "/var/packages/EmbyServer/target/var/transcoding-temp/35068d1055a4a879cab336d840c40511.ts" ffmpeg version 3.2.4-20170217T125043UTC Copyright (c) 2000-2017 the FFmpeg developers built with gcc 5.4.0 (GCC) configuration: --prefix=/var/packages/EmbyServer/target/ffmpeg --enable-cross-compile --cross-prefix=x86_64-pc-linux-gnu- --target-os=linux --disable-rpath --arch=x86_64 --enable-libzimg --enable-libmfx --enable-vaapi --enable-yasm --enable-gpl --enable-shared --disable-static --disable-debug --disable-ffplay --disable-ffserver --disable-doc --disable-htmlpages --disable-manpages --disable-podpages --disable-txtpages --enable-gnutls --enable-libass --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libfreetype --enable-fontconfig --enable-gray --enable-libfribidi --enable-libvidstab --disable-indev=sndio --disable-outdev=sndio --extra-version=20170217T125043UTC --extra-libs='-lm -ldl -lrt -lpthread -llzma -lz -lstdc++ ' libavutil 55. 34.101 / 55. 34.101 libavcodec 57. 64.101 / 57. 64.101 libavformat 57. 56.101 / 57. 56.101 libavdevice 57. 1.100 / 57. 1.100 libavfilter 6. 65.100 / 6. 65.100 libswscale 4. 2.100 / 4. 2.100 libswresample 2. 3.100 / 2. 3.100 libpostproc 54. 1.100 / 54. 1.100 Input #0, matroska,webm, from
  12. My issue is related to playing to a chromecast and the server transcoding an HD mkv file instead of direct playing a folder-synced chromecast-quality version. Below is my setup: Emby Server 3.1.2.0 Folder Sync Plugin, version 3.0.6149.23393 Folder Sync Job HD TV Shows synced to external drive Sync job setup to convert new episodes ripped to mkv at 1080p resolution to the HD TV Shows sync folder using the General profile (which mentions compatability with chromecast) and High quality: For purposes of the log files attached, I attempted to play the s02e04 - Chuck Versus the Cougars - Chuck episode. My expectations is that when I cast one of my synced episodes to my Chromecast device, that the server would see the episode has a synced version that is compatible with the Chromecast device and direct play that version. This is how I interpret the Folder Sync help page's explanation of how it should work as well. However, the server is choosing the transcode the original mkv on the fly. I'm sure that I just don't have something setup correctly, or have missed an option somewhere but I can't seem to track it down on my own. Thanks to anyone and everyone who can help point me in the right direction. server-63619862400.txt ffmpeg-transcode-99604d7b-e27c-4328-8dbb-67c917a948d8.txt
  13. Kimballslice1890

    Media loading/transcoding

    This issue is present for me on the current version of Emby server, not sure what version the issue began. I have not changed any of my server setup settings. The issue I am currently now having is accessing the Emby server and beginning to stream media, the full duration of the video starts at about 0:09 and gradually increases as watching. For example, if a video were to be 45 minutes long, when beginning to stream emby will show 0:00/0:09 and as I jump to the end the duration increases incrementally. This is very annoying especially if I am trying to seek through the playback or continue where I may have left off on another computer or account I have to have the video playing and continuously click the end of the video to expand my available seek. Looking for any help I can get with this. Its happening more frequently now, especially with newly added media content. I have tested on different browsers and client devices. Have attempted setting the quality to different levels, including auto, issue is present throughout all tests. This issue occurs when connecting inside of my LAN via HTTP and externally via HTTPS with the emby generated self signed cert. My server is running on Windows server 2008 R2 Virtual Machine 16 thread Xeon E5 2660 dedicated to the machine 8GB of RAM 12TB 7200RPM RAID 5 NAS for storage 70/70MBPS WAN and Gigabit LAN with a dedicated port on motherboard and switch for the VM. Maximum bandwidth for server is set to 35mbps via emby server management.
  14. nwcatalyst

    Add HW Encoding for ODROID C2

    As discussed in this thread, would like to add HW encoding support for the ODROID C2. Another developer from the Hardkernel community has created a program that does the video encoding. We would just need team emby to create the code to re-pipe this into ffmpeg... The C2 would be an awesome and fully capable $40 emby box with this ability (for me, anyway... only looking to do a single 1080/720 stream). Thanks,
  15. ShoutingMan

    Comments on transcoding

    (I'd somewhat highjacked someone else's thread on transcoding. I'll leave theirs be and start this new one.) I had confusing experiences with Emby's transcoding. I did some intentional tests and better understand what's happening. These aren't bug reports. But I'm looking for more insights on how to best use Emby and ideally be able to live transcode content instead of having duplicate pre-transcoded copies. My system: Emby Premiere (3.2.9.0 during testing) ffmpeg is March 10, 2016 (I think) (installed by Emby into the Emby folders, I believe) Skylake i5 3.2 GHz (6th Gen 6500) Intel Graphics HD 530 Windows 10 Connected by 100Mbps switch to 1Gpbs LAN Testing by streaming to a 4th Gen AppleTV connected to the same 100Mbps switch running tvOS Emby
  16. The beta is certainly pretty and generally working well for me. However, I have run into an issue that affects me and probably others whose servers do not support transcoding very well. The problem has to do with subtitles. I first ran into this on a Japanese-language blu-ray that has also has an English audio track. The English audio track is the default, but I would prefer to hear the original and see the English captions that also come with the disc. Playback is smooth and continuous if captions are turned off. It starts and stops (with loading screens while stopped) if captions are turned on. Clearly, this is due to transcoding at the server end. I am running Emby server on my Synology 1813+, which has no hardware support for transcoding. FWIW, the video quality setting in the Roku app is set to AUTO. I have replicated this problem with another 1080p video. Turning on captions also causes the same behavior. I can supply log files if that would help, but from these data points it is pretty clear that the issue is transcoding at the server end. Is there any workaround for this? My Roku 4 is connected via HDMI to a Marantz av7702mkii receiver, and that sends the video via HDMI to an LG OLED65B6P UHDTV. Both the receiver and the HDTV have their own video decoding capabilities, so even if the Roku 4 may not be able to handle captions (I am not sure), either the receiver or the HDTV may be able to. Perhaps the answer to this is to put an option in the Roku app that tells it to take anything the server has directly (no transcoding at the server end) and then pass along anything that IT cannot transcode to whatever is upstream. Thanks!
  17. Hi Everyone, Quick question: Is the Video Acceleration API (VA API) (found under: Emby Server, Transcoding, Hardware Acceleration, Video Acceleration API (VA API) (experimental) compatible with AMD GPUs? Thanks!
  18. I was experimenting with ffmpeg and I noticed that when Emby is transcoding it has ffmpeg leave the black bars untouched. Wouldn't it be more efficient to remove the black bars while transcoding since clients will put them back in on their own anyway? If I understand correctly, there would be performance gains and smaller file sizes in cropping out the black bars. Please correct me if I'm wrong.
  19. Greetings, I have NextPVR set up with my HDHR Connect to schedule and record live TV. The initial recording is a .ts file and for an hour show it was huge like 7-8 GB. Using ffmpeg I re-encoded the .ts file to an mp4 using these options: -c:v libx264 -preset slow -crf 26 -c:a aac. I've used these options before with mkv files and the resulting mp4 is able to be direct played on my xbox one, which is what I thought would happen here. Anyway, heres the problem: I try and play the new mp4 on my xbox one and it says I'm transcoding. (bitrate setting on app is set to auto) Weird. So I do my best to troubleshoot and try to play the same file on emby theater on my win 10 pc where my server lives. Still transcoding. So then I hook up my Dad's roku just to see what would happen and it direct streamed it with no buffering or stopping at all. For some reason the transcoding would not allow it to just play all the way through. So I guess I have two questions: 1) Why does my xbox have to transcode something i know it can direct play since all of my movies are mp4 and direct plays them with no problems. 2) If it can't direct play the file why can't the xbox direct stream it like the roku did which was great quality and no buffering/stopping? Attached are the server, remux, transcode log files, plus the media info for the file at hand. Thanks, server-63621468333.txt ffmpeg-remux-f42d1527-bb15-40a4-b4c3-e638d82bd902.txt ffmpeg-transcode-ab54a10c-5673-4f4d-8c50-e0e3b49e60c8.txt
  20. Hello, I have done a lot of reading up transcoding and multiple movie versions of the same title, but how things affect my exact scenario are a little unclear. I have a movie (movieA) of which I have two versions. One is a full blu ray rip, the other is a compressed version of the blu ray rip (via handbrake) that should be compatible with any playback client. Both are h264; each has different audio codec. /media/movies/movieA/movieA - bluray_rip.mkv (w/ dts master audio; 40mb/s total bitrate) /media/movies/movieA/movieA - compressed.mp4 (w/ AAC audiuo; 7mb/s total bitrate) Emby server picks up the multiple versions properly as expected. Here are my questions: If I try to play movieA on a client that fully supports the full blu ray rip file and has enough network bandwidth, the server should direct play the full blu ray rip. However, if I tried to play movieA on a client that supported everything in the full blu ray rip with the exception of the audio, would it still play the full blu ray rip file and only transcode the audio? Or would it just play the compressed file instead since the audio in that one should be compatible? (Would it sacrifice the far superior video quality just to avoid transcoding audio?) If I tried to play movieA on a client that supported everything in the full blu ray rip, but just didn't have enough bandwidth (bandwith at 30mb/s), would it just play the compressed file instead? Or would it transcode the full blu ray rip? There is a huge bitrate difference between the two files. My server should be capable of transcoding on the fly at a higher bitrate than the compressed file. (Since in this example the bandwidth is 30mb/s, would it sacrifice video quality by playing the compressed file instead of transcoding the full one at ~30mb/s?) I apologize if the answers are obvious. Just trying to understand exactly what happens behind the curtains.
  21. onehans

    Panasonic tv wont play transcoded MKV

    after struggle i found a way to play probably all video in my library via DLNA( the ones i have checked works ) i have two panasonic tv one old probably 7 years and one new just bought. profile that works for me on both tv is in transcoding tab TS, h264, mp3 it has to have option "enable M2ts mode" ON and other two off in advanced, and i removed MOV profile as well as DTS and AC3 from all profiles since they will not work on panasonic. now the problem 1. i have is that this tvs will play subtitles only on MKV container and as i said it wont play if i change TS to MKV. problem 2. is i cant pause or rewind for some reason despite trying options in advanced tab of profile and all posible combinations of MKV TS MP4 AVI my setup is QNAP 253 PRO and EMBY Version 3.1.2.0 my server is on intel and im using ffmpeg binary static 3.2.2 pls help
  22. Hi all. I'd really appreciate a steer on where I'm going wrong with my Emby setup - it's becoming really frustrating! I have Emby Server (3.1.266.0 beta) set up in Lubuntu 16.04. My machine specs are as follows: i5 6600t HD 7950 3 GB 8GB RAM 1 TB 7200rpm HDD for media I have a powerline based home network using AV2 compliant adapters. I've tried a couple of different playback approaches - DNLA via my Bravia TV, Emby for Kodi on my RPi 2 and an old Android TV box (Minix Neo X7) but none work reliably. My media is really mixed in terms of formats and bitrates. I used to have an HTPC in the living room so had no problems with playback, but since moving to a server in another room I have had real trouble getting many things to play successfully. Higher quality files often stutter then fail and I have problems getting HEVC and other files to play at all at times. I'm happy that my network speed is decent - so I guess the issue is transcoding? I have used the Bravia 2014 profile in the past, but this didn't really help. Can someone please tell me what I need to look for in the logs? There's no info on profiles in the wiki so I'm a bit lost as to what to change to force transcoding and what settings would be best to ensure reliable playback. Attached are some recent logs - these will only show DNLA access via the TV I think Cheers ffmpeg-transcode-5b0315be-5855-4daa-8a47-e9bb820f6493.txt server-63618980178.txt
  23. So I've searched google and the forums and haven't really come up with anything for my issue other than the fact that others seem to being having it in some form or another. As the title suggests, I have a Roku 3 and it seems to be transcoding content when it shouldn't be doing so. Rundown of system components: Roku 3 Model 4200X - Software Version: 7.5.0 build 4099-04 I've tried the regular Emby app (v2.25) and Emby Blue Neon Night (v4.01) Linux box running MB Server 3.1.2.0 I've attached a log file which shows my issue. I have (to the best of my knowledge) ensured that my files are in a suitable format for direct play but for whatever reason, transcoding persists. My current server is not suited to transcoding on the fly which is why this is important to me. Now, it's my understanding that the Roku 3 should be able to play H264 video and AAC audio in an MKV container directly. I have confirmed as much by inserting a flash drive containing such files directly into the Roku and watching them without incident. I am just at a loss at this point as to why the Roku will play these files from a flash drive but will not play the same files in the context of the Emby system. I've tried both the regular emby app and BNN versions. On the BNN version, forcing DirectPlay fails. Forcing DirectStream works but buffers at times (is this indicating a LAN speed issue?). When DirectStream is forced the server dashboard indicates that the file is being direct played. I'm not sure if that terminology is meant to be interchangeable like this but it is confusing and doesn't make it easier for me to reach any definitive conclusions. I've increased the bitrate to 30Mb/s on the MB client settings. The Roku is connected to a 1080p capable LG TV with onboard stereo speakers. Audio settings on the Roku app are set to "auto detect" and is accurately detecting that the TV is a stereo system. I'm not completely sure what all I'm looking at in the log file. I'm reasonably familiar with ffmpeg usage but emby is naturally using far more parameters than I would ever use and I haven't set down to decipher the complete command as of yet. I see the usage of the word "scale" with some math/variables and the numbers 1080 and 1920 being thrown around. It concerns me that the server may be upscaling the video from 720 to 1080 which I believe would be more efficiently handled by the TV or Roku. If this is indeed what is going on, can this behavior be turned off? Do the log files contain any of the "decision making" done by the server? By that, I mean, the server is deciding - based on a number of factors - to transcode and stream or to hand over a resource location to the client and let it play it handle it over the network. Are the relevant factors used in that decision making process logged anywhere? Are they in this log file and can someone tell me what they are? Can they be added to the log file by increasing verbosity in the logging system? My goal is to choose a file and have it direct play without being forced. I'm willing and able to do super complicated things the average user may not want to do in an effort to fix my system and help uncover issues which may be affecting others. Let me know if I can provide additional information. Log.txt
  24. When playing a Live TV stream the app defaults to full quality. When I try and change to a lower bitrate, the app stops playing and displays an error: Playback error: There was an error processing the request. Please try again later. Android app is 2.8.39 and Emby is running 3.1.2.0 on a QNAP NAS. Android app log and server log are attached. 5760c215-6535-4a20-a41c-628d5f29a1b3.log server.txt
  25. Right now I have Emby running on a NAS which was perfect for me at the beginning. It has plenty of storage and is always on. The downside is that it can only transcode 1 stream reliably, so if multiple people are watching remotely it can't keep up. I am looking for a box that will just be running the Emby server and has enough CPU to do multiple transcode streams (probably will use an SSD for transcode cache). I will still use the NAS for storage. I don't need any video card or anything along those lines (unless it is more cost effective to get one and utilize it for encoding, but I think a good processor is probably cheaper). I would like to keep the cost down as well. I have looked at some of the higher end NUC's, but the ones with better CPU's get pretty spendy because they are more targeted for gaming and have nice GPUs as well. Anyone have some good recommendations?
×
×
  • Create New...