Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
P132, P164, P232(U) and P332 RDS Encoders / Re: FCC Cybersecurity Rules
« Last post by Jan on September 25, 2026, 04:12:25 pm »
We are preparing an update to the internal website that will allow you to set a longer password than is currently possible. While this will not affect security in any way, it will ensure formal compliance with an FCC requirement.

If you do not want to wait, you can set a 15-character password right now. Use the Magic RDS 4 program's GUI to do so.
22
P132, P164, P232(U) and P332 RDS Encoders / P132/P332 - FCC Cybersecurity Rules
« Last post by bobcvols on September 25, 2026, 03:44:54 pm »
Good morning, Jan -

We have 3 P332's that we use on three facilities - extremely dependent!

We are staring down new U.S. FCC cybersecurity rules which require enhanced security measures for our EAS system and devices that are connected to it through our program chain.  RDS units have been mentioned in some of the discussion that I have seen, although that may refer to RDS that is generated by transmitters.  Here is a set of FCC FAQ's that it released earlier this week:
https://www.fcc.gov/faqs-EAS-Cybersecurity-Requirements

Do the Pira boxes qualify, in your estimation?  If so, with our exposure to the Internet, I wanted to change our password on these units to a 15-character, randomly-generated password.  But, the Pira interface only allows me to insert 10 characters. What would you suggest?

Thanks!
23
General Discussion about the RDS / Re: Windows 11 Pro Insider Preview + vpn
« Last post by Jan on September 24, 2026, 03:54:31 pm »
I understand your frustration, but I think there are two important points that need to be clarified.

First, the Magic RDS license is a lifetime license. You do NOT need to purchase Magic RDS 4 again when the license becomes invalid due to system change. Your existing User ID remains valid, and if the Installation ID changes, a new license key can be generated for the new Installation ID. I also reset your account in June specifically to allow further key generation.

So please do not purchase another license. If you have any problem generating a replacement key for your existing license, contact me and we will solve it.

Second, we need to find out why the license becomes invalid. When this happens and Magic RDS falls back to Basic, please go to:
Help - License Manager - Diagnose

Please save this diagnostic information each time the problem occurs. By comparing it with the previous one, we can determine whether Windows is changing the system identifiers used by the licensing system.

However, I also have to point out that you are running a Windows 11 Insider Preview / Evaluation build. Preview versions of Windows are development and testing versions and make changes to the operating system that do not occur on regular released versions. We cannot guarantee correct operation or license persistence on such Windows builds, because Microsoft may any time change system components or identifiers on which applications rely.

In previous posts, I explained how and where the problem arises, how to work with the purchased license, and also how to determine in advance that a specific system is unsuitable for installing the application.

If the diagnostic data shows that the Installation ID changes after an Insider Preview update, there is probably nothing that we can do to prevent this. In that case, the appropriate solution would be to use a regular released version of Windows for a system where stable Magic RDS operation is required.
24
General Discussion about the RDS / Re: Windows 11 Pro Insider Preview + vpn
« Last post by delta67 on September 24, 2026, 03:23:03 pm »
I've absolutely had it with this! for 3 time i'll payed for Magic rds! It's that windows 11 Pro Inside preview Evaluatie-exemplaar. Build 29671.1000.rs_prorelease.260911-1426 that changing Magicrds from Standard to Basic ... within a half year several times! Now i'm don with it!!!!

25
General Discussion about the RDS / Re: RVR TEX300LCD built-in RDS encoder board setup
« Last post by Jan on September 23, 2026, 07:29:49 pm »
Sure, it’s not your fault that we all got so confused by this. But it wasn’t intentional, either. It is actually possible that the final series of this transmitter model really did contain the P232 chip, meaning the documentation is valid — it just doesn’t apply to every single variant they used to manufacture. Unfortunately, this isn't an isolated case; some users of transmitters from brands like BW, for example, have had similar experiences.
26
Configuration Options and Possibilities / Re: Version 4 help (reading XML file)
« Last post by Jan on September 23, 2026, 07:24:34 pm »
If you run into any issues, please let me know. It is important to us that everything works properly. However, I will likely need more information, as it clearly works fine under "standard" operating conditions.
27
General Discussion about the RDS / Re: RVR TEX300LCD built-in RDS encoder (P232) board setup
« Last post by andrew01 on September 23, 2026, 07:12:59 pm »
Quote from: 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.
Thank you for offering your encoders as an option, I have already recommended a model (P164) from your production line to another station that wants to ditch their old 90's AEV RDS encoder and take their RDS setup to the next level ;D , although, in this case, the people with this RVR transmitter already have recent RDS solutions from DEVA Broadcast, and we mostly wanted to test that this function embedded in the transmitter does work.

It's honestly shocking for a "respected" company to fake their documentations, as these are usually the most trustworthy (or should be), pieces of information you can have for the transmitter you own, especially from the manufacturer!  :-[

In this case, it would probably be a good idea to update the debtors page on your site, adding RVR and other companies alike that have unpaid debts, just so people are aware when choosing to collaborate with them.  ;)

Thanks again for the support through this messy "trip" with the built-in RDS encoder!  :)
28
Configuration Options and Possibilities / Re: Version 4 help (reading XML file)
« Last post by dennism on September 23, 2026, 06:49:52 pm »
Thank you for replying. I think I will try a uninstall and reinstall. Something may have been corrupted.
29
Configuration Options and Possibilities / Re: Version 4 help (reading XML file)
« Last post by Jan on September 23, 2026, 05:41:50 pm »
I would like to help you, but unfortunately, I don't know how. When I save and load your file, everything works normally. See the attached image.

Either there is an unknown issue with file access rights, or (unlikely) your Windows installation is corrupted and the XML library is not working. Could you copy the file to another location and try reading it there?
30
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, 04:37:47 pm »
I actually didn't send the whole file, just the title/artist portion. This is a complete file:

<?xml version='1.0' encoding='ISO-8859-1' ?>
<PlayList>
<Entry Event="00"
Type="Playing"
Category="SONG"
Id="MUS6048"
Title="My Sweet Lord"
Artist="George Harrison"
Album=""
Composer=""
MusicId=""
Outcue=""
StationId="WECK_FM"
Duration="00:04:30"
StartTime="2026-09-23 09:55:20"
/>
</PlayList>

I checked and the version I have is the latest.
Pages: 1 2 [3] 4 5 ... 10