Recent Posts

Pages: 1 [2] 3 4 ... 10
Yes, the communication normally works with the BW TX V3 (with regard to the exception mentioned above).

It seems to be a configuration issue. Well, I think you can discover the cause. In the Communication monitor, you can see the outgoing data. Please make a comparison between data sent after manually pressing the Radiotext - Test button and the data sent by External text tool. Copy&paste both cases to this forum so we can decide.
Thank Jan, Using 'RDS Content' and clicking 'Read' it always shows what static text I've entered into the V3 GUI.  Also, if I enter some test text (in Magic RDS 4) then READ it, it always does show the test text!  So it seems like the Magic 4 RDS software does know how to communicate with the V3.
Release News / Re: Release News
« Last post by Jan on May 16, 2023, 10:10:21 pm »
Version 4.1.0

The External text sources are finally completely redesigned. Further text outputs are now allowed, each with selectable format and destinations. Single instance of the application can now serve several radio stations.
MP3 audio recorder added.
PI calculator added.
Bug fixes: PIRA32 RTP if final Radiotext doesn't match any RT+ template, JSON parser access violation error, JS infinite loop protection and much more.

The version 4.1.0 brings the biggest update from the date of origination. Although we spent a lot of time on testing, we strongly recommend to check the External text sources configuration after updating from older versions, to verify that all settings were converted successfully to the new environment. Please report any bugs.

Known issues:
The Text Replacing now applies to Text conditions as well. As the result, the Text conditions may work different way after the update. Please wait for the fix.
Bug Reports / Re: added text showing
« Last post by Jan on May 15, 2023, 03:39:45 pm »
Go to Help - License manager.
The key is permanent in the context of the installation. After reinstall of the PC, deleting the configuration xml file or another operation of such kind, you can simply generate a new key using your existing user ID. Click on the Buy license / Get key button.
Bug Reports / added text showing
« Last post by dlake76 on May 15, 2023, 03:27:52 pm »
Hi, I bought a license a few months ago and installed the key.  But today, I noticed it's displaying at the end of every song.  Sorry, but how do I get rid of this?  Thanks. I'm using Magic4 on a PC.
It seems you did everything right. The BW V3 transmitters were known for a bug in their TCP stack implementation. See for example here:

To verify this, please make a test: In the same time the V3 is not showing the text from the automation, try to send some RT manually, using the RDS Content - Radiotext - TEST.  The RT is encoded same way in both cases so I would expect the same result.
Hello, I'm trying to do the easiest thing with your great software.  Simply to dynamically get the Song Title and Artist to the RBDS encoder in our BW Broadcast transmitter.  I've read the help screens, but apparently don't really understand the basics of what I have to do!

I've set up an RDS encoder (Readbest) and it is connected to the BW Broadcast transmitter (via TCP).  I can change the static RT text or read the static RT text using Magic RDS 4.  So far so good!

I have also set up virtual port for it which listens to data sent from the NEXGEN automation system.  It is receiving the song title and artist as it is sent in the RDS Encoder as I can see it on the "overview" screen (with the communications monitor "on").  The song title and artist are even displayed next to the station's call letters on the "overview" screen. 

But it isn't sending this data to the BW Broadcast transmitter's RBDS encoder!

Am I supposed to be using the "External Text Sources"?  Or do I also have to add a "bridge" ?

The software seems wonderful... but I am missing something critical here!

Control Software / Re: MAGIC4 Bridge virtual port TCPIP telnet syntax
« Last post by davidmb on May 12, 2023, 06:41:00 pm »
Hi Jan,

ok, thanks for the feedback.
Great info! :)
Any timline already in place when can we expect user-selectable separator to be implemented?

Br, David
P132, P164, P232(U) and P332 RDS Encoders / Re: sending UTF8
« Last post by wbtcpip on May 12, 2023, 06:30:00 pm »
thank you
P132, P164, P232(U) and P332 RDS Encoders / Re: sending UTF8
« Last post by Jan on May 12, 2023, 04:20:25 pm »
I've sent the conversion table to your email.
First word is the EBU Latin character (128-255), next three words are appropriate Unicode characters in hex representation. 0 means unused position.
Pages: 1 [2] 3 4 ... 10