Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[RolandG]

New firmware 3.3. Problems with JRiver allegedly fixed.  I haven't had time to test it yet.

http://support.auralic.com/hc/en-us/articles/206579677-Current-Firmware-Version-3-3-Build-20160418

Current Firmware Version 3.3 Build 20160418

About This Release:

18th April, 2016
This update will request reboot of device after the download is done.
Devices with firmware from Version 1.8.2 and earlier will need to update the boot code after reboot. There will be a message displayed on device warning people to not to power off the unit during this stage. The updating of boot code will take about 70 - 80 seconds. The unit will reboot after boot code has been updated.

Please make sure you do not reboot or turn off the unit during the update of boot code, or else the unit will no longer be able to boot up (will have to return to factory for flashing the boot code).

Fixes:

uPnP Renderer mode wont work with JRiver Media Center 21
Improvement:

Bump kernel version to 4.1.18
Sound quality imporvement
Known Issues:

Device will wait at 176.4K or 352.8K rather than DSD64 or DSD128 when DAC Delay function is enabled.
Device may not work with particular type of USB drive in Mac OS X journaled format.
Device may not work with particular type of USB drive or SSD drive which request power over 5V/500mA.
USB DACs running on Wavelength USB firmware can not use USB playback function due to a confirmed bug of Wavelength USB firmware under Linux. The known effected brands are: Ayre, Aesthetix and Berkeley Audio.
Disable "DSD over PCM" only works on USB DACs that support sampling rate to 352.8K.
Certain kinds of 24bit AIF files will be reported as 32bit due to decoder bug.

[AndrewFG]

Just for info..

There is a new version of the DMR Analyzer in my sig, which adds some specific diagnostics for finding for problems like those encountered on the older version of the Auralic.

So it would be good if you can post here the new DMRA renderer report for this new Auralic version...

[paul45]

New firmware 3.3. Problems with JRiver allegedly fixed.  I haven't had time to test it yet.

It's working!  Very pleased... in MC v21 tracks advance and playlists repeat.  I have now uninstalled MC v20 (strangely the Aries wasn't showing up in there anymore, but who cares).

Andrew - I tried your updated DMR Analyser and it reports "no media renderers found". 

[paul45]

Just for info..

There is a new version of the DMR Analyzer in my sig, which adds some specific diagnostics for finding for problems like those encountered on the older version of the Auralic.

So it would be good if you can post here the new DMRA renderer report for this new Auralic version...

Also adding to above, I can say that NOTHING shows up in the Analyzer.  Using this other program I can see devices (Dining Room UPnP is the Aries btw).

[AndrewFG]

Hmm. Could you please try again, but this time with "Use Windows Discovery" box checked? It's on the top right of the screen..

[paul45]

Hmm. Could you please try again, but this time with "Use Windows Discovery" box checked? It's on the top right of the screen..

That enabled it to see my Sonos and MC, but not the Aries.

[AndrewFG]

Hmm. It seems that there is still something odd with the Aries then...

[sg60]

I just updated the firmware on my Auralic Aries and so far it seems to be working properly. I've also run the DMR Analyzer and I'm attaching the Render Report and the HTTP log file.

[AndrewFG]

^

Hi. Thank you for the reports.

It looks certainly a lot better. However there are still a few errors where the Aries is still non compliant to the UPnP norms.

1) It uses apostrophe signs ' (aka ') instead of quote signs " (aka ") in many of its XML attributes.

The XML specification only allows quote signs.

<?xml version="1.0"?>
<e:propertyset xmlns:e="urn:schemas-upnp-org:event-1-0">
<e:property>
<LastChange>
<Event xmlns='urn:schemas-upnp-org:metadata-1-0/RCS'>
<InstanceID val='0'>
<Mute channel="Master" val="1"/>
<Volume val="0" channel="Master"/>
</InstanceID>
</Event>
</LastChange>
</e:property>
</e:propertyset>

2) It accepts event subscriptions for a Timeout of 10 seconds only.

The analyzer requests for a Timeout of 300 seconds (5 minutes). The renderer only accepts it for 10 seconds. Ten seconds is a totally useless Timeout, since it barely gives any time for the initial event to be sent, before the subscription times out again. Ten seconds is not even the duration of a normal music track. => Auralic must extend the Timeout value to whatever value the Subscriber demands, or to at least 300 seconds. This is the UPnP specification.

10:29:17.908 Client Connected.
SUBSCRIBE /lightningRender-bc-34-00-a0-04-de/upnp.org-AVTransport-1/event HTTP/1.1
Connection: close
Date: Wed, 20 Apr 2016 16:29:17 GMT
NT: upnp:event
TIMEOUT: Second-300
CALLBACK: <http://192.168.1.69:31415/event/avt>
Host: 192.168.1.122:40678
Accept-Encoding: identity
User-Agent: Whitebear/1.0, UPnP/1.0, RendererAnalyser/1.0

HTTP/1.1 200 OK
SERVER: Posix/200809.0 UPnP/1.1 ohNet/1.0
SID: uuid:lightningRender-bc-34-00-a0-04-de-24
TIMEOUT: Second-10
Connection: close

10:29:17.908 Client Disconnected.
10:29:17.908 Client Warning: Subscription Timeout Too Short.

3) It uses Chunked encoding on SOAP responses.

This is very odd, and asking for trouble.

10:29:18.133 Client Connected.
POST /lightningRender-bc-34-00-a0-04-de/upnp.org-AVTransport-1/control HTTP/1.1
Connection: close
Content-Type: text/xml; charset=utf-8
Content-Length: 430
Date: Wed, 20 Apr 2016 16:29:18 GMT
SOAPACTION: "urn:schemas-upnp-org:service:AVTransport:1#GetTransportInfo"
Host: 192.168.1.122:40678
Accept: text/xml
Accept-Encoding: identity
User-Agent: Whitebear/1.0, UPnP/1.0, RendererAnalyser/1.0

... cut ...

HTTP/1.1 200 OK
Ext:
Content-Type: text/xml; charset="utf-8"
SERVER: Posix/200809.0 UPnP/1.1 ohNet/1.0
Transfer-Encoding: chunked
Connection: close

1b7
<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:GetTransportInfoResponse xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"><CurrentTransportState>STOPPED</CurrentTransportState><CurrentTransportStatus>OK</CurrentTransportStatus><CurrentSpeed>0</CurrentSpeed></u:GetTransportInfoResponse></s:Body></s:Envelope>
0


10:29:18.138 Client Disconnected.
10:29:18.138 Client Succeeded: HTTP 200 OK.