That was the part I was missing to do hardware transcoding appreciate you posting.
Mine is doin Hardware transcoding just fine.
Thank you very much for that writeup. The SSH method got me up and running again, and authenticating with YouTubeTV works! To add to the writeup:
I was careful to uninstall the Channels DVR package from the Synology before installing Channels DVR into Docker via SSH. I'd had the Synology package set up to use /volume1/DVR and uninstalling the package did not delete the contents of /volume1/DVR. After installing the Channels DVR to Docker, going to its webpage presented me with the window to log into my Channels account, but below that in small text was the import wizard, and using that to direct the Docker Channels to /volume1/DVR worked just fine, using the backups in the Databases folder. All of the settings and passes and recordings were still there; all I had to do was set up the YouTubeTV source again.
I checked but the Docker version of Channels is not able to login in with Gmail's 2FA, either; it ends with a screenshot of the 2FA window. Channels is obviously not going to be able to do that, so you still need to use the throwaway Google family group email address without 2FA.
Logging into https://www.nbc.com/live and logging into an NBCUniversal profile before adding YouTubeTV as a source is presumably still needed for best results. It doesn't cause any problems if those are signed in with your main Gmail address with 2FA instead of the throwaway family group email.
I did need to manually direct my TV's Channels install to connect to the server; for example, if the IP address of the Synology is 192.168.100.100, I needed to tell it to connect to:
192.168.100.100:8189
You sure about that because I have a backup DVR that I used the UI on my Synology DS1019+ and there is no hardware transcoding even available.
Would you be so kind as to show us the results of this command run on your Synology?
docker inspect --format='{{json .HostConfig.Devices}}' channels-dvr-tve
replace channels-dvr-tve with the name of your docker container
If you SSH'd in as an admin user, you may have to run it with sudo
sudo docker inspect --format='{{json .HostConfig.Devices}}' channels-dvr-tve
One thing if you want to use the Docker as your main DVR you have to set the ports to 8089:8089 and also --net=host has to be used for remote access.
sudo docker run --detach --name=channels-dvr-tve --net=host --env TZ=America/Los_Angeles -p 8089:8089 --restart=on-failure:10 --device /dev/dri:/dev/dri --volume /volume1/docker/channels-dvr:/channels-dvr --volume /volume1/DVR:/shares/DVR fancybits/channels-dvr:tve
You must have at one time issued a command to Enable hardware transcoding.
Nope I just reinstalled everything Saturday and I know I did not enable it. I am on DSN 7 fresh install. Pulled the TVE version
Using the Channels DVR Synology DSM 7.0 package or in a Docker Container?
Unless you mapped the device /dev/dri for a docker container you shouldn't be getting hardware transcoding. In fact I just duplicated what you said you did and don't get hardware transcoding.
Can you run the command I previously posted?
Would like to know how you did it just using the Synology Docker GUI.
I also just created a docker from the GUI and no hardware transcoding.
Guess he's the only one with the secret sauce and is unwilling to share the secret 
Here's the settings page of the one I just created from the Synology Docker GUI
Just gives me null
Did you update to Pre-release?
No.
Can you screenshot yours like I did mine above
I'm wondering if that setting appears because you restored from a backup that had it enabled.
If you actually play something that needs transcoding, does it hardware transcode?
how did you get the full screen shot?
Firefox capture screen
Strange.
Does it actually use hardware transcoding when you play an OTA channel from your HDHR in the web UI?
Only difference I see between yours and mine (besides the newer CPU in your NAS) is the TVE docker container Linux Alpine version.
I'm running the latest TVE image and mine shows
linux alpine
3.14.0_alpha20210212 (kernel: 4.4.180+)
where yours shows
linux alpine
3.10.3 (kernel: 4.4.180+)




