V4L2 problem with 32bit and 64bit

Open
#3,236 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
linux, raspberry-pi

Research direction

Start by reproducing the reported behavior with the 32-bit and 64-bit Raspberry Pi images built through BitBake poky, comparing V4L2 availability and playback in GStreamer and QMultimedia. Check the GStreamer 1.16 and Qt 5.13 configurations, then document the cause of the decoder difference and verify that the affected MP4 files play with hardware decoding.

Written by the indexing model from the issue text.

Description

Waiting for external input

Hello,
I've two different problems with v4l2 codec on 32 and 64 bit raspberry linux

I've build 32 and 64 bit image for RPI4 with bitbake poky master branch because there is a problem with MESA on Warrior.

RPI4-32bit master GStreamer 1.16 Qt 5.13 v4l2 decoder is active but I'm not able to play mp4 files, work on .mov with gst-launch and some particular mp4 codec but not in QMultimedia. It play only mkv on QMultimedia and Gstreamer but with 2fps

RPI4-64bit master GStreamer 1.16 Qt5.13 v4l2 decoder is not enabled (and don't know why) all video play in both GStreamer and QMultimedia but via avdec_h264 (ffmpeg libav) software decode CPU over 250% for the same video file that play on RPI3 at 18-20% CPU

RPI-32bit burster light with Qt 5.12.3 cross compiled and Gstreamer 1.16 (not compiled by me) same problem ad RPI4-32bit master

There something wrong in my configuration?

Dominant language
C
Stars
13.2k
Forks
5.5k
Avg merge
2d 21h
Merged PRs (30d)
21

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/linux

All issues in raspberrypi/linux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.