Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
Configuration Options and Possibilities / Re: Version 4 help (reading XML file which is has not a valid XML structure)
« Last post by dennism on September 23, 2026, 03:21:34 pm »
Thanks for the reply Jan.

I thought I had the latest version. I will check.

Regarding the "XML" file, we've been using it for years with Verion 3. It's generated by our PlayoutONE automation. It also works fine with our stream provider for metadata. I'll pursue the text replace function.

Thank you.
22
Configuration Options and Possibilities / Re: Version 4 help
« Last post by Jan on September 23, 2026, 07:05:06 am »
I would proceed as follows:

1) Download the latest version of Magic RDS 4, as the version you are currently using is outdated. You will immediately see what the issue with the file is.

2) The file you attached is not a valid XML file; therefore, it cannot be processed as XML. The application that generated the file is likely malfunctioning, so you should ask the author to fix it. If that is not possible, you must process the file as "Entire file as plain text" and use text replacement tools to remove anything you do not want in the final output.
23
General Discussion about the RDS / Re: RVR TEX300LCD built-in RDS encoder (P232) board setup
« Last post by Jan on September 23, 2026, 06:50:11 am »
Please, let us not mislead other users with incorrect information. This device does not contain a P232 chip or any other encoder manufactured by us.

Unfortunately, RVR has caused us harm — not only through unpaid debts but also by including misleading information in their documentation.

If the built-in encoder does not meet your needs, we can offer you an external encoder; however, we certainly cannot provide support or software for unknown legacy products.
24
General Discussion about the RDS / Re: RVR TEX300LCD built-in RDS encoder (P232) board setup
« Last post by andrew01 on September 23, 2026, 12:22:07 am »
Hi!
Sorry for the late response, we forgot to check on the transmitter for a while, but, after the battery replacement I have mentioned, the encoder was reset to it's default settings,there are no more group losses, and the group sequence indicated seems is the same as Pira encoders, so there definetly is a P232 chip!
We have contacted RVR's support team for the original control software, and we will see how the embedded RDS chip will perform from now on.

Also, I know I have said it before, but, it's quite weird seeing a external application that controls chips from your production line have an extra function to set a custom exact group sequence, while Magic RDS, the original control application doesn't have this function, while I understand the legacy logic behind the current group sequence, something to coexist with the legacy Dynamic PS oriented mode, and the "modern" exact group function, would be the final touch that makes the software more... to the liking of the user.  ;)

25
Configuration Options and Possibilities / Version 4 help (reading XML file)
« Last post by dennism on September 22, 2026, 10:13:17 pm »
I'm new to Magic RDS V 4, having been forced to upgrade from 3. I searched for this but couldn't find anything yet.

In trying to set up the parsing from an XML file, clicking the Find Element button brings up a blank window, no information inside. I know the path to the file is correct. I tried entering the element name several different ways but nothing works. This is a sample of the XML data:

<?xml version='1.0' encoding='ISO-8859-1' ?>
<PlayList>
<Entry Event="00"
Type="Playing"
Category="SONG"
Id="MUS7541"
Title="Hot Stuff"
Artist="Donna Summer"
Album=""

This error shows in the log: 26-09-22 16:13:37; Application Error: Access violation at address 00405FEF in module 'magicrds.exe'. Read of address 00000000

I'm sure I'm missing something but I don't know what. Please help. Thanks.
26
P132, P164, P232(U) and P332 RDS Encoders / Re: P164 RDS Encoder - can't log in
« Last post by Jan on September 21, 2026, 09:06:59 pm »
The * RDS * is showed until you set your program service name (Default PS). You should do this in any case, regardless of whether you want to broadcast song titles as well. Once you are satisfied with the name display, press Apply (or enter *PS in the terminal). This saves the configured PS to permanent memory.

Song titles are broadcast via Radiotext (fortunately, the days of using PS for this purpose are long gone). Radiotext is enabled by default in this encoder, so you do not need to configure anything else; simply proceed with the instructions in Magic RDS 4 – External Text Sources (extsrc.pdf).
27
P132, P164, P232(U) and P332 RDS Encoders / Re: P164 RDS Encoder - can't log in
« Last post by Dan on September 21, 2026, 08:49:27 pm »
Thanks. I got it up and running, and now it's displaying *RDS* in the PS field before it displays the actual artist entitle, I can't seem to find where this is originating. Any thoughts?
28
P132, P164, P232(U) and P332 RDS Encoders / Re: P164 RDS Encoder - can't log in
« Last post by Jan on September 18, 2026, 08:12:38 pm »
If you have disabled the web interface or changed its port in the settings, no special procedure is required to restore the original configuration. You can find the exact steps for establishing a connection in the PDF manual. The procedure remains the same and works independently of previous settings: simply connect the USB cable and configure the necessary parameters in Magic RDS 4 under Device Setup > LAN Settings. You will also find other possible methods there.
29
P132, P164, P232(U) and P332 RDS Encoders / P164 RDS Encoder - can't log in
« Last post by dlake76 on September 18, 2026, 08:01:22 pm »
Hi,
I have a P164 RDS Encoder unit that lost it's mind.  I've unplugged and rebooted but the GUI doesn't come up in any browser. I can PING the ip. Is there a way to reset or flash the unit? Thanks.
30
Configuration Options and Possibilities / Re: Text Retransmission
« Last post by Jan on September 14, 2026, 07:59:19 am »
Repeatedly sending the same text is permissible only if the device documentation explicitly states that the device compares the content of the new text with the existing one. I do not believe that is the case here. Doing so could, for instance, lead to an unintended change in the RT Type flag, effectively triggering a restart of the existing text on the receiver.

If the port timeout cannot be extended, I recommend using the Magic RDS scheduler to send — at regular intervals — any command that does not affect any RDS service. There is even a sample preset already created for this purpose (TA status reading). Alternatively, you can send your station name at regular intervals; that causes no issues (PS=xxxxxxx). You could also ask the device manufacturer to recommend a suitable "dummy" command.

Advanced RDS encoders also feature a text timeout function. If you broadcast long segments (such as podcasts), it is advisable to include an additional text source in the loop so that the text changes at least occasionally. The additional source may point to a file with a fixed text or it may be fed by the Text Campaigns, etc.
Pages: 1 2 [3] 4 5 ... 10