DRM channels being passed to Emby Live TV

[d00zah 127]

Emby Server v3.3.0.0, ServerWMC plugin v1.1.3.1, ServerWMC v1.0.1244.0

 

This is an old issue...

 

Pretty sure I have this configured correctly..

 

~40 Music Choice channels play fine in WMC... Playready, of course.

 

I've configured ServerWMC (I think) to not pass on DRM/copy protected channels to Emby:

 

 

Music Choice channels which are clearly 'Copy Never":

 

 

& obviously won't play in Emby:

 

 

There are also a few other 'Copy Once' channels & all still show up in Emby's Live TV > channels view.

 

Is this a configuration issue? An issue with ServerWMC? An issue with Emby?

 

If logs would help, please let me know which ones & I'll produce a 'clean' set.

Edited February 24, 2018 by d00zah

[krustyreturns 191]

Not sure what is going, but its definitively not an Emby issue.  It might be a an issue with serverwmc not checking DRM correctly for audio-only channels.  If you want me to see what's going on, you can set "Debug_ChannelDetail" to true in the serverwmc settings then  restart serverwmc and post the resulting log after it starts up.  Also tell me the channels to look at in the log.  

 

The other way to fix it right now, is just filter these channels manually in in serverwmc so they are never sent to emby.

[d00zah 127]

Thanks for responding!

 

Music Choice Channels 903 - 948 are all definitely 'Copy Never' like the screen cap above. There were a couple of 'Copy Once' channels in the line-up, but I don't have time to tune each & check the Ceton UI right now.

 

Update:

 

656-658 (the 'plexes)

812 (Sundance)

818,822-4 (religion)

835-7 (the CSPANs)

840-1 (sports)

 

also report 'One Copy' while playing based on a quick scan

             

 

Requested log:

Edited February 25, 2018 by d00zah

[krustyreturns 191]

IMPORTANT:

I forgot to mention: set the Debug_ChannelDetail setting back to false or your swmc logs will be much longer then they need to be.

 

All the DRM detection is failing according to your log, so that is why you have the problem.  I'm not sure why its failing, but one strange thing about your log is wmc is reporting six tuners with no devices attached to them (in addition to your actual tuners).  See this part of the log:

 

2018/02/25 12:40:03.318 EnumerateRecorders> Tuner Devices and TuningSpaces found:

2018/02/25 12:40:03.321 EnumerateRecorders> ContentRecorder: 0

2018/02/25 12:40:03.326 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2018/02/25 12:40:03.326 EnumerateRecorders> ContentRecorder: 1

2018/02/25 12:40:03.327 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2018/02/25 12:40:03.327 EnumerateRecorders> ContentRecorder: 2

2018/02/25 12:40:03.327 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2018/02/25 12:40:03.327 EnumerateRecorders> ContentRecorder: 3

2018/02/25 12:40:03.327 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2018/02/25 12:40:03.327 EnumerateRecorders> ContentRecorder: 4

2018/02/25 12:40:03.327 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2018/02/25 12:40:03.327 EnumerateRecorders> ContentRecorder: 5

2018/02/25 12:40:03.327 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2018/02/25 12:40:03.327 EnumerateRecorders> ContentRecorder: 6

 

So I am just guessing, but I assume its due to this that DRM detection is not working.  This problem is probably due to something in your wmc setup history and it would likely go away if you reconfigure wmc - but I don't recommend doing that.

 

I suggest just setting wmc to ignore these channels.  The easiest way to do that is to define a master channel group in the settings file.  Here are instructions:

 

    A group can be designated as the master channel group by naming the group _MasterChannelGroup_. 

    Look for XmlDefinedChannelGroups example.  Here is an additional example with comments:

 

<XmlDefinedChannelGroups>

 

    <XmlDefinedChannelGroup>

 

      <Name>My Channel Group</Name>    <!-- the name of the channel group;  using the name "_MasterChannelGroup_" will use this group as the master channel list -->

 

      <IncludeChannelNumbers>645, 700-800, 837, 891</IncludeChannelNumbers>  <!-- include these channels ranges and numbers, leaving this blank will include all channels -->

 

      <IncludeChannelCallSigns>msNBC, CNN</IncludeChannelCallSigns>  <!-- include channels with these call signs -->

      <ExcludeChannelNumbers>720-725, 715</ExcludeChannelNumbers>  <!-- exclude these channel ranges and numbers -->

      <ExcludeChannelCallSigns>TBNHD, FNCHD</ExcludeChannelCallSigns>  <!-- call signs to exclude -->

      <HDOnly>true</HDOnly>  <!-- include only channels flagged as HD capable -->

 

      <SDOnly>false</SDOnly>  <!-- include only channels that are SD only -->

 

      <IncludeTheseLanguagesOnly>en, es</IncludeTheseLanguagesOnly> <!-- only include channels that have programming in these languages -->

 

    </XmlDefinedChannelGroup>

 

  </XmlDefinedChannelGroups>

Edited February 25, 2018 by krustyreturns

[d00zah 127]

IMPORTANT:

I forgot to mention: set the Debug_ChannelDetail setting back to false or your swmc logs will be much longer then they need to be.

 

Thanks for the warning, I had assumed & already done that. B^)

 

All the DRM detection is failing according to your log, so that is why you have the problem.  I'm not sure why its failing, but one strange thing about your log is wmc is reporting six tuners with no devices attached to them (in addition to your actual tuners).  See this part of the log:

 

Odd. Just started fresh w/ EPG123 not too long ago, including clearing all tuner history via Ceton Diags. No good answer here.

 

All that said, based on the instructions, I came up with this in the config:

 

-- begin  snip --

  <EnableXmlChannelGroups>true</EnableXmlChannelGroups>

  <XmlDefinedChannelGroups>

    <XmlDefinedChannelGroup>

      <Name>_MasterChannelGroup_</Name>

      <ExcludeChannelCallSigns>CSPANHD, CSPN2HD, CSPN3HD, EWTNHD, INDIEHD, INSPHD, MC01, MC02, MC03, MC04, MC05, MC06,

 

MC07, MC08, MC09, MC10, MC11, MC12, MC13, MC14, MC15, MC16, MC17, MC18, MC19, MC20, MC21, MC22, MC23, MC24, MC25,

 

MC26, MC27, MC28, MC29, MC30, MC31, MC32, MC33, MC34, MC35, MC36, MC37, MC38, MC39, MC40, MC40, MC41, MC42, MC43,

 

MC44, MC45, MC46, MC47, MC48, MC49, MC50, MPLEXHD, RETROHD, SUNDHD, TBNHD, SECAHD, SECH</ExcludeChannelCallSigns>

    </XmlDefinedChannelGroup>

    <XmlDefinedChannelGroup>

      <Name>DummyName</Name>

      <IncludeChannelNumbers>645, 700-800, 837</IncludeChannelNumbers>

      <IncludeChannelCallSigns>msNBC, CNN</IncludeChannelCallSigns>

      <ExcludeChannelNumbers>720-725, 715</ExcludeChannelNumbers>

      <ExcludeChannelCallSigns>TBNHD, FNCHD</ExcludeChannelCallSigns>

      <HDOnly>true</HDOnly>

      <SDOnly>false</SDOnly>

      <IncludeTheseLanguagesOnly>en, fr</IncludeTheseLanguagesOnly>

    </XmlDefinedChannelGroup>

  </XmlDefinedChannelGroups>

-- end  snip --

 

Restarted ServerWMC & ran the Emby 'Refresh Guide' task. No change, but Emby is deep into a groud-up library scan so there may be a delay. If you see any errors, please let me know. Will report back when the dust settles...

 

PS sure wish the <ExcludeChannelCallSigns> allowed wildcards like MC* B^).

 

Thanks, again!

[krustyreturns 191]

That looks fine . Rather then wildcards, I think it would have been easier specify to specify a range on the channel numbers rather than using the call signs, for example 656-658.  But yeah, wildcards would be nice.

 

You can delete the example channelgroup called DummyName if you want.  

[garyan2 53]

