ARCHIVED FORUM -- March 2012 to February 2022READ ONLY FORUM
This is the second Archived Forum which was active between 1st March 2012 and 23rd February 2022
Hi,
since a couple of days my Essence MkII is behaving weirdly.
We usually listen to TuneIn, and most often to the second favorite station in our list of favourites. However, after streaming this radio station for a while, the Essence all of a sudden jumps to the next radio station, and starts playing the 3th station in my list of favourites.
Strangely enough, from then onwards the Essence doesn't jump to the next station, but continues to play the same station for hours.
Does anyone experience the same behaviour? Any suggestions how to solve it? I already logged out from tune-in both at product and at Tune-in level, and also restarted the Essence. Nothing seems to help.
I recently added an A6 to my set-up, but I think I already noticed this behaviour prior to buying the A6.
All suggestions and ideas are more than welcome!
BeoNut since '75
elephant: I’ll try to post some sample diagnostics shortly so others can test from their homes. BeoNut since '75
I observed the same behaviour on my BS35 when a radio signal is too weak, or stopped, or if it takes to much time to "start".
--> it may not be an issue with your Essence but with this specific radio stream (as you already imagined)
To check this hypothesis, try to change the order of your favorites: if the second station is still skipped, there’s a problem!
Another issue may come from the band choice made by the app.
Beocare told me the app automatically choose the highest flow. If it’s too weak, same problem. I don’t know if the app changes to a lower speed then?
A method may be to go to the radio website (not via the dedicated app) and to check if several flows are proposed (with the complete internet address). If yes, you can add a custom radio station in your profile on Tunein website.
The B&O app is now able to play Tunein’s custom radio.
Here is an example of a ping ... to radio.paradise ... note that while there were no errors (such as information packets being lost) there was a variation in the time taken to return the signal
ping stream-dc1.radioparadise.comPING stream-dc1.radioparadise.com (174.36.251.136): 56 data bytes64 bytes from 174.36.251.136: icmp_seq=0 ttl=50 time=241.804 ms64 bytes from 174.36.251.136: icmp_seq=1 ttl=50 time=406.841 ms64 bytes from 174.36.251.136: icmp_seq=2 ttl=50 time=325.200 ms64 bytes from 174.36.251.136: icmp_seq=3 ttl=50 time=550.187 ms64 bytes from 174.36.251.136: icmp_seq=4 ttl=50 time=469.462 ms64 bytes from 174.36.251.136: icmp_seq=5 ttl=50 time=244.939 ms64 bytes from 174.36.251.136: icmp_seq=6 ttl=50 time=306.564 ms64 bytes from 174.36.251.136: icmp_seq=7 ttl=50 time=239.312 ms^C--- stream-dc1.radioparadise.com ping statistics ---8 packets transmitted, 8 packets received, 0.0% packet lossround-trip min/avg/max/stddev = 239.312/348.039/550.187/108.998 ms
jans: elephant: I’ll try to post some sample diagnostics shortly so others can test from their homes. BeoNut since '75 That would be very helpful for me!
I’ll try to post some sample diagnostics shortly so others can test from their homes. BeoNut since '75
That would be very helpful for me!
So the ping test is shown above.
What follows is a trace of the route to get to radio.paradise ... then intent is to see which hops take longer than others or indeed time out ... frankly I find this one somewhat confusing ! (I am more used to this test under a Windows environment)
traceroute stream-dc1.radioparadise.comtraceroute to stream-dc1.radioparadise.com (174.36.251.136), 64 hops max, 52 byte packets 1 192.168.0.1 (192.168.0.1) 5.390 ms 2.958 ms 4.015 ms 2 10.112.0.1 (10.112.0.1) 12.632 ms 12.371 ms 11.832 ms 3 * * * 4 * * * 5 * * * 6 198.142.250.205 (198.142.250.205) 25.563 ms 198.142.250.197 (198.142.250.197) 26.037 ms 26.097 ms 7 198.142.139.114 (198.142.139.114) 23.497 ms 24.636 ms 23.591 ms 8 * * * 9 * * *10 * * *11 80.81.69.153 (80.81.69.153) 28.639 ms 27.124 ms 33.614 ms12 ge-3-1-0.0.pjr02.lax002.flagtel.com (85.95.27.181) 175.501 ms 173.441 ms 174.613 ms13 xe-1-0-3.0.pjr03.lax002.flagtel.com (62.216.140.117) 173.245 ms 173.088 ms 173.265 ms14 ge-1-0-0.0.pjr01.lax002.flagtel.com (62.216.140.126) 183.578 ms ge-2-0-0.0.pjr01.lax002.flagtel.com (62.216.140.109) 173.441 ms 173.510 ms15 80.77.2.82 (80.77.2.82) 175.805 ms 172.367 ms 173.277 ms16 ae6.cbs01.cs01.lax01.networklayer.com (50.97.17.64) 170.568 ms * 172.282 ms17 * * *18 69.12.2da9.ip4.static.sl-reverse.com (169.45.18.105) 201.209 ms 198.947 ms 199.421 ms19 * * *20 * ae0.cbs01.tl01.atl01.networklayer.com (50.97.17.163) 220.520 ms 420.101 ms21 ae0.cbs01.eq01.wdc02.networklayer.com (50.97.17.164) 307.427 ms * *22 ae29.bbr01.eq01.wdc02.networklayer.com (50.97.17.145) 243.226 ms 503.617 ms 307.708 ms23 ae0.dar01.wdc01.networklayer.com (173.192.18.197) 307.943 ms 305.958 ms 306.353 ms24 po1.fcr01.sr01.wdc01.networklayer.com (208.43.118.134) 307.396 ms 308.233 ms 305.065 ms25 * * *
CB:I observed the same behaviour on my BS35 when a radio signal is too weak, or stopped, or if it takes to much time to "start". --> it may not be an issue with your Essence but with this specific radio stream (as you already imagined) To check this hypothesis, try to change the order of your favorites: if the second station is still skipped, there’s a problem! Another issue may come from the band choice made by the app. Beocare told me the app automatically choose the highest flow. If it’s too weak, same problem. I don’t know if the app changes to a lower speed then? A method may be to go to the radio website (not via the dedicated app) and to check if several flows are proposed (with the complete internet address). If yes, you can add a custom radio station in your profile on Tunein website. The B&O app is now able to play Tunein’s custom radio.
I also asked the question to BeoCare. This is their feedback: