curl transfer slower via asset than eg tversity

[zzz1]

We are having a few issues with Asset (v2) running on winxp

We have an embedded linux device and can't get enough throughput for streaming 24/96 WAV content. We can stream the same content from the same winxp machine using several other upnp servers (WMP12, tversity, twonky)

We are doing the following test on our device
. curl <asset audio URL> > /dev/null
. curl <tversity audio URL> > /dev/null

The average download rate we get for Asset is approx 2/3 the rate of Tversity download.

Is this a known issue ? Any ideas why the download speeds are so different ?

[Spoon]

Re: curl transfer slower via asset than eg tversity

Try Asset v3

[zzz1]

Re: curl transfer slower via asset than eg tversity

Upgraded to v3 and still pretty much the same.

Heres what we did. Top one is Tversity. Bottom is Asset. Tversity and Asset both running on same winxp machine.

(tversity)
curl http://192.168.106.57:41952/geturl/0...0%26ext%3d.wav
> /dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 129M 100 129M 0 0 588k 0 0:03:45 0:03:45 --:--:-- 564k

(asset v3)
curl http://192.168.106.57:26125/content/...00/d1-co43.wav > /dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 129M 100 129M 0 0 403k 0 0:05:29 0:05:29 --:--:-- 411k

[Spoon]

Re: curl transfer slower via asset than eg tversity

Try on a PC connected to the network paste the address into Internet explorer:

http://192.168.106.57:26125/content/c2/b24/f96000/d1-co43.wav

And save the file, it should save the file in a matter of seconds (should be 10,000KB a second).

[zzz1]

Re: curl transfer slower via asset than eg tversity

Both tversity and asset are a lot faster when downloading via a linux i386 machine on same network. However they still show that asset is only able to download at approx 70% of the rate of tversity.

I'm not claiming Asset is incapable of streaming 24/96 WAV. Just that for us the speed differential between Asset and Tversity means that we can't currently use Asset for 24/96 WAV streaming.

(tversity)
curl http://192.168.106.57:41952/geturl/0...0%26ext%3d.wav > /dev/null
curl: /usr/local/lib/libcurl.so.4: no version information available (required by curl)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 129M 100 129M 0 0 10.9M 0 0:00:11 0:00:11 --:--:-- 10.8M

(asset)
curl http://192.168.106.57:26125/content/...00/d1-co43.wav > /dev/null
curl: /usr/local/lib/libcurl.so.4: no version information available (required by curl)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 129M 100 129M 0 0 8499k 0 0:00:15 0:00:15 --:--:-- 8221k

[zzz1]

Re: curl transfer slower via asset than eg tversity

and same sort of results with wget on i386 linux

(tversity)
$ wget http://192.168.106.57:41952/geturl/0...0%26ext%3d.wav > /dev/null
--09:48:57-- http://192.168.106.57:41952/geturl/0...0%26ext%3d.wav
=> `02+1%2c000%2c000.wav.wav?type=audio%2fx-wav&url=file%3a%2f%2fc%3a%2fmusic_asset%2fwav%2f&t itle=02+1%2c000%2c000&ext=.wav'
Connecting to 192.168.106.57:41952... connected.
HTTP request sent, awaiting response... 200 OK
Length: 136,068,444 (130M) [audio/x-wav]

100%[================================================== ================================================== ================================================== =============>] 136,068,444 11.02M/s ETA 00:00

(asset)
$ wget http://192.168.106.57:26125/content/...00/d1-co43.wav > /dev/null
--09:49:23-- http://192.168.106.57:26125/content/...00/d1-co43.wav
=> `d1-co43.wav.1'
Connecting to 192.168.106.57:26125... connected.
HTTP request sent, awaiting response... 200 OK
Length: 136,068,444 (130M) [audio/wav]

100%[================================================== ================================================== ================================================== =============>] 136,068,444 8.76M/s ETA 00:00

[Spoon]

Re: curl transfer slower via asset than eg tversity

A 24/96 wave file, 2 channel would be a bit rate of - 576KB a second, Asset is more than 10x faster than required to stream it on i386. What was the device streaming the first one? at 411KB? Tversity only just makes the cut.

[zzz1]

Re: curl transfer slower via asset than eg tversity

Yes, tversity is just good enough on our system.

In theory we might be able to increase our tversity throughput but we estimate the max we'd get is approx 6Mbps. It would be a fairly large effort for us to get to that point and even then we'd probably still be getting approx 4Mbps via Asset which is not enough.

I'm guessing there's no magic tweaking you can do to the Asset http server to get performance in line with Tversity ? If not, we probably lose.

[zzz1]

Re: curl transfer slower via asset than eg tversity

The specific device has not been released yet but I believe the Brand have contacted you direct in relation to this. I think you'll also find the same issue on a Morpheus.

[Spoon]

Re: curl transfer slower via asset than eg tversity

Please drop me an email direct:

http://www.dbpoweramp.com/email.htm

I can test various possible fixes.