Thank you for all the great information

Thank you for all the great information

I wonder if you could use a PS4 (or a PS3) in the same way as others are using the macmini

I have a PS4 and it's attached to my avant 

Dear All

I also have the BeoSound Moment and experience the slowly ness from the Jukebox: regarding covers, total GUI not responsive, volume controls delayed etc. I my search how to solve I found out no matter what I do (tried all possible swapped WIFI and even build an access point within 1 meter from the moment) that ping results from the Jukebox are relay bad see just a few below:

PING 192.168.1.55 (192.168.1.55): 56 data bytes

64 bytes from 192.168.1.55: icmp_seq=0 ttl=64 time=285.393 ms

64 bytes from 192.168.1.55: icmp_seq=1 ttl=64 time=203.110 ms

64 bytes from 192.168.1.55: icmp_seq=2 ttl=64 time=134.412 ms

64 bytes from 192.168.1.55: icmp_seq=3 ttl=64 time=353.057 ms

64 bytes from 192.168.1.55: icmp_seq=4 ttl=64 time=280.083 ms

64 bytes from 192.168.1.55: icmp_seq=5 ttl=64 time=1.619 ms

64 bytes from 192.168.1.55: icmp_seq=6 ttl=64 time=114.676 ms

64 bytes from 192.168.1.55: icmp_seq=7 ttl=64 time=35.494 ms

64 bytes from 192.168.1.55: icmp_seq=8 ttl=64 time=267.982 ms

64 bytes from 192.168.1.55: icmp_seq=9 ttl=64 time=186.677 ms

64 bytes from 192.168.1.55: icmp_seq=10 ttl=64 time=106.312 ms

64 bytes from 192.168.1.55: icmp_seq=11 ttl=64 time=27.967 ms

64 bytes from 192.168.1.55: icmp_seq=12 ttl=64 time=255.274 ms

64 bytes from 192.168.1.55: icmp_seq=13 ttl=64 time=175.714 ms

64 bytes from 192.168.1.55: icmp_seq=14 ttl=64 time=95.245 ms

64 bytes from 192.168.1.55: icmp_seq=15 ttl=64 time=16.844 ms

64 bytes from 192.168.1.55: icmp_seq=16 ttl=64 time=6.394 ms

64 bytes from 192.168.1.55: icmp_seq=17 ttl=64 time=165.415 ms

64 bytes from 192.168.1.55: icmp_seq=18 ttl=64 time=93.959 ms

0 0 1 192 1098 100%HILDE 9 2 1288 14.0 Normal 0 false false false EN-US JA X-NONE

64 bytes from 192.168.1.55: icmp_seq=19 ttl=64 time=309.959 ms

With these ping results i don't wonder any longer all is slow given:

Theoretical network limit

rough estimation: rate < (MSS/RTT)*(C/sqrt(Loss)) [ C=1 ] (based on the Mathis et.al. formula)

network limit (MSS 1460 byte, RTT: 200.0 ms, Loss: 10-08 (10-06%)) : 584.00 Mbit/sec.

Bandwidth-delay Product and buffer size

BDP (65 Mbit/sec, 200.0 ms) = 1.62 MByte 

required tcp buffer to reach 65 Mbps with RTT of 200.0 ms >= 1586.9 KByte 

0 0 1 71 407 100%HILDE 3 1 477 14.0 Normal 0 false false false EN-US JA X-NONE

maximum throughput with a TCP window of 64 KByte and RTT of 200.0 ms <= 2.62 Mbit/sec.

Which means on a wifi b/g/n network connected at 65Mbit/sec and 200ms latency you can have 2,62Mbit/s ore 0,3275MB which is really bad

Could others please also see what there ping results to the Jukebox are doing ore do I have a bad unit?

Kind Regards,

Erwin

erwinnw wrote:

Could others please also see what there ping results to the Jukebox are doing ore do I have a bad unit?

Kind Regards,

Erwin

Are you still happy with your Moment?

mbolo01 wrote:

erwinnw wrote:

Could others please also see what there ping results to the Jukebox are doing ore do I have a bad unit?

Kind Regards,

Erwin

Erwinnw - You don't have a bad unit, Jukeboxes are really bad, inconsistent behavior including ping responses. BeoCare had my device replaced and the new behaves the same as the first one I got. Look at my other posts and you may find symptoms you see with yours. I'm discovering new issues each time I use it 🙁

Pinging 192.168.1.109 with 32 bytes of data:

Reply from 192.168.1.109: bytes=32 time=325ms TTL=64

Reply from 192.168.1.109: bytes=32 time=726ms TTL=64

Reply from 192.168.1.109: bytes=32 time=3ms TTL=64

Reply from 192.168.1.109: bytes=32 time=63ms TTL=64

Ping statistics for 192.168.1.109:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 3ms, Maximum = 726ms, Average = 279ms

Just pinged it out of curiousity....... see the results above

Hi Erwin

You can not rely any problems within the ping results you added. 

I suppose you used Mac OsX terminal to ping, with this command: Ping <Target IP Address or Target IP Host Name> 

Windows will, by default, generate the echo request four times and then summarize results. Mac OsX runs continually by default. By adding the -c 4 option, you can make a ping under OsX behave as it would under Windows and run four times. So enter  the following command: Ping –c 4 <Target IP Address or Target IP Host Name> and then hit return.

