Recent Posts

Pages: 1 ... 7 8 [9] 10
81
Hello Jan. Thanks for your reply and assistance. We have one Pira P164 connected via IP from our DJB automation Air server on the same protected subnet. The P164 output is connected directly to a Nautel VS1 transmitter SCA/RDS BNC input. We are getting DJB ASCII metadata and default dynamic PS and RT rotating messages programmed into the P164. We have a Nautel V10 transmitter at a remote site that we need to send the DJB metadata to another P164 encoder there. A separate TCP/IP connection is not available so we presume an RS232 serial connection conveyed via a Comrex or Barix link may work. In order to do that, I presume we need to deploy the Magic RDS4 app on a DJB LAN connected machine to receive the DJB metadata and then feed both a TCP/IP connection from there to the VS1 transmitter and a serial connection to the V10 transmitter.  The manual shows a block diagram in section 6.3 of multiple transmitters connected from a PC running Magic RDS4 via TCP ethernet ports. But I do see any descriptions of how remote transmitters with a local P164 can be fed with serial data from Magic RDS4 running on a PC. Can you provide the detail on setting up that connection?
82
PIRA32 RDS Encoder / Re: RDS RT Jazler SOHO
« Last post by Ivan on June 26, 2025, 03:45:18 pm »
Hello, you need to install the Universal Driver UP Universal, it will display the artist and song!
83
P132, P164, P232(U) and P332 RDS Encoders / Re: ' character doesn't appear on RT - P132
« Last post by Lucas G on June 09, 2025, 06:23:21 pm »
Thank you Jan for the reply.
My friend has moved to Magic RDS in order to manage the data, the issue is fixed!

I didn't know that firmware version he used. I will tell him anyway.
84
This issue did exist in the first firmware versions, but that was about 10 years ago. In current versions, this has long been fixed.
Please update the firmware and the embedded website to current version. The product site can be found in Support section.
85
P132, P164, P232(U) and P332 RDS Encoders / ' character doesn't appear on RT - P132
« Last post by Lucas G on June 09, 2025, 04:27:48 pm »
Hello,

A friend of mine has an issue with a ' character that doesn't appear on the RT of his station. He uses a P132 encoder and manages it directly from the web interface.
The "À" character works very well for example, but ' doesn't appear on the slogan.

The RT contains the slogan (sent "locally" from the encoder configuration) and the current song title (sent remotely).
The ' character seems to be displayed correctly on the current song title.

I've tried to find a solution on the manual and on the forum, without success.

Thanks in advance for your reply,
Lucas G.
86
Configuration Options and Possibilities / Re: Text Campaigns and Expire After
« Last post by radiosavage on June 06, 2025, 07:59:38 pm »
Thank you.  I did have it misconfigured with the text sources.  I made the change, and it is working as expected.  I was under the impression when using the instructions that you only added an internal channel if you did not have one.  This makes a lot more sense.  Thank you.
87
Configuration Options and Possibilities / Re: Text Campaigns and Expire After
« Last post by Jan on June 05, 2025, 08:10:26 am »
Yes, what you're doing now is telling the application "stop sending the song name after 3 minutes".
A second step is missing, telling "what to display instead of that".

Put both Sources to the Output, the song, as well as the text campaign loop.

For the song, set 'Go to next after' to 99999 or something similar
For the TC, set 'Go to next after' to 30.

That's one of the approaches possible.
88
Configuration Options and Possibilities / Text Campaigns and Expire After
« Last post by radiosavage on June 05, 2025, 02:50:21 am »
I just upgraded to the latest version with Text Campaigns, and it works great except for one issue that may be a misconfiguration on my end but not sure how to track it down or what I am doing wrong.

I have one text source at a time.  I enabled a text campaign and set the main text source so that it expires after 180 seconds since they want the text campaign to be the standard message when the "Expires After" times out.  However, I am finding that it will continue to display the text source song well after the 180 seconds.  I know the documentation says that when using a single source that the "Expires After" setting has little effect.  Is this the correct behavior?  Thoughts on how to make this work.  I was thinking the Text Campaign becomes the second source. 

Thank you!



89
General Discussion about the RDS / Re: EON Questions?
« Last post by Jan on June 03, 2025, 09:08:14 pm »
Same content with different commercial breaks, that's a typical scenario for using regional variants rather than EON.

Regional variants however require that both PI have the same last two digits, for example E3AA and E4AA. If this is not the case, you may use EON for linking the stations.
90
General Discussion about the RDS / EON Questions?
« Last post by bluemax on June 03, 2025, 08:55:11 pm »
Hi,
Could someone please point me in the right direction to help me understand EON?

Looking on Google isnt really helping me.

Im trying to see if it work help with my scenario in Spain.

Two networks with two separate PI codes - and separate commercials on each network. Apart from the commerical breaks - the content is the same.

Would EON help me - by allowing me to operate with one PI code? Both networks overlap in areas and by sharing a PI would help with coverage for listeners in cars. My understanding is EON is used in the UK by the BBC for localised content.

Thanks in advance!
Pages: 1 ... 7 8 [9] 10