Recent Posts

Pages: 1 ... 4 5 [6] 7 8 ... 10
51
Feature Requests / Re: Truncation of long titles to be usable for Radiotext
« Last post by Jan on May 01, 2026, 06:10:11 pm »
Using the built-in text replacement (regular expression), you can easily shorten the text as desired. Additionally, if you drop the prefix "Afrika Bambaataa presents" from the text, or place the show name in another text in a loop, you can fit an even longer song title in there. Do you want to give an example here?
52
Feature Requests / Truncation of long titles to be usable for Radiotext
« Last post by andrew01 on May 01, 2026, 05:57:09 pm »
Is it possible for a toggleable option to be added into Magic RDS 4 to truncate titles that exceed 64 characters? I have seen in action such script made with the help of AI at a station here (it was included within the main purpose of adding tags for RT+ for the metadata source so it can be compatible for Stereo Tool's RDS). It's nice seeing long titles like: Afrika Bambaataa Presents: Khayan & The New World Power - Feel The Vibe (Vibe Mix) be reduced to Afrika Bambaataa Presents: Khayan - Feel The Vibe
53
P132, P164, P232(U) and P332 RDS Encoders / Re: Configure RCS NexGen and Pira.cz P164
« Last post by brianradioguy on May 01, 2026, 03:44:38 pm »
Good Day Jan,
Thank you taking time to try and help.  Very much appreciated.  I will give your suggestions a try.  I have a call into RCS now to see if they can help with the setup on their side.  Have a good day.
Brian
54
RDS Spy / Re: UTF-8 Characters bugged in Long PS section
« Last post by Jan on April 29, 2026, 11:16:52 pm »
You are absolutely right that the font could be bigger. The application is almost 20 years old and needs a more significant facelift.
55
RDS Spy / Re: UTF-8 Characters bugged in Long PS section
« Last post by andrew01 on April 29, 2026, 11:07:50 pm »
Ah, I always thought it was something revolving the font size, or the font itself. Cheers for clarifying! ;D
56
P132, P164, P232(U) and P332 RDS Encoders / Re: Configure RCS NexGen and Pira.cz P164
« Last post by Jan on April 29, 2026, 10:48:00 pm »
There are several ways here. I'll assume that your station is supposed to have a modern feel, so we'll also broadcast RT+ straight away.

There are two basic steps:
  • In the NexGen, enable XML export to a file. Ask the NexGen community for all details and options. Make sure the song artist and title fields are included. Other fields can be present as well, this is no problem for further processing.
       
  • In the Magic RDS 4, use the External Text Sources for reading such file. Other supported options include TCP or HTTP (using the redirecting method or internal HTTP server, as described in Help - m4vp.pdf). But I understand that you're still discovering the world of tagged text broadcast, so you should probably start with the "Local File" option as it's the easiest.

    See the tutorials at
    https://pira.cz/forum/index.php?topic=987.0
    https://pira.cz/forum/index.php?topic=990.0

Estimated setup time is about 3 to 10 minutes.
57
P132, P164, P232(U) and P332 RDS Encoders / Configure RCS NexGen and Pira.cz P164
« Last post by brianradioguy on April 29, 2026, 10:34:13 pm »
Good Day,
This is my first Pira.cz RDS P164.  I have searched the forum making changes I see, and tried to get help from a local source.  Nothing I've done has worked to get the NexGen data to the P164.  Would somebody be willing to give me screen shots and/or talk with me on a step by step workflow to get this going?  I'm at a loss.  I'm using Magic 4, and have even tried Magic 3 to no avail.  I would very much appreciate some expertise help.
Thank you,
Brian
58
RDS Spy / Re: UTF-8 Characters bugged in Long PS section
« Last post by Jan on April 29, 2026, 09:37:59 pm »
Windows API functions are used to assign characters and render them. I'm sorry but I'm not aware of any issue there.

59
RDS Spy / UTF-8 Characters bugged in Long PS section
« Last post by andrew01 on April 29, 2026, 09:10:02 pm »
Hello! I have noticed a small bug while playing around with the latest version of RDS Spy (1.0.9), that being that the characters Șș and Țț (especially the capital letters) are having problems with the font used in the Long PS section. I have also seen this exact issue on a RDS recording I did a bit of time ago of another station.
60
P132, P164, P232(U) and P332 RDS Encoders / Re: Radio Text triggering via GPIO
« Last post by Jan on April 22, 2026, 01:38:30 pm »
Yes, you can accomplish this task with any of our RDS encoders that has a corresponding switching port, either externally or on the board.

However, based on our experience with broadcast studios, I must tell you that this method of manual control is deprecated and is it no longer recommended for professional use. The reason is that you are manually controlling the RDS content, CD playback and probably also the playback of songs from the PC, and possibly also corresponding audio paths. This method does not guarantee a consistent result and there is a big room for operator mistake.

Consider some kind of stream deck device where you can assign any number of tasks to a single button. You can use a single button to switch RDS content via http API (no switch needed), control audio paths or play CDs via MIDI, and even control the broadcast automation system via its API.

Well, back to your question:

There are several options here, the easiest for you will be to switch between Program 1 and Program 2 using an external switch.

Initially you set each of the program sets as needed, so one will have RT1 turned on with the song displayed from the PC, the other will have RT2 turned on with fixed text. Basic content will be equal.

Finally, you type in the terminal
Code: [Select]
PROGRAM=0
*PROGRAM
However, you must take into account that before editing RDS content, you must switch back to Program 1 or Program 2.

Follow the user manual for exact pinout of the GPIO connector and the PROGRAM command behaviour.
Pages: 1 ... 4 5 [6] 7 8 ... 10