61
News:
Thank you for using this forum as the technical support base for your device.
● You can format the text and attach screenshots, photos and RDS Spy records
● Faster reply: 50 % of questions are answered within 30 minutes
● You don't need to register (but registration is possible)
● The members represent a wide range of experts
● The resolution will be helpful for other users
● You'll be notified by email about new post
Recent Posts
62
Configuration Options and Possibilities / File to server ICecast
« Last post by radioroccella on March 13, 2024, 07:54:08 pm »I can send metadata files to a Shoutcast server. How to do the same operation with an Icecast server?
63
P132, P164, P232(U) and P332 RDS Encoders / Re: P164 IP assignment
« Last post by Jan on March 08, 2024, 07:32:28 pm »The IP configuration is easy.
Using existing connection (either USB or Ethernet), go to Device Setup - LAN Settings in the Magic RDS 4.
Fill the network parameters as required and click on Apply button. After 20 seconds, the device is available on the network, with the new parameters applied. Existing IP connection is closed.
The device supports status via UDP broadcast, so in local network you can click on the ConfigTool button to see current status, e.g. current IP address assigned by DHCP. That is all.
Hardware watch-dog timer is available as well, if you enable the Fail-safe monitor. Whatever happens with the network, the device will always restore the connection once the network is operating again.
Older encoders should be updated to firmware version 2.2e to ensure compatibility with latest Magic RDS version.
We are not following the RDS2 progress in particular countries. As a manufacturer, we only guarantee compliance with latest IEC 62106 standard release. Not all countries have it implemented yet. We would recommend to consult that with national authority before going on-air with the station logo. I'm having some opinion but it may not be relevant.
Using existing connection (either USB or Ethernet), go to Device Setup - LAN Settings in the Magic RDS 4.
Fill the network parameters as required and click on Apply button. After 20 seconds, the device is available on the network, with the new parameters applied. Existing IP connection is closed.
The device supports status via UDP broadcast, so in local network you can click on the ConfigTool button to see current status, e.g. current IP address assigned by DHCP. That is all.
Hardware watch-dog timer is available as well, if you enable the Fail-safe monitor. Whatever happens with the network, the device will always restore the connection once the network is operating again.
Older encoders should be updated to firmware version 2.2e to ensure compatibility with latest Magic RDS version.
We are not following the RDS2 progress in particular countries. As a manufacturer, we only guarantee compliance with latest IEC 62106 standard release. Not all countries have it implemented yet. We would recommend to consult that with national authority before going on-air with the station logo. I'm having some opinion but it may not be relevant.
64
P132, P164, P232(U) and P332 RDS Encoders / P164 IP assignment
« Last post by joelwitkowski on March 08, 2024, 07:01:25 pm »Hello all,
I cannot seem to assign the IP address on this p164 device, or change the configuration to DHCP.
I could connect to the device's web GUI in default config mode, after adding an address in the same network segment.
I then connected the device using USB/Serial and I can make changes, apply, read them back, and that all seems to work -I'm connected. But upon changing the address, I do not connect if trying to use the IP address in the control software thereafter. The web GUI likewise doesn't load and no response from a ping request.
I think I might be missing something with the Special WIZ network config button.. Or perhaps the "Connect to" must be populated with the PC I am trying to establish the connection with?
I'm missing something. Any guidance you can offer is appreciated greatly.
Thanks!
Also, RDS2, can I flip this on in the United States now?
I cannot seem to assign the IP address on this p164 device, or change the configuration to DHCP.
I could connect to the device's web GUI in default config mode, after adding an address in the same network segment.
I then connected the device using USB/Serial and I can make changes, apply, read them back, and that all seems to work -I'm connected. But upon changing the address, I do not connect if trying to use the IP address in the control software thereafter. The web GUI likewise doesn't load and no response from a ping request.
I think I might be missing something with the Special WIZ network config button.. Or perhaps the "Connect to" must be populated with the PC I am trying to establish the connection with?
I'm missing something. Any guidance you can offer is appreciated greatly.
Thanks!
Also, RDS2, can I flip this on in the United States now?
65
Release News / Re: Release News
« Last post by Jan on March 02, 2024, 10:31:37 pm »Version 4.1.8
http://pira.cz/rds/magicrds/MagicRDS_Setup.exe
Known issues:
This version cannot be used for loading LAN settings to the encoder. The configuration sent to the encoder is corrupted.
http://pira.cz/rds/magicrds/MagicRDS_Setup.exe
- P164, P264(U): Updated section Device Setup / Station Logo. Audio stream URL option added.
Existing logo files should be uploaded again to the encoders to fully comply with the latest IEC 62106 standard release.
Known issues:
This version cannot be used for loading LAN settings to the encoder. The configuration sent to the encoder is corrupted.
66
Configuration Options and Possibilities / Re: RDS information to XML
« Last post by Jan on March 02, 2024, 05:32:16 pm »There are more options available.
For example, you may redirect the Virtual port to the External text source. See the m4vp.pdf help file, section 'Redirecting to External Text Sources'.
Then, add a new connection, kind Encoder, model XML Template. The pictures below show the setup. Such setup will probably require Standard license.
For example, you may redirect the Virtual port to the External text source. See the m4vp.pdf help file, section 'Redirecting to External Text Sources'.
Then, add a new connection, kind Encoder, model XML Template. The pictures below show the setup. Such setup will probably require Standard license.
67
Configuration Options and Possibilities / Re: RDS information to XML
« Last post by sj87 on March 02, 2024, 04:45:08 pm »I am using Jazler Soho as my radio playout software. I have configured Jazler to send Pira RDS 132.
I have setup Magic RDS to receive this, with a Virtual port. This connection works fine.
I cannot workout how to create an XML using this information. Any advice would be appreciated.
I have setup Magic RDS to receive this, with a Virtual port. This connection works fine.
I cannot workout how to create an XML using this information. Any advice would be appreciated.
68
Configuration Options and Possibilities / Re: RDS information to XML
« Last post by Jan on March 02, 2024, 04:20:19 pm »What does it mean "receiving RDS information"? It is via the Virtual port? Or via the External text source? What is the "RDS information" source? Anyway, the Magic RDS 4 can save it to a XML file in all cases.
69
Configuration Options and Possibilities / RDS information to XML
« Last post by sj87 on March 02, 2024, 04:00:55 pm »Hi. I would like to put RDS information in an XML file. All documentation I can find want to go the other way around.
I can get Magic RDS to receive RDS information. I cannot put this information into a file.
Can anyone help?
Thanks
I can get Magic RDS to receive RDS information. I cannot put this information into a file.
Can anyone help?
Thanks
70
P132, P164, P232(U) and P332 RDS Encoders / Re: Dollar Sign on P164
« Last post by Jan on February 27, 2024, 07:40:10 pm »There's no such restriction in the P164 for the dollar sign. It can be showed, of course.
Sometimes the problem is that on common devices, the dollar sign ASCII code is 0x24, while in the original RDS code table the dollar sign has code 0xAB. The solution needs to identify the code table currently in use for the encoder's data input, so it depends on what software and what command do you use for loading the data to the encoder.
The PIRA-family encoders support two code tables on the communication interface: RDS (EBU Latin G0) and UTF-8.
The UTF-8 is used for X-Command, the EBU Latin G0 for other ASCII commands and for UECP.
For the UTF-8, the encoder converts 0x24 to 0xAB itself. For the EBU Latin G0 the conversion obviously needs to be made by the application which sends the data.
Many receivers however do not respect the difference so the dollar sign can never be showed properly on all receivers. You can send 0x24 or 0xAB but not both at the same position... No ultimate solution exists for the $ issue. Maybe it is better to type 'USD'.
Sometimes the problem is that on common devices, the dollar sign ASCII code is 0x24, while in the original RDS code table the dollar sign has code 0xAB. The solution needs to identify the code table currently in use for the encoder's data input, so it depends on what software and what command do you use for loading the data to the encoder.
The PIRA-family encoders support two code tables on the communication interface: RDS (EBU Latin G0) and UTF-8.
The UTF-8 is used for X-Command, the EBU Latin G0 for other ASCII commands and for UECP.
For the UTF-8, the encoder converts 0x24 to 0xAB itself. For the EBU Latin G0 the conversion obviously needs to be made by the application which sends the data.
Many receivers however do not respect the difference so the dollar sign can never be showed properly on all receivers. You can send 0x24 or 0xAB but not both at the same position... No ultimate solution exists for the $ issue. Maybe it is better to type 'USD'.