In reply to:

---

If you see other frequencies in AF Debug, then the station you're listening to (claims that it) has more than one frequency. Perhaps your radio station is broken - did you try with different broadcasters? Ideally, unrelated broadcasters - e.g. in Britain I'd compare a BBC station with an independent one.

---

Well, this is how I understand this, correct me if I am wrong:

The station I am listening to (Radio24) has a number of different frequencies depending on what area of the Country you're in. Consider it is a nation-wide station, so supposedly it broadcasts all over Italy.

All the frequencies available are sent to the empeg as "alternate frequencies" in the RDS signal, so that when you move though the Country the empeg can pick up the strongest frequency, as long as it still is Radio 24 and not any other station.

My point is that in Rome specifically Radio 24 only broadcasts on ONE frequency. When the empeg detetcts a stronger singnal on any of the alternate frequencies, it is actually listening to some other (local, but not only) station that in the area of Rome is occupying that frequency, and that is not Radio24. In other words. it seems to me that the problem consists in bot being able to check whether the station remains the same when switching to an alternate frequency.

To answer your question, yes, I did try with other stations. Consider that the empeg continues to switch to different stations, apparently randomly. I remember four (for the Romans in here, if there's any: Radio 24, Radio Dee Jay, Radio Dimensione Suono, Radio Subasio), but I am quite sure there are more...


Now, propbably I am missing the correct logic behind the AF function, in which case I'm sorry

The empeg can check the signal strength quickly (a few milliseconds), which is what it uses to poll AFs.

However, to pick up the PID (16-bit station ident code) from RDS requires - with 100% RDS reception - up to 104+103 bit times (104 bits is a packet, assuming the worst case of coming in one bit too late). At 1187bps, this is about 174ms.

In actual fact, you may need to wait a little to get everything settled; say 250ms. The empeg should be tuning to the wrong station for no longer than half a second before switching back - though I'm not sure if it "blacklists" AFs that it's found no PID on (it really should do this for a period of time like an hour or so).

Really high end RDS radios have twin tuners, allowing them to verify AFs before switching to them totally seamlessly.

Hugo

The empeg should be tuning to the wrong station for no longer than half a second before switching back

I see. Maybe than it is this checking stage that does not work properly and the empeg does not switch back to the right station... ? At least this is what it seems to be doing in my case...

Un fortunately this bug is really preventing me from listening to the radio.

So I can't really help asking "the" question :

1) Empeg team, could you let us know if you think a patch will be released anytime soon?
2) Can I upload beta13 to the Empeg, and have it work with emplode 2.00 final, or is this going to cause problems of any kind?

Thank you very much in advance!

After another weekend away and a couple more TA interruptions, it seems that traffic announcements work correctly in Tuner mode (including returning to the original programme at the end), but I've had no success in Player mode. It seems to give a burst of the traffic station, then switch back to the usual radio station immediately.

The performance of AF following whilst in Player mode seems a little flakey; I don't know if this is related to the problems with presets?