UPnP search on 'Album Artist' ?

[CraigD]

I'm developing a Qt5 open-home control point. As part of this, I want to be able to search for tracks in the media server – i.e. minimserver. To obtain the search capabilities of the server, I send a GetSearchCapabilities request. Minimserver responds with:

Code:

upnp:class,dc:title,dc:creator,upnp:artist,upnp:album,upnp:genre,dc:date,@refID,​upnp:artist[@role="Composer"],upnp:artist[@role="AlbumArtist"]

When searching for tracks I use all the returned capabilities. If I want to search for 'abba' I send the following XML to minim:

Code:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<s:Body>
<u:Search xmlns:u="urn:schemas-upnp-org:service:ContentDirectory:1">
<ContainerID>0</ContainerID>
<SearchCriteria>(upnp:class = &quot;object.item.audioItem.musicTrack&quot; and (dc:title contains &quot;abba&quot; or dc:creator contains &quot;abba&quot; or upnp:artist contains &quot;abba&quot; or upnp:album contains &quot;abba&quot; or upnp:artist[@role=&quot;Composer&quot;] contains &quot;abba&quot; or upnp:artist[@role=&quot;AlbumArtist&quot;] contains &quot;abba&quot;))</SearchCriteria>
<Filter>*</Filter>
<SortCriteria></SortCriteria>
<StartingIndex>0</StartingIndex>
<RequestedCount>100</RequestedCount>
</u:Search></s:Body>
</s:Envelope>

This causes mimim server to fail, with an error logged as:

Code:

MinimServer: exception while processing action request: java.lang.ArrayIndexOutOfBoundsException: 8 (see crash file for stack trace)

If I omit all the search capabilities that contain '[' (e.g. upnp:artist[@role="AlbumArtist"] ) then the search succeeds. However, doing so means I cannot search on 'Album Artist'

How can I perform a search of tracks with a certain 'Album Artist' ?

I've attached the crash file - but I'm not sure it's of any real use.

[simoncn]

Thanks for letting me know about this. I understand what's causing the problem and I am working on a fix.

[simoncn]

(11-04-2016 14:00)simoncn Wrote:  Thanks for letting me know about this. I understand what's causing the problem and I am working on a fix.

This error is now fixed in update 81. Thanks very much for your help with finding this problem.

[CraigD]

Works perfectly now! Thanks for the very quick fix :-)