Recent Posts

Pages: [1] 2 3 ... 10
1
Thanks!  Will start trying this out.
2
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.


3
Release News and Tutorials / Re: Release News and Change Log
« Last post by Jan on November 15, 2026, 11:12:42 am »
Version 4.3.6

https://magicrds.com/download/MagicRDS_Setup.exe

  • New model added: General Text Output - JSON Template
  • RT+ template can now be used for parsing a plain text line into text segments (elements %1% to %4%). These segments can be provided to other devices or applications via XML, JSON, or HTTP.
4
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?
5
What is the simplest way to combine multiple text sources into a single line?

Yes, sometimes it is better to present information on a single line (or within a single Radiotext message) rather than displaying it sequentially. This is particularly relevant for very short messages or data values, ensuring that the final text does not exceed any applicable length limits.

Follow these steps:

  • Note the ID of all text sources you want to merge into one line.
  • Add a new source, source type Internal channel
  • Locate the N/A text field and write a template for the final text.
    To insert a text source, use the tag %SOURCExTEXT% where x is the source ID
  • Finally, put the new source into the output sequence.

See the pictures for example.
6
Release News and Tutorials / Re: Release News and Change Log
« Last post by Jan on November 12, 2026, 03:33:53 pm »
Version 4.3.5

https://magicrds.com/download/MagicRDS_Setup.exe

External text sources:
  • File reading has been moved out of the main thread and now occurs asynchronously. This prevents occasional sluggish responsiveness, such as when reading from a busy network drive.
  • XML/JSON: N/A text fixed
  • If the N/A text is filled in and the appropriate conditions are met, the N/A text is always used, even if JS is enabled.
7
This peak is not present in your previous image.

It is likely to be a fault in the PC power supply unit. These older devices were relatively sensitive to the quality of the power supply. In the devices we manufacture today, the power supply is handled differently, and a dedicated voltage regulator is always used.

You do not mention the origin of the device. We do not have your email in our database. It is also possible that the previous owner handed it over to you in a damaged condition. The only way to determine this is to test it on another PC.
8
Another question: I’ve noticed a signal appearing on the FFT at 27 kHz on virtually every station I tune into. It seems the equipment is picking up this information and displaying it incorrectly—it’s impossible for every station on the dial to have the exact same issue.
I am using the device connected to a computer, with an external antenna attached.
I’ve taken care to ensure there are no noise sources near the equipment; is there any way to resolve this? How should I proceed?
9
You can find the relevant setting for the margin in the menu Options - Preferences - General.

Regarding your other question: Yes, the FCC once introduced the parameter "percentage modulation," which is still in use today. The FCC's concept of "percentage modulation" provides a convenient way to define and evaluate regulatory modulation limits. It does not establish a physical unit of frequency deviation, nor does it require measuring instruments to display frequency deviation in percentages instead of kHz.

Frequency deviation remains a physical quantity expressed in kHz, while percentage modulation is simply a derived, dimensionless value referenced to a specified frequency deviation (75 kHz in USA).

Since the P275 also provides advanced frequency deviation analysis, including deviation histograms, it is important to retain kHz as the fundamental unit of measurement throughout the instrument and the software. Replacing kHz with percentages would, for example, result in histograms x-axis expressed in percentages. While mathematically valid, this would be unnecessarily confusing and counterintuitive.

The FM Scope supports % in the FM deviation bar, you may toggle the unit by clicking on its scale.
10
That puts my mind at ease!

Regarding other observations, is it possible to display the measurements as a percentage rather than as a deviation value?

Another detail: would it be possible to extend the deviation error margin—currently at 5 kHz—to 7.5 kHz or 10 kHz? In my country, an error margin of up to 7.5 kHz is permitted (within a total of 82.5 kHz at 110%) for stations that use RDS.
Pages: [1] 2 3 ... 10