MediaInfo | MacOS Finder Extension to show information | Video Utils library

The error simple has gone, dont know why but now dont appears in the xaml, without doing any change

Here's a working (work on my machine™️) script in Node.js. Hope it helps. I use the test video from https://www.webmfiles.org/demo-files/

I was able to reproduce the issue, seems that the encoding used is the root cause, I used the gcloud ml speech recognize command and I got no responses:

Answering my own question. The following ffmpeg-python code works as expected:

AAC content, announced as mono. But AAC may have an hidden Parametric Stereo feature which makes this announcement not the reality 99.99% of the time (HE-AAC is rarely used for mono content).

FFmpeg is not able to switch from mono to stereo if stereo is detected after decoder init so it forces its output to stereo due to some anticipation of getting Parametric Stereo at some point.

MediaInfo does not have this limitation so shows stereo only if Parametric Stereo is detected. Parametric Stereo is not detected in this file.

In this case MediaInfo shows the correct value (mono) and FFmpeg shows an incorrect value (stereo). Not blaming FFmpeg here, their developers decided to do that for good reasons (decoding and handling lot of tools not able to deal with channel count change in the middle of a file), just not what you are looking for.

If you are not convinced, try to decode each channel in a different file, and compare files. There is only 1 byte not same between the 2 files, it is the byte saying that this is the left channel vs the right channel. Audio data is same: your file is really mono and even FFmpeg agrees on that when it decodes (in practice it duplicates the mono channel).

Jérôme, developer of MediaInfo.

I still cannot drill into ingestData, but I managed to avoid the issue by passing bucketName and objectName to create the s3 URL to link to the upload data in mongo and passing the whole mediaAnalysis to mongo.

You need to use Bit Stream Video Filter for setting h264 metadata.

When a video player plays a video file, it looks for metadata that attached to the video stream (h264 metadata for example).
The H.264 metadata parameters that affects the colors and brightness are: video_format, colour_primaries, transfer_characteris and matrix_coefficients.

If the parameters are not set, there are defaults.
The defaults for low resolution video are "Limited Range" BT.601 (in most player - I am not sure about MAC OS).
The default gamma curve (affects the brightness) is sRGB gamma curve.
The player converts the pixels from YUV color space to RGB (for displaying the video). The conversion formula is done according to the metadata.

Your input video file input.mp4 has H.264 metadata parameters that are far from the default.

We can assume that scale video filter does not change the color characteristics (the filter applies the YUV elements without converting to RGB).

The characteristics of input.mp4 applies BT.2020, and HLG gamma curve, but converted as if they were default (BT.601 and sRGB gamma), so the colors and brightness are very different from what they should have been.

When FFmpeg encodes a video stream, it does not copy the metadata parameters from the input to the output - you need to set the parameters explicitly.

The solution is using a Bit Stream Video Filter for setting the metadata parameters.

Try using the following command:

After updating version of retrofit and okHttp it works!

The Windows command processor (cmd.exe) is processing a batch file. Its successor is the much more powerful script interpreter PowerShell (powershell.exe). The usage of PowerShell within a batch file does not really make sense as in this case it would be better to do the entire task with a PowerShell script using PowerShell syntax. For that reason I wrote a pure Windows command processor solution.

A file/folder name should be always referenced enclosed in " as otherwise a batch file could fail to process file/folder names containing a space or one of these characters &()[]{}^=;!'+,`~. Most argument strings referencing a file or folder name are enclosed in double quotes in code posted in question, but some are not.

See: Syntax error in one of two almost-identical batch scripts: “)” cannot be processed syntactically here

The first FOR loop is not working as it should: