HD Homerun Dual Legacy channels not appearing in client Channel Collections

I've had this issue for some time but haven't taken the time to write about it here. I have a very old HD Homerun Dual Legacy (the old beige model) whose channels do not show up in Channel Collections on any of my clients.

I can add channels from that source to a channel collection on the server interface and they show in the guide on the server interface. However, for some reason the channels do not show up in the guide on any of my Apple TV clients (or iPad) when filtering to that collection. The channels show up fine on those clients when All Channels is active.

Here are the channels added to the Channel Collection in the server interface:

Here are the channels showing up fine in the guide's Channel Collection:

But the channels are not being shown in any of my client's Channel Collection:

I don't have any special client settings made in the server interface, and all of my other custom Channel collections for my Quad Flex tuner and TVE sources work fine on the clients.

Thanks in advance for your help!
Tim

This is a known issue with that model.

That model does not provide the same information to clients as the rest of the models. Channel Collections is just one thing it doesn’t work in.

It’s an extremely legacy device that only sort of works in Channels.

We don’t exclude it from being a tuner because it does work, it we don’t technically support it because of these things.

Thanks for confirming! That sames me time beating my head against the wall trying to remedy this.

I tried a clunky workaround thanks to the flexibiity built into Channels by making a Custom channel source referencing the Dual's channels from the Channels m3u. Adding those channels from the custom source now show up in the channel collection but now they are transcoded to play on the client (not ideal).

This is really the only drawback from the old Dual that impacts me, so I'll take it. The tuners built into it are stronger than the ones in the Flex (but maybe that's due to only splitting the incoming signal twice instead of four times).

Thanks again for the quick reply!
Tim

It doesn’t have to transcode.

Read up on the docs:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.