softworkz 3338 Posted February 21, 2019 Share Posted February 21, 2019 (edited) @@BrettDioson How do you run Emby? As a service or inside a user session? What kind of session? console or remote desktop? When do you start it? Automatically on Windows startup? Could you please try to connect keyboard and monitor to the physical machine and start Emby this way? (console session) Edited February 21, 2019 by softworkz Link to comment Share on other sites More sharing options...
BrettDioson 4 Posted February 23, 2019 Share Posted February 23, 2019 (edited) I have server 2012R2. I usually RDP to the server and start emby manually with the "as administrator" option (I have found issues if you don't run it as administrator). I have started it from console today (I updated the Radeon drivers to 17.21.1 as this is the last one I could find for Windows 2012 that work) and have a monitor attached to the Radeon RX 480 via HDMI. Attached is the latest hardware detection log. *Edit: also added transcode log. looks like its not using hardware still. Emby Hardware Detection Log 20190223.txt Emby Transcode log 20190223a.txt Edited February 23, 2019 by BrettDioson Link to comment Share on other sites More sharing options...
iinthesky73 4 Posted February 24, 2019 Author Share Posted February 24, 2019 @@softworkz Thanks for replying!Ok so i ran the command as you instructed. I'm not sure if this is intended behavior or not, but the command does not appear to execute fully. It hangs forever-- the command does not exit back to the prompt. I'm not sure if this is some buggy behavior or if this is how it is intended to operate. The latter of course would seem unlikely. If you have a new version of ffmpeg/ffdetect I'm more than willing to try anything to get this to work properly. Anyway here is the output: C:\Users\Admin\AppData\Roaming\Emby-Server\system>ffdetect.exe -hide_banner -show_program_version -loglevel 99 -show_error -show_log 99 -print_format json amfenc { "ProgramVersion": { "Version": "4.0.2-emby_2018_12_09-g5abbb1430d+238", "Copyright": "Copyright © 2018-2018 softworkz for Emby Llc", "Compiler": "gcc 8.2.1 (Rev1, Built by MSYS2 project) 20181207", "Configuration": " --disable-autodetect --enable-amf --enable-bzlib --enable-cuda --enable-cuvid --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-nvenc --enable-zlib --enable-sdl2 --disable-debug --enable-ffnvcodec --enable-nvdec --enable-gmp --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-fontconfig --enable-libass --enable-libbluray --enable-libfreetype --enable-libmfx --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libwavpack --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libshine --enable-gpl --enable-avisynth --enable-libxvid --enable-libaom --enable-version3 --enable-libzvbi --enable-gnutls --extra-cflags=-DLIBTWOLAME_STATIC --extra-libs=-lstdc++ --extra-cflags=-DLIBXML_STATIC --extra-libs=-liconv" }, "Device": { "DeviceIndex": 0, "DeviceInfo": { "Description": "Radeon RX 570 Series", "DirectXType": "DX11_1", "DeviceId": 26591, "VendorId": 4098, "SubSysId": 3815120290, "AdapterLuidHigh": 0, "AdapterLuidLow": 47136 }, "Encoders": [ { "CodecName": "h264", "CodecComponentId": "AMFVideoEncoderVCE_AVC", "AccelerationType": "AMF_ACCEL_HARDWARE", "AccelerationTypeInt": 0, "MaxProfile": 100, "MaxLevel": 52, "MaxNumOfStreams": 16, "MaxBitRate": 100000000, "MaxTemporalLayers": 1, "MaxInstanceCount": 1, "Input_MinWidth": 64, "Input_MaxWidth": 4096, "Input_MinHeight": 64, "Input_MaxHeight": 2160, "Input_WidthAlignment": 1, "Input_HeightAlignment": 32, "Input_SupportsInterlaced": 0, "MinWidth": 64, "MaxWidth": 4096, "MinHeight": 64, "MaxHeight": 2160, "WidthAlignment": 1, "HeightAlignment": 32, "SupportsInterlaced": 0 }, { "CodecName": "hevc", "CodecComponentId": "AMFVideoEncoder_HEVC", "AccelerationType": "AMF_ACCEL_HARDWARE", "AccelerationTypeInt": 0, "MaxProfile": 1, "MaxLevel": 186, "MaxNumOfStreams": 16, "MaxBitRate": 2147483647, "MaxTier": 1, "MaxInstanceCount": 1, "Input_MinWidth": 192, "Input_MaxWidth": 4096, "Input_MinHeight": 128, "Input_MaxHeight": 2176, "Input_WidthAlignment": 1, "Input_HeightAlignment": 32, "Input_SupportsInterlaced": 0, "MinWidth": 192, "MaxWidth": 4096, "MinHeight": 128, "MaxHeight": 2176, "WidthAlignment": 1, "HeightAlignment": 32, "SupportsInterlaced": 0 } ] } <-- gets stuck here and does not exit back to prompt One other thing-- just to restate: I am running with an attached monitor and when I go into Manage Server, i can see that the AMD card is listed for decoding but there is nothing at all listed for encoding. Link to comment Share on other sites More sharing options...
iinthesky73 4 Posted February 24, 2019 Author Share Posted February 24, 2019 @@softworkz Actually correction-- it does exit back to the prompt after some time. It also prints out: "Log": [ ] } Then goes back to the prompt. Sorry-- Link to comment Share on other sites More sharing options...
Luke 37091 Posted February 24, 2019 Share Posted February 24, 2019 I have server 2012R2. I usually RDP to the server and start emby manually with the "as administrator" option (I have found issues if you don't run it as administrator). I have started it from console today (I updated the Radeon drivers to 17.21.1 as this is the last one I could find for Windows 2012 that work) and have a monitor attached to the Radeon RX 480 via HDMI. Attached is the latest hardware detection log. *Edit: also added transcode log. looks like its not using hardware still. Try launching the server directly on the machine, not from RDP. Link to comment Share on other sites More sharing options...
BrettDioson 4 Posted February 24, 2019 Share Posted February 24, 2019 Try launching the server directly on the machine, not from RDP. @@Luke, I did launch it from directly on the machine (console) yesterday. The most recent attached logs are from that one. Link to comment Share on other sites More sharing options...
softworkz 3338 Posted February 24, 2019 Share Posted February 24, 2019 (edited) @@softworkz Actually correction-- it does exit back to the prompt after some time. It also prints out: "Log": [ ] } Then goes back to the prompt. Sorry-- Thanks, this is very helpful information. So what is most likely happening is that your encoders are detected properly but there's some holdup during cleanup/shutdown of ffdetect. Probably it is hitting a timeout when it is run by Emby and that's why Emby doesn't get the output. Could you please try with the latest version of ffdetect: ... If there's still a delay - how long does it take to complete? Edited February 25, 2019 by softworkz Link to comment Share on other sites More sharing options...
cptlores 23 Posted February 24, 2019 Share Posted February 24, 2019 (edited) I've done my due diligence, using a EDID HDMI dongle to make sure the Intel graphics (4600) activate without a monitor, using latest Intel graphics drivers (Win7) and not running Emby as a service. But after the 4.0.x update I am still getting transcoding artifacts. No playback errors per say and dashboard status says Quicksync is used for both decoder and encoder. But it has lots of artifacts in the picture that wasn't there in the 3.x versions of Emby. Edited February 24, 2019 by cptlores Link to comment Share on other sites More sharing options...
softworkz 3338 Posted February 24, 2019 Share Posted February 24, 2019 I've done my due diligence, using a EDID HDMI dongle to make sure the Intel graphics (4600) activate without a monitor, using latest Intel graphics drivers (Win7) and not running Emby as a service. But after the 4.0.x update I am still getting transcoding artifacts. No playback errors per say and dashboard status says Quicksync is used for both decoder and encoder. But it has lots of artifacts in the picture that wasn't there in the 3.x versions of Emby. Could you please create a separate thread? Also see 'How to report a problem': https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/ Link to comment Share on other sites More sharing options...
iinthesky73 4 Posted February 24, 2019 Author Share Posted February 24, 2019 @@softworkz Ok I unzipped the binary to a temp dir and executed the following: X:\Temp\ffdetect>.\ffdetect.exe -version ffdetect version 4.0.3-emby_2019_02_23-g5abbb1430d+405 Copyright © 2018-2018 softworkz for Emby Llc built with gcc 8.2.1 (Rev1, Built by MSYS2 project) 20181214 configuration: --disable-autodetect --enable-amf --enable-bzlib --enable-cuda --enable-cuvid --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-nvenc --enable-zlib --enable-sdl2 --disable-debug --enable-ffnvcodec --enable-nvdec --enable-cuda-nvcc --enable-gmp --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-fontconfig --enable-libass --enable-libbluray --enable-libfreetype --enable-libmfx --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libwavpack --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libshine --enable-gpl --enable-avisynth --enable-libxvid --enable-libaom --enable-version3 --enable-libzvbi --enable-gnutls --extra-cflags=-DLIBTWOLAME_STATIC --extra-libs=-lstdc++ --extra-cflags=-DLIBXML_STATIC --extra-libs=-liconv libavutil 56. 14.100 / 56. 14.100 PS X:\Temp\ffdetect> Measure-Command {start-process .\ffdetect.exe -argumentlist "-hide_banner -show_program_version -logl evel 99 -show_error -show_log 99 -print_format json amfenc" -wait} Days : 0 Hours : 0 Minutes : 2 Seconds : 28 Milliseconds : 99 Ticks : 1480996897 TotalDays : 0.00171411677893519 TotalHours : 0.0411388026944444 TotalMinutes : 2.46832816166667 TotalSeconds : 148.0996897 TotalMilliseconds : 148099.6897 According to this it takes ~2.5 minutes to finish executing ffdetect with the params specified Link to comment Share on other sites More sharing options...
BrettDioson 4 Posted February 25, 2019 Share Posted February 25, 2019 (edited) I tried the executable. It seems to have a significant memory leak for me. It doesn’t finish (let it run for 20 min) and it ate up over 50gb of memory. My server has 128gb ram. Edited February 25, 2019 by BrettDioson Link to comment Share on other sites More sharing options...
softworkz 3338 Posted February 25, 2019 Share Posted February 25, 2019 (edited) Thanks for reporting. Could you please retry with the attached version? ... Edited February 25, 2019 by softworkz Link to comment Share on other sites More sharing options...
iinthesky73 4 Posted February 25, 2019 Author Share Posted February 25, 2019 (edited) @@softworkz Ok this one behaves differently-- but the problem with it is that after it does the detect is starts to spit out a single line (pasted below) in an infinite loop. So this one actually never exits. X:\Temp\ffdetect2>ffdetect.exe -hide_banner -show_program_version -loglevel 99 -show_error -show_log 99 -print_format json amfenc { "ProgramVersion": { "Version": "4.0.3-emby_2019_02_25-g5abbb1430d+406", "Copyright": "Copyright © 2018-2018 softworkz for Emby Llc", "Compiler": "gcc 8.3.0 (Rev1, Built by MSYS2 project)", "Configuration": " --disable-autodetect --enable-amf --enable-bzlib --enable-cuda --enable-cuvid --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-nvenc --enable-zlib --enable-sdl2 --disable-debug --enable-ffnvcodec --enable-nvdec --enable-cuda-nvcc --enable-gmp --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-fontconfig --enable-libass --enable-libbluray --enable-libfreetype --enable-libmfx --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libwavpack --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libshine --enable-gpl --enable-avisynth --enable-libxvid --enable-libaom --enable-version3 --enable-libzvbi --enable-gnutls --extra-cflags=-DLIBTWOLAME_STATIC --extra-libs=-lstdc++ --extra-cflags=-DLIBXML_STATIC --extra-libs=-liconv" }, "Device": { "DeviceIndex": 0, "DeviceInfo": { "Description": "Radeon RX 570 Series", "DirectXType": "DX11_1", "DeviceId": 26591, "VendorId": 4098, "SubSysId": 3815120290, "AdapterLuidHigh": 0, "AdapterLuidLow": 47136 }Start DetectAmfDx11.CheckDeviceDx11. Start CheckDeviceDx11.AddEncoders. , "Encoders": [ { "CodecName": "h264", "CodecComponentId": "AMFVideoEncoderVCE_AVC", "AccelerationType": "AMF_ACCEL_HARDWARE", "AccelerationTypeInt": 0, "MaxProfile": 100, "MaxLevel": 52, "MaxNumOfStreams": 16, "MaxBitRate": 100000000, "MaxTemporalLayers": 1, "MaxInstanceCount": 1, "Input_MinWidth": 64, "Input_MaxWidth": 4096, "Input_MinHeight": 64, "Input_MaxHeight": 2160, "Input_WidthAlignment": 1, "Input_HeightAlignment": 32, "Input_SupportsInterlaced": 0, "MinWidth": 64, "MaxWidth": 4096, "MinHeight": 64, "MaxHeight": 2160, "WidthAlignment": 1, "HeightAlignment": 32, "SupportsInterlaced": 0 }, { "CodecName": "hevc", "CodecComponentId": "AMFVideoEncoder_HEVC", "AccelerationType": "AMF_ACCEL_HARDWARE", "AccelerationTypeInt": 0, "MaxProfile": 1, "MaxLevel": 186, "MaxNumOfStreams": 16, "MaxBitRate": 2147483647, "MaxTier": 1, "MaxInstanceCount": 1, "Input_MinWidth": 192, "Input_MaxWidth": 4096, "Input_MinHeight": 128, "Input_MaxHeight": 2176, "Input_WidthAlignment": 1, "Input_HeightAlignment": 32, "Input_SupportsInterlaced": 0, "MinWidth": 192, "MaxWidth": 4096, "MinHeight": 128, "MaxHeight": 2176, "WidthAlignment": 1, "HeightAlignment": 32, "SupportsInterlaced": 0 } ]End CheckDeviceDx11.AddEncoders. Start CheckDeviceDx11.Cleanup. End CheckDeviceDx11.TerminateContext. End CheckDeviceDx11.ReleaseContext. End DetectAmfDx11.CheckDeviceDx11. }Start DetectAmfDx11.ReleaseDevice. End DetectAmfDx11.ReleaseDevice. Start DetectAmfDx11.ReleaseAdapter. End DetectAmfDx11.ReleaseAdapter. Start DetectAmfDx11.ReleaseAdapter_0. Start DetectAmfDx11.ReleaseAdapter_0. Start DetectAmfDx11.ReleaseAdapter_0. Start DetectAmfDx11.ReleaseAdapter_0. Start DetectAmfDx11.ReleaseAdapter_0. Start DetectAmfDx11.ReleaseAdapter_0. Start DetectAmfDx11.ReleaseAdapter_0. Start DetectAmfDx11.ReleaseAdapter_0. Start DetectAmfDx11.ReleaseAdapter_0. Start DetectAmfDx11.ReleaseAdapter_0. Start DetectAmfDx11.ReleaseAdapter_0. Start DetectAmfDx11.ReleaseAdapter_0. .... .... .... It looks like the detection goes smoothly-- that happens in ~1 second, but then this line above gets repeated forever. I let it run for 10 minutes -- it never exits. Edited February 25, 2019 by iinthesky73 Link to comment Share on other sites More sharing options...
iinthesky73 4 Posted February 25, 2019 Author Share Posted February 25, 2019 @@softworkz One other thing-- might be relevant--might not be. So i ran the command again with a > redirect output to a file. It seems to confirm that the command is executing quickly and it also shows me (presuming stdout and stderr are two different file handles in Windows) that the normal output sent to stdout gets recorded in the output file i redirected to. The infinite loop lines must be getting sent to stderr or whatever the Windows equivalent is because those lines do not appear in the file just using a > redirect. Link to comment Share on other sites More sharing options...
softworkz 3338 Posted February 25, 2019 Share Posted February 25, 2019 So i ran the command again with a > redirect output to a file. It seems to confirm that the command is executing quickly and it also shows me (presuming stdout and stderr are two different file handles in Windows) that the normal output sent to stdout gets recorded in the output file i redirected to. The infinite loop lines must be getting sent to stderr or whatever the Windows equivalent is because those lines do not appear in the file just using a > redirect. Yes, that's supposed to work like this: Good news, the problem should be fixed now: ffdetect.zip Link to comment Share on other sites More sharing options...
BrettDioson 4 Posted February 25, 2019 Share Posted February 25, 2019 OK, that new file worked for me and doesn't appear to have the memory issue. Also it seems to have completed successfully. I replaced the ffdetect.exe in my emby system directory with this new one to see if it would do anything but it appears Emby is still only using software to encode. I have attached log files (emby server run from console). Emby Hardware Detection Log 20190225.txt Emby Server Log 20190225.txt Emby Transcode log 20190225.txt ffdetect 20190225.txt Link to comment Share on other sites More sharing options...
iinthesky73 4 Posted February 25, 2019 Author Share Posted February 25, 2019 (edited) Yes, that's supposed to work like this: Good news, the problem should be fixed now: ffdetect.zip @@softworkz Ok this one looks much different (better) and it's executing in a couple seconds. Question, just to be clear what i am to do-- i have to go into the emby system directory and replace the ffdetect there with this one and then either reboot the box or restart emby server.. So for example-- For my installation-- i would replace the ffdetect in the following dir (where emby server runs out of): C:\Users\Admin\AppData\Roaming\Emby-Server\system\ Correct? Here's the output for reference: X:\Temp\ffdetect3>ffdetect.exe -hide_banner -show_program_version -loglevel 99 -show_error -show_log 99 -print_format json amfenc { "ProgramVersion": { "Version": "4.0.3-emby_2019_02_25-g5abbb1430d+407", "Copyright": "Copyright © 2018-2018 softworkz for Emby Llc", "Compiler": "gcc 8.3.0 (Rev1, Built by MSYS2 project)", "Configuration": " --disable-autodetect --enable-amf --enable-bzlib --enable-cuda --enable-cuvid --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-nvenc --enable-zlib --enable-sdl2 --disable-debug --enable-ffnvcodec --enable-nvdec --enable-cuda-nvcc --enable-gmp --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-fontconfig --enable-libass --enable-libbluray --enable-libfreetype --enable-libmfx --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libwavpack --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libshine --enable-gpl --enable-avisynth --enable-libxvid --enable-libaom --enable-version3 --enable-libzvbi --enable-gnutls --extra-cflags=-DLIBTWOLAME_STATIC --extra-libs=-lstdc++ --extra-cflags=-DLIBXML_STATIC --extra-libs=-liconv" }, "Device": { "DeviceIndex": 0, "DeviceInfo": { "Description": "Radeon RX 570 Series", "DirectXType": "DX11_1", "DeviceId": 26591, "VendorId": 4098, "SubSysId": 3815120290, "AdapterLuidHigh": 0, "AdapterLuidLow": 47136 }Start DetectAmfDx11.CheckDeviceDx11. Start CheckDeviceDx11.AddEncoders. , "Encoders": [ { "CodecName": "h264", "CodecComponentId": "AMFVideoEncoderVCE_AVC", "AccelerationType": "AMF_ACCEL_HARDWARE", "AccelerationTypeInt": 0, "MaxProfile": 100, "MaxLevel": 52, "MaxNumOfStreams": 16, "MaxBitRate": 100000000, "MaxTemporalLayers": 1, "MaxInstanceCount": 1, "Input_MinWidth": 64, "Input_MaxWidth": 4096, "Input_MinHeight": 64, "Input_MaxHeight": 2160, "Input_WidthAlignment": 1, "Input_HeightAlignment": 32, "Input_SupportsInterlaced": 0, "MinWidth": 64, "MaxWidth": 4096, "MinHeight": 64, "MaxHeight": 2160, "WidthAlignment": 1, "HeightAlignment": 32, "SupportsInterlaced": 0 }, { "CodecName": "hevc", "CodecComponentId": "AMFVideoEncoder_HEVC", "AccelerationType": "AMF_ACCEL_HARDWARE", "AccelerationTypeInt": 0, "MaxProfile": 1, "MaxLevel": 186, "MaxNumOfStreams": 16, "MaxBitRate": 2147483647, "MaxTier": 1, "MaxInstanceCount": 1, "Input_MinWidth": 192, "Input_MaxWidth": 4096, "Input_MinHeight": 128, "Input_MaxHeight": 2176, "Input_WidthAlignment": 1, "Input_HeightAlignment": 32, "Input_SupportsInterlaced": 0, "MinWidth": 192, "MaxWidth": 4096, "MinHeight": 128, "MaxHeight": 2176, "WidthAlignment": 1, "HeightAlignment": 32, "SupportsInterlaced": 0 } ]End CheckDeviceDx11.AddEncoders. Start CheckDeviceDx11.Cleanup. End CheckDeviceDx11.TerminateContext. End CheckDeviceDx11.ReleaseContext. End DetectAmfDx11.CheckDeviceDx11. }Start DetectAmfDx11.ReleaseDevice. End DetectAmfDx11.ReleaseDevice. Start DetectAmfDx11.ReleaseAdapter. End DetectAmfDx11.ReleaseAdapter. Start DetectAmfDx11.ReleaseAdapter_0. End DetectAmfDx11.ReleaseAdapter_0. Start DetectAmfDx11.ReleaseFactory. End DetectAmfDx11.ReleaseFactory. Start DetectAmfDx11.CloseDxgi. End DetectAmfDx11.CloseDxgi. Start DetectAmfDx11.CloseD3D. End DetectAmfDx11.CloseD3D. , "Log": [ { "Level": 40, "Category": 0, "Message": "Start DetectAmfDx11.CheckDeviceDx11." }, { "Level": 40, "Category": 0, "Message": "Start CheckDeviceDx11.AddEncoders." }, { "Level": 40, "Category": 0, "Message": "End CheckDeviceDx11.AddEncoders." }, { "Level": 40, "Category": 0, "Message": "Start CheckDeviceDx11.Cleanup." }, { "Level": 40, "Category": 0, "Message": "End CheckDeviceDx11.TerminateContext." }, { "Level": 40, "Category": 0, "Message": "End CheckDeviceDx11.ReleaseContext." }, { "Level": 40, "Category": 0, "Message": "End DetectAmfDx11.CheckDeviceDx11." }, { "Level": 40, "Category": 0, "Message": "Start DetectAmfDx11.ReleaseDevice." }, { "Level": 40, "Category": 0, "Message": "End DetectAmfDx11.ReleaseDevice." }, { "Level": 40, "Category": 0, "Message": "Start DetectAmfDx11.ReleaseAdapter." }, { "Level": 40, "Category": 0, "Message": "End DetectAmfDx11.ReleaseAdapter." }, { "Level": 40, "Category": 0, "Message": "Start DetectAmfDx11.ReleaseAdapter_0." }, { "Level": 40, "Category": 0, "Message": "End DetectAmfDx11.ReleaseAdapter_0." }, { "Level": 40, "Category": 0, "Message": "Start DetectAmfDx11.ReleaseFactory." }, { "Level": 40, "Category": 0, "Message": "End DetectAmfDx11.ReleaseFactory." }, { "Level": 40, "Category": 0, "Message": "Start DetectAmfDx11.CloseDxgi." }, { "Level": 40, "Category": 0, "Message": "End DetectAmfDx11.CloseDxgi." }, { "Level": 40, "Category": 0, "Message": "Start DetectAmfDx11.CloseD3D." }, { "Level": 40, "Category": 0, "Message": "End DetectAmfDx11.CloseD3D." } ] } Edited February 25, 2019 by iinthesky73 Link to comment Share on other sites More sharing options...
iinthesky73 4 Posted February 25, 2019 Author Share Posted February 25, 2019 (edited) @@softworkz So I went ahead and replaced the ffdetect.exe at the location I specified. While these results look better, and even if there was some sort of timeout condition, this is likely gone now. However, our main problem still stubbornly remains. After replacing the binary I went ahead and ran an .avi which always gets transcoded before playing and I notice the same old circumstances. The GPU is not used and the CPU usage spikes to near 100%. I've attached screenshot of the config and the logs below. I'm not sure how it's supposed to look but as you can see.. Decoders are present but it has nothing under the Encoder heading... Probably nothing we haven't seen before. In the Transcode log it still looks like Emby is selecting the cpu. ffmpegTranscodeLog.txt HardwareDetectLog.txt EmbyServerLog.txt Edited February 26, 2019 by iinthesky73 Link to comment Share on other sites More sharing options...
itsjust_khris 4 Posted February 27, 2019 Share Posted February 27, 2019 I am unable to get logs at the moment but the same issue occurs with my Radeon Vii. The Hardware Decoders tab is filled but there’s nothing under the encoders tab. The FFdetect.exe provided in the thread recognizes the AMF encoder but using it in Emby shows no change in the encoders tab. I’ve also attempted to use the beta build but the only difference is that the decoders are now using direct x 11. No change in the encoders tab. 1 Link to comment Share on other sites More sharing options...
Luke 37091 Posted February 27, 2019 Share Posted February 27, 2019 I am unable to get logs at the moment but the same issue occurs with my Radeon Vii. The Hardware Decoders tab is filled but there’s nothing under the encoders tab. The FFdetect.exe provided in the thread recognizes the AMF encoder but using it in Emby shows no change in the encoders tab. I’ve also attempted to use the beta build but the only difference is that the decoders are now using direct x 11. No change in the encoders tab. We'll need to see the log files, thanks. Link to comment Share on other sites More sharing options...
softworkz 3338 Posted February 27, 2019 Share Posted February 27, 2019 I am unable to get logs at the moment but the same issue occurs with my Radeon Vii. The Hardware Decoders tab is filled but there’s nothing under the encoders tab. The FFdetect.exe provided in the thread recognizes the AMF encoder but using it in Emby shows no change in the encoders tab. I’ve also attempted to use the beta build but the only difference is that the decoders are now using direct x 11. No change in the encoders tab. The detection has already been fixed internally, but there's a few other things undergoing some work right now, so it may take a few days... Please be patient... 2 Link to comment Share on other sites More sharing options...
BrettDioson 4 Posted February 27, 2019 Share Posted February 27, 2019 The detection has already been fixed internally, but there's a few other things undergoing some work right now, so it may take a few days... Please be patient... Thanks for the update, standing by. Let us know if there are any other logs or tests you need. Link to comment Share on other sites More sharing options...
itsjust_khris 4 Posted February 28, 2019 Share Posted February 28, 2019 Hey, no rush I didn't intend to sound impatient sorry! Here are the logs: hardware_detection-63686855851.txt ffmpeg-transcode-1ef29121-ac3d-444a-b5f3-f3b5fcc93201_1.txt embyserver.txt Link to comment Share on other sites More sharing options...
softworkz 3338 Posted March 8, 2019 Share Posted March 8, 2019 @@iinthesky73 @@itsjust_khris @@BrettDioson The new beta should fix the AMF detection. Please retry and let me know if it's working now.. Thanks 1 Link to comment Share on other sites More sharing options...
iinthesky73 4 Posted March 8, 2019 Author Share Posted March 8, 2019 @@softworkz Ok so.. I should grab the setup.exe from the "Beta Channel" link from the download page and just install it over my existing installation? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now