Post reply

Name:
Email:
Subject:
Message icon:

Verification:
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: Bill
« on: Yesterday at 08:29:10 pm »

Thanks!  Will start trying this out.
Posted by: Jan
« on: November 15, 2026, 11:26:41 am »

I liked your idea so much that I implemented it into the current version, 4.3.6, over the weekend.

  • Add a new Connection: General Text Output - JSON Template. Internal channel, save to file.
  • Follow the standard procedure for sending external text to the selected Connection.
  • Enable RT+ support in the text source and fill in the template:
    Text=<not_assigned/> - <not_assigned/> - <not_assigned/> - <not_assigned/> - .
    You may assign any RT+ tags as you like, for use with an RDS encoder, but it has no effect on the JSON content.
  • In the JSON output, be sure to adjust the JSON template to match the actual structure required by the target application.


Posted by: Bill
« on: November 13, 2026, 11:32:48 pm »

Our automation only outputs a single line of plain text:  Text=cut duration seconds - category - artist - title - .    Can Magic RDS parse to values %1%, %2%, %3%, %4% and output to json for DTS Autostage?