Posted by: admin
« on: December 25, 2015, 01:24:33 pm »Thanks for the clarification.
That solution can be applied to any existing station and has the benefit that the logo is available immediately after tuning to the station. Initially, the "station logo" RDS feature will be much slower, say 5 to 30 minutes after first tuning of the station, depending on the logo size in bytes, number of RDS subcarriers and bandwidth reserved for this service. The "station logo" is planned as an ODA application so it would work with existing UECP encoders as well.
Update (October 2016): In current RDS2 draft, the logo feature has been completely removed and replaced by a general file transfer function. This file transfer function is unfortunately not compatible with RDS1 so existing RDS encoders (across all brands) will not be able to send logo using this function.
That solution can be applied to any existing station and has the benefit that the logo is available immediately after tuning to the station. Initially, the "station logo" RDS feature will be much slower, say 5 to 30 minutes after first tuning of the station, depending on the logo size in bytes, number of RDS subcarriers and bandwidth reserved for this service. The "station logo" is planned as an ODA application so it would work with existing UECP encoders as well.
Update (October 2016): In current RDS2 draft, the logo feature has been completely removed and replaced by a general file transfer function. This file transfer function is unfortunately not compatible with RDS1 so existing RDS encoders (across all brands) will not be able to send logo using this function.