Official moOde 7.0.1 support thread

[Mark Dirac]

Thanks. That worked ...

Why did you suggest that? As a workaround, or because you know of something that has changed in 7.0.1 which might have impacted BubbleUPnP when using UPnP only?

The version of the code used in moOde to provide UPnP renderers was updated in v7, and it now offers both UPnP A/V and OpenHome options, so the moOde interface now lets you choose.  The OpenHome renderer appears to accept an entire playlist where as the A/V one appears to send things one track at a time.

I have found that BubbleUPnP seems to "remember" attributes of renderers even after they vanish or change and so when changing things in moOde I would either need to wait for quite some time, or quit and restart the BubbleUPnP control point (maybe more than once) before it behaved properly.

Many thanks bertrum - that's really crucial news! I had browsed around (release notes & elsewhere) for documentation of some change like this, but without success.

Since efung's experience was so different to mine, here is my config:

First I disabled moOde's UPnP renderer and enabled moOde's DLNA renderer. With this config, BubbleUPnP couldn't see any renderer at all.

Then I tried enabling both the UPnP renderer and the DLNA renderer. And this worked (in terms of playlist advance).