Post Reply 
Melco MinimServer compatibility issue
12-02-2023, 19:38 (This post was last modified: 12-02-2023 19:39 by simoncn.)
Post: #3
RE: Melco MinimServer compatibility issue
Thanks for uploading the file. I am seeing the same results as you.

I have checked what MinimServer and Twonky are sending to the Melco renderer. The stream contents are identical but there is a difference in the metadata. This file is 88.2 kHz 24-bit and the resource metadata is as follows:

(from MinimServer)

<res duration="0:09:04.694" size="288514558" bitsPerSample="24" bitrate="529200" sampleFrequency="88200" nrAudioChannels="2" protocolInfo="http-get:*:audio/x-aiff:DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01700000000000000000000000000000">http://192.168.0.33:9790/minimserver/*/wiggly/03*20Giorgio*20by*20Moroder.aiff</res>

(from Twonky)

<res size="288514558" sampleFrequency="44100" protocolInfo="http-get:*:audio/x-aiff:*">http://192.168.0.33:9050/disk/NON-DLNA-OP01-FLAGS01700000/O0$1$8I238091.aiff</res>

The most obvious difference is that MinimServer sends the correct sample rate (88200) and bit depth (24) whereas Twonky sends an incorrect sample rate (44100) and no bit depth.

There is also a difference in protocolInfo which might be significant. MinimServer sends some DLNA information in protocolInfo and Twonky doesn't.

Do all the tracks that cause the problem have a sample rate of 88200 and a bit depth of 24?
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Melco MinimServer compatibility issue - simoncn - 12-02-2023 19:38

Forum Jump:


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