Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
Control Software / Re: 0x0D issue in Magic RDS
« Last post by mrandrew01 on April 19, 2026, 12:41:33 am »
Perhaps, it can be a separate option on how the end user wants the CR character to function, 0x0D then spaces, or spaces then 0x0D bit :), also... there are many users who probably don't have the latest firmware (example offline broadcast sites, etc.)

Also, unrelated to car tuners, but on the fm-dx webserver platform, when 0x0D is detected, the radiotext field gets centered, adding spaces "ruins" that spacing.

Now, related to car tuners, many have their own "way" of implementing the RDS spec, some maunfacturers don't account if the RT field even properly ends with 64 characters, or 0x0D,they will show the text that was decoded  (skoda,vw), or DPS not being accounted sometimes for safety... etc. There are many examples of DOs and DON'Ts, but if we had to account for all old tuners, with outdated specs, or careless implementation... we would have been removing 99% of features :)
22
Control Software / Re: 0x0D issue in Magic RDS
« Last post by Jan on April 19, 2026, 12:09:25 am »
You have a great observation. This is not a fault, it is an implementation from a time when it was more convenient to do it this way for compatibility with some old receivers. Receiver support for shortened text has not always been very good in the past. You are right that today there is probably no reason to place the CR character always at the end of a segment.

Given that today the most widely used RDS encoders are probably from our production, we are reluctant to change any detail that has been set in some way for 20 years, so as not to unintentionally influence something. However, if a different opinion prevails, a change is of course possible.
23
Control Software / 0x0D issue in Magic RDS
« Last post by mrandrew01 on April 18, 2026, 11:40:02 pm »
Hello! I have noticed a very small "fault" if you could say ;D with the carriage return character 0x0D, that being the addition of spaces before the 0x0D character. Implementation from other known brands include 0x0D as the first character in the 2A group, and afterwards how many spaces are needed to fill the group.
EXAMPLE : Benassi_Bros._Feat._Dhany_-_Hit_My_Heart___<0D> could be : Benassi_Bros._Feat._Dhany_-_Hit_My_Heart<0D>___

24
Control Software / Linux CLI tool for RDS encoder control
« Last post by Jan on April 15, 2026, 09:30:51 pm »
https://github.com/tuxikcz/pira_rds

Supports mRDS1322, PIRA32 and all compatible models.

Thanks to Tuxik  :)
25
P275 FM Analyzer / Re: P275E
« Last post by Jan on April 15, 2026, 11:57:39 am »
Okay, so the cause has been found and it was a faulty power adapter. If anyone experiences a similar problem in the future, we will replace the power adapter with another one free of charge. We no longer supply power adapters from the mentioned series.

The P275E documentation has been updated (section Recovery, added instructions for resetting the password).
26
Feature Requests / Re: MagicRDS4 UECP
« Last post by Jan on April 14, 2026, 06:43:12 pm »
Unfortunately, direct implementation in Magic RDS is not possible at the moment. I recommend choosing the virtual port method I suggested earlier.

Since the old program does not support TCP or UDP, use the com0com utility according to this procedure:

To allow communication between Magic RDS and third-party software that supports only serial (COM) ports, you can use a virtual serial port pair (also known as a "virtual null-modem cable").

I recommend using the free utility com0com, which creates two interconnected virtual COM ports.

Setup procedure:
Download and install the com0com package from:
https://sourceforge.net/projects/com0com/
After installation, open the setup command prompt (included with com0com) or use the graphical setup if available.

Create a virtual port pair. For example:

COM10
COM11

These two ports are internally connected – any data sent to COM10 will appear on COM11 and vice versa.

Configure the third-party application to use one port (e.g. COM10).
Configure Magic RDS application (Virtual Port) to use the other port (e.g. COM11).

Notes:
Both ports behave like standard hardware serial ports.
Baud rate and other serial settings should match on both sides.
If a port number is already in use, choose a different one.
Administrator privileges may be required during installation.
27
Feature Requests / Re: MagicRDS4 UECP
« Last post by zvykov on April 14, 2026, 02:24:02 pm »
Are there solutions to this problem using only MagicRDS?
An example of the required synchronization command is available.
28
Bug Reports / Re: Full Version Key does not work
« Last post by Jan on April 13, 2026, 10:28:54 pm »
Thank you for purchasing the Magic RDS 4 license.

You're using more than 4 years old version of the software. Please update to recent version. Then generate valid key using current installation ID and your existing user ID.
29
Bug Reports / Full Version Key does not work
« Last post by weather01089 on April 13, 2026, 10:25:07 pm »
Hello went into license manager, clicked the link, paid, got a license key. Verified the Installasion ID is right
The key does not work, says "Invalid Key" Also does rds4 support uploading a logo to the pira box? The pira does display a default logo.

Thanks, Ray
30
Control Software / Re: Magic RDS 4 - Internet Website Text Source - javascript(s)
« Last post by Jan on April 13, 2026, 09:36:17 pm »
What you are trying to achieve — loading and processing a complex web page directly in Magic RDS — is unfortunately not the right approach, for several fundamental reasons:

  • Magic RDS is not a web browser
    Modern web pages are designed to be rendered by full-featured web browsers (such as Google Chrome or Mozilla Firefox), which include sophisticated HTML parsers, JavaScript engines, CSS rendering, and dynamic content handling. Magic RDS does not implement this kind of environment and is not intended to replace a browser. There is currently no simpler or lightweight alternative that can reliably interpret such complex, script-dependent pages.
  • Periodic fetching creates significant overhead and stability risks
    To keep the displayed text up to date, the system would need to repeatedly download and process the page. With complex pages, this implies:
    High CPU usage (due to parsing and potential script handling),
    increased data transfer,
    risk of instability or crashes.
    This is far beyond what is practical or safe for a system like Magic RDS, which is designed for efficiency and reliability.
  • No reliable way to extract the required text
    Even if the page could be loaded, there is still the unresolved problem of identifying and extracting the specific text you want.
    In modern web pages, the desired content is often generated dynamically via JavaScript, meaning it is not directly available in the raw HTML. Without a full browser engine, there is no reliable way to locate and isolate the correct data.

Recommended approach

The correct solution is to use a simple and dedicated data source, for example:

A plain text file (TXT)
A simple XML or JSON endpoint
A lightweight server-side script that extracts and provides only the required text

In other words, the Magic RDS can only retrieve a single file which should ideally contain a simple and consistent text data structure or the already prepared, clean text. The text in this form is always present on the web server or in associated database. Contact support to gain access to this data.
Pages: 1 2 [3] 4 5 ... 10