NewDisplayName Posted January 18, 2019 Share Posted January 18, 2019 I guess, i cant use it. Now it just dropped intel quick sync and even the h264 preset is no longer working. If its not automatic, i rather just delete videos which are not working. Thanks for your help anyway! Quote Link to comment
Djoss Posted January 21, 2019 Author Share Posted January 21, 2019 On 1/18/2019 at 5:49 AM, nuhll said: I guess, i cant use it. Now it just dropped intel quick sync and even the h264 preset is no longer working. If its not automatic, i rather just delete videos which are not working. Thanks for your help anyway! If the built-in presets don't work, you can try reset them to their default (under the Presets menu). Quote Link to comment
NewDisplayName Posted January 21, 2019 Share Posted January 21, 2019 The problem is its not working relialable, i can get it work, and maybe it works 2 days, but then i need to restart server to get it working again. thats no solution for me, maybe its really bc that old cpus are not supported anymore. Ill add this again when i get someday new hardware. thanks for your help anyway! Quote Link to comment
Taddeusz Posted January 24, 2019 Share Posted January 24, 2019 (edited) It seems that in v1.15.0 of your container it's no longer picking up the /dev/dri device correctly and so the QSV encoders aren't showing. Edited January 24, 2019 by Taddeusz Quote Link to comment
Djoss Posted January 24, 2019 Author Share Posted January 24, 2019 7 hours ago, Taddeusz said: It seems that in v1.15.0 of your container it's no longer picking up the /dev/dri device correctly and so the QSV encoders aren't showing. If you look at the container's log, you should see the reason why QSV is not enabled. Quote Link to comment
Taddeusz Posted January 24, 2019 Share Posted January 24, 2019 3 hours ago, Djoss said: If you look at the container's log, you should see the reason why QSV is not enabled. I think it's showing that it's enabled. Not showing that it's not. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 00-app-niceness.sh: executing... [cont-init.d] 00-app-niceness.sh: exited 0. [cont-init.d] 00-app-script.sh: executing... [cont-init.d] 00-app-script.sh: exited 0. [cont-init.d] 00-app-user-map.sh: executing... [cont-init.d] 00-app-user-map.sh: exited 0. [cont-init.d] 00-clean-logmonitor-states.sh: executing... [cont-init.d] 00-clean-logmonitor-states.sh: exited 0. [cont-init.d] 00-clean-tmp-dir.sh: executing... [cont-init.d] 00-clean-tmp-dir.sh: exited 0. [cont-init.d] 00-set-app-deps.sh: executing... [cont-init.d] 00-set-app-deps.sh: exited 0. [cont-init.d] 00-set-home.sh: executing... [cont-init.d] 00-set-home.sh: exited 0. [cont-init.d] 00-take-config-ownership.sh: executing... [cont-init.d] 00-take-config-ownership.sh: exited 0. [cont-init.d] 00-xdg-runtime-dir.sh: executing... [cont-init.d] 00-xdg-runtime-dir.sh: exited 0. [cont-init.d] 10-certs.sh: executing... [cont-init.d] 10-certs.sh: exited 0. [cont-init.d] 10-cjk-font.sh: executing... [cont-init.d] 10-cjk-font.sh: exited 0. [cont-init.d] 10-nginx.sh: executing... [cont-init.d] 10-nginx.sh: exited 0. [cont-init.d] 10-vnc-password.sh: executing... [cont-init.d] 10-vnc-password.sh: exited 0. [cont-init.d] 10-web-index.sh: executing... [cont-init.d] 10-web-index.sh: exited 0. [cont-init.d] 95-check-optical-drive.sh: executing... [cont-init.d] 95-check-optical-drive.sh: looking for usable optical drives... [cont-init.d] 95-check-optical-drive.sh: found optical drive /dev/sr0, group 19. [cont-init.d] 95-check-optical-drive.sh: exited 0. [cont-init.d] 95-check-qsv.sh: executing... [cont-init.d] 95-check-qsv.sh: Processor: Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz [cont-init.d] 95-check-qsv.sh: Device /dev/dri/renderD128 group is 100. [cont-init.d] 95-check-qsv.sh: exited 0. [cont-init.d] handbrake.sh: executing... [cont-init.d] handbrake.sh: core dump file location: core [cont-init.d] handbrake.sh: core dump file size: 0 (blocks) [cont-init.d] handbrake.sh: exited 0. [cont-init.d] done. [services.d] starting services [services.d] starting s6-fdholderd... [services.d] starting certsmonitor... [services.d] starting nginx... [services.d] starting xvfb... [nginx] starting... [certsmonitor] disabling service: secure connection not enabled. [xvfb] starting... [services.d] starting autovideoconverter... [services.d] starting statusmonitor... [statusmonitor] no file to monitor: disabling service... [services.d] starting logmonitor... [logmonitor] no file to monitor: disabling service... [services.d] starting openbox... [autovideoconverter] starting... [openbox] starting... [autovideoconverter] Processing watch folder '/watch'... [autovideoconverter] Watch folder '/watch' processing terminated. [services.d] starting x11vnc... [services.d] starting app... [x11vnc] starting... [app] starting HandBrake... Quote Link to comment
Taddeusz Posted January 24, 2019 Share Posted January 24, 2019 Weird, not sure what happened but apparently it's working again. Quote Link to comment
Taddeusz Posted January 25, 2019 Share Posted January 25, 2019 On 1/24/2019 at 4:43 AM, Djoss said: If you look at the container's log, you should see the reason why QSV is not enabled. Ok, I got this figured out. After I upgraded to 6.7.0-rc2 this morning Handbrake was again not able to use QSV. I noticed that /dev/dri/card0 had owner root:video while the rest of the items in the /dev/dri folder are set nobody:users. I chowned card0 to nobody:users and it is working again. It's weird that that particular device file is not getting chowned on boot like the rest of the /dev/dri folder. The only thing that I can guess is that the card0 device isn't yet available when my user script is run. I'm going to change my script to wait till the card0 device exists to run the chmod and chown commands. 1 Quote Link to comment
Taddeusz Posted January 25, 2019 Share Posted January 25, 2019 Ok, the while statement didn't work because the device file already existed. I ended up putting a "sleep 4" in my script between the modprobe statement and the chmod & chown statements so it now, for anyone else who might be having issues, looks like this: modprobe i915 sleep 4 chmod -R 777 /dev/dri chown -R nobody:users /dev/dri Quote Link to comment
mbc0 Posted January 30, 2019 Share Posted January 30, 2019 Hi, I am revisiting this docker again and just have a question regarding the cpu priority. I have an i7-3770K overclocked to 4.2Ghz and would like Handbrake to use all of it unless something else calls for the CPU power (Windows 10 VM, Plex, etc) It says in the documentation that 19 is the lowest priority, does anyone have any real world expierience with this or would it be better to use CPU pinning? Another option but I cannot find it is to encode during the middle of the night. Quote Link to comment
Hoopster Posted January 31, 2019 Share Posted January 31, 2019 (edited) On 1/25/2019 at 8:25 AM, Taddeusz said: Ok, I got this figured out. After I upgraded to 6.7.0-rc2 this morning Handbrake was again not able to use QSV. I noticed that /dev/dri/card0 had owner root:video while the rest of the items in the /dev/dri folder are set nobody:users. I chowned card0 to nobody:users and it is working again. It's weird that that particular device file is not getting chowned on boot like the rest of the /dev/dri folder. The only thing that I can guess is that the card0 device isn't yet available when my user script is run. I'm going to change my script to wait till the card0 device exists to run the chmod and chown commands. Ran into the same problem. Card0 was owned by root:video. I chowned it to nobody:users (like the rest of /dev/dri) and the QSV encoding options appeared again. Thanks for the tip. Edited February 1, 2019 by Hoopster Quote Link to comment
Jobine Posted February 1, 2019 Share Posted February 1, 2019 Hi, Since the last update, when I convert my files, these don't work on my iPad with Plex. I did't change my presets, I always use the same. Thank, Quote Link to comment
Djoss Posted February 1, 2019 Author Share Posted February 1, 2019 On 1/30/2019 at 9:26 AM, mbc0 said: Hi, I am revisiting this docker again and just have a question regarding the cpu priority. I have an i7-3770K overclocked to 4.2Ghz and would like Handbrake to use all of it unless something else calls for the CPU power (Windows 10 VM, Plex, etc) It says in the documentation that 19 is the lowest priority, does anyone have any real world expierience with this or would it be better to use CPU pinning? Another option but I cannot find it is to encode during the middle of the night. CPU pinning only limit cores on which the container can run. If you want use all resources unless needed by something else, you can try to set the priority like you did, or configure CPU shares: Quote Link to comment
Djoss Posted February 1, 2019 Author Share Posted February 1, 2019 9 hours ago, Jobine said: Hi, Since the last update, when I convert my files, these don't work on my iPad with Plex. I did't change my presets, I always use the same. Thank, Are you using a built-in preset? Quote Link to comment
NewDisplayName Posted February 1, 2019 Share Posted February 1, 2019 (edited) On 1/30/2019 at 3:26 PM, mbc0 said: Hi, I am revisiting this docker again and just have a question regarding the cpu priority. I have an i7-3770K overclocked to 4.2Ghz and would like Handbrake to use all of it unless something else calls for the CPU power (Windows 10 VM, Plex, etc) It says in the documentation that 19 is the lowest priority, does anyone have any real world expierience with this or would it be better to use CPU pinning? Another option but I cannot find it is to encode during the middle of the night. Just add -c=128 to extra parameters... It means ur handbrake gets all power, when no other need it and if power is needed elsewhere it gets at least ((your cpu power / 1024) * 128). If no c is set, it means the docker get 1024 (full power). Set all your dockers u dont need (everything exept plex normally) to 128 and youre good to go. VM and Plex always highest "priority". Edited February 1, 2019 by nuhll Quote Link to comment
Jobine Posted February 1, 2019 Share Posted February 1, 2019 (edited) 3 hours ago, Djoss said: Are you using a built-in preset? No, mine and is the same since 2 years... All files before the last update works ! Edited February 1, 2019 by Jobine Quote Link to comment
Djoss Posted February 1, 2019 Author Share Posted February 1, 2019 6 hours ago, Jobine said: No, mine and is the same since 2 years... All files before the last update works ! Make sure the "Profile" and "Level" settings under the Video tab are compatible with your iPad. I know that HandBrake can adjust the preset according the video you load. Maybe something in this area changed in the latest version. Quote Link to comment
Jobine Posted February 1, 2019 Share Posted February 1, 2019 Profile : high level : 4.2 the same since 2 and the old videos works :( Quote Link to comment
Djoss Posted February 1, 2019 Author Share Posted February 1, 2019 11 minutes ago, Jobine said: Profile : high level : 4.2 the same since 2 and the old videos works Which iPad model/generation do you have? Are you able to read the video on other devices? You can also compare characteristics of a working video and a non-working one. This can be done with Plex (by selecting "get info" of video) or with mediainfo. Quote Link to comment
Jobine Posted February 1, 2019 Share Posted February 1, 2019 iPad mini 4 iPad Air iPad 4 works on my Apple TV 4K, Apple TV 4, iPhone 7 and iPhone XS. Quote Link to comment
Djoss Posted February 1, 2019 Author Share Posted February 1, 2019 1 hour ago, Jobine said: iPad mini 4 iPad Air iPad 4 works on my Apple TV 4K, Apple TV 4, iPhone 7 and iPhone XS. Try to encode with a level of 4.1. That’s what is supported by these devices: https://support.apple.com/kb/SP662?locale=en_CA Quote Link to comment
Jobine Posted February 1, 2019 Share Posted February 1, 2019 Ok, I'll try, but why old movies, work in level 4.2? Quote Link to comment
Djoss Posted February 1, 2019 Author Share Posted February 1, 2019 Just now, Jobine said: Ok, I'll try, but why old movies, work in level 4.2? Did you verify that they are really at this level ? Quote Link to comment
Jobine Posted February 1, 2019 Share Posted February 1, 2019 (edited) Yes, in Plex ! Look these images. The first one work, and the second not. Edited February 1, 2019 by Jobine Quote Link to comment
Jobine Posted February 1, 2019 Share Posted February 1, 2019 I just converted it to level 4.1 and it does't work anymore. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.