Part Number: PROCESSOR-SDK-DRA8X-TDA4X
Hi TI:
I tried to run the encoder demo through ./run_app_encode.sh.
When the demo was finished, encode_output.h264 was generated in the app_cam_out directory, and then I use ffplay encode_output.h264
to play this .h264 file, I found that it is not the same as the NV12 data before encoding.
Before encoding, my nv12 data is continuous, for example, its sequence is 1, 2, 3, 4, 5, 6, 7, 8 ,9..., but after encoding, I found that the video sequence became 1111,5555,9999..., which made my stream stuck. I tried to modify the tivxSetNodeParameterNumBufByIndex(obj->imgMosaicObj.node, 1, APP_BUFFER_Q_DEPTH); in the app_create_graph(AppObj *obj) function to tivxSetNodeParameterNumBufByIndex(obj->imgMosaicObj.node, 1, 1);, then the result after encoding was correct .
So I want to ask if your company has the same problem and how fix this problem.
The attachment is my file, one is the h264 bitstream of dump before modifying tivxSetNodeParameterNumBufByIndex, the other is the bitstream after modifying tivxSetNodeParameterNumBufByIndex.
regards!encoder_output.zip