I've noticed that the song title is not being received propperly on my Philips Streamium SL5520. Its replaces by the filename. I'm not sure if the streamium device is doing that or mediatomb is sending a wrong fieldname.
I've noticed this behaviour on 0.8.1. If you need more details let me know.
If you want to take a look at this, I'dd really appreciate it.
Thnx,
Andy
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
did you compile MediaTomb with id3lib or taglib support? Only then id3 information is extracted, also,
did you compile with libjs support? If you are browsing PC-Directory then you have the filename titles,
if you are browsing virtual containers - like Audio/All Audio/etc., the titles should be different.
And then of course it's always a possibility that the SL5520 does not like something :)
Let's figure out the questions above and then we will see how we proceed.
Greetings,
Jin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I compiled Mediatomb with id3lib version 3.8.3 , libjs version 1.5 and libextractor 0.5.16.
(along with MySQL and libmagic enabled)
All others values are showing correctly on the SLA5520.
When using Cidero Debug Monitor I see a warning sent by the SLA5520 about wrong metadata, but its not well readable because of the error parsing raw XML bug also appearing in the same text:
I have an idea what might be the problem. As I understand Cidero is executing a UPnP action on your SL5520 device - GetPositionInfo(),
the SL5520 is returning a DIDL-Lite XML.
It seems that they forget to escape the '&' character correctly - we use this character in our URL. So if I understand the whole picture correctly - there is a bug in the SL5520. You could make a quick test to check this. Start with a clean database, then go to the server UI and add an External URL item, use an url which does not contain any ampersands or anything that needs to be escaped in the XML.
If you're into heavy music you could try this one ;) http://www.deadlock.dhs.org/192/Deadlock_Veteran.04.Uznik.mp3
Do not add any other items, then repeat the steps that you did with Cidero - does the problem still occur?
If not - then my theory regarding the SL5520 is probably correct. If the problem still occurs we should continue digging.
We are currently (21:19 CET, 04.01.07) online on chat.freenode.net IRC, in the #mediatomb channel, so you can drop by if you want to do some realtime debugging :>
Greetings,
Jin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I've noticed that the song title is not being received propperly on my Philips Streamium SL5520. Its replaces by the filename. I'm not sure if the streamium device is doing that or mediatomb is sending a wrong fieldname.
I've noticed this behaviour on 0.8.1. If you need more details let me know.
If you want to take a look at this, I'dd really appreciate it.
Thnx,
Andy
Hi,
did you compile MediaTomb with id3lib or taglib support? Only then id3 information is extracted, also,
did you compile with libjs support? If you are browsing PC-Directory then you have the filename titles,
if you are browsing virtual containers - like Audio/All Audio/etc., the titles should be different.
And then of course it's always a possibility that the SL5520 does not like something :)
Let's figure out the questions above and then we will see how we proceed.
Greetings,
Jin
Hi Jin,
I compiled Mediatomb with id3lib version 3.8.3 , libjs version 1.5 and libextractor 0.5.16.
(along with MySQL and libmagic enabled)
All others values are showing correctly on the SLA5520.
When using Cidero Debug Monitor I see a warning sent by the SLA5520 about wrong metadata, but its not well readable because of the error parsing raw XML bug also appearing in the same text:
08:46:23.687 Action: Philips SLA5520: GetPositionInfo Status: WARNING ErrorCode: 712(Bad metadata)
Details:
Action: GetPositionInfo
InArg: InstanceID 0
OutArg: Track 1
OutArg: TrackDuration 0:04:09
OutArg: TrackMetaData
<DIDL-Lite>
<item>
<dc:title>Cry Wolf</dc:title>
<res duration="00:04:09">http://192.168.2.100:50001/content/media?object_id=3678Error parsing XML - Raw XML string:
<DIDL-Lite xmlns="urn:schemas-upnp-org:metadata-1-0/DIDL-Lite" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:upnp="urn:schemas-upnp-org:metadata-1-0/upnp/"><item><dc:title>Cry Wolf</dc:title><res duration="00:04:09">http://192.168.2.100:50001/content/media?object_id=3678&res_id=0</res></item></DIDL-Lite>
OutArg: TrackURI http://192.168.2.100:50001/content/media?object_id=3678&res_id=0
OutArg: RelTime 0:00:04
OutArg: AbsTime 0:00:04
OutArg: RelCount 4000
OutArg: AbsCount 4000
On more thing: I have been running uShare and GMediaserver on the same machine. They do show the title correctly on my SLA5520.
I really appreciate your time spending on this problem.
Thnx,
Andy
I have an idea what might be the problem. As I understand Cidero is executing a UPnP action on your SL5520 device - GetPositionInfo(),
the SL5520 is returning a DIDL-Lite XML.
It seems that they forget to escape the '&' character correctly - we use this character in our URL. So if I understand the whole picture correctly - there is a bug in the SL5520. You could make a quick test to check this. Start with a clean database, then go to the server UI and add an External URL item, use an url which does not contain any ampersands or anything that needs to be escaped in the XML.
If you're into heavy music you could try this one ;)
http://www.deadlock.dhs.org/192/Deadlock_Veteran.04.Uznik.mp3
Do not add any other items, then repeat the steps that you did with Cidero - does the problem still occur?
If not - then my theory regarding the SL5520 is probably correct. If the problem still occurs we should continue digging.
We are currently (21:19 CET, 04.01.07) online on chat.freenode.net IRC, in the #mediatomb channel, so you can drop by if you want to do some realtime debugging :>
Greetings,
Jin