Tweet
Hi,
Is there any way without re-tagging to get Asset to support a custom container? I know it supports custom tags, but that's not exactly what I need.
I've written a proxy to allow Asset to be picked up as WMP on the Sonos controller. To work correctly I have to reconfigure the Asset browse tree, as the Sonos is looking for containers in response to some of its searches and items in response to others further down the search path. Whilst I'm able to reconfigure the tree (and Asset works as WMP on the Sonos controller with full album play etc), that obviously means that other users of Asset within my household (e.g. on the PS3) then also have to suffer the same tree. It would be great if I could create a dummy Sonos container with the tree structure I want inside, and use that for Sonos and the normal tree for everything else. I can create the tree, but I don't want to have to tag every item as Sonos to get them to be returned on browsing - I know that's the right answer, just wondered if there was any alternative, such as creating a dummy root (all the containers within the Sonos container are standard containers)?
One more question - do you intend to make Asset behave as WMP in a future Release (at least as an option), so that the Sonos controller can pick it up directly?
Mark.
Is there any way without re-tagging to get Asset to support a custom container? I know it supports custom tags, but that's not exactly what I need.
I've written a proxy to allow Asset to be picked up as WMP on the Sonos controller. To work correctly I have to reconfigure the Asset browse tree, as the Sonos is looking for containers in response to some of its searches and items in response to others further down the search path. Whilst I'm able to reconfigure the tree (and Asset works as WMP on the Sonos controller with full album play etc), that obviously means that other users of Asset within my household (e.g. on the PS3) then also have to suffer the same tree. It would be great if I could create a dummy Sonos container with the tree structure I want inside, and use that for Sonos and the normal tree for everything else. I can create the tree, but I don't want to have to tag every item as Sonos to get them to be returned on browsing - I know that's the right answer, just wondered if there was any alternative, such as creating a dummy root (all the containers within the Sonos container are standard containers)?
One more question - do you intend to make Asset behave as WMP in a future Release (at least as an option), so that the Sonos controller can pick it up directly?
Mark.
Comment