Post Reply 
MinimServer SLOW!
06-01-2015, 13:53
Post: #11
RE: MinimServer SLOW!
Most issues with the ARIES not playing steadily are network related. If you can hardwire the ARIES this is a a great test to see if it's the WIFI network or not. Even if it take a 100' Ethernet wire to try it could save you a lot of hassle. Sometimes just a better router is needed.
Find all posts by this user
Quote this message in a reply
06-01-2015, 14:05 (This post was last modified: 06-01-2015 14:06 by simoncn.)
Post: #12
RE: MinimServer SLOW!
(06-01-2015 13:11)promao Wrote:  Dear Simon,

Yes, I did did stop the music playing before you changed the logging level back to Info.

I may have a clue: Could this abnormal behavior be consistent to a fault in the wifi network? I have an older Airport Extreme on the living room (where system resides) connecting wirelessly to an Apple Time Capsule on a more distant location. Apparently all devices, iPad included (controlling the DS application of Aries) are in fact only connecting to the distant Time Capsule and not to this Airport Extreme, for some reason.

Could this mean that the delay occurs on the transmission the command on the iPad DS application that only reaches the server with that delay? The delay in seconds on the music was much more than 6 seconds.

Sorry if this may seem a silly question...

Many Thanks.

Pedro

Working backwards, if you stopped the music at 22:15:47.464 and the delay was much more than 6 seconds, it seems there was a long delay between the iPad sending the Play command and Minimserver receiving the HTTP GET request to play the music.

To confirm this, you can repeat the test but modify it slightly, as follows:

1) Browse to a test track that shows the problem but don't play it yet
2) From the minim icon, select 'Show log'
3) In the log window, change the logging level from Info to Debug
4) In the log window, click Clear to clear the log window
5) Leave the log window open

Now play the test track while you are watching the log window. As soon as you select Play, you should see these messages:

Code:
22:15:44.116 Thread-39: HTTPService: accepted incoming connection
22:15:44.116 Thread-39: HTTPService: waiting for incoming connection
22:15:44.117 Thread-38: HTTPService: received request, Socket[addr=/192.168.1.68,port=56211,localport=9790]
22:15:44.117 Thread-38: HTTPService: adding connection org.jminim.lib.HTTPConnection@1752b9e
22:15:44.118 Thread-3614: HTTPConnection: writer thread waiting for request
22:15:44.118 Thread-3615: HTTPConnection: reading HTTP request
22:15:44.119 Thread-3615: GET /minimserver/*/music/John*20Lurie/African*20Swim*20and*20Manny*20*26*20Lo*20-*20Two*20Film*20Scores*20By*20John*20Lurie/01*20Main*20Titles.aif HTTP/1.1
22:15:44.119 Thread-3615: User-Agent: Music Player Daemon 0.18.5, Host: 192.168.1.252:9790, Accept: */*, Icy-Metadata: 1

If there is a long delay before you see these messages, it means the transmission of the Play command is being delayed by the network.
Find all posts by this user
Quote this message in a reply
06-01-2015, 14:14 (This post was last modified: 06-01-2015 14:14 by jtwrace.)
Post: #13
RE: MinimServer SLOW!
One other thing to look at is to make sure that the setting for the dac delay within DS Lightning (Control Point App) doesn't have a delay set.

Simon - I'm not trying to make it harder for you but just trying to help on the ARIES side. :-)


Attached File(s) Thumbnail(s)
   
Find all posts by this user
Quote this message in a reply
06-01-2015, 15:08
Post: #14
RE: MinimServer SLOW!
Thanks for helping. Unfortunately no delay set and the Aries is hardwired.

Pedro

(06-01-2015 14:14)jtwrace Wrote:  One other thing to look at is to make sure that the setting for the dac delay within DS Lightning (Control Point App) doesn't have a delay set.

Simon - I'm not trying to make it harder for you but just trying to help on the ARIES side. :-)
Find all posts by this user
Quote this message in a reply
06-01-2015, 15:23
Post: #15
RE: MinimServer SLOW!
Hi Simon.

