Problem with AssetUPnP and new Bang and Olufsen app

[nunovi]

Hi,

I'm testing AssetUPnP v5.1.1 running on Linux with the new Bang and Olufsen app and I'm getting some problems. Using the default browse tree, Genres just gets grayed out and when navigating to Artist / Album, it lists the A..Z structure but clicking on any item just gets a "Could not handle the DLNA content". Sames happens to Albums but Composers works fine.

I've been investigating this and here are some of the things I tried:

1. I've tested with other 3 well-known UPnP servers and the app works well with all of them.
2. I have the same problem using AssetUPnP 6 running on Windows so it doesn't look like a Linux specific problem.
3. AssetUPnP works fine with BubbleUPnP as the Control Point so looks some incompatibility between the B&O app and Asset

I've enabled debugging and created a simple Browse Tree. This is the DIDL-Lite response obtained when accessing through the B&O app:

"urn:schemas-dlna-org:metadata-1-0/">

	<container id="co87FDA0703FB7C640" parentID="0" restricted="0" searchable="1">

		<dc:title>Artist</dc:title><dc:creator>Unknown</dc:creator><upnp:artist></upnp:artist><upnp:genre>Unknown</upnp:genre><upnp:albumArtURI dlna:profileID="JPEG_TN">http://192.168.0.16:26125/aa/00041481/userart.jpg</upnp:albumArtURI><upnp:class>object.container.person</upnp:class></container><container id="coC3D9140FB30099A6" parentID="0" restricted="0" searchable="1">


		<dc:title>Album</dc:title><dc:creator>Unknown</dc:creator><upnp:artist></upnp:artist><upnp:genre>Unknown</upnp:genre><upnp:albumArtURI dlna:profileID="JPEG_TN">http://192.168.0.16:26125/aa/0002B06F/userart.jpg</upnp:albumArtURI><upnp:class>object.container.album</upnp:class></container><container id="co7DEC673866E85DF6" parentID="0" restricted="0" searchable="1">


		<dc:title>Genre</dc:title><dc:creator>Unknown</dc:creator><upnp:artist></upnp:artist><upnp:genre>Unknown</upnp:genre><upnp:albumArtURI dlna:profileID="JPEG_TN">http://192.168.0.16:26125/aa/00029B4D/userart.jpg</upnp:albumArtURI><upnp:class>object.container.genre</upnp:class></container><container id="coA6B4BA5B30FCDEB8" parentID="0" restricted="0" searchable="1">



		<dc:title>Composer</dc:title><dc:creator>Unknown</dc:creator><upnp:artist></upnp:artist><upnp:genre>Unknown</upnp:genre><upnp:albumArtURI dlna:profileID="JPEG_TN">http://192.168.0.16:26125/aa/0006ACD8/userart.jpg</upnp:albumArtURI><upnp:class>object.container</upnp:class>

	</container>

</DIDL-Lite>

And this is what I get from another UPnP server that works:

<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/" xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/">

	<container id="0$albums" parentID="0" restricted="1" searchable="1">
		<dc:title>254 albums</dc:title><upnp:userAnnotation>albums</upnp:userAnnotation><upnp:class>object.container</upnp:class>
	</container>
		
	<container id="0$items" parentID="0" restricted="1" searchable="1">
		<dc:title>3064 items</dc:title><upnp:userAnnotation>items</upnp:userAnnotation><upnp:class>object.container </upnp:class>
	</container>
	
	<container id="0$=Artist" parentID="0" restricted="1" searchable="1">
		<dc:title>Artist</dc:title><upnp:class>object.container</upnp:class>
	</container>
	
	<container id="0$=Date" parentID="0" restricted="1" searchable="1">
		<dc:title>Date</dc:title><upnp:class>object.container</upnp:class>
	</container>
	
	<container id="0$=Genre" parentID="0" restricted="1" searchable="1">
		<dc:title>Genre</dc:title><upnp:class>object.container</upnp:class>
	</container>
	
	<container id="0$=All Artists" parentID="0" restricted="1" searchable="1">
		<dc:title>All Artists</dc:title><upnp:class>object.container</upnp:class>
	</container>
	
	<container id="0$=Composer" parentID="0" restricted="1" searchable="1">
		<dc:title>Composer</dc:title><upnp:class>object.container</upnp:class>
	</container>
	
	<container id="0$=Conductor" parentID="0" restricted="1" searchable="1">
		<dc:title>Conductor</dc:title><upnp:class>object.container</upnp:class>
	</container>
	
	<container id="0$=Orchestra" parentID="0" restricted="1" searchable="1">
		<dc:title>Orchestra</dc:title><upnp:class>object.container</upnp:class>
	</container>
	
	<container id="0$folders" parentID="0" restricted="1" searchable="1">
		<dc:title>[folder view]</dc:title><upnp:class>object.container.storageFolder</upnp:class>
	</container>
	
</DIDL-Lite>

They do have quite different structures but what picked my interest was the <upnp:class> tag on the AssetUPnP response. It can be a coincidence but the Composer entry has a object.container entry whereas the Artist, Album and Genre have object.container.person, object.container.album and object.container.genre, respectively. None of those work so I wonder if the app doesn't understand that specialization of the object.container object.

The other UPnP Servers I have tried all return just object.container so that seems to be a more generic way to do it.

If this in fact is confirmed, is there any possibility to have a Control Point override so that the response comes just with object.container rather than the specializations?

Thanks for any help.

Nuno

[Spoon]

Re: Problem with AssetUPnP and new Bang and Olufsen app

>object.container.person

If it does not recognize these, they are fundamentals in UPnP. You will find other mainstream upnp servers give the same so it will not be this.

[umfried]

Re: Problem with AssetUPnP and new Bang and Olufsen app

Nunovi,

I can confirm your findings from a end-user perspective (I am not able to debug). Asset Upnp and the new Bang&Olufsen App (the one availaible since 1.6.2017 and replacing the old Beomusic-App) - in one way or another - do not 100% understand each other yet. I have updated it recently to version 1.03.6915 and still it behaves the same.
Seems there is a long way to go still ;-). Let us stay in contact Nuno and see how we can possibly follow up collaboratively on this. Have you contacted B&O already about this issue?

@Dear Spoon:
Thank you for your swift reply to Nuno's question which is my question too. Just in case you have plans to deep dive into this or need more information. Please let us know. "Asset UPnP Release 6" at my site is running on W10 Pro 1607 BS build 14393.1358, on 64bit with i7 processor and 32GB RAM. (btw. still with those nasty behavior when running multiple instances, but this is already discussed in another thread).

Kind regards
umfried