If you look at the preview screen of the frontend sample, you can see that the bounding box (indicated by the blue arrow) is displayed.
However, there is no bounding box in the encoded video.
Hi,
It is a bit confusing and we would like to make clarification. In attached code, it looks like you would like to put text hello world gc camera to video frames. Do we misunderstand the request? Please help clarify this.
Attach the h.265 encoded video.
I want to encode basic shape osd like text or rectangle with yuv overlaid.
It seems to be applied only when the osd previews display.
I want the osd to be applied to outputx.h.265 as output.
I want the osd to be applied to outputx.h.265 as output.
Is this possible?
The frontend sample description states as follows, and I understood that when the video is encoded in h.264, h.265, it is encoded with the osd drawn on the video.
If I apply what you said, will the video be encoded with the osd applied?
That is, if you check the encoded video, can you check the osd(text, rectangle, etc…)?
When I run the frontend example, the program sometimes dies with an error like the following, can you tell what the problem is?
imx327@imx327-desktop:/usr/src/jetson_multimedia_api/samples/frontend_orig$ sudo ./frontend --deploy …/…/data/Model/GoogleNet_three_class/GoogleNet_modified_threeClass_VGA.prototxt --model …/…/data/Model/GoogleNet_three_class/GoogleNet_modified_threeClass_VGA.caffemodel
[INFO] (NvEglRenderer.cpp:110) Setting Screen width 640 height 480
Full resolution: 1920x1080
[86817.449607] trt: Creating TRT model…
Net has batch_size, channel, net_height, net_width:1 3 368 640
Using cached TRT model
Using an engine plan file across different models of devices is not recommended and is likely to affect performance or even cause errors.
[86821.977451] trt: Batch size: 1
Error generated. main.cpp, runArgusProducer:97 Failed to get ICaptureSession interface
Hi,
Do you mean you don’t see bounding boxes in trt.h264? Since the samples is open source we would suggest trace the code to get more information and understanding. So that you are able to do customization.
In the function it does rendering and encoding. We can see bounding boxes on screen and encoded trt.h264. Please confirm if you run the default sample. Probably you have done certain customization so see different result.
Thank you for your effort.
What fd should I use when calling nvosd in the frontend sample to display the osd in output.h26x rather than trt.h264?
I encountered a segmentation fault when I called nvosd_put_text(nvosd_text_context, MODE_CPU, buffer->planes[0].fd, 1, &textParam); inside the VideoEncoder::encoderCapturePlaneDqCallback function in VideoEncoder.cpp as follows.
Hi,
Encoded buffers are compressed h264/h265 stream. You have to put text/rectangles on YUV frame data. Please move the code to apply to buffers before feeding to encoder.