Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
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.
22
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.
23
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!



24
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.
25
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!
26
Configuration Options and Possibilities / Re: Setting up DJB Zones automation with a Pira P164 and Magic RDS4
« Last post by Jan on May 31, 2025, 09:33:24 am »
Compared to older models, the P164 is more robust and easy to set up if you follow the instruction. Some functions, like the RDS web UI or additional TCP ports, were moved to the Magic RDS 4 middleware. Although this change does not seem to bring many advantages for a station with a single transmitter, for larger broadcasting networks the benefit is quite significant as such network needs some kind of middleware in any case and all RDS encoders are now accessible from one place, one IP address and under one login.

For example: Need to change PS name on all 40 encoders in the network? You need no more than 30 seconds for such task:
Menu Script/Execute: send connection:* command:"PS=New PS" command:"*PS"
You are done. Imagine how long does this take if you need to log into each encoder individually. Or how to feed "now-playing" data or TMC data to each encoder individually, how many public IP addresses you need etc.

Back to your question: The P164 allows both modes of operation, either with or without the Magic RDS 4 middleware. If you don't need the benefits of the middleware, you can connect your broadcast automation system directly. The broadcast automation system must support some of the common data formats, like ASCII, UECP or XCMD.

In your case, if you specified the RDS encoder's IP address in your system, the encoder needs to be set up as TCP server. The easiest way how to make initial TCP setup is to use the Magic RDS 4 and USB connection, as described in the manual, section 'Ethernet Connection'. You may keep the Magic RDS 4 connected to the USB, click on the RDS Spy button to verify that your system sends the data correctly. Then you may close the Magic RDS 4 as the setup is done.

If you decide the use the Magic RDS 4 middleware, your broadcast automation system will not connect to the RDS encoder(s) but to the Magic RDS 4. For this purpose the Magic RDS 4 supports the Virtual Ports. They operate the same way like any other TCP ports and they represent common data inputs for particular encoders or for all encoders, with data visualization feature included. See the m4vp.pdf help file for details and examples.
27
Configuration Options and Possibilities / Setting up DJB Zones automation with a Pira P164 and Magic RDS4
« Last post by Tom McGinley on May 31, 2025, 08:22:17 am »
I am asking a very basic setup question here. I have a brand new PIRA P164 encoder that can receive RDS data via serial or TCP/IP. I have it connected to receive RDS data from our DJB Air server via an ethernet switch that handles our DJB subnet. The Magic RDS4 app is loaded for now on a separate DJB file server. The P164 pulled a DHCP IP on the DJB subnet at 192.168.91.211.  I've tried to get it configured to receive the RDS text data being generated from the DJB Air server which we see scrolling on the Hercules data capture app on a connected DJB production machine. I added the PIRA P164 IP as the target device in the DJB Air server Metadata setup screen: 192.64.91.211:10001. The Magic RDS4 tool allows setting up the P164 encoder as either a TCP client or TCP server. I have it set as a TCP server.  I presume other DJB machines with the Magic RDS4 app loaded and running will be TCP clients and can show the RDS scrolling data as air events change. The P164 shows as connected to the Magic RDS4 Tool but I am not seeing any text data coming into that app's Viewer from DJB. Perhaps I don't have the TCP setup or ports assigned correctly.

I am quite familiar with the older PIRA RDS ethernet connected encoders without any middleware with good success. Those models had a much easier web UI to do the IP setup plus static PS and RT messages with windows that scrolled the RDS PS and RT data as it updated from the automation. It didn't need the Magic RDS4 tool. The P164 web UI (port 80) does not offer that and only shows the static ethernet setup parameters.   What am I missing to get this configuration corrected before I try connecting the P164 to my transmitters SCA input to see RDS texting on car radios?
28
Release News and Tutorials / Automatically save playlist to different file each day
« Last post by Jan on May 29, 2025, 08:08:25 pm »
Once you successfuly configured the artist and title publishing for currently playing song, you may follow these simple steps to save daily playlists.

  • Add a new Connection of kind 'Bridge', named 'Save Playlist'.
    Select Connection Type: Internal Channel.
    Fill the Data Distribution box as follows:
    saveto prefix:"%DATETIME:hh:nn:ss%; " file:"C:\yourfolder\Playlist %DATETIME:yyyy-mm-dd%.txt" mode:"append"
       
  • In the External Text Sources, add a new Output.
    Move existing source to the Output.
    As the Destination, fill sendto "Save Playlist"
29
Release News and Tutorials / Re: Release News and Change Log
« Last post by Jan on May 29, 2025, 07:34:27 pm »
Version 4.2.5

http://pira.cz/rds/magicrds/MagicRDS_Setup.exe

  • External Text Sources: New text processing preset added: ARTIST (in uppercase) - Title (in titlecase)
  • External Text Sources: The Window Title source now allows filtering based on the process exe file name
  • saveto command now accepts dynamic elements in the file name parameter, for example %DATETIME:dd-mm-yy%.txt
  • sendhttp command now supports %1% to %4% dynamic elements for use with XML/JSON source
  • sendhttp command now fully supports Unicode
  • Configuration: Auto Save options added to Preferences
  • Bug fix: TA timeout setting
  • Bug fix: UDP communication with P132/P332
  • Bug fix: The titlecase text processing preset has unexpectedly applied to %GOTONEXT% and other commands
30
PIRA32 RDS Encoder / Re: Firmware update fail. Help
« Last post by Jan on May 28, 2025, 03:33:03 pm »
Please download again: https://pira.cz/rds/rdsup.zip

If the update fails, save the log and post it to me.
Pages: 1 2 [3] 4 5 ... 10