Not getting the Full Channel list.

[BrainStormer]

XBMC Only gets the first 100 channel is the lineup.
I tried on the Latest Nightly for Windows, RaspBMC and android.

In the intel Device Validator it doens't pass all the tests. perhaps this is where the error occurs:

Code: Select all

    <LogEntry importance="Error">"Browse Filter" terminating early. Reason =&gt; "Browse Filter" is terminating early because Browse("CableTV/v2", BROWSEMETADATA, "@protocolInfo", 0, 0, "") returned a media object (ID='CableTV/v2') with no resources DIDL-Lite when it should have returned at least 1 res objects. DIDL-Lite ==&gt; &lt;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/"&gt;&lt;item id="CableTV/v2" parentID="CableTV" restricted="1"&gt;&lt;dc:title&gt;2 TVGUIDE west&lt;/dc:title&gt;&lt;upnp:class&gt;object.item.videoItem.videoBroadcast&lt;/upnp:class&gt;&lt;/item&gt;&lt;/DIDL-Lite&gt;</LogEntry>

[BrainStormer]

Also Device Discovery seems to have a bug.

WARNING: Device not choosing Random interval based on MX value <<Standard Deviation: 0.4722956>>

[Diverge]

Try power cycling your tuner. That happened to me, was only showing first 10 channels on PS3. Soon as I power cycled they all showed up.

Also, on my initial channel scan from the tuners config program, it missed a couple of channels the 1st time I scanned. I did it again and it got the ones I was missing.

[nickk]

Also Device Discovery seems to have a bug.

WARNING: Device not choosing Random interval based on MX value <<Standard Deviation: 0.4722956>>

The HDHomeRun chooses a random interval based on the MX value compliant with the UPnP and DLNA specifications.

Two packets are sent (as per UPnP requirements).

The first packet is always sent within the first half of the MX value (actual time is random within the first half).
The second packet is always sent withing the second half of the MX value (actual time is random within the second half).
This prevents two packets being sent back-to-back at the end of the MX time due to the random delays chosen.

Nick

[BrainStormer]

Try power cycling your tuner. That happened to me, was only showing first 10 channels on PS3. Soon as I power cycled they all showed up.

Also, on my initial channel scan from the tuners config program, it missed a couple of channels the 1st time I scanned. I did it again and it got the ones I was missing.

Weired I had tried rebooting it several times yesterday. and it worked today...

[member]

I had the same issue - at about 1:30am I called it quits and went to bed. In the morning all was fine. Next step is chan logos + guide. any ideas?

[BrainStormer]

Try the Satuday morning paper

I guess the next step is to add support for the channel metadata.

[nickk]

Try the Satuday morning paper

I guess the next step is to add support for the channel metadata.

Reporting channel metadata is supported by the HDHomeRun Prime.

The issue here looks to be that the UPnP client is requesting a filter containing only one requested element, and the HDHomeRun does not have that element listed as valid. If the filter was set to "*" or "res" or other expected filter string/list you would get the metadata you expect. We will double-check the UPnP and DLNA specifications and report back.

Nick

[member]

Try the Satuday morning paper

I guess the next step is to add support for the channel metadata.

Reporting channel metadata is supported by the HDHomeRun Prime.

The issue here looks to be that the UPnP client is requesting a filter containing only one requested element, and the HDHomeRun does not have that element listed as valid. If the filter was set to "*" or "res" or other expected filter string/list you would get the metadata you expect. We will double-check the UPnP and DLNA specifications and report back.

Nick

Nick - is there any chance I could scrape the metadata from schedulesdirect? I find their metadata more comprehensive.

[mborland]

Wondering if the thread>
Devices cannot see all the channels in playlist
belongs here instead?

[nickk]

I guess the next step is to add support for the channel metadata.

Reporting channel metadata is supported by the HDHomeRun Prime.

The issue here looks to be that the UPnP client is requesting a filter containing only one requested element, and the HDHomeRun does not have that element listed as valid. If the filter was set to "*" or "res" or other expected filter string/list you would get the metadata you expect. We will double-check the UPnP and DLNA specifications and report back.

My reading of the UPnP ContentDirectory specification is that @protocolInfo is an invalid filter because protocolInfo is not a property of the container/item but a property of res. The tool should be requesting res@protocolInfo.

Nick