d00zah, could you use the epg123 client to do a backup and send me the zip file? I'd like to see what I can find out about those 6 recorders with no devices ... and would like an example of a CableCard lineup for future capability of adding channels in the client GUI.

 

The backup copies the backup lineup, recordings, and subscriptions files for your WMC setup. I can then "restore" them on my machine and it will duplicate your setup... just it won't work because I don't have your tuners!

[d00zah 127]

I opted for call signs reasoning that while channel lineups periodically change, call signs were more likely to remain static. Call me lazy...

 

Seems that I mistakenly edited the config in a back-up dir (created during troubleshooting). Once I edited the 'live' config, Emby reported the stripped-down lineup. I left the dummy stuff in as a future template. Thanks again for the tip!

 

Nothing plays right now in Emby, but I'm gonna chaulk that up to the latest server & the pending plugin update for now.

[d00zah 127]

d00zah, could you use the epg123 client to do a backup and send me the zip file? I'd like to see what I can find out about those 6 recorders with no devices ... and would like an example of a CableCard lineup for future capability of adding channels in the client GUI.

 

The backup copies the backup lineup, recordings, and subscriptions files for your WMC setup. I can then "restore" them on my machine and it will duplicate your setup... just it won't work because I don't have your tuners!

 

Here ya go!

 

[attachment withdrawn]

 

Please let me know when you have what you need so I can purge the upload. Thx!

Edited February 26, 2018 by d00zah

[garyan2 53]

Please let me know when you have what you need so I can purge the upload. Thx!

 

Got it. Thanks!

[Sammy 735]

Double post.

Edited February 27, 2018 by Sammy

[Sammy 735]

Here ya go!

 

[attachment withdrawn]

 

Please let me know when you have what you need so I can purge the upload. Thx!

Got it. Thanks!

Awe man! I wanted to snoop your log! LOL

 

Sent from my SM-G930P using Tapatalk

[d00zah 127]

Awe man! I wanted to snoop your log! LOL

 

Sent from my SM-G930P using Tapatalk

ya snooze, ya lose. ;^)

[Sammy 735]

ya snooze, ya lose. ;^)

Reason being I'm investigating some issues with ServerWMC not respecting custom channel mapping done with GuideTool where epg123 works just fine. I'm also wanting to purge a bunch of SD channels from Emby DVR too and I'm scouring to see what DRM channels I have and if they're populating Emby LiveTV. Getting ready to shave my package..

 

Sent from my SM-G930P using Tapatalk

[d00zah 127]

Reason being I'm investigating some issues with ServerWMC not respecting custom channel mapping done with GuideTool where epg123 works just fine. I'm also wanting to purge a bunch of SD channels from Emby DVR too and I'm scouring to see what DRM channels I have and if they're populating Emby LiveTV. Getting ready to shave my package..

 

Sent from my SM-G930P using Tapatalk

 

Here's a new copy of the log.

 

& just a follow-up note if Krusty or Garyan2 checks in. Under guide settings, WMC only lists the 6 physical tuners (ContentRecorder: 7-12), so I have no clue where the 'six tuners with no devices attached' enter into the picture.

[garyan2 53]

I haven't been able to find anything from your backup. The only thing I can think of is this is a side effect of using more than 4 tuners per type. Maybe if you perform a TV Setup with tuners already set up (as you have to do after increasing the tuner limit to get more than 4 per type), then the original tuners get "removed/emptied" and set up again.

Deleted(02/01/2018 01:03:16): 34bcc31b-1f5e-4aa1-bb6c-d3fe571f1479 - Ceton InfiniTV Ethernet (00-80-81-50) Tuner 1 (00-00-22-00-00-80-81-50)
Ceton InfiniTV Ethernet (00-80-81-50) Tuner 2 (00-00-22-00-00-80-81-50)
Ceton InfiniTV Ethernet (00-80-81-50) Tuner 3 (00-00-22-00-00-80-81-50)
Ceton InfiniTV Ethernet (00-80-81-50) Tuner 4 (00-00-22-00-00-80-81-50)
Ceton InfiniTV Ethernet (00-80-81-50) Tuner 5 (00-00-22-00-00-80-81-50)
Ceton InfiniTV Ethernet (00-80-81-50) Tuner 6 (00-00-22-00-00-80-81-50)
Ceton InfiniTV Ethernet (00-80-81-50) Tuner 1 (00-00-22-00-00-80-81-50)
Hauppauge WinTV-7164 Analog TV Tuner #1

