Post reply

Message icon:

Unregistered users must pass a verification:

Please enter the number from the picture above which is showing FM broadcast antenna:

shortcuts: hit alt+s to submit/post or alt+p to preview

Topic Summary

Posted by: nuno
« on: February 01, 2022, 05:20:52 pm »

Thank you so much.
Posted by: Jan
« on: January 29, 2022, 06:43:19 pm »

Thank you for your suggestions, they will be implemented soon.
Posted by: nuno
« on: January 29, 2022, 12:27:10 pm »

That's awesome!

Another useful thing is in User defined rds encoder setup ability to define the ascii comand output to put another command before text and some commands after text!

And there's any character conversion to special characters if I send data directly from my radio automation software using an UDP or a TCP conection?
If I send data to a text file and read that file to send to RT conversion is made. If I send info directly for a UDP or TCP port its not. Do you know why?
Another form is read from file magic rds4 can decode that file but if I write resulted RT to a file it writes without char conversion..

Example: "história" appears like hist†ria

Posted by: Jan
« on: January 29, 2022, 11:19:56 am »

This feature is planned for near future - to implement a custom defined table: xml tag ⇨ RT+ tag
Posted by: nuno
« on: January 29, 2022, 10:12:40 am »

Magic RDS is a great software. It can now generate rt+ based on artist title separator but will be more reacher, in my point of view, if is it possible to generate RT+ based on tags sent it from automation software or from external sources like we do in xcmd.

Now text from external source or a simple line sent from automation software its not interpreted to generate RT+. It was very useful if it could be like item.title for example..
How about that?