EId indicated in SPI bearer ignored

[Peterdoo]

Hello,

here are two raw recordings:
8B: https://mega.nz/file/3Vs2yKjY#xRNUYXinl14qxoLGpwi_hE_DelCYj3UMA9KX9FiPago
8D: https://mega.nz/file/CEM1RY4B#ttCXByxnSYE2LG9EfvM4G3-Ej2g685J8MJsijf3vL2M

The service with identical SId E2-E205 is present in both ensembles. In 8D it is called "Activa FM". In 8B it is called "Activa FM 8B". Depending from which ensemble I select them, correct name is displayed.

However there is a problem with SPI logos. Each ensemble transmits its own different SPI logo which is only assigned to the bearer containing EId.
In 8B there is a SPI logo for bearer SCIds="0" ECC="E2" EId="EAAD" SId="E205"/.
In 8D there is a SPI logo for bearer SCIds="0" ECC="E2" EId="E302" SId="E205"/.

When Abracadabra displays a logo it simply takes the last one received where ECC and SId match, ignoring EId, although that one can be for the wrong EId. For example after receiving the service on 8D, first the correct logo for that one (ECC="E2" EId="E302" SId="E205") is displayed:

Then I select that service from 8B. Instead of displaying the correct SPI logo for that one (ECC="E2" EId="EAAD" SId="E205), it keeps displaying the wrong logo that is only linked to EId E302:

After some time, it will display the correct SPI logo for EId E2-EAAD (it has two dots in the bottom edges):

And so on every switch of ensemble, the wrong logo is displayed.

In my opinion, the four parameters from bearer indicated in SPI should be respected by receiver. So it should always cache the logos for all EIds and try to use the logo where all four parameters from bearer match to the values where the service is being received. Only when a logo with exactly identical parameters is not available, I would try to use a logo where EId does not match. Or where SCIds value does not match. There is a service E2-E205 with SCIds 1 in the 8B. As that one does not have its own logo in SPI, one could use the logo for the service E2-E205 SCIds 0. But only when no logo for E2-E205 SCIds 1 is present.

There are broadcasters in Europe that have a service that splits to 50 or more regional variants. The SId in the form of Ex11 inherited from RDS PI code only allows for 12 different values to be used. DAB does not provide a means for better signaling of regional variants. So as soon as a broadcaster covers more than 12 regions, it is inevitable that there will be versions with identical SId (but different EId) which would have different logo carrying the name of its corresponding region. So not matching EId when selecting the logo and dropping EId information when storing logos is not a good idea except when a logo with exact match is not found. The same goes for SCIds.

[KejPi]

This is very interesing case, thank you very much for sharing the recordings. SPI feature development is difficult for me because I have no SPI available on air and I rely only on recordings I was able to collect. I agree that current behavior is not correct, this is the first time that I can see that actually there can be different service logo for different ensemble. I will try to include this modification in coming 4.0.0 because the change will actually invalidate all SPI cache entries.

EDIT: I am not sure about secondary service proposal but I agree with EID logic.

[Peterdoo]

Thank you KejPi. Even so Abracadabra has one of the best and most robust SPI implementations. These are really details that one does not see really often.

I leave the decision about treatng SCIds to you. You are probably right. In the case of the above recording, the secondary service carries the audio of the service +Activa which has a different logo than its primary service.

[KejPi]

Please check 3.99.1 and provide feedback.

[Peterdoo]

Thank you! This was fast. Very nice the way you have solved the possibility for various EIds.

It works perfectly now.