For rts_osd2_type_text when the string buffer has more than 31 characters, the trailing characters are not printing sometimes and total text ignored if more than 36+ characters are available.
As the changes of maximum char limit might involve the update of library, would you mind to print the characters in multiple separate blocks, where each block prints up to 31 char?
I didn’t see any maximum char limit supported by Text OSD in SDK code or Realtek AmebaPro2 application note — AmebaPro2's Documentation v0.1 documentation , the only example you provided has char array of 64 bytes, so anynone can assume like it may support upto 63 characters, but in reality it is not printing if more than 31 characters found in the text OSD buffer.
The answers I am expecting from you are below.
What is the Text OSD max supported characters length?
Is it posible to increase this length in next release?
While we are working on the library update, you may apply this patch for the immediate fix. The value of OSD_TEXT_STR_MAX is set to 128, so technically you can print up to 127 characters per block as long as they can fit into the display by adjusting the width and height.