Happy2Play 9780 Posted January 25, 2019 Posted January 25, 2019 (edited) Same or different version of ffdetect.exe between 3.x and 4.x versions? If different what happens if you use the version from 3.x while 4.x is installed? (suggesting this only for diagnostic purposes) There is no automated detection in versions before v4. Edited January 25, 2019 by Happy2Play 1
MischievousMet 0 Posted January 26, 2019 Author Posted January 26, 2019 Same or different version of ffdetect.exe between 3.x and 4.x versions? If different what happens if you use the version from 3.x while 4.x is installed? (suggesting this only for diagnostic purposes) This gave me an idea that worked and is keeping me on Emby! I deleted Emby.ServerUpdater.exe along with the associated DLLs. While it still tries to update to v4 and tells me that it has been updated, I am on 3.5.3 and it is allowing me to use my GPU for both decoding and encoding. When new versions are released, I will back up my 3.5.3, give the new version a go in hopes that it solves my weird issue.
Luke 42077 Posted January 26, 2019 Posted January 26, 2019 Can you supply an ffmpeg log example from 3.5? thanks.
MischievousMet 0 Posted January 26, 2019 Author Posted January 26, 2019 Can you supply an ffmpeg log example from 3.5? thanks. There you go. Hopefully this is of some help. ffmpeg-transcode-f24197f9-3389-49e6-8832-79047a0fe299.txt
MischievousMet 0 Posted January 27, 2019 Author Posted January 27, 2019 Talking to one of my users about then issue and he had a thought. If I could remove the update exe and dlls in 3.5.3, could I delete ffdetect in v4? Would that break HW dec/enc all together or would it be like 3.5 and give me the option of everything?
Luke 42077 Posted January 28, 2019 Posted January 28, 2019 That's not a scenario we're testing, but we will go over your issue in detail this week. Thanks.
softworkz 5066 Posted February 7, 2019 Posted February 7, 2019 Talking to one of my users about then issue and he had a thought. If I could remove the update exe and dlls in 3.5.3, could I delete ffdetect in v4? Would that break HW dec/enc all together or would it be like 3.5 and give me the option of everything? Please do not delete any files from the Emby installation. You should not delete ffdetect, that would only make things worse. Also you shouldn't consider the "option of everything" in Emby 3.5 as a removed feature. Instead, we just stopped displaying invalid options. Regarding QuickSync, please try the latest beta. Thank you.
Luke 42077 Posted February 10, 2019 Posted February 10, 2019 Have you by any chance disabled Windows User Account Control? (UAC) ? It seems error code 1073741819 is related to that.
softworkz 5066 Posted February 11, 2019 Posted February 11, 2019 Have you by any chance disabled Windows User Account Control? (UAC) ? It seems error code 1073741819 is related to that. No it isn't. This is hex number C0000005 which is unfortunately a rather generic number that could come from anywhere. In this case it is probably due to a function used in more recent nvidia drivers that we were not dyn-loading (cuMipmappedArrayDestroy). @@MischievousMet - This should be fixed in the latest beta (since ffdetect 4.0.3-emby_2019_01_21)
MischievousMet 0 Posted February 12, 2019 Author Posted February 12, 2019 No it isn't. This is hex number C0000005 which is unfortunately a rather generic number that could come from anywhere. In this case it is probably due to a function used in more recent nvidia drivers that we were not dyn-loading (cuMipmappedArrayDestroy). @@MischievousMet - This should be fixed in the latest beta (since ffdetect 4.0.3-emby_2019_01_21) 4.1.0.8-beta?
MischievousMet 0 Posted February 12, 2019 Author Posted February 12, 2019 I gave the beta a test and I'm still getting the same issue. I attached the logs as well as the console command you asked me to run on the v4 stable release. embyserver-63685525380.txt hardware_detection-63685524873.txt cmd test.txt
softworkz 5066 Posted February 12, 2019 Posted February 12, 2019 Hmpf, I had expected this to be fixed... Thanks for posting the logs. Which version of the Nvidia Drivers do you have installed? respectively - have you installed drivers from Nvidia or did you just stick to those that are included with Windows? If not, please install the latest Nvidia drivers and restart the system. Another thing you could try would be removing one of the Nvidia boards. For our multi-GPU tests we were always using two identical boards, while you have two different ones. That's just a shot in the dark, though...
MischievousMet 0 Posted February 13, 2019 Author Posted February 13, 2019 Hmpf, I had expected this to be fixed... Thanks for posting the logs. Which version of the Nvidia Drivers do you have installed? respectively - have you installed drivers from Nvidia or did you just stick to those that are included with Windows? If not, please install the latest Nvidia drivers and restart the system. Another thing you could try would be removing one of the Nvidia boards. For our multi-GPU tests we were always using two identical boards, while you have two different ones. That's just a shot in the dark, though... Removing a GPU did work. It'd be nice if you could get it to work if they aren't the same. Until that happens, I'll stick with one. It's likely not a priority, but having a second older card to offload transcodes and physx to helps gameplay out a tad.
Diedrich 377 Posted February 13, 2019 Posted February 13, 2019 [popcorn] Wow! That was like a really good movie. It had a beginning, middle and even an ending with a twist! Glad you got it sorted out (or at least found the culprit). [/popcorn] 1
softworkz 5066 Posted February 13, 2019 Posted February 13, 2019 Removing a GPU did work. It'd be nice if you could get it to work if they aren't the same. Until that happens, I'll stick with one. It's likely not a priority, but having a second older card to offload transcodes and physx to helps gameplay out a tad. Thanks for the update. We'll see what we can do for the next version. Have you tried both GPU boards alone or just the more recent one? It would be very helpful to know whether this error happens only when using both GPUs or if it would also happen with the older GPU board in single-mode..
MischievousMet 0 Posted February 13, 2019 Author Posted February 13, 2019 Thanks for the update. We'll see what we can do for the next version. Have you tried both GPU boards alone or just the more recent one? It would be very helpful to know whether this error happens only when using both GPUs or if it would also happen with the older GPU board in single-mode.. I did test both to be sure. It worked for both when they were individually plugged in.
softworkz 5066 Posted February 13, 2019 Posted February 13, 2019 Thanks again for trying, this is very good to know, because now I can focus on better isolating the detection sequences for both gpus from each other. 1
maegibbons 1287 Posted February 13, 2019 Posted February 13, 2019 Well done @@softworkz for all your continuing outstanding work on HWA. It is much appreciated so please keep going!! Krs Mark 2
softworkz 5066 Posted February 21, 2019 Posted February 21, 2019 @@MischievousMet - the new beta is out! Please try again, I made some changes to the detection code...
MischievousMet 0 Posted February 25, 2019 Author Posted February 25, 2019 @@MischievousMet - the new beta is out! Please try again, I made some changes to the detection code... I slipped on some ice mid last week and have a pretty bad concussion. I'm not allowed to do anything that might push my mind right now and was given a look from the girlfriend when I started to open my PC to put in the old card. So, once I get the okay, I will give it a test and let you know. Likely couple weeks at the earliest.
Luke 42077 Posted February 25, 2019 Posted February 25, 2019 Sorry to hear that. Hopefully you'll have a speedy recovery.
MischievousMet 0 Posted March 15, 2019 Author Posted March 15, 2019 (edited) Sorry to hear that. Hopefully you'll have a speedy recovery. I'm back! I've been given the thumbs up to do some toying around. The most recent beta with 2 different GPUs is not recognizing either Nvidia GPU, but it is allowing me to use my iGPU. It's an improvement I can get away with for now. Something is better than nothing! Keep up the work guys! I should also mention that I can use Nvidia GPUs to decode, but not encode. Edited March 15, 2019 by MischievousMet
Luke 42077 Posted March 15, 2019 Posted March 15, 2019 Thanks. What happens when you try to use it to encode?
softworkz 5066 Posted March 26, 2019 Posted March 26, 2019 I'm back! I've been given the thumbs up to do some toying around. The most recent beta with 2 different GPUs is not recognizing either Nvidia GPU, but it is allowing me to use my iGPU. It's an improvement I can get away with for now. Something is better than nothing! Keep up the work guys! I should also mention that I can use Nvidia GPUs to decode, but not encode. @@MischievousMet - Good to hear that you're better now. Would you be able to post a hw detection log? As discussed earlier, I would be really curious to see what happens with only one of the GPU boards...
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