39 seconds after I pressed play on the iPad the message appears. Music starts immediately.

So after all its network related... Right?

As I am used to spinning vinyl this is the time it takes to pick a record from the shelf and start playing it, but I am looking to optimize it.

Thanks for making clear what the problem was (is).

Pedro


(06-01-2015 14:05)simoncn Wrote:  
(06-01-2015 13:11)promao Wrote:  Dear Simon,

Yes, I did did stop the music playing before you changed the logging level back to Info.

I may have a clue: Could this abnormal behavior be consistent to a fault in the wifi network? I have an older Airport Extreme on the living room (where system resides) connecting wirelessly to an Apple Time Capsule on a more distant location. Apparently all devices, iPad included (controlling the DS application of Aries) are in fact only connecting to the distant Time Capsule and not to this Airport Extreme, for some reason.

Could this mean that the delay occurs on the transmission the command on the iPad DS application that only reaches the server with that delay? The delay in seconds on the music was much more than 6 seconds.

Sorry if this may seem a silly question...

Many Thanks.

Pedro

Working backwards, if you stopped the music at 22:15:47.464 and the delay was much more than 6 seconds, it seems there was a long delay between the iPad sending the Play command and Minimserver receiving the HTTP GET request to play the music.

To confirm this, you can repeat the test but modify it slightly, as follows:

1) Browse to a test track that shows the problem but don't play it yet
2) From the minim icon, select 'Show log'
3) In the log window, change the logging level from Info to Debug
4) In the log window, click Clear to clear the log window
5) Leave the log window open

Now play the test track while you are watching the log window. As soon as you select Play, you should see these messages:

Code:
22:15:44.116 Thread-39: HTTPService: accepted incoming connection
22:15:44.116 Thread-39: HTTPService: waiting for incoming connection
22:15:44.117 Thread-38: HTTPService: received request, Socket[addr=/192.168.1.68,port=56211,localport=9790]
22:15:44.117 Thread-38: HTTPService: adding connection org.jminim.lib.HTTPConnection@1752b9e
22:15:44.118 Thread-3614: HTTPConnection: writer thread waiting for request
22:15:44.118 Thread-3615: HTTPConnection: reading HTTP request
22:15:44.119 Thread-3615: GET /minimserver/*/music/John*20Lurie/African*20Swim*20and*20Manny*20*26*20Lo*20-*20Two*20Film*20Scores*20By*20John*20Lurie/01*20Main*20Titles.aif HTTP/1.1
22:15:44.119 Thread-3615: User-Agent: Music Player Daemon 0.18.5, Host: 192.168.1.252:9790, Accept: */*, Icy-Metadata: 1

If there is a long delay before you see these messages, it means the transmission of the Play command is being delayed by the network.
Find all posts by this user
Quote this message in a reply
06-01-2015, 16:28
Post: #16
RE: MinimServer SLOW!
(06-01-2015 15:23)promao Wrote:  Hi Simon.

39 seconds after I pressed play on the iPad the message appears. Music starts immediately.

So after all its network related... Right?

As I am used to spinning vinyl this is the time it takes to pick a record from the shelf and start playing it, but I am looking to optimize it.

Thanks for making clear what the problem was (is).

Pedro

It seems like it, but I don't understand why doesn't this happen with the Synology media server as well. If it's network related, it should take just as long for the Synology media server to receive a Play request.

Do you by any chance have a VPN server running on the NAS? This could possibly cause a problem like this. If so, please try disabling the VPN server and try again.
Find all posts by this user
Quote this message in a reply
07-01-2015, 01:54
Post: #17
RE: MinimServer SLOW!
I was questioning the same regarding the Sinology app. No, no VPN server running... Any other ideas?

(06-01-2015 16:28)simoncn Wrote:  
(06-01-2015 15:23)promao Wrote:  Hi Simon.

39 seconds after I pressed play on the iPad the message appears. Music starts immediately.

So after all its network related... Right?

As I am used to spinning vinyl this is the time it takes to pick a record from the shelf and start playing it, but I am looking to optimize it.