Looking at the devices you do have, you can see that Tuner 1 was deleted and then re-added.

[d00zah 127]

Maybe if you perform a TV Setup with tuners already set up (as you have to do after increasing the tuner limit to get more than 4 per type), then the original tuners get "removed/emptied" and set up again.

 

Installation of Ceton drivers ups the tuner limit prior to setup so the initial scan should get them all. Since I have my channel map & schedule backed up, I MAY try a clean setup if I can find the time.

[krustyreturns 191]

@@Sammy

 

You can use the xml code for the 'master channel group' in serverwmc to automatically filter out sd channels (see my earlier post in this thread).  As for the channels that aren't being mapped correctly, if you want to pursue it, post the serverwmc log with channel detail set true (also described in this thread).

[Sammy 735]

IMPORTANT:

I forgot to mention: set the Debug_ChannelDetail setting back to false or your swmc logs will be much longer then they need to be.

 

All the DRM detection is failing according to your log, so that is why you have the problem.  I'm not sure why its failing, but one strange thing about your log is wmc is reporting six tuners with no devices attached to them (in addition to your actual tuners).  See this part of the log:

 

2018/02/25 12:40:03.318 EnumerateRecorders> Tuner Devices and TuningSpaces found:

2018/02/25 12:40:03.321 EnumerateRecorders> ContentRecorder: 0

2018/02/25 12:40:03.326 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2018/02/25 12:40:03.326 EnumerateRecorders> ContentRecorder: 1

2018/02/25 12:40:03.327 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2018/02/25 12:40:03.327 EnumerateRecorders> ContentRecorder: 2

2018/02/25 12:40:03.327 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2018/02/25 12:40:03.327 EnumerateRecorders> ContentRecorder: 3

2018/02/25 12:40:03.327 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2018/02/25 12:40:03.327 EnumerateRecorders> ContentRecorder: 4

2018/02/25 12:40:03.327 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2018/02/25 12:40:03.327 EnumerateRecorders> ContentRecorder: 5

2018/02/25 12:40:03.327 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2018/02/25 12:40:03.327 EnumerateRecorders> ContentRecorder: 6

 

So I am just guessing, but I assume its due to this that DRM detection is not working.  This problem is probably due to something in your wmc setup history and it would likely go away if you reconfigure wmc - but I don't recommend doing that.

 

I suggest just setting wmc to ignore these channels.  The easiest way to do that is to define a master channel group in the settings file.  Here are instructions:

 

    A group can be designated as the master channel group by naming the group _MasterChannelGroup_. 

    Look for XmlDefinedChannelGroups example.  Here is an additional example with comments:

 

<XmlDefinedChannelGroups>

 

    <XmlDefinedChannelGroup>

 

      <Name>My Channel Group</Name>    <!-- the name of the channel group;  using the name "_MasterChannelGroup_" will use this group as the master channel list -->

 

      <IncludeChannelNumbers>645, 700-800, 837, 891</IncludeChannelNumbers>  <!-- include these channels ranges and numbers, leaving this blank will include all channels -->

 

      <IncludeChannelCallSigns>msNBC, CNN</IncludeChannelCallSigns>  <!-- include channels with these call signs -->

      <ExcludeChannelNumbers>720-725, 715</ExcludeChannelNumbers>  <!-- exclude these channel ranges and numbers -->

      <ExcludeChannelCallSigns>TBNHD, FNCHD</ExcludeChannelCallSigns>  <!-- call signs to exclude -->

      <HDOnly>true</HDOnly>  <!-- include only channels flagged as HD capable -->

 

      <SDOnly>false</SDOnly>  <!-- include only channels that are SD only -->

 

      <IncludeTheseLanguagesOnly>en, es</IncludeTheseLanguagesOnly> <!-- only include channels that have programming in these languages -->

 

    </XmlDefinedChannelGroup>

 

  </XmlDefinedChannelGroups>

 

 

