I would like Wiim pro plus to become JPLAY Certified

[steadyshot]

I would like Wiim pro plus to become JPLAY Certified since I heavily use JPLAY app. Eversolo became recently …

 

[steadyshot]

I was talking specifically about sound quality, because if the benefit comes from reduced network traffic, by using the WHA (and closing it) you have the ultimate solution as there will be no unnecessary network traffic. Try it for yourself you'll be amazed!

I have tried the WHA extensively. I can still discern the difference. The sound quality is still better. However the user experience is vastly better.

 

[Wiimer]

Is this like a Hi-Res certification?

 

[simbun]

I have tried the WHA extensively. I can still discern the difference. The sound quality is still better. However the user experience is vastly better.

The ONLY difference between JPLAY and any other control point (which JPLAY attribute to sound improvement) is reduced polling to the renderer (to get track progress).
If you use the WHA to start a queue then closed the app, there will be no communication between the two at all. JPLAY on the other hand will still need to serve the URL of the next track when requested.

If users are unable to discern the difference between an active or inactive WHA, they will be incapable of perceiving any distinction with JPLAY.

BubbleUPnP can be configured to poll every 10 seconds; if that affects sound quality then there's a fundamental problem with the streamer.

 

[hgo58]

The ONLY difference between JPLAY and any other control point (which JPLAY attribute to sound improvement) is reduced polling to the renderer (to get track progress).
If you use the WHA to start a queue then closed the app, there will be no communication between the two at all. JPLAY on the other hand will still need to serve the URL of the next track when requested.

If users are unable to discern the difference between an active or inactive WHA, they will be incapable of perceiving any distinction with JPLAY.

And even reduced network traffic will have no impact on sound quality. It's simply not how it is working.

 

[onlyoneme]

Why don’t you make an experiment ? Get the free trial of the app and set the update time to 12000 in settings

I will.

 

[steadyshot]

The ONLY difference between JPLAY and any other control point (which JPLAY attribute to sound improvement) is reduced polling to the renderer (to get track progress).
If you use the WHA to start a queue then closed the app, there will be no communication between the two at all. JPLAY on the other hand will still need to serve the URL of the next track when requested.

If users are unable to discern the difference between an active or inactive WHA, they will be incapable of perceiving any distinction with JPLAY.

BubbleUPnP can be configured to poll every 10 seconds; if that affects sound quality then there's a fundamental problem with the streamer.

Right. I have it configured it to poll every 20 minutes. Probably also other technicalities come into play. Not only how frequently it communicates with the streamer. Maybe we can invite the developers of JPLAY ios app and have a QA session.

 

[simbun]

Right. I have it configured it to poll every 20 minutes.

I wonder if that's why you're encountering errors. Have you tried reducing the polling interval?

Probably also other technicalities come into play. Not only how frequently it communicates with the streamer.

It's just the polling, although they have claimed that browsing a media server during playback (not located on the renderer) can also affect sound quality which is why they cache metadata locally.

I'll try and track down a post from their forum.

 

[steadyshot]

I wonder if that's why you're encountering errors. Have you tried reducing the polling interval?



It's just the polling, although they have claimed that browsing a media server during playback (not located on the renderer) can also affect sound quality which is why they cache metadata locally.

I'll try and track down a post from their forum.

No the occasional errors did not increase with that setting. They are the same as they were with the default 10seconds...

It happen when I quickly change tracks to progress to other tracks