FFMPEG Unrecognized option 'cq:v'
I am trying to enable HW acceleration on Immich-latest
I setup the HW-Transcoding.yml and uncommented the lines out of the docker-compose.yml
unfortunatly nvidia-smi and nvtop both dont show the process and when i took a docker log immich_server it gave the results of.
[Nest] 7 - 02/07/2025, 2:56:01 AM ERROR [Microservices:MediaService] Error occurred during transcoding: ffmpeg exited with code 8: Unrecognized option 'cq:v'.
Error splitting the argument list: Option not found
Is this a bad config on my end or is ffmpeg needing to be update on immich side?
Everything works perfectly without HW accel. And I did see a line on the FAQ's that Raspberry PI is not supporting HW accel at the moment. Not sure if that is related considering the AARCH64.
IE. I am using this setup
Computer: ipi.wiki Ampere Altra Dev Kit
CPU: Ampere Altra Q80-30 AARCH64
RAM: 93.8Gb
GPU: RTX 3060
OS: Ubuntu 24.04
8 Replies
:wave: Hey @Mistox,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.The arm64 build for ffmpeg probably isn’t built with nvenc support. You can ask the folks at jellyfin-ffmpeg if they want to support this: https://github.com/jellyfin/jellyfin-ffmpeg
You are correct ffmpeg returns
@ ~> sudo docker exec -it immich_server ffmpeg -hide_banner -hwaccels
Hardware acceleration methods:
drm
opencl
rkmpp
can I request that ffmpeg be compiled with nvenc support on immich
I have a workaround by using the default ffmpeg supplied by ubuntu. Each time I update immich I also run
docker exec -it immich_server apt update
docker exec -it immich_server apt install ffmpeg
And now HW accel works on my aarch64 but it be nice if it was just in the original docker img
We use Jellyfin-ffmpeg for a lot of compatibility improvements, if you use the Ubuntu one you'll get HWA sure but lose all of the other things
Well okay if compiling jellyfin-ffmpeg with a flag set for hw acceleration on aarch64 is out of your control or just not important to you then i guess we can close this
Note that they're constantly improving jellyfin-ffmpeg to add different sorts of hardware encoding/decoding support. See https://github.com/jellyfin/jellyfin-ffmpeg/pull/536