markusbr

Seen this often with non-LTS releases... would you have a change to check with e.g. Ubuntu 22.04 (LTS) (or do a quick check within a Ubuntu-LTS docker container)?

Interesting question. @pvigier are you online, still supporting this repository?

From the discussions in the issue "https://github.com/dlstreamer/dlstreamer/issues/445" it looks like the JSON-part of `gvametaconvert` is done in "https://github.com/dlstreamer/dlstreamer/blob/350a6a4fd480628332fc000e04df37322738a939/src/monolithic/gst/elements/gvametaconvert/jsonconverter.cpp". Do you see a chance to "fake" your additional "base64img" data as...

Have a look into these older issues: - https://github.com/dlstreamer/dlstreamer/issues/329 - https://github.com/dlstreamer/dlstreamer/issues/178

So far I haven't looked into `gvametapublish`, it's quite a long chain before it gets finally written into a JSON-file in "https://github.com/dlstreamer/dlstreamer/blob/350a6a4fd480628332fc000e04df37322738a939/src/monolithic/gst/elements/gvametapublish/file/gvametapublishfile.cpp". Have you checked the two issues mentioned above,...

You could check with a gst pipeline graph which format actually was negotiated and provided to each plugin. Or check the format `finfo` within video_info. What do you wanted to...

You are storing `frame_data`, but not `bgr`.

Can you get more details about the received format? Can you just try e.g. `bgr = cv2.cvtColor(frame_data, cv2.COLOR_YUV2BGR)` and then `cv2.imwrite()`?

There is a similar discussion here, e.g. "https://github.com/dlstreamer/dlstreamer/issues/197#issuecomment-805582108". You need to find out more about the exact format, first. E.g. write the raw frame data and then use a raw-image-viewer...

Some of us are just allergic for prebuilt executables with contained crypto-miners ;-)