An important bug about nvargus and tee /queue when captured by using multiple sensors ?

The issue is not about resolution. It hits constraint of CPU capability due to the memory copy. For getting CPU pointer of NVMM buffer, we would suggest use NvBuffer APIs instead of copying the whole buffer. Please refer to this sample:
How to run RTP Camera in deepstream on Nano - #29 by DaneLLL

So that you can get NvBuffer in appsink and call NvBufferMemMap() to get CPU pointer.

Do you know how to get the NVMM to memory by using dmabuf_fd?

I need the buffer to save yuv-file

Please refer to this code:

        char filename[256];

        std::ofstream *outputFile = new std::ofstream(filename);
        if (par.pixel_format==NvBufferColorFormat_YUV420)

        delete outputFile;

dump_dmabuf() is in

1 Like

Thank you for your guidance.I had try it, but the yuV images saved were abnormal.It seems to have a problem with the pixels,it was NV12 format after capture.

device1_.yuv (17.2 MB)

Probably the buffer is in blocklinear. Please set this property of nvvidconv to false:

  bl-output           : Blocklinear output, applicable only for memory:NVMM NV12
 format output buffer
                        flags: readable, writable
                        Boolean. Default: true

And try again.

After set to “bl-output” it will call error:

PosixMemMap (48) failed
nvbuf_utils: NvBufferMemMap function failed… Exiting…
NvBufferMap failed

I noticed other something strange,the pitch no equal to 4000,does it have anything to do with it?

Hello DaneLLL
I can set “bl-output” successfully by commenting out the following code, now I can get normal YUV data
But it created a new problem,the framerate was drop down after set nvvidconv “bl-output”.Is there any issue that can do “BL-output” processing for NVMM data received by appsink separately,not nvVidConv.

A new topic is created:
How to do "bl-output" for a single NVMM-buffer(NV12) which was been received by appsink?

Let’s continue discussion in the topic.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.