Closed tanglebridge closed 1 year ago
It's definitely a bug but not clear where, could also be a bug in the amlogic driver. Does this work if you run it on the host?
Ah. My host has different hardware, and the point is to accelerate the hardware on the target. As you can see ffmpeg correctly loads the module. Might even be a driver issue - you are correct.
By host I mean the os running docker. Instead of running ffmpeg in frigate (in the docker container) I'm asking if the results are different running it in the host OS.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the problem you are having
I am trying to set up hardware acceleration. I have a VIM3/Amlogic A311D board (I use a coral USB TPU).
The board supports hardware acceleration for video and trying to make that work. I ran this line from documentation to test:
To test I run, inside the container:
ffmpeg -c:v h264_v4l2m2m -re -stream_loop -1 -i https://streams.videolan.org/ffmpeg/incoming/720p60.mp4 -f rawvideo -pix_fmt yuv420p pipe: > /dev/null
Note the hardware acceleration arguments I added. In the docker compose file I added
/dev/video0
to devices, because ffmpeg complained abount not being able to access it.When I run the above command I get a segfault! See snippet below. This is an ffmpeg issue but I hope someone here has an idea. Either way it is a bug?
Thank you for making this!
Version
0.11.1-2eada21
Frigate config file
docker-compose file or Docker CLI command
Relevant log output
FFprobe output from your camera
Operating system
Other Linux
Install method
Docker Compose
Network connection
Mixed
Camera make and model
d-link tapo
Any other information that may be helpful
No response