After displaying the detailed results, you will be shown a summary, which is what we really care about. I show you an example of ping results to my Moment. The Soundheart uses the address 192.168.1.7 and the Jukebox 192.168.1.8. Take notice that the Soundheart is hard-wired to the network.

I’m trying now not to be very technical in my explanation and keep it informal.

The most important is packet loss, you want that number always to be zero. If it isn’t then either your network is undergoing a momentary and severe stress, or it is engineered incorrectly. If “loss” is non-zero, you are probably already noticed problems before with the Moment . Non-zero loss always requires further monitoring and likely action.

The goal is to have consistently low latency on a network, and ping will tell you how long it took for each echo to traverse the network i.e., make the round trip. The statistics in the summary will show how consistent the latency is. If you start seeing large swings in the ping response time, that is not good. That variation in latency is known as jitter. Could this be of any problem to the Moment, no, but it could be for latency-sensitive, real-time applications like VOIP. Temporary fluctuations in round-trip time can also just indicate a busy, in my case wireless network.

Hi Chris,

I am aware how to ping on a Mac, I always use sudo ping -i .1 where .1 stands for 100ms which is the best for the Moment. For Mac Gear .2 is a better fit. My Home network is setup with enterprise equipment using v-lans and internal dns and has no issues at all.

After the Jukebox was reset with the paperclip methode (again )the ping results are a way better, see below:

64 bytes from 192.168.1.55: icmp_seq=237 ttl=64 time=4.353 ms

64 bytes from 192.168.1.55: icmp_seq=238 ttl=64 time=2.216 ms

64 bytes from 192.168.1.55: icmp_seq=239 ttl=64 time=2.541 ms

64 bytes from 192.168.1.55: icmp_seq=240 ttl=64 time=2.260 ms

64 bytes from 192.168.1.55: icmp_seq=241 ttl=64 time=2.445 ms

64 bytes from 192.168.1.55: icmp_seq=242 ttl=64 time=2.209 ms

64 bytes from 192.168.1.55: icmp_seq=243 ttl=64 time=2.810 ms

64 bytes from 192.168.1.55: icmp_seq=244 ttl=64 time=9.035 ms

64 bytes from 192.168.1.55: icmp_seq=245 ttl=64 time=5.432 ms

64 bytes from 192.168.1.55: icmp_seq=246 ttl=64 time=2.872 ms

64 bytes from 192.168.1.55: icmp_seq=247 ttl=64 time=2.136 ms

64 bytes from 192.168.1.55: icmp_seq=248 ttl=64 time=2.272 ms

64 bytes from 192.168.1.55: icmp_seq=249 ttl=64 time=2.701 ms

64 bytes from 192.168.1.55: icmp_seq=250 ttl=64 time=2.204 ms

64 bytes from 192.168.1.55: icmp_seq=251 ttl=64 time=4.474 ms

64 bytes from 192.168.1.55: icmp_seq=252 ttl=64 time=18.424 ms

^C

--- 192.168.1.55 ping statistics ---

253 packets transmitted, 253 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 2.020/7.454/116.897/24.684 ms

And to show the results to other gear on the network (to machine on WIFI 5Ghz):

64 bytes from 192.168.1.10: icmp_seq=37 ttl=64 time=1.460 ms

64 bytes from 192.168.1.10: icmp_seq=38 ttl=64 time=1.674 ms

64 bytes from 192.168.1.10: icmp_seq=39 ttl=64 time=1.419 ms

64 bytes from 192.168.1.10: icmp_seq=40 ttl=64 time=1.531 ms

64 bytes from 192.168.1.10: icmp_seq=41 ttl=64 time=1.427 ms

64 bytes from 192.168.1.10: icmp_seq=42 ttl=64 time=1.504 ms

Ore to a machine on a kabel connection:

64 bytes from 192.168.1.11: icmp_seq=7 ttl=255 time=0.291 ms

64 bytes from 192.168.1.11: icmp_seq=8 ttl=255 time=0.365 ms

64 bytes from 192.168.1.11: icmp_seq=9 ttl=255 time=0.298 ms

64 bytes from 192.168.1.11: icmp_seq=10 ttl=255 time=0.295 ms

Hope you see the difference. In my opinion the wireless driver on the Jukebox has an issue which get worse as longer the Jukebox is online have seen this behaviour before on wireless products from USI (Universal Scientific Industrial where the wireless stack from the Jukebox comes from) The Soundhart has no issues on the wireless but that part comes from Texas Instruments,

Hope you are with me that the Jukebox has an issue being slow and in my opinion it could be network related. Also don't understand that Bang & Olufsen has selected the 2,4 Ghz JUNK band for their HIGH END sound system.

And of course we all know that a new product can have an issue, but meanwhile the product is on the market 9 months and I don't have the feeling the guys in Struer have the answer to all the problems the Moment is plagued with. And yes I am a real dedicated Bang & Olufsen Fan Boy since my youth but also realistic, ore maybe not, given if  this product would be from an other vendor I would have returned it already

Regards,

Erwin

hi,

I have cut out of the music problem with my moment.

first i think it was problem with my NAS (but the soundheart is linked with cat6 to my router and my NAS too) and sometimes with deezer.

But today i use my bluray player with the line in of the moment and I have some cut out of the sound (more in action scene when there is music, explosion...lot of sound i thunk) so what is the problem, the moment entry, moment speaker out, moment sound processing or my speaker?????

have you the same issue???

thanks