Thanks for the warning, I had assumed & already done that. B^)

 

 

Odd. Just started fresh w/ EPG123 not too long ago, including clearing all tuner history via Ceton Diags. No good answer here.

 

All that said, based on the instructions, I came up with this in the config:

 

-- begin  snip --

  <EnableXmlChannelGroups>true</EnableXmlChannelGroups>

  <XmlDefinedChannelGroups>

    <XmlDefinedChannelGroup>

      <Name>_MasterChannelGroup_</Name>

      <ExcludeChannelCallSigns>CSPANHD, CSPN2HD, CSPN3HD, EWTNHD, INDIEHD, INSPHD, MC01, MC02, MC03, MC04, MC05, MC06,

 

MC07, MC08, MC09, MC10, MC11, MC12, MC13, MC14, MC15, MC16, MC17, MC18, MC19, MC20, MC21, MC22, MC23, MC24, MC25,

 

MC26, MC27, MC28, MC29, MC30, MC31, MC32, MC33, MC34, MC35, MC36, MC37, MC38, MC39, MC40, MC40, MC41, MC42, MC43,

 

MC44, MC45, MC46, MC47, MC48, MC49, MC50, MPLEXHD, RETROHD, SUNDHD, TBNHD, SECAHD, SECH</ExcludeChannelCallSigns>

    </XmlDefinedChannelGroup>

    <XmlDefinedChannelGroup>

      <Name>DummyName</Name>

      <IncludeChannelNumbers>645, 700-800, 837</IncludeChannelNumbers>

      <IncludeChannelCallSigns>msNBC, CNN</IncludeChannelCallSigns>

      <ExcludeChannelNumbers>720-725, 715</ExcludeChannelNumbers>

      <ExcludeChannelCallSigns>TBNHD, FNCHD</ExcludeChannelCallSigns>

      <HDOnly>true</HDOnly>

      <SDOnly>false</SDOnly>

      <IncludeTheseLanguagesOnly>en, fr</IncludeTheseLanguagesOnly>

    </XmlDefinedChannelGroup>

  </XmlDefinedChannelGroups>

-- end  snip --

 

Restarted ServerWMC & ran the Emby 'Refresh Guide' task. No change, but Emby is deep into a groud-up library scan so there may be a delay. If you see any errors, please let me know. Will report back when the dust settles...

 

PS sure wish the <ExcludeChannelCallSigns> allowed wildcards like MC* B^).

 

Thanks, again!

 

 

@@Sammy

 

You can use the xml code for the 'master channel group' in serverwmc to automatically filter out sd channels (see my earlier post in this thread).  As for the channels that aren't being mapped correctly, if you want to pursue it, post the serverwmc log with channel detail set true (also described in this thread).

 

 

So where does one find this settings xml file to edit?

 

I need to grab some logs and post them too.. Both for ServerWMC and epg123.

[d00zah 127]

%ProgramData%\VDSoftware\ServerWMC\config.xml

 

%ProgramData%\VDSoftware\ServerWMC\ServerWMC.log (or ServerWMC_Service.log if running as a service)

[krustyreturns 191]

An easier way to get to both the settings file and the log file is on the 'debug' tab of serverwmc.

[Sammy 735]

This shows as answered but also says we're not sure why ServerWMC is failing to flag DRM recordings???

[d00zah 127]

The suspicion was that the 6 'ghost' tuners in my config were queering the DRM detection. Are you experiencing something similar?

[Sammy 735]

The suspicion was that the 6 'ghost' tuners in my config were queering the DRM detection. Are you experiencing something similar?

When I deleted tuners I added in addition to those populated by ServerWMC I ended up with the 6 I have.

 

I'll look again but I haven't noticed DRM Recordings or channels since doing that.

 

Sent from my SM-G930P using Tapatalk