This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4AL-Q1: multi-cam Recorded video splash screen

Part Number: TDA4AL-Q1

Dear TI 

       I run the  script  ./run_app_multi_cam_codec.sh but  Recorded video splash screen。single-cam review normal

       The relevant logs are as follows,Please assist in analysis thanks

./run_app_multi_cam_codec.sh
APP: Init ... !!!
MEM: Init ... !!!
MEM: Initialized DMA HEAP (fd=4) !!!
MEM: Init ... Done !!!
IPC: Init ... !!!
IPC: Init ... Done !!!
REMOTE_SERVICE: Init ... !!!
REMOTE_SERVICE: Init ... Done !!!
44.621358 s: GTC Frequency = 200 MHz
APP: Init ... Done !!!
44.621441 s: VX_ZONE_INIT:Enabled
44.621452 s: VX_ZONE_ERROR:Enabled
44.621459 s: VX_ZONE_WARNING:Enabled
44.622101 s: VX_ZONE_INIT:[tivxInitLocal:130] Initialization Done !!!
44.622178 s: VX_ZONE_INIT:[tivxHostInitLocal:93] Initialization Done for HOST !!!
44.631148 s: ISS: Enumerating sensors ... !!!
44.631492 s: ISS: Enumerating sensors ... found 0 : SENSOR_OX08B40_MAX96717
44.631502 s: ISS: Enumerating sensors ... found 1 : IMX623_RAW
44.631508 s: ISS: Enumerating sensors ... found 2 : IMX623_UYVY
Sensor selected : SENSOR_OX08B40_MAX96717
Querying SENSOR_OX08B40_MAX96717
44.631523 s: ISS: Querying sensor [SENSOR_OX08B40_MAX96717] ... !!!
44.631813 s: ISS: Querying sensor [SENSOR_OX08B40_MAX96717] ... Done !!!
WDR mode is supported
Expsoure control is supported
Gain control is supported
Sensor DCC is enabled
Sensor width = 3840
Sensor height = 2160
Sensor DCC ID = 840
Sensor Supported Features = 0x00000378
Sensor Enabled Features = 0x00000158
Capture->Encode Selection Yes(1)/No(0)
[MCU2_0] 44.631344 s: ImageSensor_RemoteServiceHandler: IM_SENSOR_CMD_ENUMERATE
[MCU2_0] 44.631659 s: ImageSensor_RemoteServiceHandler: IM_SENSOR_CMD_QUERY
[MCU2_0] 44.631689 s: Received Query for SENSOR_OX08B40_MAX96717
1
Decode->Display Selection Yes(1)/No(0)
0
Max number of cameras supported by sensor SENSOR_OX08B40_MAX96717 = 8
Please enter number of channels to be enabled
1
srcType = 0,sinkType = 1
51.775746 s: front ISS: Initializing sensor [SENSOR_OX08B40_MAX96717], doing IM_SENSOR_CMD_PWRON ... !!!
51.776153 s: front ISS: Initializing sensor [SENSOR_OX08B40_MAX96717], doing IM_SENSOR_CMD_CONFIG ... !!!
[MCU2_0] 51.775930 s: ImageSensor_RemoteServiceHandler: IM_SENSOR_CMD_PWRON
[MCU2_0] 51.775961 s: IM_SENSOR_CMD_PWRON : channel_mask = 0x10
[MCU2_0] 51.776015 s: OX08B40_PowerOn : chId = 0x4
[MCU2_0] 51.776295 s: ImageSensor_RemoteServiceHandler: IM_SENSOR_CMD_CONFIG
[MCU2_0] 51.776325 s: Application requested features = 0x158
[MCU2_0]
[MCU2_0] 51.776354 s: IM_SENSOR_CMD_CONFIG channel_mask = 10
[MCU2_0] 51.776413 s: maxDesSerCfg config start
[MCU2_0] 51.783501 s: End of maxDesSerCfg config
[MCU2_0] 51.783719 s: front_camera_devid_i2c_ReadReg success: devid = 0xbe
[MCU2_0] 51.783755 s: max96716 config start
[MCU2_0] 51.788320 s: End of max96716 config
[MCU2_0] 51.827900 s: front camera Link ok, count = 3
[MCU2_0] 51.827946 s: OX08B40_Probe chId: 0x4
[MCU2_0] 51.827970 s: Configuring camera # 4
[MCU2_0] 51.828018 s: OX08B40_Config chId: 0x4, sensor_features_requested = 344
[MCU2_0] 51.828048 s: max96717 config start : slaveAddr = 0x40
[MCU2_0] 51.930154 s: End of max96717 config
[MCU2_0] 51.930194 s: OX08B40_Sensor_RegConfig E sensor_cfg_script_len = 1257
[MCU2_0] 51.930240 s: Configuring OX08B40 imager 0x36.. Please wait till it finishes
52.123970 s: ISS: Initializing sensor [SENSOR_OX08B40_MAX96717] ... Done !!!
captureObj->params.numDataLanes = 4
captureObj->params.dataLanesMap[0] = 1
captureObj->params.dataLanesMap[1] = 2
captureObj->params.dataLanesMap[2] = 3
captureObj->params.dataLanesMap[3] = 4
captureObj->params.numDataLanes = 4
captureObj->params.dataLanesMap[0] = 1
captureObj->params.dataLanesMap[1] = 2
captureObj->params.dataLanesMap[2] = 3
captureObj->params.dataLanesMap[3] = 4
---------chInstMap[0] = 1 ch 0
[MCU2_0] 52.123709 s: OX08B40_Sensor_RegConfig X = regCnt = 1257
[MCU2_0] 52.123763 s: OX08B40_Config chId: 0x4, sensor_features_requested = 344, status = 0
[MCU2_0] 52.123795 s: IM_SENSOR_CMD_CONFIG returning status = 0
gst_wrapper: GstCmdString:
appsrc format=GST_FORMAT_TIME is-live=true do-timestamp=true block=false name=myAppSrc0 ! queue
! video/x-raw, width=(int)3840, height=(int)2160, framerate=(fraction)30/1, format=(string)NV12, interlace-mode=(string)progressive, colorimetry=(string)bt601
! v4l2h264enc bitrate=10000000
! h264parse
! mp4mux
! filesink location=output_video_0.mp4

