reverend
Well-Known Member
- Joined
- Apr 22, 2014
- Messages
- 5,715
- Reaction score
- 4,105
- Country
- United Kingdom
- Dash Cam
- Too many
My situation was similar to his fault! I performed on G90c A7la70When I try to edit bitratetable, I get error message "BitrateTable not found. Invalid PRI partition or pattern mismatch!"
When I try to edit bitratetable, I get error message "BitrateTable not found. Invalid PRI partition or pattern mismatch!"
This is the start address of the bitrate of the table.1) how did you get that value ?
Constant bitrate is more stable and allows more optimal and predictable result...i want to know if someone here has tested and found the "best values"
Hum, when I've edited my SJ5000+ Firmware (A7 SoC) I didn't have anything to modify.This is the start address of the bitrate of the table.
These tables all firmware Ambarella identical in structure..
According to me the VBR was allowing a more adaptative response (but you're right you can have some loss).... but whatever, in fact even in VBR it looks more or less like CBR ! :Constant bitrate is more stable and allows more optimal and predictable result..
Thank you for the response. Could you provide some further information, what offset should I choose and why? I can't understand how this thing works yetthe custom offset youve entered does not seem to match the offset of the table inside the firmware
Yes it fails everytime. Tried every possible setting in that drop down menu, get the same error until leaving custom ofset (dec) blank. I could provide a link with software I am trying to play with, its 20160601a_gs90c_a7la70_gps_ZhongXing_ard17_v2508 I found on DaschCamTalk forum and using in my cameraDoes it fail to find the table using search patterns from the drop down on the top left of the window?