Thanks for making clear what the problem was (is).

Pedro

It seems like it, but I don't understand why doesn't this happen with the Synology media server as well. If it's network related, it should take just as long for the Synology media server to receive a Play request.

Do you by any chance have a VPN server running on the NAS? This could possibly cause a problem like this. If so, please try disabling the VPN server and try again.
Find all posts by this user
Quote this message in a reply
07-01-2015, 01:55
Post: #18
RE: MinimServer SLOW!
Do you have the NAS set to hibernate after a certain amount of time?
Find all posts by this user
Quote this message in a reply
07-01-2015, 09:48
Post: #19
RE: MinimServer SLOW!
Folks,

Thanks for all the help. We have been searching in the wrong direction, I think.

Before splashing money on a new airport extreme I tried, out of curiosity, the Linn Kinsky app, instead of the Auralic one /DS Lightning.

Kinky does not show this abnormal situation, Auralic Aries starts to play the music immediately as soon as I select it on Kinsky.

So, it's app related, at least partially. To sum up:

- With DS Lightning and Sinology server all OK (Except that MinimServer is way better);
- With DS Lightning and MinimServer there is a 30 second gap between selecting a music and it starting to play;
- With Kinsky and MinimServer server all OK.

Go figure.

Thanks again for all help, I am using Kinsky (although I like DS Lightning better) until this is fixed.

Small glitch from Auralic's app possibly but it does not detract from the great quality of their gear and the excellent support, I am sure that if this is App related as it seems to be, they will figure it out very quickly.

I will post the developments in case anyone is out there with same problem.

Thanks again for all the help.

Pedro

(07-01-2015 01:54)promao Wrote:  I was questioning the same regarding the Sinology app. No, no VPN server running... Any other ideas?

(06-01-2015 16:28)simoncn Wrote:  
(06-01-2015 15:23)promao Wrote:  Hi Simon.

39 seconds after I pressed play on the iPad the message appears. Music starts immediately.

So after all its network related... Right?

As I am used to spinning vinyl this is the time it takes to pick a record from the shelf and start playing it, but I am looking to optimize it.

Thanks for making clear what the problem was (is).

Pedro

It seems like it, but I don't understand why doesn't this happen with the Synology media server as well. If it's network related, it should take just as long for the Synology media server to receive a Play request.

Do you by any chance have a VPN server running on the NAS? This could possibly cause a problem like this. If so, please try disabling the VPN server and try again.
Find all posts by this user
Quote this message in a reply
07-01-2015, 10:13
Post: #20
RE: MinimServer SLOW!
(07-01-2015 09:48)promao Wrote:  Folks,

Thanks for all the help. We have been searching in the wrong direction, I think.

Before splashing money on a new airport extreme I tried, out of curiosity, the Linn Kinsky app, instead of the Auralic one /DS Lightning.

Kinky does not show this abnormal situation, Auralic Aries starts to play the music immediately as soon as I select it on Kinsky.

So, it's app related, at least partially. To sum up:

- With DS Lightning and Sinology server all OK (Except that MinimServer is way better);
- With DS Lightning and MinimServer there is a 30 second gap between selecting a music and it starting to play;
- With Kinsky and MinimServer server all OK.

Go figure.

Thanks again for all help, I am using Kinsky (although I like DS Lightning better) until this is fixed.

Small glitch from Auralic's app possibly but it does not detract from the great quality of their gear and the excellent support, I am sure that if this is App related as it seems to be, they will figure it out very quickly.

I will post the developments in case anyone is out there with same problem.

Thanks again for all the help.

Pedro

Thanks for this information. I hope Auralic will be able to find and fix the problem.

It might be that the Lightning DS app is sending incorrect XML to MinimServer and the ohNet stack (used by MinimServer) is rejecting it with an error response. This wouldn't show up in the MinimServer log window because the faulty request isn't passed to MinimServer by ohNet. The Synology server might not be checking the XML as strictly as ohNet does, so the problem doesn't occur.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)