FFprobe does not return side_data_list stream info

Open
  • Is something wrong?
#121 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
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
flutter
Domain
mobile-dev

Research direction

Run the shown ffprobe command directly and through the plugin on the same video, then compare the video-stream output and logs. The issue names no source files or tests, so first trace how the plugin invokes ffprobe and passes stream metadata through; done means the plugin output includes the side_data_list shown in the terminal output.

Written by the indexing model from the issue text.

Description

When I record a video on a Pixel 8 in portrait mode, the width and height of the video are reversed and there is a side_data_list metadata info that tells me the rotation of the video so I can play it correctly.

Running following command in terminal works correctly and gives me the side_data_list info under the video stream:

./ffprobe -v quiet -print_format json -show_streams -show_format video.mp4

"side_data_list": [
                {
                    "side_data_type": "Display Matrix",
                    "displaymatrix": "\n00000000:            0       65536           0\n00000001:       -65536           0           0\n00000002:            0           0  1073741824\n",
                    "rotation": -90
                }
            ]

But the same command run with this plugin omits the side_data_list object entirely. It does not get passed into the logs at all. I also tested it with the original plugin and it works correctly there too. I also tested both ffprobe 6.0.2 and 8 separately and they output the correct data.

So there must be some change in this plugin's code that affected this logic. If you can tell me where to look exactly, I can try coming up with a fix.

Dominant language
C
Stars
182
Forks
122
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 sk3llo/ffmpeg_kit_flutter

All issues in sk3llo/ffmpeg_kit_flutter

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.