Radio Data System (RDS) > Control Software
Nexgen config for Pira32 encoder
Jan:
Not only the "title and artist" interface is the nightmare for FM broadcasters. Standards are missing also for kHz/Vpp modulation sensitivity of FM exciters (very big problem), file formats generated by broadcast automation systems or behaviour of receivers in various situations. Insufficient text features of original RDS result in terrible solutions like dynamic/scrolling PS whose function cannot be guaranteed in principle... Where standards are missing, the RDS encoder must be able to comply with various solutions of particular manufacturers. This extends the number of setting and adjusting elements. You're right, absolutely.
For placing the song info to Radiotext, configure the NexGen as follows:
* Go to the Export Format(s) dialogue box and select 'Standard' for Format. Select appropriate option for Output (for remote connection this is usually 'TCP/IP').
* Check the 'Remove Header' box down in the lower left hand corner of the window.
* In the lower right, depending on the Output selection, configure the parameters for connection to the RDS encoder.
* In the Standard Format Settings area on Line 1, enter the Lead Text as 'TEXT='
* Select 'Title' from the Output Field.
* On Line 2, leave the Lead Text blank but select 'Artist' from the Output Field.
* In the Field / Record Separators section, select 'Other Space' for the Field Separator and for the Record Separator, select 'CR/LF'.
* Finally, click OK and restart the NexGen.
The PIRA32/P164/P132/P232/P332 encoders support among others these commands for song info:
* For placing the text to Radiotext 1: TEXT= or RT1= or UECP RT command
* For placing the text to Dynamic PS 1: DPS1ENQ= or DPS=
* For placing the text to both the Radiotext and Dynamic PS: any of the option above + the encoder must be pre-configured by the command EQTEXT1=1 (see the technical manual for details) or by enabling the 'RT1 equal to DPS1' option in Magic RDS / Text setup.
The text must be terminated by <CR> or <CR><LF>.
Example:
TEXT=Now playing XXX - YYY<CR><LF>
See more info in 'Technical manual', section 'Broadcast Automation System Link-up' or in 'P132 - Communication ports and internet function', section 'Frequently Asked Questions'.
mikehagans:
My five NexGen ASERV machines currently feed old Audemat FMB80s serially, with dead web-configuration interfaces. I'd like to replace the FMB80s with P164s. I want NexGen to feed them over the network (TCP) instead of serially. I do not want to have additional PC software in the path for the Title and Artist data. I would ALSO like to include dynamic PS messages that changes on a schedule throughout the day. I don't mind using another PC (running Magic RDS4) for the scheduled changes to the PS. Will this work: direct-feeding the P164 with T&A, while also making dynamic PS changes using Magic RDS4? I'm sorry if this is repetitive. I will read the manual, and ask more questions if needed during install, but need to order the devices soon if they are to arrive in time. B/R Mike
Jan:
You no longer need to feed each encoder individually if the Magic RDS 4 is running anywhere. (On the other hand, you can still keep such setup as a backup - alternative configuration). You do not need any extra PC. The Magic RDS 4 is a full featured RDS server software, so it takes over all tasks related to the RDS network management, incl. data distribution to each encoder. It's usually much more convenient. The P164 was primarily developed for this mode of operation.
So you can send data from Nexgen while sending scheduled messages from the Magic RDS 4. The Nexgen will connect to the Magic RDS 4 instead of the encoders.
Navigation
[0] Message Index
[*] Previous page
Go to full version