In Kodi it is simple, just press the O key.
The CPU usage is a very good indication and this is ultimately why you use hwaccel…
There should be a lot of v4l2-request info in the debug output.
At the moment I cannot try myself to check my output
In Kodi it is simple, just press the O key.
The CPU usage is a very good indication and this is ultimately why you use hwaccel…
There should be a lot of v4l2-request info in the debug output.
At the moment I cannot try myself to check my output
Try something like this:
ffmpeg -loglevel debug -hwaccel drm -hwaccel_output_format drm_prime -i journal.ts -f null /dev/null
I think I remember you also need to add -hwaccel_output_format to enable v4l2-request.
Edit:
Does it work now?
Actually, for newest ffmpeg v4l2-request, it (already) has 4.4.1, so use this instead:
git clone https://github.com/jernejsk/FFmpeg
git checkout v4l2-request-hwaccel-4.4.1-Nexus-Alpha1
git merge --no-edit v4l2-drmprime-v6-4.4.1-Nexus-Alpha1
Yes it works for ffmpeg command-line, thanks. Had no time to build and check kodi.
Btw, is merging the drmprime branch a mandatory? what is the functionality there?
Yes it is, you need the output format to handle the buffers output directly in memory.