Hi,
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.
Hi,
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.
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?
palne:0,width:4000,height:3000,pitch:4096,psize:12320768
palne:1,width:2000,height:1500,pitch:4096,psize:6160384
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.