cls-nebadje writes

When I add audio to MediaTomb upplay doesn’t seem to refetch the content directory properly. It sends out invalid URLs to the media renderer and MediaTomb of course complains with

2016-04-12 00:17:05   ERROR: Object not found: 125522
2016-04-12 00:49:58   ERROR: Object not found: 125493
...
2016-04-12 00:50:00   ERROR: Object not found: 125558

Furthermore it seems that it doesn’t update the playlist items or browser when the content directory issues an UPnP update event.

Sometimes it helps, when I delete the items from the playlist and re-add 'em. But only if upplay holds valid items within its browser though.

As always let me know if you should require more info.

Regards Uli

medoc92 writes

Hi, and thanks for these detailed reports. I have to work on something else right now, but I’ll come back to them as soon as I can.

Jf

cls-nebadje writes

Hi Jf, don’t worry, we just keep on reporting ;)

medoc92 writes

Thinking of this between 2 things: I can certainly reload directories on update events, but there does not seem to be anything I can do about the playlist if object id and URIs change ! Changing object ids and URis just seem moronic. Actually I think that minidlna does it too and that it’s one of the main reasons why I have settled on minimserver… Do you have any idea about the playlist by any chance ?

cls-nebadje writes

An ID-less solution would be to use the content directory’s item path (Audio/Artist/<album >/<track > instead of its ID or URI to identify an item within a playlist or library. This way the id and URI within an item can change and you don’t have to worry.

medoc92 writes

It seems to me that this would suppose using search for finding the uris when recreating the playlist, and Mediatom has no search…

There is no specification of the tree view presented by a Content Directory, so it’s mostly impossible to walk the tree, for example, by artist, album, title, each server has its way of doing things.

So, as far as I can see, the choice is to invalidate the playlist, or go on and pray and hope. The approach chosen could be a config parameters, with defaults pre-set for some well known servers.

medoc92 writes

The current git version (15th Apr) should at least detect directory update events and propose to reset the browse state. The basic mechanism to process container and system update events is in place, but I’m not too sure what to do with it. I catched a bug in libupnpp while doing this, so you need to update both libupnpp and upplay.