52.673183 s: ISS: Starting sensor [SENSOR_OX08B40_MAX96717] channel_mask = 0x10 ... !!!
[MCU2_0] 52.673676 s: ImageSensor_RemoteServiceHandler: IM_SENSOR_CMD_STREAM_ON
[MCU2_0] 52.673743 s: IM_SENSOR_CMD_STREAM_ON: channel_mask = 0x10
[MCU2_0] 52.673779 s: IM_SENSOR_CMD_STREAM_ON: 2 channel_mask = 0x10 chId 0
[MCU2_0] 52.673838 s: IssSensor_Start chId = 4
[MCU2_0] 52.673875 s: OX08B40_StreamOn chId: 0x4
[MCU2_0] 52.678717 s: max96716 config start2
[MCU2_0] 52.678891 s: End of max96716 config2
[MCU2_0] 52.678932 s: OX08B40_StreamOn chId: 0x4, status = 0
52.683826 s: ISS: Starting sensor [SENSOR_OX08B40_MAX96717] ... !!!

  thanks

  • Hi,

    May I know if this sensor is tested with the multi cam application and you are able to see the image correctly on the display?
    if not, could you check the same?

    May I know what is the format that is being output from the sensor?

    Regards,

    Nikhil

  • HI NiKhill 

          I tested multi-cam,it could save photo and  it is ok

          sensor output  format  is raw12

         can you  tell me  how to close the ldc enable of multi-cam_codec?

  • Hi,

    LDC disable option was not provided here because the input to the codec should be NV12, hence LDC is also used to convert to NV12.

    If you already have NV12 output from VISS node, then you would have to manually remove the LDC from the application and point the obj->enc_pool.arr to obj->vissObj.output_arr (if you are not using downscale)

    Regards,

    Nikhil

  • Hi NiKhill

        I just modified that  point the obj->enc_pool.arr to obj->vissObj.output_arr ,as the below picture,Is this how the modification was made?Did not solve the stripe problem。

    thanks!

  • Hi NiKhill

      Changing the output resolution to 1920 * 1080  normal recording video

  • Hi NiKhill

        I am sorry to provided incorrect information.if  I just modified that  point the obj->enc_pool.arr to obj->vissObj.output_arr,runing app will report error as below.thanks!

    106.317766 s: VX_ZONE_ERROR:[vxGetObjectArrayItem:207] Provided reference was not an object array, returning an error reference
    106.317838 s: VX_ZONE_ERROR:[vxSetParameterByIndex:239] Invalid type 0x00000811!
    106.317849 s: VX_ZONE_ERROR:[vxSetParameterByIndex:287] Specified: parameter[7] type:00000811 => 0xffffa897a938
    106.317856 s: VX_ZONE_ERROR:[vxSetParameterByIndex:289] Required: parameter[7] dir:1 type:0000080f
    106.317866 s: VX_ZONE_ERROR:[ownReleaseReferenceInt:294] Invalid reference
    106.317874 s: VX_ZONE_ERROR:[vxGetStatus:700] Reference is NULL
    [LDC-MODULE] Unable to create LDC node with DCC config!

    (process:1185): GStreamer-CRITICAL **: 18:10:22.798: gst_object_unref: assertion 'object != NULL' failed
    106.336002 s: ISS: De-initializing sensor [SENSOR_OX08B40_MAX96717] ... !!!
    106.336398 s: ISS: De-initializing sensor [SENSOR_OX08B40_MAX96717] ... Done !!!
    106.336872 s: VX_ZONE_ERROR:[ownReleaseReferenceInt:294] Invalid reference
    106.336941 s: VX_ZONE_ERROR:[ownReleaseReferenceInt:294] Invalid reference
    106.337225 s: VX_ZONE_WARNING:[vxReleaseContext:1055] Found a reference 0xffffa897b9b0 of type 00000813 at external count 1, internal count 0, releasing it
    106.337235 s: VX_ZONE_WARNING:[vxReleaseContext:1057] Releasing reference (name=viss_node_output_arr) now as a part of garbage collection
    106.337285 s: VX_ZONE_INIT:[tivxHostDeInitLocal:107] De-Initialization Done for HOST !!!

  • Hi,

    Changing the output resolution to 1920 * 1080  normal recording video

    Is this correct?

    106.317766 s: VX_ZONE_ERROR:[vxGetObjectArrayItem:207] Provided reference was not an object array, returning an error reference
    106.317838 s: VX_ZONE_ERROR:[vxSetParameterByIndex:239] Invalid type 0x00000811!
    106.317849 s: VX_ZONE_ERROR:[vxSetParameterByIndex:287] Specified: parameter[7] type:00000811 => 0xffffa897a938
    106.317856 s: VX_ZONE_ERROR:[vxSetParameterByIndex:289] Required: parameter[7] dir:1 type:0000080f
    106.317866 s: VX_ZONE_ERROR:[ownReleaseReferenceInt:294] Invalid reference
    106.317874 s: VX_ZONE_ERROR:[vxGetStatus:700] Reference is NULL
    [LDC-MODULE] Unable to create LDC node with DCC config!

    You would have to remove the ldc module completely from the graph as this is linked to the viss_node. i.e. remove ldc_init, create, delete APIs from the application.
    I hope you are not using MSC node right?

    Regards,

    Nikhil

  • Hi Daohong

    This is not splash, but some problems caused by the wrong/initial DCC parameter. You may do the following change to disable LDC.

    1 comment line 1204-1208(main.c)

    2 modify line 1215 (main.c)

    Or you can add the correct LDC parameters after LDC tuning.

  • Hi Adam

          To modify and close LDC as you mentioned, you need to enable obj ->downscale,but still repord some error,I am sending you the code currently using. Could you please help me take a look

     and Where is initial DCC parameter?0647.main.c

  • Hi Daohong

    DCC parameter is under RSDK/imaging/sensor_drv/src/<sensor name>/dcc_xmls. You may try restore the modification I put above and disable LDC in LDC xml:

    After changing the dcc xml, run generate_dcc.sh under the same directory. 

    Then remake imaging to make the modification in effect.

    Best regards,

    Adam.

  •  Hi Adam

           Directly modify dcc_ xml ,Turn off LDC for XML,run generate_dcc.sh but the recording issue remains unchanged.

  •  Hi Adam 

         Can you take a look at the C file I sent and how to directly remove the LDC driver and run it without reporting any errors?

           thanks

  • Hi daohong

    I have tested disable LDC on xml and it has been proven useless too. You may try another demo app_multi_cam. This demo can disable LDC by setting app_muti_cam.cfg.

    I am looking at your code and trying to see how to disable LDC. Please wait for some time.

    Best Regards,

    Adam

  • Hi

    I tested multi-cam,it could save photo and  it is ok

    You had mentioned that you were able to get the multi-cam demo working right? 
    Could you please confirm if you were displaying the output here with LDC enabled or LDC disabled?

    Regards,

    Nikhil

  • Hi 

         I also comfirmed multi-cam demo ,There's no difference for LDC enabled or LDC disabled.save photo normal,thanks

  • Hi Daohong

    After closely looking at your video, I think the LDC has been tuned in your sensor. Would you please add a folder 'app_cam_out' under 'vision_apps' and enable the following to enable saving images:

    When running the demo, press 's' to save the images, which will appear in 'app_cam_out', to see where is the problem introduced.

    further more, what is the property of the video you shared?

  • Hi Adam

            Running multi cam, the saved images are normal, but the recording is not normal. The attribute of recording is 4k.

  • Hi,

    Running multi cam, the saved images are normal, but the recording is not normal. The attribute of recording is 4k

    Sorry, did not understand this. Could you please elaborate what is saved images here (i.e. output of which node) and what is recording (output of which node) and how are you recording?

    Regards,

    Nikhil

  • What is the size of the saved images?

    I think the problem is not resulted from LDC. If the image input to encoder is much less than 4k, the encoded 4k image should have such strange distortions. Please confirm that the output of LDC is 4K.

  • Hi Adam  

        I  run the nulti-cam_codec app ,press 'S' to save photo and recording video,save photo of output  node is ldc node,the  attribute of save photo also  is 4K,the photo and video  all have the same problem。so the input of encode have problem.thanks

  • Hi Adam

        How to set resolution of ldcObj output? I attempt to modify  "LDC_TABLE_WIDTH" value ,It doesn't seem right?

  • Hi Adam

        How to set resolution of ldcObj output? I attempt to modify  "LDC_TABLE_WIDTH" value to 4K of single-cam ,It doesn't seem right?An error occurred while running the single-app

  • Hi daohong

    The resolution of LDC is not configurable directly. The resolution of the raw image is set by sensor driver. The raw image go through VISS without change in resolution. LDC will change the resolution based on the LDC LUT.  The resolution can be changed in MSC. However, MSC is only able to scale down the image but not scale up. Would you please share the image captured from VISS, LDC and the initial raw image?

  • Hi Adam

       I can't upload image to e2e,but when  I run ./run_app_multi_cam_codec.sh save image information ,the resolution is samed with setting of  poolObj->width and poolObj->height.

    Record a 2M video ,the output of ldc is2M,Record a 8M video ,the output of ldc is8M

  • the resolution of ldc output is samed with setting of  poolObj->width and poolObj->height

  • Hi daohong

    Is this CSI input raw and the viss_img_out normal? You may paste the screenshots of the images if the images are too big to upload or pack images to a zipped file and upload or send to me directly through email. 

  • Hi Adam

        CSI input raw and the viss_img_out  is normal,only 8M output of ldc and 8M record video is  abnormal 

     

      thanks!

  • Hi Adam   

       this is recoed 8M video ,saved photo of ldc and viss,the ldc output is abnormal

         

  • Hi Daohong

    please check the LDC xml parameters as follows,

    I think the LDC of your sensor is just tuned for a smaller size than 4K or the LUT is not correct. If so, just get your ISP tuning team to tune the LDC again. 

  • Hi Daohong

    And how did you change the output of LDC in multi_cam_codec demo?

  • Hi Adam 

         I didn't changed successfully if I changed the parameter "LDC_TABLE_WIDTH" to 4k resolution ,it will report an error 

  • Hi Adam 

     just change  poolObj->height and poolObj->width

  • Hi daohong

    I successfully replicate your problem by directly setting LDC output image size to a larger size.

    I set the size here: obj->ldc_out=vxCreateImage

    So this problem will occur when the input to LDC is smaller than output of LDC.

    This means somehow you set the LDC input size too small .