Based on sensor.h, currently only GC4653 is supported.
If support for GC4663 is required, we will need to conduct an internal review to assess feasibility. To support it, bringing up the sensor is needed, similar to what this user did ( Trying to use a JX-F57 camera sensor, how can I do so? ).
althpough i do a see an entry for gc4663 in sensor.h:
When we enable HDR mode, we are not getting stream in RTSP. When we checked the log, it looks like failed to initialize. Check below log.
hal_voe_ready 0x0 0xbf1208
read fcs_status 0x000000bf
[video_init] uvcd iq is null, use default.
[video_init] uvcd SNR is null, use default.
IQ:FW size (108314)
sensor:date 2026/6/29 version:RTL8735B_VOE_1.7.1.0
sensor:FW size (7116)
sensor timestamp: 2026/06/29
iq timestamp: 2024/04/18 15:00:02
voe_heap malloc 0x713a9c40, size 60440320
ISP:1 ENC:1 H265:1 NN:1
hal_voe_ready 0x0 0xbf1208
voe :RTL8735B_VOE_1.7.1.0
sensor:RTL8735B_VOE_1.7.1.0
hal :RTL8735B_VOE_1.7.1.0
load time sensor:89us iq:1341us itcm:0us dtcm:0us ddr:0us ddr2:0us
Set H264 default HIGH profile
rc_version RC_v1
[video_pre_init_procedure] START
[VOE]ext_in = 0 sync = 0
[VOE][Ini set0]init dn 0 hdr 1 mirrorflip 0x0
[VOE]g_init_fps: 20
[VOE]md init success
[VOE]algo ver 2e6d096
[VOE]pack_v 0x0000 0x0003 cus_v 7 iq_id 0 dn 0 day 0 night 1 other 2 offset 224 length 16567 iq_size 32012
[VOE]Ver 0x0001000c Fast3A Cnt AE 2 AWB 1 period AE 2 AWB 1 delay 1 2
[VOE]hdr_mode 0 sensor driver num 2
[VOE]fps max 30.000000 min 0.702741
[VOE]exposure_step 22.222221
[VOE]change sensor mode => 2560x1440@30.000000fps - ‘linear’
[VOE]min_fps 0.702741, max_fps 30.000000, exp_step 22.222221 dyn_fps 20.000000
[VOE]md ver 0x6d640100
[VOE]ae ver 0x61650200
[VOE]awb ver 0x77620100
[VOE]cur_hdr_mode = 0
[VOE]fps max 20.000000 min 0.500508
[VOE]exposure_step 15.619565
[VOE]change sensor mode => 2560x1440@20.000000fps - ‘hdr line 2to1’
[VOE]min_fps 0.500508, max_fps 20.000000, exp_step 15.619565 dyn_fps 20.000000
[VOE]pack_v 0x0000 0x0003 cus_v 7 iq_id 1 dn 0 day 3 night 4 other 5 offset 49985 length 19040 iq_size 37868
[VOE]Ver 0x0001000c Fast3A Cnt AE 0 AWB 0 period AE 1 AWB 0 delay 2 3
[VOE]md ver 0x6d640100
[VOE]ae ver 0x61650200
[VOE]awb ver 0x77620100
[VOE]VOE MEM Size = 59023 Used= 5951 KB Free=53072 KB (54346240)
[VOE]stream 0 buffer 0: 0x71986100 size 5529600
[VOE]stream 0 buffer 1: 0x71ecc200 size 5529600
[VOE]first_config_osd2_block_num[0]: 1
[VOE]osd2_block_num[0]: 24
[VOE][Ini set] gray mode off
[VOE][Ini set] mirrorflip 0x0
[VOE][Ini set] BRIGHTNESS 0
[VOE][Ini set] SATURATION 0
[VOE][Ini set] CONTRAST 0
[VOE][Ini set] FLICKER 0
[VOE][Ini set] WDR_MODE 1
[VOE][Ini set] WDR_LEVEL 50
[VOE]turn direct_i2c_mode 1
[VOE]fast mask en
[VOE]color 0x000000 status 2 2 2 2 2
[VOE]NV12 2560x1440 1/20
[VOE]dynamic set fps 0 → 20 ok
[VOE][ae_s_ctrl][1388]Errset ae ctrl fail ops=61473 → -34
[VOE][rtsv_ctrl_handler_setup][1464]Errrtsv_ctrl_handler_setup AE min FPS s_ctrl -34
[VOE][mod_control_start_isp][118]Errfail to start isp pipeline → -34
[VOE][isp_mod_do_action][400]Errmodule control do action 0x80024500 fail -34
[VOE][rtscam_isp_message_call][534]ErrISP:{rtscam_isp_message_call} message exec failed
[VOE][__rtscam_isp_set_fps][1744]Err__rtscam_isp_set_fps rtscam_isp_message_call -34
[VOE][rtscam_zoom_enable_stream][689]Errrtscam_zoom_enable_stream zoom->isp->set_fps 20 ret: -34
[VOE][rts_v4l2_streamon][578]Errv4l2 ioctl STREAMON fail, -34
[VOE]start_stream stream on failed -34
[VOE]voe_open isp_open_stream ch0 failed -34
hal_voe_send2voe too long 246869 cmd 0x00000206 p1 0x00000000 p2 0x00000000
VOE command 0x206 fail ret 0x0
Set H264 default HIGH profile
rc_version RC_v1
[VOE]ext_in = 0 sync = 0
[VOE]isp_device_probe had done
[VOE]isp_soc_start already done
[VOE]VOE MEM Size = 59023 Used= 16772 KB Free=42251 KB (43265696)
[VOE]stream 1 buffer 0: 0x72412300 size 1382400
[VOE]stream 1 buffer 1: 0x72563c00 size 1382400
[VOE]first_config_osd2_block_num[1]: 1
[VOE]osd2_block_num[1]: 24
[VOE]NV12 1280x720 1/20
[VOE]dynamic set fps 20 → 20 ok
[VOE][ae_s_ctrl][1388]Errset ae ctrl fail ops=61473 → -34
[VOE][rtsv_ctrl_handler_setup][1464]Errrtsv_ctrl_handler_setup AE min FPS s_ctrl -34
[VOE][mod_control_start_isp][118]Errfail to start isp pipeline → -34
[VOE][isp_mod_do_action][400]Errmodule control do action 0x80024500 fail -34
[VOE][rtscam_isp_message_call][534]ErrISP:{rtscam_isp_message_call} message exec failed
[VOE][__rtscam_isp_set_fps][1744]Err__rtscam_isp_set_fps rtscam_isp_message_call -34
[VOE][rtscam_zoom_enable_stream][689]Errrtscam_zoom_enable_stream zoom->isp->set_fps 20 ret: -34
[VOE][rts_v4l2_streamon][578]Errv4l2 ioctl STREAMON fail, -34
[VOE]start_stream stream on failed -34
[VOE]voe_open isp_open_stream ch1 failed -34
But, it is working in linear mode (without HDR). Is the IQ file has valid tuned HDR data? Becasue HDR IQ pack has zero AE/AWB calibration points (Cnt AE 0 AWB 0 vs the linear pack’s Cnt AE 2 AWB 1)
We tested the provided iq file and it is working fine with HDR mode, but we are seeing the frames becoming more white after full run of 12+ hours at night and stays at same white frames even after 10 days. See below images.
Could you please provide the log for us to debug the issue?
It would be better if you can enable metadata for your streaming and/or provide us the recorded video with metadata enabled.
Once you have the metadata enabled video, you may use the Ameba Meta Analyzer tool to view the ISP info. Please let us know if you need the tool for debugging, else you can share your video with us.
We recorded video with meta data enabled, and added to meta analyzer tool, but no options to export as csv file to share with you. It looks like the meta anlayzer tool user guide and executable links you provided are for different versions.
Thank you for sharing the video with us. I have tried to export your video to csv file using the released version meta analyzer tool, and I am able to obtain the csv file. Please give us some time to look into the issue and get back to you.
Meanwhile, if you are still having issues with the tool, please ensure that you have placed the ameba_meta_analyzer.exe in the same folder as MetaScript.ini. Then, after opening your video using the tool, you should be able to generate the csv file in the same directory as your video.
Upon checking the metadata value in the generated csv file (as attached), we are unable to identify the changes in exposure value. Based on our understanding on the issue, the initial image in HDR mode after camera boots looked normal, then it turned more white (overexposed) after 12+ hours of full run.
May we trouble you to share with us a metadata enabled video recording with normal exposure during the initial camera boot? please share the log with us too, this would help us to cross-verify the exposure value for IQ tuning reference. Thank you.
We are little confused, normal exposure means sensor linear mode? or something else? How much duration is required?
As the issue starts after 12+ hours, do you need video+logs from camera boot or only after 12+ hours?
One more issue we observed with HDR mode is antiflicker is not working, but it is fine with 50Hz in linear mode, Do you need anything from us to understand this issue?
Based on the logs provided, it can be confirmed that HDR mode is enabled, as indicated by the following log entry:
[VOE]change sensor mode => 2560x1440@20.000000fps - 'hdr line 2to1'
However, the anti-flicker setting appears to be disabled, as indicated by the following log entry:
[VOE][Ini set] FLICKER 0
I would like to clarify a few things:
How was HDR mode enabled on your end? Was it configured directly in video_api.c, or through the following initialization parameter? init_params.init_isp_items.init_hdr_mode = 0x01;
Was isp_init_enable set to 1 in your application?
For linear mode, the SDK uses the default settings, where anti-flicker is enabled by default.
You may try explicitly enabling anti-flicker in your application by setting:
If isp_init_enable is not enabled in your application, you can modify the parameters including anti-flicker, hdr mode setting directly in video_api.c, starting from line 1920 for testing.
You may also share the logs and videos demonstrating the white color issue for us to investigate as well also with VOE log enabled (#define APP_VOE_LOG_EN 1).