71
Bug Reports / Re: RT+ with Stereo Tool
« Last post by davidbiz on April 06, 2024, 11:50:43 pm »Thank you! Updated ST to the latest version and it seems to work now. Thanks again.
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
72
Bug Reports / Re: RT+ with Stereo Tool
« Last post by Jan on April 06, 2024, 10:02:38 pm »Thanks for your post which makes it completely clear.
The reason for such behaviour is that there's a second RT+ encoder running in the ST. This RT+ encoder sends blank data. On the receiver side that results in periodical switching between correct RT+ from the Magic RDS and blank RT+ from the ST.
You need to reset the ST or disable its internal RT+ module.
The Magic RDS periodically sends only
<FE><00><00><00><07><24><06><16><00><00><4B><D7><6D><4A><FF>
<FE><00><00><00><07><24><16><08><80><0E><09><6B><77><FC><FF>
that means:
ODA AID group 3A assigning group type 11A to the RT+
and RT+ data in the group 11A.
The UECP buffer mode for such data is "flush and forget", the Magic RDS does not set any permanent transmission for such data, so even changing the Magic RDS settings in the RT+ extension cannot result in such behaviour.
The reason for such behaviour is that there's a second RT+ encoder running in the ST. This RT+ encoder sends blank data. On the receiver side that results in periodical switching between correct RT+ from the Magic RDS and blank RT+ from the ST.
You need to reset the ST or disable its internal RT+ module.
The Magic RDS periodically sends only
<FE><00><00><00><07><24><06><16><00><00><4B><D7><6D><4A><FF>
<FE><00><00><00><07><24><16><08><80><0E><09><6B><77><FC><FF>
that means:
ODA AID group 3A assigning group type 11A to the RT+
and RT+ data in the group 11A.
The UECP buffer mode for such data is "flush and forget", the Magic RDS does not set any permanent transmission for such data, so even changing the Magic RDS settings in the RT+ extension cannot result in such behaviour.
73
Bug Reports / Re: RT+ with Stereo Tool
« Last post by davidbiz on April 06, 2024, 09:36:02 pm »Thnx for your feedback. Before we were using Magic RDS 3.8 with ASCII mode and RT+ worked, but with new version I cannot even get radiotext through lite ASCII, so that is why we are using Generic UECP. Also We have enabled RT+ Encode in Software Extensions - 11A. Even if I try with others it seems that it makes no difference.
Anyway, sending communication monitor data and recording from RDS Spy.
Anyway, sending communication monitor data and recording from RDS Spy.
74
Bug Reports / Re: RT+ with Stereo Tool
« Last post by Jan on April 06, 2024, 12:18:01 pm »UECP has no explicit support for the RT+ so you either need a RDS encoder with X-Command support or enable the RT+ UECP extension, which is a PC software-based RT+ encoder.
The RT+ UECP extension works correctly with encoders which comply with UECP specification.
To see what's wrong, I would need a sample record from the RDS Spy (at least 1 minute) and a sample listing from the Magic RDS - Overview - Communication Monitor.
The RT+ UECP extension works correctly with encoders which comply with UECP specification.
To see what's wrong, I would need a sample record from the RDS Spy (at least 1 minute) and a sample listing from the Magic RDS - Overview - Communication Monitor.
75
Bug Reports / RT+ with Stereo Tool
« Last post by davidbiz on April 06, 2024, 12:38:39 am »Hello,
I just bought 2 instances of Magic RDS 4 to use it on FM, but I cannot get RT+ right. We have connection through TCP/IP and UECP to Stereo Tool 10.21 standalone app. Radiotext goes through, but if I want to enable RT+ I must enable software extension, but then RT+ keeps appearing and dissappearing. RT+ is active only for second or two. I tried much everything (different groups, sequence in ST).
Can you help please?
I just bought 2 instances of Magic RDS 4 to use it on FM, but I cannot get RT+ right. We have connection through TCP/IP and UECP to Stereo Tool 10.21 standalone app. Radiotext goes through, but if I want to enable RT+ I must enable software extension, but then RT+ keeps appearing and dissappearing. RT+ is active only for second or two. I tried much everything (different groups, sequence in ST).
Can you help please?
76
Control Software / Re: MagicRDS4 and Nautel
« Last post by Erics on April 02, 2024, 10:16:48 pm »I am looking at this software to use with the internal RDS encoder in the Nautel VS2.5. Have you had any success with the NVLT yet?
Thanks Jan,
I have been experimenting and it does work with ASCII Lite and UECP but I haven't figured it out enough to be confident yet.
Thanks,
77
P132, P164, P232(U) and P332 RDS Encoders / Re: P164 Logo
« Last post by radioroccella on April 02, 2024, 12:46:04 pm »Grazie acnora. 
78
Silence Detector / Re: Ubuntu and WINE
« Last post by Jan on March 31, 2024, 08:21:29 pm »I'm not the Ubuntu user but I suppose that WINE will provide some generic audio driver which you can select in the Silence Detector. Installing any Windows driver does not sound to me as an appropriate way.
79
Silence Detector / Ubuntu and WINE
« Last post by felkman on March 31, 2024, 08:16:44 pm »I'm trying to use the Silence Detector on Ubuntu OS using WINE. Do I need to install windows drivers for my sound card with WINE, or will Pira be able to use drivers installed on the Ubuntu OS? Thanks.
80
P132, P164, P232(U) and P332 RDS Encoders / Re: P164 Logo
« Last post by Jan on March 31, 2024, 06:58:35 pm »The size of 3 kB is mentioned in the latest release of the IEC 62106 standard. I think it is appropriate. For the best user experience, it is important how fast the logo loads, rather than how many graphic details are there. The LCD area which is dedicated on receivers for the logo display, is usually small, so sending larger files only result in longer transfer time.
The P164, however, does not have such technical limitation. It is able to send over 8 kB file from its internal memory or up to 163 kB when driven by external application. The Magic RDS 4 is now restricted to 6 kB, as some space is reserved for other RDS2 features. In my opinion, best results can be obtained with a file size of 3 to 5 kB.
If there is an interest, I can clarify the technical background of why the RDS2 system is not able to meet the original expectations or why 4 carriers may be slower than 2 carriers, etc. The original idea of sending different graphics and large files was very naive. After some experiments made on various stations around the world, the standard has been updated to the present form.
Some logo examples are attached below. They have all about 3 kB. Click for full size.
Typical transfer time of 3 kB file is under 1 minute if FM reception is excellent.
The P164, however, does not have such technical limitation. It is able to send over 8 kB file from its internal memory or up to 163 kB when driven by external application. The Magic RDS 4 is now restricted to 6 kB, as some space is reserved for other RDS2 features. In my opinion, best results can be obtained with a file size of 3 to 5 kB.
If there is an interest, I can clarify the technical background of why the RDS2 system is not able to meet the original expectations or why 4 carriers may be slower than 2 carriers, etc. The original idea of sending different graphics and large files was very naive. After some experiments made on various stations around the world, the standard has been updated to the present form.
Some logo examples are attached below. They have all about 3 kB. Click for full size.
Typical transfer time of 3 kB file is under 1 minute if FM reception is excellent.