Matt Angus

It seems that [l4t multimedia api supports 10 bit](https://docs.nvidia.com/jetson/l4t-multimedia/group__ee__nvbuffering__group.html#ggaae53b45fe3f04b8f9135cb80baeac6e4a4de0818f45efde4ace1c36bb54c26b98). Am I interpreting this correctly? I'm going to try and add this feature but I'm really not sure what I'm doing...

Ok, when I have the time I can set up a dockerfile for building ffmpeg in [jocover/jetson-ffmpeg](https://github.com/jocover/jetson-ffmpeg), and then the jellyfin one can pull from that. But It seems like...

I have now moved the building of ffmpeg to another container. I also added the wrapper script from @LinusCDE. @cvium is this moving in the right direction?

The only modification I made to your script @LinusCDE is turning off hardware acceleration when the pixel format is unsupported.

@TomErnst1972 I have a jetson nano and it works fine for me. Can you post the following: ``` $ jetson_release - NVIDIA Jetson Nano (Developer Kit Version) * Jetpack 4.5.1...

Also post `ffprobe ` so we can see if it has something to do with the encoding.

I actually happend to encounter an issue like this myself. Here is a photo. It only happens on my android tv. Here is a photo: ![WhatsApp Image 2022-03-19 at 3...

this is now part of the docs: https://hookstate.js.org/docs/exceptions/#hookstate-111 closing.

Oops saw 101 and read 111 😅

I think I found the culprate. The buffer being red is always `unsigned byte` because the type is never checked here https://github.com/vispy/vispy/blob/main/vispy/gloo/framebuffer.py#L257 My hack is to check the internal type:...