ffmpeg | a java library interface to access ffmpeg | Wrapper library

I want to convert my mp4 file to gif format. I was used the command that is working in command prompt. i.e., converting my .mp4 into gif but in go lang it is not done anything. Here is my command:

I have an electron repo (https://github.com/MartinBarker/RenderTune) which used to work on windows 10 fine when ran with command prompt. After a couple months I come back on a new fresh windows 10 machine with an Nvidia GPU, and the electron app prints an error in the window when starting up:

I have been trying to convert a BGR captured frame into the YUYV format.

In OpenCV Python I can do convert YUYV into BGR with COLOR_YUV2BGR_YUY2 conversion code but I cannot do the reverse of this operation (there is no conversion code for this operation, I have tried COLOR_BGR2YUV but it is not converting correctly). I am curious about how to convert 3-channel BGR frame into the 2-channel YUYV frame.

Here you can see the code that I am using to change camera mode to capture YUYV and converting it into BGR, I am looking for the replacement of the cap.set(cv2.CAP_PROP_CONVERT_RGB, 0) so I can capture BGR and convert it into YUYV without cap.set(cv2.CAP_PROP_CONVERT_RGB, 0) (Because it is an optional capture setting and Windows DirectShow ignores this flag)

I'm looking to do some in-browser video work using good-ol' FFmpeg and Rust. Simple examples, where the caller is interacting with the ffmpeg command-line abound. More complex examples are harder to find. In my case I wish to extract, process and rotate discrete frames.

Clipchamp makes impressive use of WASM and FFmpeg, however the downloaded WASM file (there's only one) will not reveal itself to wasm-nm nor wasm-decompile, both complaining about the same opcode:

• wasm-nm: Unknown opcode 253
• wasm-decompile: unexpected opcode: 0xfd 0x0

Has anyone wisdom to share on how I can (1) introspect the WASM module in use or (2) more generally advise on how I can (using WASM and Rust, most likely) work with video files?

I wrote a python script that generates a xstack complex filter command. The video inputs is a mixture of several formats described here:

I have 2 commands generated, one for the xstack filter, and one for the audio mixing.

Here is the stack command: (sorry the text doesn't wrap!)

In case of invalid parameters, cv2.VideoWriter writes stuff to stderr. here is a minimal example:

I have implemented a simple randomized, population-based optimization method - Grey Wolf optimizer. I am having some trouble with properly capturing the Matplotlib plots at each iteration using the camera package.

I am running GWO for the objective function f(x,y) = x^2 + y^2. I can only see the candidate solutions converging to the minima, but the contour plot doesn't show up.

Do you have any suggestions, how can I display the contour plot in the background?

GWO Algorithm implementation

Yesterday i pushed the base image layer for my app that contained the environment needed to run my_app.

That push was massive but it is done and up in my repo.

This is currently the image situation in my local machine:

In order to record the composite-video signal from a variety of analog cameras, I use a basic USB video capture device produced by AverMedia (C039).

I have two analog cameras, one produces a PAL signal, the other produces an NTSC signal:

1. PAL B, 625 lines, 25 fps
2. NTSC M, 525 lines, 29.97 fps (i.e. 30/1.001)

Unfortunately, the driver for the AverMedia C039 capture card does not automatically set the correct video standard based on which camera is connected.

I would like the capture driver to be configured automatically for the correct video standard, either PAL or NTSC, based on the camera that is connected.

The basic idea is to set one video standard, e.g. PAL, check for signal, and switch to the other standard if no signal is detected.

By cobbling together some examples from the DirectShow documentation, I am able to set the correct video standard manually, from the command line.

So, all I need to do is figure out how to detect whether a signal is present, after switching to PAL or NTSC.

I know it must be possible to auto-detect the type of signal, as described e.g. in the book "Video Demystified". Moreover, the (commercial) AMCap viewer software actually proves it can be done.

However, despite my best efforts, I have not been able to make this work.

Could someone explain how to detect whether a PAL or NTSC signal is present, using DirectShow in C++?

The world of Windows/COM/DirectShow programming is still new to me, so any help is welcome.

Using the IAMAnalogVideoDecoder interface, I can read the current standard (get_TVFormat()), write the standard (put_TVFormat()), read the number of lines, and so on.

The steps I took can be summarized as follows: